MiniCFE not coming up and no ping on 192.168.1.1
Seems like its bricked because I tried to flash latest merlin instead of flashing default asus firmware first ... will put it back in the closet where it was for last 5 years ...
Thanks for trying to help.
Tried the steps from post #8 and after "mtd-erase2 nvram" it gave "segmentation fault" error, so I tried to reboot with WPS button with no luck, power lid is solid light and no flashing, tried multiple times with reset button and same .... solid power led and no others.
Also tried the firmware...
I just noticed "Auto USB Backup WAN" in Dual Wan section :
When I enable it and click apply it just reboot and enable dual wan.
If I turn on the "Enable Dual Wan" it does the same,
So what's the difference between "Auto USB Backup WAN" and "Enable Dual Wan"?
Updated my RT-AX86U to 386.78_2 but wan events problem still exists.
Kernel detects wan down but firmware not trigger wan-disconnect event and also wan-stopping and wan-stopped are triggered after wan connected again
Is this an addons problem or firmware problem?
Log:
Wan cable disconnected...
Its more seems like firmware problem not addons issue.
Kernel detects wan cable disconnected but firmware not trigger wan disconnected event on my router and on yours not until after its connected again.
Thread should not have been moved to addons section
Tried wan-event to trigger start and stop VPN_Failover by @Martineau
wan0-connected script works fine and triggers VPN_Failover start, but wan0-disconnected not triggers and there is no event in syslog as wan0-disconnected.
Also posted my problem on github: No wan-event in syslog as...
So I checked almost all the threads on Asus failover/failback found by google and it seems like this is a known and not solved issue on all Asus routers both original and merlin firmwares
I have 2 cable networks and want use one as failover.
These are my settings:
Primary WAN: WAN
Secondary WAN: LAN 4
Dual WAN Mode failover with Allow failback
Detect Interval 5 seconds
Failover Execution Time: Continuous 12 times (60 seconds) detect network failed
Failback Execution Time...