This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Bricked AC1200 - issue rebooting firmware via tftp on mac os
Like others, I got a notification on my phone that there's a new firmware for my router. I hit install, and it said it installed successfully, but then immediately after my wifi network disappeared and stopped working. When I turn on my router, all I get is a solid green power light (never turns orange or blinks). None of the other lights are on.
I figured it was bricked due to the firmware update so I have been trying to reboot the firmware via TFTP mac os Catalina (10.15.7).
I have successfully connected to the router via an Ethernet cable and am able to sucessfully ping it. Example ping response:
64 bytes from 192.168.1.10: icmp_seq=93 ttl=64 time=0.279 ms
I am able to connect to it via tftp and get a status
Connected to 192.168.1.1.
Mode: octet Verbose: off Tracing: on
Rexmt-interval: 5 seconds, Max-timeout: 25 seconds
But then when I try the "put" command to transfer the img file over, it says the host is down. I turned tracing on. Here's what happens:
tftp> put R6230_V1.1.0.104_1.0.1.img
sent WRQ <file=R6230_V1.1.0.104_1.0.1.img, mode=octet>
sent WRQ <file=R6230_V1.1.0.104_1.0.1.img, mode=octet>
sent WRQ <file=R6230_V1.1.0.104_1.0.1.img, mode=octet>
sent WRQ <file=R6230_V1.1.0.104_1.0.1.img, mode=octet>
sent WRQ <file=R6230_V1.1.0.104_1.0.1.img, mode=octet>
sent WRQ <file=R6230_V1.1.0.104_1.0.1.img, mode=octet>
tftp: sendto: No route to host
If I don't have tracing on, I run the command and nothing happens (I have waited for many hours, others have said it should take less than an hour to transfer the file).
For my network settings I created a static location, and I put:
Configure IPv4: Manually IP Address: 192.168.1.10
Subnet Mask: 255.255.255.0
Router: I have tried leaving it blank or putting in 192.168.1.10. Neither worked.
Could use some help. I am a networking noob and have gotten this far by google searching and reading this forum so please dumb it down for me. How do I overcome this "no route to host" error?
6. Then, I followed the instructions in the github page. These are the commands I used specifically:
./nmrpflash -L
to pull up the list of connections and find the name of my ethernet port connected to the router (Find the one with IP 192.168.1.10)
7. Then you turn OFF the router.
8. For the rest of this example, let's assume that your router is connected toeth2, and that you want to flash a firmware image namedR6230_V1.1.0.104_1.0.1.img.
./nmrpflash -i eth2 -f R6230_V1.1.0.104_1.0.1.img
At this point I got an error saying I need to "run as root" so I simply added "sudo" to the beginning of the command.
9. And then I turned on my router. I did have the reset button pushed in while turning it on. Once I turned it on, I noticed only the internet light was on. All others were off. I'd never had that happen in the past day when I was trying to fix this thing, so I knew something was going well.
After that, it should do its thing. You will see some messages in terminal but sometimes there will be a minute or two with no updates, just wait. It took about 5 minutes, I just had to wait. Once nmrpflash tells you to reboot your device, do so and it should work now.
10. Funny enough once I got the router back on and reconfigured it, it offered to install new firmware. I went ahead and did it via my app (which is what bricked it in the first place), figuring they had patched the bug. Looks like I was right. The new version is 106 and it restarted fine this time, but if it fails again then you can always use nmrpflash to reboot it.
Hope this helps those who are mac users. For windows users I imagine it might be a bit easier to run nmrpflash but I don't know.
Re: Bricked AC1200 - issue rebooting firmware via tftp on mac os
> [...] Example ping response:
What was the "ping" _command_? To me, that looks as if you tried: ping 192.168.1.10 which would verify that your computer can talk to itself (192.168.1.10), not to the router (192.168.1.1).
> Connected to 192.168.1.1.
With TFTP, that's mostly a lie; nothing really happens until the GET or PUT.
> tftp: sendto: No route to host
Except as an indication of a failure, I wouldn't trust the "No route to host" there, either. I can get that (sometimes) by specifying an IP address where there is no device to respond.
> Router: I have tried leaving it blank or putting in 192.168.1.10. > Neither worked.
Shouldn't matter. This transaction is all on your LAN; no routing required.
> [...] When I turn on my router, all I get is a solid green power light > (never turns orange or blinks). None of the other lights are on.
I wouldn't expect orange ("amber") from a model with a one-color LED.
I know nothing, but the Netgear KB articles suggest fiddling with the Reset button to get a flashing Power indicator. For example:
1. Regarding the ping - it would stop working when I unplugged the router, so I figured I had done it right. But I will try again with the other IP.
2. This is a super noob question but 192.168.1.1 and 192.168.1.10 are 2 different IPs, right? If yes, why do the instructions have me set almost the same IP for my manual connection as the router? That seems confusing!
3. For the timing and reset button - I have fiddled with all of that. If I turn it on with the reset button held, the wifi and internet LEDs start flashing one at a time like a train crossing. Neither that or the regular bootup mode seems to work. Same for the timing of the put command - I have tried it right as the ping starts going, or a while after. No difference.
4. However if the answer to #2 is the IPs are different, then should my tftp be connecting to 192.168.1.10 and not 192.168.1.1? Could that be the problem?
Re: Bricked AC1200 - issue rebooting firmware via tftp on mac os
> 1. Regarding the ping - [...]
Which is still invisible...
> [...] 192.168.1.1 and 192.168.1.10 are 2 different IPs, right? If yes, > why do the instructions have me set almost the same IP for my manual > connection as the router? That seems confusing!
Don't your neighbors have similar but different street addresses? "almost the same" means "different".
Instant IP[v4] network addressing:
Given a netmask of "255.255.255.0" ("/24"), which is about all you'll ever see in this context...
In an address like "a.b.c.d", the "a.b.c" ("network") part is common to all devices on the LAN; the "d" ("host") part identifies the individual device.
With the router at its default IP address of "192.168.1.1", any device on your LAN must have an address like "192.168.1.x". Any such local device expects to be able to reach any other such local device (say, "192.168.1.y") by just specifying that local destination address for the message.
To send a message to an address with a different network part, like, say "172.217.4.46", which is _not_ on your LAN, the local device would need to send the message to a router (gateway), and hope that that router knows how to get it delivered.
To make this stuff work, your computer needs to have its own address on the same subnet as the router ("192.168.1.x", x > 1).
> [...] should my tftp be connecting to 192.168.1.10 and not > 192.168.1.1? [...]
Nope. Your computer's address is "192.168.1.10"; your router's address is "192.168.1.1". In the "tftp" command, you specify the destination address, that of the router.
> 3. For the timing and reset button [...]
I have no special wisdom on that. I can tell you how to get the TFTP program to talk to the router, but getting the router into a receptive state is a different problem.
OK, now that I have tried to ping the correct IP, it is not working. The log is below. Sso even though my mac is showing the connection as "connected", it looks like it's not actually connecting. And the whole time I thought the tftp command was the issue...
I got the same result both in "flashing lights" / reset button mode and regular mode.
What else can I do to troubleshoot this?
PING 192.168.1.1 (192.168.1.1): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
Request timeout for icmp_seq 0
ping: sendto: No route to host
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
ping: sendto: No route to host
Request timeout for icmp_seq 7
ping: sendto: Host is down
Request timeout for icmp_seq 8
ping: sendto: Host is down
Re: Bricked AC1200 - issue rebooting firmware via tftp on mac os
> What else can I do to troubleshoot this?
If the Ethernet interface on your Mac is configured manually to use address "192.168.1.10", and you can't get a positive response from "192.168.1.1" using "ping" or a TFTP "put", with any Reset/timing variations, then my supply of ideas may be about exhausted.
6. Then, I followed the instructions in the github page. These are the commands I used specifically:
./nmrpflash -L
to pull up the list of connections and find the name of my ethernet port connected to the router (Find the one with IP 192.168.1.10)
7. Then you turn OFF the router.
8. For the rest of this example, let's assume that your router is connected toeth2, and that you want to flash a firmware image namedR6230_V1.1.0.104_1.0.1.img.
./nmrpflash -i eth2 -f R6230_V1.1.0.104_1.0.1.img
At this point I got an error saying I need to "run as root" so I simply added "sudo" to the beginning of the command.
9. And then I turned on my router. I did have the reset button pushed in while turning it on. Once I turned it on, I noticed only the internet light was on. All others were off. I'd never had that happen in the past day when I was trying to fix this thing, so I knew something was going well.
After that, it should do its thing. You will see some messages in terminal but sometimes there will be a minute or two with no updates, just wait. It took about 5 minutes, I just had to wait. Once nmrpflash tells you to reboot your device, do so and it should work now.
10. Funny enough once I got the router back on and reconfigured it, it offered to install new firmware. I went ahead and did it via my app (which is what bricked it in the first place), figuring they had patched the bug. Looks like I was right. The new version is 106 and it restarted fine this time, but if it fails again then you can always use nmrpflash to reboot it.
Hope this helps those who are mac users. For windows users I imagine it might be a bit easier to run nmrpflash but I don't know.
