RT68U/ 384.8_2 : radios, openVPN turning themselves off

[UserUnknown]

The former has happened twice this week, and the latter I discovered at the most recent event.
Wireless/professional/ enable radio set to 'off' for both bands.

This is a unit I picked up used, reset to default, and flashed through the stock versions to get to most current.

Not using QoS, but I do have a usb drive (upnp server) to feed to a Roku.

Is there anything specific I should be digging for in my logs?

I have noticed that this unit logs me out pretty quickly.

 

[martinr]

You reset AFTER
flashing firmware, not before.

Can’t work out are you now running stock firmware or Merlin’s firmware?

 

[UserUnknown]

I am currently on Merlin 384.8_2.
I couldn't flash straight to the most current Merlin from the original Asus version that it shipped with (3.0.0.4.374)
I've had no issues with this version of Merlin for a couple of months (?). The radio issue is new this week, although I did configure the VPN within a week or so.

 

[martinr]

I am currently on Merlin 384.8_2.
I couldn't flash straight to the most current Merlin from the original Asus version that it shipped with (3.0.0.4.374)....

You say you couldn’t flash to the current Merlin firmware from the firmware it shipped with, so, how did you do it: what process did you use so that you could flash 384.8_2?

 

[UserUnknown]

Stepwise updates of the OEM Asus versions to their most recent, then to Merlin.
per here; https://github.com/RMerl/asuswrt-merlin/wiki/Installation
(specifically, items 1 and 2)

 

[UserUnknown]

The VPN issue is my error. I did not have 'automatic start at boot time' checked, so it did not restart at the last reboot.

 

[UserUnknown]

I reset to (merlin) default settings and spent the time reconfiguring, but got another episode of the radios turning off overnight. I turned the VPN off to eliminate a variable.
Any suggestions?

 

[Grisu]

Stepwise updates of the OEM Asus versions to their most recent, then to Merlin.
per here; https://github.com/RMerl/asuswrt-merlin/wiki/Installation
(specifically, items 1 and 2)

asus pulled ALL firmwares older than 3 months or something like this, you cant download any needed steps.
Go directly with last Asus or change to older Merlin and make the "steps" with him.

 

[UserUnknown]

Thank you for responding.
The oldest Merlin available at SF is 378.55. I should revert to this, and then update to 384.8?

The logs for the last time the radios turned off:
Jan 29 03:57:04 rc_service: watchdog 272:notify_rc stop_amas_wlcconnect
Jan 29 03:57:04 rc_service: watchdog 272:notify_rc stop_amas_bhctrl
Jan 29 03:57:04 rc_service: waitting "stop_amas_wlcconnect" via watchdog ...
Jan 29 03:57:05 rc_service: watchdog 272:notify_rc stop_obd
Jan 29 03:57:05 rc_service: waitting "stop_amas_bhctrl" via watchdog ...
Jan 29 03:57:07 kernel: br0: port 2(eth1) entering forwarding state
Jan 29 03:57:07 kernel: device eth1 left promiscuous mode
Jan 29 03:57:07 kernel: br0: port 2(eth1) entering disabled state
Jan 29 03:57:07 kernel: br0: port 3(eth2) entering forwarding state
Jan 29 03:57:07 kernel: device eth2 left promiscuous mode
Jan 29 03:57:07 kernel: br0: port 3(eth2) entering disabled state
Jan 29 03:57:10 kernel: wl_module_init: passivemode set to 0x0
Jan 29 03:57:10 kernel: wl_module_init: igs set to 0x0
Jan 29 03:57:10 kernel: wl_module_init: txworkq set to 0x1
Jan 29 03:57:10 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.126 (r561982)
Jan 29 03:57:10 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.126 (r561982)
Jan 29 03:57:10 kernel: device eth1 entered promiscuous mode
Jan 29 03:57:10 kernel: br0: topology change detected, propagating
Jan 29 03:57:10 kernel: br0: port 2(eth1) entering forwarding state
Jan 29 03:57:10 kernel: br0: port 2(eth1) entering forwarding state
Jan 29 03:57:10 kernel: device eth2 entered promiscuous mode
Jan 29 03:57:10 kernel: br0: topology change detected, propagating
Jan 29 03:57:10 kernel: br0: port 3(eth2) entering forwarding state
Jan 29 03:57:10 kernel: br0: port 3(eth2) entering forwarding state

 

[Grisu]

yes, could not be bad to do so.
Maybe you need to use recovery tool or mini-web to load old firmware, afterwards full reset needed.
Than load 380.70 and 384.9beta at the end with factory reset each time.

 

[UserUnknown]

Thank you, I will try that. Are there any red flags in my log?

 

[RMerlin]

Your log shows that you are using AiMesh, which is not supported by my firmware. Do a factory default reset and manually reconfigure everything.

 

[Grisu]

That would mean you have a recent firmware on your router, why do you write its very old 374?

Maybe you only picked up the wrong 86U instead of 68U firmware from Merlin?

 

[UserUnknown]

Your log shows that you are using AiMesh, which is not supported by my firmware. Do a factory default reset and manually reconfigure everything.

I haven't purposely enabled that and can't find the setting for it. Is there another way to manually disable it?

I recently did a reset (administration....factory default....restore) but can attempt it again.

 

[UserUnknown]

That would mean you have a recent firmware on your router, why do you write its very old 374?

Maybe you only picked up the wrong 86U instead of 68U firmware from Merlin?

It arrived with 374, and I upgraded after I got it.

 

[UserUnknown]

Another piece of possibly relevant information: I have my older AC66U (newest stock Asus firmware 3.0.0.4.382) connected to my LAN in AP mode, but as a wired switch with its radios turned off.

 

[Grisu]

so whats your problem now using latest firmware available?
Your Wifi is only much weaker now with new firmware, as they limited power about 2015 to some few mW.
Maybe you only had much more coverage with your very old firmware.

BTW: your 66U is not able to run Aimesh (only RT-AC66U_B1 can do).

 

[UserUnknown]

so whats your problem now using latest firmware available?
.

The radios will turn off overnight (wireless...professional....enable radio....no) without my intervention. WiFi works fine otherwise; great range and throughput.

 

[Grisu]

maybe your wifi-scheduler is active
https://www.snbforums.com/threads/rt-ac68u-wireless-scheduler.44418/

 

[UserUnknown]

maybe your wifi-scheduler is active
https://www.snbforums.com/threads/rt-ac68u-wireless-scheduler.44418/

no.