sm00thpapa
Very Senior Member
I'm actually turning the router off for 30 seconds to fix the NAT issue and it helps.
Sent from my LG-D800 using Tapatalk
Sent from my LG-D800 using Tapatalk
WRT1900AC Spontaneous Reboots, lockups
- Thread starter RogerSC
- Start date
htismaqe
Very Senior Member
Yeah, I only use backups if for some reason I have a failure or corruption (like due to a power outage) where I reset to defaults without flashing firmware.
I don't use and have never used firmware auto-updates. And I've never used a backup config after flashing firmware, even it's the same version.
One universal thing I've noticed whether it's Netgear, Linksys, Belkin, Zyxel, or another provider is that's one of the first things support asks - did you try re-flashing firmware and configuring the router from scratch instead of loading from backup config?
I don't use and have never used firmware auto-updates. And I've never used a backup config after flashing firmware, even it's the same version.
One universal thing I've noticed whether it's Netgear, Linksys, Belkin, Zyxel, or another provider is that's one of the first things support asks - did you try re-flashing firmware and configuring the router from scratch instead of loading from backup config?
htismaqe
Very Senior Member
If you can manage, I would encourage you to see how much uptime you can get without rebooting manually.
Of course, if the NAT issue is a deal breaker, don't refrain from fixing just to satisfy my curiosity.
Speaking of curiosity, I haven't access the web GUI since the last time I talked to Linksys support. 50 hours and counting...
Code:
UpTime:
22:46:38 up 2 days, 2:06, load average: 1.26, 1.27, 1.30
Last edited:
sm00thpapa
Very Senior Member
Sure no problem. I like to reboot every couple of days anyway so I can have a fresh connection while gaming online.
Sent from my LG-D800 using Tapatalk
Sent from my LG-D800 using Tapatalk
sm00thpapa
Very Senior Member
speedingcheetah
Senior Member
I had the WRT IP set to static ip of 192.168.0.202. When I connected it to my asus router, which is 192.168.0.200, just to check for firmware updates...and to play around with the UI some more...the Linksys reset it self to an ip address of 10.0.X.X (don't remember the exact address) and cleared all my DHCP reservations automatically.
I can see this possibly making this easier for folks that just want it to work, but what do I do if I want the WRT to be at a certain address, and to operate as a different subnet/network. I did try chaining it back to 198.168.0.202...but it refused to stick. Only when I set it to AP(bridge) mode will it stay at the set static IP address I set for it. But that mode disables most everything in the router, as its supposed to.
As I have mentioned, no other routers I have used will do this. They will just change its WAN ip address(if WAN is set for Auto - DHCP mode), and all other settings(including the web gui address and DHCP settings) stay fine.
Last edited:
chadster766
Very Senior Member
I have a couple of suggestions you could try: (you probably already tried them
) - Set the ASUS LAN to 192.168.200.1
- Connect the ASUS WAN set to DHCP to the WRT LAN port and connect your computer to the ASUS
Or
- Set ASUS to LAN to 192.168.0.200
- Disable ASUS DHCP
- Connect ASUS LAN to WRT LAN
Or
- Set ASUS WAN to 192.168.0.200
- Set ASUS LAN to 192.168.200.1
- Connect ASUS WAN to WRT LAN
- Connect computer to ASUS LAN
For bridge mode (AP mode), you connect to the WAN port as per instructions. For LAN to LAN cascade, obviously the WAN port goes unused. An additional step for newer Linksys routers is to disable NAT when using a LAN to LAN cascade. That tidbit can be found on their support website. It's in the "videos" but not in the written instructions. And then you set the static IP address and disable DHCP server. All of this should be done while it's not connected to your primary router. Connecting to the LAN port is the final step.
Having said all that, the daemon that automatically changes your scope to 10.x.x.x or 172.x.x.x can be a little buggy at times. For example, from my experience, a power outage can cause it to change from the 192.x.x.x. to 10.x.x.x for unknown reasons. One might assume that a spontaneous reboot or router crash might also cause that too.
If you think you may want to flip back and forth between LAN to LAN, Bridge mode, and LAN to WAN on a different scope using DHCP reservations, then save a configuration file to your computer of the LAN to WAN setup. Then when you want to switch, just reset it to defaults and restore your backup configuration.
Ultimately, the smart wifi firmware is a mainstream consumer product. Linksys may get some returns because a handful of people don't like the auto scope daemon, but there will be far more mainstream users that don't understand networking and need that feature.
Last edited:
speedingcheetah
Senior Member
Thanks for all the suggestions and thoughts, however, changing anything on my Asus router side is not an option. It has a static DHCP reservation set(in the Asus router)as 192.168.0.202 for the MAC of the WRT, however the WRT ignores it and also refuses to stay on the same network for its assigned web GUI IP and will revert to 10.0.... network address.
Having to change and tweak things so much, just to do a quick hook up to do a test or check firmware, is unacceptable to me. I am not going to take the time to reset all the WRT's settings, nor can I simply replace the asus with the WRT just to save the WRT from re-setting it self as it does.
Since open source firmwares are pretty much a dud at this point(or just to plain buggy/risky to use at the moment, imo) back on my storage shelf it goes.
Having to change and tweak things so much, just to do a quick hook up to do a test or check firmware, is unacceptable to me. I am not going to take the time to reset all the WRT's settings, nor can I simply replace the asus with the WRT just to save the WRT from re-setting it self as it does.
Since open source firmwares are pretty much a dud at this point(or just to plain buggy/risky to use at the moment, imo) back on my storage shelf it goes.
htismaqe
Very Senior Member
The WRT can't accept a DHCP address on a LAN interface. It can only use DHCP on the WAN interface. The WAN interface and the LAN interface cannot exist in the same subnet.
If you're cascading Asus LAN to WRT WAN port, the MAC address in the DHCP reservation on the Asus has to match the WAN port on the WRT, not the LAN port. If you're using the LAN port MAC, that's why the WRT is ignoring it. To do what you want, you need to cascade LAN-to-LAN and reserve the MAC address of the LAN side of the WRT. Since the WAN port never gets an address, the router won't detect an IP conflict so it shouldn't reset the IP address of the LAN port.
I know you say it doesn't happen with any other router but I have a WNDR3700 right here that absolutely does do this exact same thing. I can't comment on Asus because I never tried it but every Netgear I've ever own does exactly what you describe (except for nuking the DHCP reservations, that's unique to the WRT).
chadster766
Very Senior Member
Excellent
Why is the avg load so high? I would expect it to be much closer to 0, unless the router was constantly transferring data at its max capacity.
htismaqe
Very Senior Member
Good question. I haven't paid close attention but from what I can remember those numbers don't look all that different from what they are after a fresh reboot.
I haven't transferred any disk images since the last reboot. Actual data transferred since last reboot isn't all that high:
Code:
ifconfig:
br0 RX bytes:1278031055 (1.1 GiB) TX bytes:25175503170 (23.4 GiB)
br1 RX bytes:526911749 (502.5 MiB) TX bytes:1886934511 (1.7 GiB)
eth0 RX bytes:1054228290 (1005.3 MiB) TX bytes:3617430998 (3.3 GiB)
eth1 RX bytes:2183744632 (2.0 GiB) TX bytes:1880468821 (1.7 GiB)
lo RX bytes:4410115 (4.2 MiB) TX bytes:4410115 (4.2 MiB)
wdev0 RX bytes:429823888 (409.9 MiB) TX bytes:3447753974 (3.2 GiB)
wdev0ap0 RX bytes:221940133 (211.6 MiB) TX bytes:3355252620 (3.1 GiB)
wdev0ap1 RX bytes:36399723 (34.7 MiB) TX bytes:216851613 (206.8 MiB)
wdev1 RX bytes:830032300 (791.5 MiB) TX bytes:3644166011 (3.3 GiB)
wdev1ap0 RX bytes:159785774 (152.3 MiB) TX bytes:3541355224 (3.2 GiB)
wdev1ap1 RX bytes:490711886 (467.9 MiB) TX bytes:1807438786 (1.6 GiB)Can you post the output from "top"? I'm curious, especially considering this is a dual core CPU.
htismaqe
Very Senior Member
I'm pulling that from a cgi script that is accessible via HTTP. I can't actually telnet or serial to the device and run shell commands. Fortunately it looks like top is part of the script.
Code:
top -bn1
Mem: 90724K used, 160260K free, 0K shrd, 3948K buff, 24444K cached
CPU: 0.0% usr 0.0% sys 0.0% nic 100% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 1.18 1.24 1.29 1/115 15972
PID PPID USER STAT VSZ %MEM CPU %CPU COMMAND
15972 15882 root R 2764 1.1 1 0.0 top -bn1
9 2 root SW 0 0.0 1 0.0 [ksoftirqd/1]
913 1 root S 95540 37.9 0 0.0 /sbin/syseventd
31519 1 root S 19796 7.8 1 0.0 /sbin/wl_link_status_monitor
27567 1 root S < 19736 7.8 0 0.0 /usr/bin/guardian
20168 1 root S 19460 7.7 0 0.0 devidentd -r /tmp/devregex.json -p
2699 1 root S 13020 5.1 0 0.0 /usr/sbin/linkmgr
28044 1 root S 8072 3.2 0 0.0 /usr/bin/redirector
12584 1 root S 7120 2.8 0 0.0 /sbin/smbd
12606 12584 root S 7120 2.8 1 0.0 /sbin/smbd
28071 1 root S 6260 2.4 1 0.0 stunnel /tmp/stunnel.conf
28623 1 root S 6176 2.4 1 0.0 lighttpd -f /etc/lighttpd.conf
11906 1 root S 5576 2.2 0 0.0 /sbin/nmbd -D
29998 1 root S 4260 1.6 0 0.0 /usr/sbin/guest-access -d
28940 1 quagga S 3820 1.5 0 0.0 /usr/sbin/zebra -d -f /etc/zebra.c
31472 1 root S 3372 1.3 1 0.0 hostapd /tmp/hostapd-wdev0ap0.conf
15882 28623 root S 2768 1.1 0 0.0 /bin/sh /www/sysinfo.cgi
911 1 root S 2764 1.1 0 0.0 /sbin/syslogd -l 6
1 0 root S 2764 1.1 1 0.0 init
11210 1 root S 2764 1.1 0 0.0 crond -l 9
866 1 root S 2764 1.1 1 0.0 /sbin/klogd
10269 1 root S 2764 1.1 0 0.0 udhcpc -R -S -b -i eth1 -h HOMNET-
29641 1 root S 2300 0.9 1 0.0 /usr/sbin/generic_link_status_moni
32002 1 root S < 2280 0.9 0 0.0 /usr/bin/nfqrecv
29341 1 root S 2180 0.8 1 0.0 mdnsd
30444 1 nobody S 2056 0.8 1 0.0 /sbin/dnsmasq -u nobody --dhcp-aut
30446 30444 root S 2056 0.8 0 0.0 /sbin/dnsmasq -u nobody --dhcp-aut
29229 1 root S 2008 0.8 1 0.0 /sbin/dhcp6s -P /var/run/dhcp6s.pi
31443 1 root S 2008 0.8 0 0.0 hostapd-mon -v -0 /tmp/hostapd-wde
31468 1 root S 2008 0.8 0 0.0 hostapd-mon -v -1 /tmp/hostapd-wde
30777 1 root S 1904 0.7 0 0.0 /sbin/dns-sd -R myrouter _http._tc
29358 1 root S 1896 0.7 1 0.0 lld2d br0
936 1 root S 1872 0.7 0 0.0 syseventd_fork_helper 8
600 1 root S < 1848 0.7 0 0.0 /sbin/udevd --daemon
28298 1 root S 1812 0.7 1 0.0 igmpproxy /tmp/igmpproxy.conf
2571 1 root S 1752 0.7 0 0.0 /usr/sbin/bdutil
13 2 root SW 0 0.0 1 0.0 [kworker/u:1]
369 2 root SW 0 0.0 0 0.0 [kworker/0:1]
214 2 root SW 0 0.0 1 0.0 [kworker/1:1]
3 2 root SW 0 0.0 0 0.0 [ksoftirqd/0]
6 2 root SW 0 0.0 0 0.0 [migration/0]
7 2 root SW 0 0.0 1 0.0 [migration/1]
209 2 root SW 0 0.0 0 0.0 [sync_supers]
3649 2 root SW 0 0.0 1 0.0 [usb-storage]
852 2 root DW 0 0.0 0 0.0 [mod_bdutil:fan]
296 2 root SW 0 0.0 1 0.0 [khungtaskd]
896 2 root SW 0 0.0 1 0.0 [ubi_bgt0d]
902 2 root SW 0 0.0 0 0.0 [ubifs_bgt0_0]
211 2 root SW 0 0.0 0 0.0 [bdi-default]
2 0 root SW 0 0.0 0 0.0 [kthreadd]
849 2 root SW 0 0.0 0 0.0 [mod_bdutil:acti]
850 2 root SW 0 0.0 0 0.0 [mod_bdutil:acti]
4 2 root SW 0 0.0 0 0.0 [kworker/0:0]
10 2 root SW< 0 0.0 0 0.0 [cpuset]
11 2 root SW< 0 0.0 0 0.0 [khelper]
12 2 root SW 0 0.0 1 0.0 [kdevtmpfs]
213 2 root SW< 0 0.0 1 0.0 [kblockd]
220 2 root SW< 0 0.0 1 0.0 [ata_sff]
232 2 root SW 0 0.0 0 0.0 [khubd]
234 2 root SW 0 0.0 1 0.0 [kethubd]
240 2 root SW< 0 0.0 0 0.0 [md]
261 2 root SW< 0 0.0 0 0.0 [rpciod]
273 2 root SW 0 0.0 0 0.0 [ocf_0]
274 2 root SW 0 0.0 0 0.0 [ocf_ret_0]
275 2 root SW 0 0.0 1 0.0 [ocf_1]
276 2 root SW 0 0.0 1 0.0 [ocf_ret_1]
301 2 root SW 0 0.0 1 0.0 [kswapd0]
302 2 root SW 0 0.0 0 0.0 [fsnotify_mark]
303 2 root SW< 0 0.0 1 0.0 [nfsiod]
304 2 root SW< 0 0.0 0 0.0 [xfs_mru_cache]
305 2 root SW< 0 0.0 1 0.0 [xfslogd]
306 2 root SW< 0 0.0 0 0.0 [xfsdatad]
307 2 root SW< 0 0.0 1 0.0 [xfsconvertd]
308 2 root SW< 0 0.0 0 0.0 [crypto]
399 2 root SW 0 0.0 1 0.0 [scsi_eh_0]
402 2 root SW 0 0.0 0 0.0 [scsi_eh_1]
416 2 root SW 0 0.0 0 0.0 [mtdblock0]
421 2 root SW 0 0.0 1 0.0 [mtdblock1]
426 2 root SW 0 0.0 0 0.0 [mtdblock2]
431 2 root SW 0 0.0 1 0.0 [mtdblock3]
436 2 root SW 0 0.0 0 0.0 [mtdblock4]
441 2 root SW 0 0.0 1 0.0 [mtdblock5]
446 2 root SW 0 0.0 0 0.0 [mtdblock6]
451 2 root SW 0 0.0 1 0.0 [mtdblock7]
456 2 root SW 0 0.0 0 0.0 [mtdblock8]
461 2 root SW 0 0.0 1 0.0 [mtdblock9]
851 2 root SW< 0 0.0 0 0.0 [wpsled_wq]
939 2 root SW< 0 0.0 0 0.0 [wdtutil]
2575 2 root SW 0 0.0 1 0.0 [button_thread]
3648 2 root SW 0 0.0 0 0.0 [scsi_eh_2]
4359 2 root SW 0 0.0 1 0.0 [kworker/u:0]
12452 2 root SW 0 0.0 1 0.0 [flush-ubifs_0_0]
19406 2 root SW 0 0.0 1 0.0 [kworker/1:2]chadster766
Very Senior Member
syseventd is using up a lot of memory but maybe that's normal.
Last edited:
htismaqe
Very Senior Member
I noticed that. It doesn't appear that things are changing over time however, so no memory leak or anything like that.
Code:
top -bn1
Mem: 99084K used, 151900K free, 0K shrd, 3948K buff, 24344K cached
CPU: 0.0% usr 0.0% sys 0.0% nic 100% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 1.24 1.25 1.28 1/114 13664
PID PPID USER STAT VSZ %MEM CPU %CPU COMMAND
13664 13574 root R 2764 1.1 1 0.0 top -bn1
13 2 root SW 0 0.0 0 0.0 [kworker/u:1]
913 1 root S 95540 37.9 0 0.0 /sbin/syseventd
20168 1 root S 27904 11.0 1 0.0 devidentd -r /tmp/devregex.json -p
31519 1 root S 19796 7.8 1 0.0 /sbin/wl_link_status_monitor
27567 1 root S < 19736 7.8 0 0.0 /usr/bin/guardian
2699 1 root S 13020 5.1 0 0.0 /usr/sbin/linkmgr
28044 1 root S 8072 3.2 0 0.0 /usr/bin/redirector
12584 1 root S 7120 2.8 0 0.0 /sbin/smbd
12606 12584 root S 7120 2.8 1 0.0 /sbin/smbd
28071 1 root S 6260 2.4 1 0.0 stunnel /tmp/stunnel.conf
28623 1 root S 6176 2.4 1 0.0 lighttpd -f /etc/lighttpd.conf
11906 1 root S 5576 2.2 0 0.0 /sbin/nmbd -D
29998 1 root S 4260 1.6 0 0.0 /usr/sbin/guest-access -d
28940 1 quagga S 3820 1.5 1 0.0 /usr/sbin/zebra -d -f /etc/zebra.c
31472 1 root S 3372 1.3 0 0.0 hostapd /tmp/hostapd-wdev0ap0.conf
13574 28623 root S 2768 1.1 0 0.0 /bin/sh /www/sysinfo.cgi
911 1 root S 2764 1.1 1 0.0 /sbin/syslogd -l 6
1 0 root S 2764 1.1 1 0.0 init
11210 1 root S 2764 1.1 0 0.0 crond -l 9
866 1 root S 2764 1.1 0 0.0 /sbin/klogd
10269 1 root S 2764 1.1 0 0.0 udhcpc -R -S -b -i eth1 -h HOMNET-
29641 1 root S 2300 0.9 0 0.0 /usr/sbin/generic_link_status_moni
32002 1 root S < 2280 0.9 0 0.0 /usr/bin/nfqrecv
29341 1 root S 2180 0.8 0 0.0 mdnsd
30444 1 nobody S 2056 0.8 0 0.0 /sbin/dnsmasq -u nobody --dhcp-aut
30446 30444 root S 2056 0.8 0 0.0 /sbin/dnsmasq -u nobody --dhcp-aut
29229 1 root S 2008 0.8 0 0.0 /sbin/dhcp6s -P /var/run/dhcp6s.pi
31443 1 root S 2008 0.8 0 0.0 hostapd-mon -v -0 /tmp/hostapd-wde
31468 1 root S 2008 0.8 0 0.0 hostapd-mon -v -1 /tmp/hostapd-wde
30777 1 root S 1904 0.7 0 0.0 /sbin/dns-sd -R myrouter _http._tc
29358 1 root S 1896 0.7 1 0.0 lld2d br0
936 1 root S 1872 0.7 0 0.0 syseventd_fork_helper 8
600 1 root S < 1848 0.7 0 0.0 /sbin/udevd --daemon
28298 1 root S 1812 0.7 0 0.0 igmpproxy /tmp/igmpproxy.conf
2571 1 root S 1752 0.7 0 0.0 /usr/sbin/bdutil
369 2 root SW 0 0.0 0 0.0 [kworker/0:1]
214 2 root SW 0 0.0 1 0.0 [kworker/1:1]
3 2 root SW 0 0.0 0 0.0 [ksoftirqd/0]
9 2 root SW 0 0.0 1 0.0 [ksoftirqd/1]
6 2 root SW 0 0.0 0 0.0 [migration/0]
7 2 root SW 0 0.0 1 0.0 [migration/1]
209 2 root SW 0 0.0 0 0.0 [sync_supers]
3649 2 root SW 0 0.0 0 0.0 [usb-storage]
852 2 root DW 0 0.0 0 0.0 [mod_bdutil:fan]
296 2 root SW 0 0.0 0 0.0 [khungtaskd]
896 2 root SW 0 0.0 1 0.0 [ubi_bgt0d]
902 2 root SW 0 0.0 0 0.0 [ubifs_bgt0_0]
211 2 root SW 0 0.0 1 0.0 [bdi-default]
2 0 root SW 0 0.0 1 0.0 [kthreadd]
849 2 root SW 0 0.0 0 0.0 [mod_bdutil:acti]
850 2 root SW 0 0.0 0 0.0 [mod_bdutil:acti]
4 2 root SW 0 0.0 0 0.0 [kworker/0:0]
10 2 root SW< 0 0.0 0 0.0 [cpuset]
11 2 root SW< 0 0.0 0 0.0 [khelper]
12 2 root SW 0 0.0 1 0.0 [kdevtmpfs]
213 2 root SW< 0 0.0 1 0.0 [kblockd]
220 2 root SW< 0 0.0 1 0.0 [ata_sff]
232 2 root SW 0 0.0 0 0.0 [khubd]
234 2 root SW 0 0.0 1 0.0 [kethubd]
240 2 root SW< 0 0.0 0 0.0 [md]
261 2 root SW< 0 0.0 0 0.0 [rpciod]
273 2 root SW 0 0.0 0 0.0 [ocf_0]
274 2 root SW 0 0.0 0 0.0 [ocf_ret_0]
275 2 root SW 0 0.0 1 0.0 [ocf_1]
276 2 root SW 0 0.0 1 0.0 [ocf_ret_1]
301 2 root SW 0 0.0 1 0.0 [kswapd0]
302 2 root SW 0 0.0 0 0.0 [fsnotify_mark]
303 2 root SW< 0 0.0 1 0.0 [nfsiod]
304 2 root SW< 0 0.0 0 0.0 [xfs_mru_cache]
305 2 root SW< 0 0.0 1 0.0 [xfslogd]
306 2 root SW< 0 0.0 0 0.0 [xfsdatad]
307 2 root SW< 0 0.0 1 0.0 [xfsconvertd]
308 2 root SW< 0 0.0 0 0.0 [crypto]
399 2 root SW 0 0.0 1 0.0 [scsi_eh_0]
402 2 root SW 0 0.0 0 0.0 [scsi_eh_1]
416 2 root SW 0 0.0 0 0.0 [mtdblock0]
421 2 root SW 0 0.0 1 0.0 [mtdblock1]
426 2 root SW 0 0.0 0 0.0 [mtdblock2]
431 2 root SW 0 0.0 1 0.0 [mtdblock3]
436 2 root SW 0 0.0 0 0.0 [mtdblock4]
441 2 root SW 0 0.0 1 0.0 [mtdblock5]
446 2 root SW 0 0.0 0 0.0 [mtdblock6]
451 2 root SW 0 0.0 1 0.0 [mtdblock7]
456 2 root SW 0 0.0 0 0.0 [mtdblock8]
461 2 root SW 0 0.0 1 0.0 [mtdblock9]
851 2 root SW< 0 0.0 0 0.0 [wpsled_wq]
939 2 root SW< 0 0.0 0 0.0 [wdtutil]
2575 2 root SW 0 0.0 1 0.0 [button_thread]
3648 2 root SW 0 0.0 0 0.0 [scsi_eh_2]
4359 2 root SW 0 0.0 1 0.0 [kworker/u:0]
19406 2 root SW 0 0.0 1 0.0 [kworker/1:2]Odd. According to this, your CPU is 100% idle.
Similar threads
Similar threads
| Thread starter | Title | Forum | Replies | Date |
|---|---|---|---|---|
| M | WRT1900AC handshake issues? | General Wi-Fi Discussion | 5 |
Similar threads
Support SNBForums w/ Amazon
If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!
Sign Up For SNBForums Daily Digest
Get an update of what's new every day delivered to your mailbox. Sign up here!
Staff online
-
thigginsMr. Easy