Experiencing constant WAN disconnect issues
So since flashing build 3.0.0.4.374.36_beta1-sdk5 for RT-N66U and after setting numerous configuration options.I am beginning to have some annoying issues where the device just reboots or stops working. This wasn't happening at all until the past 12 hours or so. Before that (which was... maybe Monday or Tuesday) when I flashed the firmware, it has been working fine up until this point.
I am not sure if it is corruption in NVRAM, configuration settings, or something else. However, after going through the firmware recovery procedure, erasing nvram with the recovery site interface, it still persisted. I am not sure if it is the beta firmware causing this problem or just the router itself. After doing nvram show, after a recovery/flash of firmware I see this:
size: 38674 bytes (26862 left)
The weird issue is that my recovery IP Address isn't 192.168.1.1 but 10.10.10.1.
Anyways, as soon as I set the LAN IP to 10.10.10.1 intead of 192.168.1.1, it causes numerous problems, set wireless configuration, port forwarding, DDNS, the router causes a fit. I don't have any other devices on the network using that IP Address. I have a bind9 server and WINS server on 10.10.10.254 (which is a static IP). I don't see why configuring the wireless would cause any issues, and the port forwarding and DDNS definitely shouldn't cause any issues.
I would love to know why the router is throwing a fit, as I am going to be away for another 5 months, and it will be a pain not having a stable router to work with.
EDIT: I have troubleshooted the issue to be something with the WAN port, or the router itself.
So since flashing build 3.0.0.4.374.36_beta1-sdk5 for RT-N66U and after setting numerous configuration options.I am beginning to have some annoying issues where the device just reboots or stops working. This wasn't happening at all until the past 12 hours or so. Before that (which was... maybe Monday or Tuesday) when I flashed the firmware, it has been working fine up until this point.
I am not sure if it is corruption in NVRAM, configuration settings, or something else. However, after going through the firmware recovery procedure, erasing nvram with the recovery site interface, it still persisted. I am not sure if it is the beta firmware causing this problem or just the router itself. After doing nvram show, after a recovery/flash of firmware I see this:
size: 38674 bytes (26862 left)
The weird issue is that my recovery IP Address isn't 192.168.1.1 but 10.10.10.1.
Anyways, as soon as I set the LAN IP to 10.10.10.1 intead of 192.168.1.1, it causes numerous problems, set wireless configuration, port forwarding, DDNS, the router causes a fit. I don't have any other devices on the network using that IP Address. I have a bind9 server and WINS server on 10.10.10.254 (which is a static IP). I don't see why configuring the wireless would cause any issues, and the port forwarding and DDNS definitely shouldn't cause any issues.
I would love to know why the router is throwing a fit, as I am going to be away for another 5 months, and it will be a pain not having a stable router to work with.
EDIT: I have troubleshooted the issue to be something with the WAN port, or the router itself.
Last edited: