I installed the Tomato build referenced upthread awhile back and got the little beastie working, then promptly forgot all about it.
Can the .chk file referenced here just install straight over the Tomato currently on the box, i.e. just browse to the file and use the Upgrade function under Tomato's Admin page? Just wanting to make sure.
I downloaded the BrainSlayer image mentioned three or so posts back and used the "upgrade firmware" function in the stock Netgear firmware to try to deploy it.
Now it's weirdly semi-bricked.
If you power it up, it tries to tftp vmlinuz fron 192.168.1.2. I've tried offering the DD-WRT image and a stock Netgear image to no avail.
If you don't have one to offer, it eventually gets to a green power LED, blue Wi-Fi LED and the ethernet LED on for whatever port you're wired to. Pressing the 'disable wi-fi' button on the router toggles the blue light.
However, it doesn't show a network for the Win10 Wi-Fi selection list, and it doesn't provide an IP address to connected PCs.
If you give the connected PC a static IP in the 192.168.1.x block, it can't ping 192.168.1.1 or 192.168.0.1 (aside from the five second window when it tries to do TFTP)
The only thing I can think of is "it's still alive somewhat if it's blinking the lights, but is maybe wildly misconfigured, something like 'don't bother setting up TCP/IP networking'... but poking the reset button when off, on, or while powering on, do nothing.
Is it time to get a USB-TTL cable (or would an old 386 with a real serial port do the same job?)
I just flashed BrainSlayers build, there is a problem with switch-robo driver in his build:
loading switch-robo
roboswitch: Probing device 'eth0'
roboswitch: No such device
roboswitch: Probing device 'eth1'
roboswitch: No such device
roboswitch: Probing device 'eth2'
roboswitch: No such device
roboswitch: Probing device 'eth3'
roboswitch: No such device
insmod: cannot insert '/lib/modules/3.10.93/switch-robo.ko': No such device
I just flashed BrainSlayers build, there is a problem with switch-robo driver in his build:
loading switch-robo
roboswitch: Probing device 'eth0'
roboswitch: No such device
roboswitch: Probing device 'eth1'
roboswitch: No such device
roboswitch: Probing device 'eth2'
roboswitch: No such device
roboswitch: Probing device 'eth3'
roboswitch: No such device
insmod: cannot insert '/lib/modules/3.10.93/switch-robo.ko': No such device
Thus network is not working. You need a usb-ttl.
Thank you for the warning. Will your build referenced earlier load over Tomato at the admin screen, or do I need to do anything special?
[EDIT] Nevermind, I see now someone did this earlier in Tomato by loading the .chk file, then using the .bin file.
Loaded and running. Only odd thing I can see is that Site Survey doesn't pick up anything - it would at least pick up the two APs out in the living room before.
Joined: 29 Aug 2015 Posts: 10 Location: Research Triangle Area, North Carolina USA
Posted: Wed Nov 25, 2015 4:27 Post subject: Change info for the Nov. 15 PTB?
Is there any way for us to get a Cliff's Notes of the changes that were made to the July 17 build to create this new build? An informal changelog would be helpful.
I'm about to deploy two WNR3500Lv2 routers in a small business setting (for a relative) and if there are any changes pertaining to OpenVPN and Samba, in particular, then I'd really like to know what those are.
BrainSlayer's current build still isn't working for this router. DO NOT INSTALL!!! Soft-brick, ethernet and wireless not responding as stated above. Had to use the USB-TTL cable to reset it.
Also wasn't able to flash Kong's .chk file from the latest official Netgear firmware 1.2.0.34. Gave a firmware error. Had to flash tomato first, then .chk, finally .bin.
Currently testing the new Kong build to see if that traff daemon, webui crashing has gone away. Site survey not working here as well.
I downloaded the BrainSlayer image mentioned three or so posts back and used the "upgrade firmware" function in the stock Netgear firmware to try to deploy it.
Now it's weirdly semi-bricked.
If you power it up, it tries to tftp vmlinuz fron 192.168.1.2. I've tried offering the DD-WRT image and a stock Netgear image to no avail.
If you don't have one to offer, it eventually gets to a green power LED, blue Wi-Fi LED and the ethernet LED on for whatever port you're wired to. Pressing the 'disable wi-fi' button on the router toggles the blue light.
However, it doesn't show a network for the Win10 Wi-Fi selection list, and it doesn't provide an IP address to connected PCs.
If you give the connected PC a static IP in the 192.168.1.x block, it can't ping 192.168.1.1 or 192.168.0.1 (aside from the five second window when it tries to do TFTP)
The only thing I can think of is "it's still alive somewhat if it's blinking the lights, but is maybe wildly misconfigured, something like 'don't bother setting up TCP/IP networking'... but poking the reset button when off, on, or while powering on, do nothing.
Is it time to get a USB-TTL cable (or would an old 386 with a real serial port do the same job?)
Got the same problem on my end...
Any information on how to get back to the admin panel, tftp acces, or some other control back?
I ran wireshark, as my router boots up and found it was using TFTP to request 192.168.1.2 for a vmlinuz file.
I installed a tftp server and put the default netgear firmware, renamed to vmlinuz, in the root directory.
Now wireshark seems to confirm that the router downloads the file, but it doesn't seem to do anything. :/
Any ideas on how to get a recovery vmlinuz file, that I can send to the router?
I downloaded the BrainSlayer image mentioned three or so posts back and used the "upgrade firmware" function in the stock Netgear firmware to try to deploy it.
Now it's weirdly semi-bricked.
If you power it up, it tries to tftp vmlinuz fron 192.168.1.2. I've tried offering the DD-WRT image and a stock Netgear image to no avail.
If you don't have one to offer, it eventually gets to a green power LED, blue Wi-Fi LED and the ethernet LED on for whatever port you're wired to. Pressing the 'disable wi-fi' button on the router toggles the blue light.
However, it doesn't show a network for the Win10 Wi-Fi selection list, and it doesn't provide an IP address to connected PCs.
If you give the connected PC a static IP in the 192.168.1.x block, it can't ping 192.168.1.1 or 192.168.0.1 (aside from the five second window when it tries to do TFTP)
The only thing I can think of is "it's still alive somewhat if it's blinking the lights, but is maybe wildly misconfigured, something like 'don't bother setting up TCP/IP networking'... but poking the reset button when off, on, or while powering on, do nothing.
Is it time to get a USB-TTL cable (or would an old 386 with a real serial port do the same job?)
Got the same problem on my end...
Any information on how to get back to the admin panel, tftp acces, or some other control back?
I ran wireshark, as my router boots up and found it was using TFTP to request 192.168.1.2 for a vmlinuz file.
I installed a tftp server and put the default netgear firmware, renamed to vmlinuz, in the root directory.
Now wireshark seems to confirm that the router downloads the file, but it doesn't seem to do anything. :/
Any ideas on how to get a recovery vmlinuz file, that I can send to the router?
Exactly the same for me... There is a TFTP request but it gets only one block...
Different behavior if i try reflashing the CFE bin file that i found here:
In this case the server uploads the whole bin file. Anyway nothing changes... Is it possible to build a CFE that autostarts the tftp server? in that way we could upload a working firmware without cable...
I downloaded the BrainSlayer image mentioned three or so posts back and used the "upgrade firmware" function in the stock Netgear firmware to try to deploy it.
Now it's weirdly semi-bricked.
If you power it up, it tries to tftp vmlinuz fron 192.168.1.2. I've tried offering the DD-WRT image and a stock Netgear image to no avail.
If you don't have one to offer, it eventually gets to a green power LED, blue Wi-Fi LED and the ethernet LED on for whatever port you're wired to. Pressing the 'disable wi-fi' button on the router toggles the blue light.
However, it doesn't show a network for the Win10 Wi-Fi selection list, and it doesn't provide an IP address to connected PCs.
If you give the connected PC a static IP in the 192.168.1.x block, it can't ping 192.168.1.1 or 192.168.0.1 (aside from the five second window when it tries to do TFTP)
The only thing I can think of is "it's still alive somewhat if it's blinking the lights, but is maybe wildly misconfigured, something like 'don't bother setting up TCP/IP networking'... but poking the reset button when off, on, or while powering on, do nothing.
Is it time to get a USB-TTL cable (or would an old 386 with a real serial port do the same job?)
Got the same problem on my end...
Any information on how to get back to the admin panel, tftp acces, or some other control back?
I ran wireshark, as my router boots up and found it was using TFTP to request 192.168.1.2 for a vmlinuz file.
I installed a tftp server and put the default netgear firmware, renamed to vmlinuz, in the root directory.
Now wireshark seems to confirm that the router downloads the file, but it doesn't seem to do anything. :/
Any ideas on how to get a recovery vmlinuz file, that I can send to the router?
Exactly the same for me... There is a TFTP request but it gets only one block...
Different behavior if i try reflashing the CFE bin file that i found here:
In this case the server uploads the whole bin file. Anyway nothing changes... Is it possible to build a CFE that autostarts the tftp server? in that way we could upload a working firmware without cable...
Posted: Thu Dec 10, 2015 4:44 Post subject: KONG build not stable yet
Hi, I loaded the KONG build, first by loading tomato, then dd-wrt.v24-K3_WNR3500Lv2.chk then dd-wrt.v24-K3_WNR3500Lv2.bin and I have the following issues:
1. The radio keeps disconnecting every minute or two from all my devices which include a laptop running linux/windows with an Intel 2200BG card, an android phone and a samsung tablet (802.11n).
2. After running for a while, if I go to the web interface I can access only the main page. Attempts to navigate to any other place give me a page error (connection refused or some such). Although the router is still functioning and I can telnet into it.