What's new
By:

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

RT-N66U - WPS Turning on by itself - wpsaide log spam - 100% CPU usage

Bobbar

Bobbar

Occasional Visitor
Hello,

I have an RT-N66U with John's fork installed, Version 374.43_52E3j9527.

I keep having issues with the WPS service running amok. I will have WPS disabled via the web interface, but I keep finding that it has turned itself back on, and the logs will be filled with repeated start/stop/waiting messages from wpsaide and notify_rc, and the process "/sbin/init noinitrd" will be running at 100% CPU usage.

Here's a log snip:
Code: 
Jan 17 23:47:17 miniupnpd[825]: shutting down MiniUPnPd
Jan 17 23:47:17 miniupnpd[918]: HTTP listening on port 33771
Jan 17 23:47:17 miniupnpd[918]: Listening for NAT-PMP/PCP traffic on port 5351
Jan 18 00:45:37 watchdog: IP address, server and hostname have not changed since the last update. (ddns-check)
Jan 18 00:52:53 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:52:59 kernel: device eth1 left promiscuous mode
Jan 18 00:52:59 kernel: br0: port 2(eth1) entering disabled state
Jan 18 00:52:59 kernel: device eth2 left promiscuous mode
Jan 18 00:52:59 kernel: br0: port 3(eth2) entering disabled state
Jan 18 00:53:02 kernel: wl_module_init: passivemode set to 0x0
Jan 18 00:53:02 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 6.30.163.2002 (r382208)
Jan 18 00:53:02 kernel: eth2: Broadcom BCM4331 802.11 Wireless Controller 6.30.163.2002 (r382208)
Jan 18 00:53:04 kernel: device eth1 entered promiscuous mode
Jan 18 00:53:04 kernel: br0: port 2(eth1) entering listening state
Jan 18 00:53:04 kernel: br0: port 2(eth1) entering learning state
Jan 18 00:53:04 kernel: br0: topology change detected, propagating
Jan 18 00:53:04 kernel: br0: port 2(eth1) entering forwarding state
Jan 18 00:53:04 kernel: device eth2 entered promiscuous mode
Jan 18 00:53:04 kernel: br0: port 3(eth2) entering listening state
Jan 18 00:53:04 kernel: br0: port 3(eth2) entering learning state
Jan 18 00:53:04 kernel: br0: topology change detected, propagating
Jan 18 00:53:04 kernel: br0: port 3(eth2) entering forwarding state
Jan 18 00:53:10 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:11 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:11 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:11 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:14 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:14 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:14 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:16 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:16 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:16 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:18 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:18 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:18 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:20 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:20 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:20 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:23 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:23 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:23 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:25 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:25 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:25 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:27 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:27 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:27 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:29 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:29 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:29 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:31 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:31 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:31 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:33 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:33 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:33 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:35 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:35 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:35 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:38 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:38 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:38 rc_service: waiting "stop_wps_method" via wpsaide ...
(continues for over 20 minutes...)

I had done a factory reset and fresh install within the last month because of this issue, but it's still keeps occurring. I can set the rc_service & rc_service_pid to nothing in nvram, and it will calm down for a while, but it always comes back randomly. I've even tried removing the gpio values for the wps button in nvram thinking that maybe the button was starting to fail and close sporadically, but that made no difference.

Has anyone had this issue with the RT-N66U before?

Thank you!
 
I repurposed my old n66 as an extra switch when it started acting funky like that. It may be time for you to consider the possibility that it's time for you to do the same
 
Bobbar said:
Hello,

I have an RT-N66U with John's fork installed, Version 374.43_52E3j9527.

I keep having issues with the WPS service running amok. I will have WPS disabled via the web interface, but I keep finding that it has turned itself back on, and the logs will be filled with repeated start/stop/waiting messages from wpsaide and notify_rc, and the process "/sbin/init noinitrd" will be running at 100% CPU usage.

Here's a log snip:
Code: 
Jan 17 23:47:17 miniupnpd[825]: shutting down MiniUPnPd
Jan 17 23:47:17 miniupnpd[918]: HTTP listening on port 33771
Jan 17 23:47:17 miniupnpd[918]: Listening for NAT-PMP/PCP traffic on port 5351
Jan 18 00:45:37 watchdog: IP address, server and hostname have not changed since the last update. (ddns-check)
Jan 18 00:52:53 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:52:59 kernel: device eth1 left promiscuous mode
Jan 18 00:52:59 kernel: br0: port 2(eth1) entering disabled state
Jan 18 00:52:59 kernel: device eth2 left promiscuous mode
Jan 18 00:52:59 kernel: br0: port 3(eth2) entering disabled state
Jan 18 00:53:02 kernel: wl_module_init: passivemode set to 0x0
Jan 18 00:53:02 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 6.30.163.2002 (r382208)
Jan 18 00:53:02 kernel: eth2: Broadcom BCM4331 802.11 Wireless Controller 6.30.163.2002 (r382208)
Jan 18 00:53:04 kernel: device eth1 entered promiscuous mode
Jan 18 00:53:04 kernel: br0: port 2(eth1) entering listening state
Jan 18 00:53:04 kernel: br0: port 2(eth1) entering learning state
Jan 18 00:53:04 kernel: br0: topology change detected, propagating
Jan 18 00:53:04 kernel: br0: port 2(eth1) entering forwarding state
Jan 18 00:53:04 kernel: device eth2 entered promiscuous mode
Jan 18 00:53:04 kernel: br0: port 3(eth2) entering listening state
Jan 18 00:53:04 kernel: br0: port 3(eth2) entering learning state
Jan 18 00:53:04 kernel: br0: topology change detected, propagating
Jan 18 00:53:04 kernel: br0: port 3(eth2) entering forwarding state
Jan 18 00:53:10 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:11 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:11 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:11 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:14 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:14 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:14 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:16 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:16 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:16 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:18 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:18 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:18 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:20 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:20 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:20 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:23 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:23 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:23 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:25 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:25 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:25 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:27 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:27 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:27 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:29 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:29 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:29 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:31 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:31 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:31 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:33 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:33 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:33 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:35 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:35 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:35 rc_service: waiting "stop_wps_method" via wpsaide ...
Jan 18 00:53:38 rc_service: wpsaide 502:notify_rc stop_wps_method
Jan 18 00:53:38 rc_service: wpsaide 502:notify_rc start_wps_method
Jan 18 00:53:38 rc_service: waiting "stop_wps_method" via wpsaide ...
(continues for over 20 minutes...)

I had done a factory reset and fresh install within the last month because of this issue, but it's still keeps occurring. I can set the rc_service & rc_service_pid to nothing in nvram, and it will calm down for a while, but it always comes back randomly. I've even tried removing the gpio values for the wps button in nvram thinking that maybe the button was starting to fail and close sporadically, but that made no difference.

Has anyone had this issue with the RT-N66U before?

Thank you!
Click to expand...
You could ssh into the router and check the status of the wps setting: nvram show | grep "wps".

If any are showing active ("1") or enabled you could try to disable in nvram:

Code: 
nvram set wps_enable=0
nvram set wl0.1_wps_mode=disabled
nvram set wl0.2_wps_mode=disabled
nvram set wl0.3_wps_mode=disabled
nvram set wps_proc_status=0
nvram set wl_wps_mode=disabled
nvram set wps_restart=0
nvram set wps_band=0
nvram set wl0_wps_config_state=0
nvram set wl1_wps_config_state=0
nvram commit

Then reboot.

If these are already showing disabled, and a reset *without* a configuration restore doesn't help, then yeah, yours might be on it's way out. Heat and time is not this router's friend.
 
dev_null said:
You could ssh into the router and check the status of the wps setting: nvram show | grep "wps".

If any are showing active ("1") or enabled you could try to disable in nvram:

Code: 
nvram set wps_enable=0
nvram set wl0.1_wps_mode=disabled
nvram set wl0.2_wps_mode=disabled
nvram set wl0.3_wps_mode=disabled
nvram set wps_proc_status=0
nvram set wl_wps_mode=disabled
nvram set wps_restart=0
nvram set wps_band=0
nvram set wl0_wps_config_state=0
nvram set wl1_wps_config_state=0
nvram commit

Then reboot.

If these are already showing disabled, and a reset *without* a configuration restore doesn't help, then yeah, yours might be on it's way out. Heat and time is not this router's friend.
Click to expand...

Thanks for the reply. I haven't tried setting many of those values, so I'll give it a shot.

Although I suspect it is just on it's way out, so I'm looking to switch to a Ubiquiti EdgeRouter & AP combo soon regardless.
 
I tried the suggested nvram settings, but still no love. It just went right back into doing the same thing shortly after rebooting. :-(

Look I'm going to be moving to a new device.

Thanks again!
 
You must log in or register to reply here.

Similar threads

J
Device all of a sudden is assigning itself a 169.254 IP address when coming out of standby
2
Replies
36
Views
4K
JTnola
J
D
Random timeouts on Firmware:3004.388.8_4
Replies
6
Views
523
dineshgyl
D
N
RT-AX86U-Pro, WAN disconnect every 36 hours
2
Replies
25
Views
2K
Nick24
N
Gangy
RT-AX92U cyclically freezes and reboots after connecting ext. HDD
Replies
5
Views
848
Gangy
Gangy
N
RT-AX88U wireless shuts down at irregular intervals
Replies
8
Views
623
Nighthawke70
N
Similar threads
Thread starter Title Forum Replies Date
P WPS functionality RT-AC68U Asuswrt-Merlin 20
S AXE11000 - WPS bug? Asuswrt-Merlin 6
P RT-AX86U WiFi not working after turning on Gear Accelerator Asuswrt-Merlin 4
U High CPU usage after turning off Wireguard/VPN Asuswrt-Merlin 2
R OpenVPN keeps on turning itself off Asuswrt-Merlin 40

Similar threads

Latest 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

Members online

Total: 751 (members: 34, guests: 717)
Back
Top