AC68U does not recover from "restart_wlcmode 0"

[DotNet]

Hi,

I now live with this problem since I got my ASUS AC68U but today I thought I would try to ask for help and hope that one of you is able to identify a solution for it.

Setup:

ASUS AC68U
currently Merlin 384.9, I think my first version I started with was "RT-AC68U_3.0.0.4_374.43_2" 2014.
Running as Media Brdige connected to FritzBox 7490
2.4 GHZ disabled, only 5 GHz enabled on AC68U

Problem:

Everyday the connection to the Internet / FritzBox is lost, sometimes multiple times in a row / day.
I have to reset the wireless connection with running this command on the AC68U manually by SSH (or now with plink ..)

service restart_wireless


Hints:

I have seen this message occuring at that time and then no internet connection is available:

rc_service: psta_monitor 858:notify_rc restart_wlcmode 0

I did not find anything here in the forum if I search for "restart_wlcmode 0" but on the internet:

https://forums.tomshardware.com/threads/is-this-a-asus-router-hack.3319853/

https://www.reddit.com/r/HomeNetwor...e_help_i_have_a_problem_with_the_asus_rpac66/


And I have found the following line in code, where it seems that there would be send the command

"restart_wireless"

after "restart_wlcmode 0" occurs if this flag is set: CONFIG_BCMWL5

https://github.com/RMerl/asuswrt-merlin/blob/master/release/src/router/rc/wireless.c#L267

Is there any way that I cen configure it to reset wireless if "restart_wlcmode 0" occurs?

MANY THANKS in advance for any help, as it is driving me crazy for some years now :/



Log:

Mar 7 17:19:10 RT-AC68U: start https:8443
Mar 7 17:19:10 RT-AC68U: start httpd:80
Mar 7 17:19:10 dropbear[1078]: Running in background
Mar 7 17:19:10 kernel: gro enabled with interval 2
Mar 7 17:19:11 Samba_Server: daemon is started

### FROM here Internet was not accessible from LAN connected PC (yellow sign at network icon)

Mar 7 17:41:51 rc_service: psta_monitor 858:notify_rc restart_wlcmode 0
Mar 7 17:41:51 FTP_Server: daemon is stopped
Mar 7 17:41:51 Samba_Server: smb daemon is stopped
Mar 7 17:41:51 kernel: gro disabled
Mar 7 17:41:51 dropbear[1078]: Early exit: Terminated by signal
Mar 7 17:41:51 avahi-daemon[545]: Interface br0.IPv4 no longer relevant for mDNS.
Mar 7 17:41:51 avahi-daemon[545]: Leaving mDNS multicast group on interface br0.IPv4 with address [AC68U-ROUTER-IP-HERE].
Mar 7 17:41:51 avahi-daemon[545]: Withdrawing address record for [AC68U-ROUTER-IP-HERE] on br0.
Mar 7 17:41:51 kernel: br0: port 3(eth2) entering forwarding state
Mar 7 17:41:51 kernel: br0: port 2(eth1) entering forwarding state
Mar 7 17:41:51 kernel: br0: port 1(vlan1) entering forwarding state
Mar 7 17:41:59 avahi-daemon[545]: Joining mDNS multicast group on interface br0.IPv4 with address [AC68U-ROUTER-IP-HERE].
Mar 7 17:41:59 avahi-daemon[545]: New relevant interface br0.IPv4 for mDNS.
Mar 7 17:41:59 avahi-daemon[545]: Registering new address record for [AC68U-ROUTER-IP-HERE] on br0.IPv4.
Mar 7 17:41:59 kernel: br0: port 3(eth2) entering forwarding state
Mar 7 17:41:59 kernel: br0: port 3(eth2) entering forwarding state
Mar 7 17:41:59 kernel: br0: port 2(eth1) entering forwarding state
Mar 7 17:41:59 kernel: br0: port 2(eth1) entering forwarding state
Mar 7 17:41:59 kernel: br0: port 1(vlan1) entering forwarding state
Mar 7 17:41:59 kernel: br0: port 1(vlan1) entering forwarding state
Mar 7 17:41:59 rc_service: preinit 1:notify_rc restart_dms
Mar 7 17:41:59 rc_service: waitting "restart_wlcmode 0" via psta_monitor ...
Mar 7 17:42:04 rc_service: psta_monitor 858:notify_rc restart_wlcmode 1
Mar 7 17:42:04 rc_service: waitting "restart_wlcmode 0" via psta_monitor ...
Mar 7 17:42:11 watchdog: restart httpd
Mar 7 17:42:11 rc_service: watchdog 208:notify_rc stop_httpd
Mar 7 17:42:11 rc_service: waitting "restart_wlcmode 0" via psta_monitor ...
Mar 7 17:42:14 rc_service: skip the event: restart_wlcmode 1.
Mar 7 17:42:14 rc_service: skip the event: restart_dms.
Mar 7 17:42:14 RT-AC68U: start https:8443
Mar 7 17:42:14 RT-AC68U: start httpd:80
Mar 7 17:42:15 dropbear[1186]: Running in background
Mar 7 17:42:15 kernel: gro enabled with interval 2
Mar 7 17:42:15 Samba_Server: daemon is started
Mar 7 17:42:15 rc_service: watchdog 208:notify_rc start_httpd
Mar 7 17:42:16 RT-AC68U: start https:8443
Mar 7 17:42:16 RT-AC68U: start httpd:80

 

[L&LD]

DotNet, when was the last time you did a full reset to factory defaults on this router?

Did you do one just before putting it into Media Bridge mode?

From which firmware version did you upgrade to 384.9 from?

 

[Grisu]

sell it and get a used second 7490 instead configured in mesh mode, or any other with mesh support, even a 1750E could be good depending on your needs.
I got 3 in mesh now and no more problems. (You need to press WPS on both then you will get blue triangle mesh-sign on both and they are paired!)

 

[L&LD]

Hard to sell something that isn't currently working, no?

 

[Grisu]

I'm quite sure hardware is ok and the problem is firmware related in his configuration, others wont have his troubles or use older stable firmware.

We all know (or those who read all postings) that media bridge mode is buggy seen by many users here!

Some solved it with repeater mode instead of bridge mode (only difference that it will share WiFi too to clients in its area).

 

[DotNet]

Thanks everybody for your replies!

DotNet, when was the last time you did a full reset to factory defaults on this router?

Did you do one just before putting it into Media Bridge mode?

From which firmware version did you upgrade to 384.9 from?

I think the last full reset was somewhen after the change from non-NG to NG but at least at that change.
I bought it to run in Media Bridge, so I never used it in a different mode, it's the first thing I configure.
But yes I could try a full reset again, but as I have this problem since very long time and I did already try resets multiple times, I have not so much ope, but is always a good thing.

I updated from RT-AC68U_384.8_2.
I nearly follow every single update, seldom I update to betas, but I even read the commits on github very often.

sell it and get a used second 7490 instead configured in mesh mode, or any other with mesh support, even a 1750E could be good depending on your needs.
I got 3 in mesh now and no more problems. (You need to press WPS on both then you will get blue triangle mesh-sign on both and they are paired!)

Sure I could by something new, but the additional thing why I bought the ASUS is the possibility to easily use widely used services (VPN, Downloader, Python) and access to the shell, that's all not so easy on a FritzBox (Freetz). But yes might be someday replaced when I buy a new model so the "old" 7490 can act as the Bridge and so the ASUS could additionally run only acting as mini server.
But for now it would be sooo great to have it fixed or only so that it would reset the wlan on it's own after the event, that would be totally enough for me.
I already thought about a daemon watching the log like "tail -f" and triggereing it if the log entry occurs ... but something solid would be nice to have ^^

Some solved it with repeater mode instead of bridge mode (only difference that it will share WiFi too to clients in its area).

Hmmm that sound promising, for sure something I should try, thanks!

 

[L&LD]

Thanks everybody for your replies!





I think the last full reset was somewhen after the change from non-NG to NG but at least at that change.
I bought it to run in Media Bridge, so I never used it in a different mode, it's the first thing I configure.
But yes I could try a full reset again, but as I have this problem since very long time and I did already try resets multiple times, I have not so much ope, but is always a good thing.

I updated from RT-AC68U_384.8_2.
I nearly follow every single update, seldom I update to betas, but I even read the commits on github very often.




Sure I could by something new, but the additional thing why I bought the ASUS is the possibility to easily use widely used services (VPN, Downloader, Python) and access to the shell, that's all not so easy on a FritzBox (Freetz). But yes might be someday replaced when I buy a new model so the "old" 7490 can act as the Bridge and so the ASUS could additionally run only acting as mini server.
But for now it would be sooo great to have it fixed or only so that it would reset the wlan on it's own after the event, that would be totally enough for me.
I already thought about a daemon watching the log like "tail -f" and triggereing it if the log entry occurs ... but something solid would be nice to have ^^



Hmmm that sound promising, for sure something I should try, thanks!

You're welcome DotNet.

I can't seem to figure out what non-NG to NG is?

When you reset the router, format the jffs partition on next boot too, and also use the WPS button method to clear the NVRAM and it won't hurt to install 384.9 once more (even if it is already installed now). Just trying to make sure that the router really isn't using old NVRAM variables or other cruft from old firmware.

 

[DotNet]

You're welcome DotNet.

I can't seem to figure out what non-NG to NG is?

Non-NG: https://github.com/RMerl/asuswrt-merlin
NG: https://github.com/RMerl/asuswrt-merlin.ng

Thanks for the detailed steps, will try that.
Just changed the mode to repeater mode and will see how that behaves, and if the problem still appears I will wipe everything again.

 

[DotNet]

Just as a short followup, even if it is not long time ago, up to now after chaning to repeater mode, I had not to manually do a "restart_wireless"!

 

[L&LD]

Just as a short followup, even if it is not long time ago, up to now after chaning to repeater mode, I had not to manually do a "restart_wireless"!

But are you happy with the wireless performance? Repeater mode incurs a 50% hit or worse on throughput.

 

[ColinTaylor]

Repeater mode incurs a 50% hit or worse on throughput.

Only when it's "repeating". As he's actually using it as wireless Ethernet bridge then presumably the penalty doesn't apply.

 

[DotNet]

So I can report today, that I still had not a single disconnect now running in repeater mode, so that really is working great. Don't know why over all the years the bridge mode was not fixed, but it is OK for me.
Regarding wireless performance: I still get full speed of my internet connection, so that is the most important one.

The connection to my NAS I have not done any speed test, if I find the time, I should compare the perfomance for both modes if there is a big difference.
Thanks for all the input! Very much appreciated.