RT AC66U with Firmware:3.0.0.4.374.39 (Merlin build)
When I run this command line "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 kabel watchdog kicks in after 60 seconds and the following log shows
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?
When I run this command line "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 kabel 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 <maxk@qualcomm.com>
Feb 12 22:14:14 kernel: device tun21 entered promiscuous mode
Feb 12 22:14:49 WAN Connection: WAN was restored.rc_service: wanduck 4001:notify_rc restart_wan_if 0
Does anyone know why this takes so long and how I can shorten it?