What's new
  • 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!

failover takes a long time

alan_smithee

Occasional Visitor
RT AC66U with Firmware:3.0.0.4.374.39 (Merlin build)

When I run this command "ifconfig eth0 down" (eth0 is wan)
The WAN connection disconnects and the router switches to the USB
This process takes about 20 to 90 seconds.

If I take out my DSL cable watchdog kicks in after 60 seconds and the following log shows

Code:
Feb 12 22:08:14 WAN Connection: WAN was exceptionally disconnected.
Feb 12 22:08:14 stop_nat_rules: apply the redirect_rules!
Feb 12 22:08:20 dnsmasq[457]: exiting on receipt of SIGTERM
Feb 12 22:08:20 dnsmasq[768]: started, version 2.68 cachesize 1500
Feb 12 22:08:20 dnsmasq[768]: asynchronous logging enabled, queue limit is 5 messages
Feb 12 22:08:20 dnsmasq-dhcp[768]: DHCP, IP range 192.168.2.2 -- 192.168.2.254, lease time 1d
Feb 12 22:08:20 dnsmasq[768]: read /etc/hosts - 5 addresses
Feb 12 22:08:20 dnsmasq[768]: read /etc/hosts.dnsmasq - 18 addresses
Feb 12 22:08:20 dnsmasq-dhcp[768]: read /etc/ethers - 20 addresses
Feb 12 22:08:20 dnsmasq[768]: using nameserver 192.168.1.1#53
Feb 12 22:08:20 dnsmasq[768]: using nameserver 192.168.1.1#53
Feb 12 22:08:20 dnsmasq[768]: using nameserver 208.67.220.220#53
Feb 12 22:08:20 dnsmasq[768]: using nameserver 208.67.222.222#53
Feb 12 22:08:43 dnsmasq-dhcp[768]: DHCPINFORM(br0) 192.168.2.208 14:da:e9:c1:15:1a 
Feb 12 22:08:43 dnsmasq-dhcp[768]: DHCPACK(br0) 192.168.2.208 14:da:e9:c1:15:1a Desktop
Feb 12 22:09:53 dnsmasq-dhcp[768]: DHCPINFORM(br0) 192.168.2.208 14:da:e9:c1:15:1a 
Feb 12 22:09:53 dnsmasq-dhcp[768]: DHCPACK(br0) 192.168.2.208 14:da:e9:c1:15:1a Desktop
Feb 12 22:10:54 dnsmasq-dhcp[768]: DHCPINFORM(br0) 192.168.2.208 14:da:e9:c1:15:1a 
Feb 12 22:10:54 dnsmasq-dhcp[768]: DHCPACK(br0) 192.168.2.208 14:da:e9:c1:15:1a Desktop
Feb 12 22:12:54 dnsmasq-dhcp[768]: DHCPINFORM(br0) 192.168.2.208 14:da:e9:c1:15:1a 
Feb 12 22:12:54 dnsmasq-dhcp[768]: DHCPACK(br0) 192.168.2.208 14:da:e9:c1:15:1a Desktop
Feb 12 22:14:11 rc_service: wanduck 317:notify_rc restart_wan_if 0
Feb 12 22:14:11 stop_wan(): perform DHCP release
Feb 12 22:14:11 kernel: Attempt to kill tasklet from interrupt
Feb 12 22:14:11 dnsmasq[768]: read /etc/hosts - 5 addresses
Feb 12 22:14:11 dnsmasq[768]: read /etc/hosts.dnsmasq - 18 addresses
Feb 12 22:14:11 dnsmasq-dhcp[768]: read /etc/ethers - 20 addresses
Feb 12 22:14:11 dnsmasq[768]: using nameserver 192.168.1.1#53
Feb 12 22:14:11 dnsmasq[768]: using nameserver 192.168.1.1#53
Feb 12 22:14:11 dnsmasq[768]: using nameserver 208.67.220.220#53
Feb 12 22:14:11 dnsmasq[768]: using nameserver 208.67.222.222#53
Feb 12 22:14:11 kernel: br0: port 1(vlan1) entering disabled state
Feb 12 22:14:11 kernel: vlan1: dev_set_promiscuity(master, 1)
Feb 12 22:14:11 kernel: br0: port 1(vlan1) entering learning state
Feb 12 22:14:11 kernel: br0: topology change detected, propagating
Feb 12 22:14:11 kernel: br0: port 1(vlan1) entering forwarding state
Feb 12 22:14:11 dnsmasq[768]: read /etc/hosts - 5 addresses
Feb 12 22:14:11 dnsmasq[768]: read /etc/hosts.dnsmasq - 18 addresses
Feb 12 22:14:11 dnsmasq-dhcp[768]: read /etc/ethers - 20 addresses
Feb 12 22:14:11 dnsmasq[768]: using nameserver 192.168.1.1#53
Feb 12 22:14:11 dnsmasq[768]: using nameserver 192.168.1.1#53
Feb 12 22:14:11 dnsmasq[768]: using nameserver 208.67.220.220#53
Feb 12 22:14:11 dnsmasq[768]: using nameserver 208.67.222.222#53
Feb 12 22:14:13 dnsmasq[768]: read /etc/hosts - 5 addresses
Feb 12 22:14:13 dnsmasq[768]: read /etc/hosts.dnsmasq - 18 addresses
Feb 12 22:14:13 dnsmasq-dhcp[768]: read /etc/ethers - 20 addresses
Feb 12 22:14:13 dnsmasq[768]: using nameserver 192.168.1.1#53
Feb 12 22:14:13 dnsmasq[768]: using nameserver 192.168.1.1#53
Feb 12 22:14:13 dnsmasq[768]: using nameserver 208.67.220.220#53
Feb 12 22:14:13 dnsmasq[768]: using nameserver 208.67.222.222#53
Feb 12 22:14:13 dhcp client: bound 192.168.1.10 via 192.168.1.1 during 30 seconds.
Feb 12 22:14:13 rc_service: wanduck 317:notify_rc restart_wan_line 1
Feb 12 22:14:13 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth3_eth3)!
Feb 12 22:14:13 dnsmasq[768]: exiting on receipt of SIGTERM
Feb 12 22:14:13 dnsmasq[1047]: started, version 2.68 cachesize 1500
Feb 12 22:14:13 dnsmasq[1047]: asynchronous logging enabled, queue limit is 5 messages
Feb 12 22:14:13 dnsmasq-dhcp[1047]: DHCP, IP range 192.168.2.2 -- 192.168.2.254, lease time 1d
Feb 12 22:14:13 dnsmasq[1047]: read /etc/hosts - 5 addresses
Feb 12 22:14:13 dnsmasq[1047]: read /etc/hosts.dnsmasq - 18 addresses
Feb 12 22:14:13 dnsmasq-dhcp[1047]: read /etc/ethers - 20 addresses
Feb 12 22:14:13 dnsmasq[1047]: using nameserver 192.168.1.1#53
Feb 12 22:14:13 dnsmasq[1047]: using nameserver 192.168.1.1#53
Feb 12 22:14:13 dnsmasq[1047]: using nameserver 208.67.220.220#53
Feb 12 22:14:13 dnsmasq[1047]: using nameserver 208.67.222.222#53
Feb 12 22:14:14 miniupnpd[1071]: HTTP listening on port 41548
Feb 12 22:14:14 miniupnpd[1071]: Listening for NAT-PMP traffic on port 5351
Feb 12 22:14:14 kernel: tun: Universal TUN/TAP device driver, 1.6
Feb 12 22:14:14 kernel: tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
Feb 12 22:14:14 kernel: device tun21 entered promiscuous mode
Feb 12 22:14:49 WAN Connection: WAN was restored.

This process takes about 5 to 10 minutes.
I run this test a couple of times and all with the same result. It just takes to long when I unplug the cable. And it seems that the failover process begins with this line
rc_service: wanduck 4001:notify_rc restart_wan_if 0

Does anyone know why this takes so long and how I can shorten it?
 
Last edited:
Since there is no reply for two week maybe I can take another approach.
I've read that HiLink mode causes some trouble with most Linux devices.
Is there a way I can use the USB_Modeswitch to change the Huawei E3131 in a serial device?

The standard method (AT^U2DIAG=0) doesn't make it stay in modem mode.
After a reboot of the router the dongle comes back in HiLink mode
 
Actually, your original post is just less than 6 days ago.

It might help others help you if you indicate which router and which firmware you are running. Along with any other relevant details?
 
Ow my bad 02-12-2014 I'm used to european time settings and just saw the first 2 :o
This thing is driving me mad though. I don't know what is causing the issue.

I'm on a RT AC66U. with Firmware:3.0.0.4.374.39 (Merlin build).
The 3G module is an Huawei E3131
hardware IDs (I've read that there are various models):
HiLink Mode: 12D1 14DB
Serial Mode: 12d1 1442
Serial Mode 2: 12d1 1C05 (after second reboot)

I'm using opendns because if the router redirects it's traffic to 192.168.1.1 (the gateway of the dongle) it goes to my cable provider web monitoring page which is also 192.168.1.1

The setup does work but a of 10 minute window to switch over to the second wan is unacceptable.

Is this normal behavior for the E3131? Is it beter to switch HiLink devices to serial?
 
No problem; time seems to be flying here too (and I can't use the European time settings excuse!). :)


I think I've seen a recent thread where someone mentioned that the Huawei is not an NA common device and therefore you may not get too many replies.

I don't use such devices and can't offer any more help either, unfortunately. Hope someone sees this with an answer for you though.
 
Thnx for the help.
The Huawei E3131 is supported along with other Huawei HiLink devices. I don't really trust those anymore.

Does anyone have Dual Wan working with an 3G module? If so which one do you use?
 
Thnx for the help.
The Huawei E3131 is supported along with other Huawei HiLink devices. I don't really trust those anymore.

Does anyone have Dual Wan working with an 3G module? If so which one do you use?

I originally used an (unsupported/listed) Infinity Wireless IW-021 but this was probably back in the 270.26b days when 3G WAN failover was still experimental, but I eventually purchased an (unlocked) Huawei E220 which turned out to be a Vodaphone branded unit when it arrived.

Regards,
 
Thanks for the reply, I just ordered an Huawei E220 :)

I was just tinkering around with my old Huawei E3131 and finaly was able to flash it to another firmware. Now the Asus recognizes an HUAWEI Mobile device instead of an HUAWEI HiLink. Also in inconfig the device is now called ppp0.

I reset my modem to factory default and run the setup for both wan connections. I enabled watchdog (just like always) and unplugged the dsl to my modem. After 60 seconds watchdog signals that the wan connection is disconnected and the following log is shown.
Code:
Feb 26 19:45:53 WAN Connection: ISP's DHCP did not function properly.
Feb 26 19:45:53 stop_nat_rules: apply the redirect_rules!
Feb 26 19:45:53 dnsmasq[473]: exiting on receipt of SIGTERM
Feb 26 19:45:53 dnsmasq[688]: started, version 2.68 cachesize 1500
Feb 26 19:45:53 dnsmasq[688]: asynchronous logging enabled, queue limit is 5 messages
Feb 26 19:45:53 dnsmasq-dhcp[688]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Feb 26 19:45:53 dnsmasq-dhcp[688]: DHCP, sockets bound exclusively to interface br0
Feb 26 19:45:53 dnsmasq[688]: read /etc/hosts - 5 addresses
Feb 26 19:45:53 dnsmasq[688]: using nameserver 62.140.138.233#53
Feb 26 19:45:53 dnsmasq[688]: using nameserver 62.140.140.251#53
Feb 26 19:45:53 dnsmasq[688]: using nameserver 212.54.35.25#53
Feb 26 19:45:53 dnsmasq[688]: using nameserver 212.54.40.25#53
And that's it again, I waited 10 minutes and nothing happened.
Wan 1 is disconnected wan 2 (3G) is in standby.

I connected the dsl cable again gave the router a reboot and this time with watchdog enabled I unplugged the UTP cable from my modem to my router.
Again after 60 seconds watchdog reports that wan 1 is disconnected and nothing else happens again... Maybe I should wait longer but that's the point I shouldn't have to wait longer then 2 minutes before even anything in the log appears.

I disable watchdog repeat both steps. If I unplug the DSL cable the router is unable to see that the wan connection is disconnected. When I unplug the UTP cable the router immediately switch over to 3G.

I don't think another 3G module will solve this issue but I will try again as soon as the E220 arrives.


So here's where I strand. Asus suggest to enable watchdog. Probably because otherwise the router isn't able the see if the internet connection is disrupted but when enabled it takes forever to switch over.

How do you guys setup the dual wan? With watchdog or without? and what do you do when the UTP connection is still connected between router en modem but the internet connection is down?
 
Think the dual Wan is still not fully baked on the Asus.. Think it's still a work in progress...

Sent from my Venue 7 3730 using Tapatalk
 
I use Huawei E220 with kinda more functionality,

h**p://forums.smallnetbuilder.com/showthread.php?t=15478

however I don't think it's supported in my country

h**p://event.asus.com/2009/networks/3gsupport/#RT

BR
 
I use Huawei E220 with kinda more functionality,

h**p://forums.smallnetbuilder.com/showthread.php?t=15478

BR

I've send you a reply on this post.

Also I don't think it matters if you're country isn't listed. My country (the Netherlands) isn't on the list either but 3G is still functional.
 
Think the dual Wan is still not fully baked on the Asus.. Think it's still a work in progress...

Sent from my Venue 7 3730 using Tapatalk

So everyone that uses dual wan with 3G has the same issues? Or they don't use watchdog?...

Should I notify Asus?
 
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!
Back
Top