Page 2 of 2
Re: Failover not detecting dropped connection
Posted: Tue Feb 24, 2015 12:56 am
by petersharon
Hi there
done as instructed
whats happening now is that it fails over to adsl connection i checked the sys log it updates the dyndns with the new ip etc but no internet connection is achieved on any equipment connected wired or wireless even rebooting laptop etc
Simulated dropped connection 3 different times with same result Fallback is working spot on as soon as cable is reconnected on Virgin router internet works flawlessly
Regards
Peter
Re: Failover not detecting dropped connection
Posted: Tue Feb 24, 2015 9:36 am
by billion_fan
petersharon wrote:Hi there
done as instructed
whats happening now is that it fails over to adsl connection i checked the sys log it updates the dyndns with the new ip etc but no internet connection is achieved on any equipment connected wired or wireless even rebooting laptop etc
Simulated dropped connection 3 different times with same result Fallback is working spot on as soon as cable is reconnected on Virgin router internet works flawlessly
Regards
Peter
Did you setup a static DNS server eg 8.8.8.8 and 8.8.4.4??
Re: Failover not detecting dropped connection
Posted: Tue Feb 24, 2015 12:51 pm
by billion_fan
billion_fan wrote:petersharon wrote:Hi there
done as instructed
whats happening now is that it fails over to adsl connection i checked the sys log it updates the dyndns with the new ip etc but no internet connection is achieved on any equipment connected wired or wireless even rebooting laptop etc
Simulated dropped connection 3 different times with same result Fallback is working spot on as soon as cable is reconnected on Virgin router internet works flawlessly
Regards
Peter
Did you setup a static DNS server eg 8.8.8.8 and 8.8.4.4??
Also make sure the 'PPPOA' interface is listed under 'Advanced Setup >> Routing >> Selected Default Gateway Interfaces'
Re: Failover not detecting dropped connection
Posted: Tue Feb 24, 2015 4:49 pm
by petersharon
Hi
have tried with static ip
it works it will fail over to ADSL and im now getting internet on all equipment but dyndns does not update my ip
heres a log before i changed it to a static dns server
Here`s the Sys lo
Feb 24 16:20:28 user info syslog: ddnsd: update xxxxxxxxxx.dyndns.biz request successfully
Feb 24 16:20:28 daemon info syslog: Lease of 86.5.xxx.xxx obtained, lease time 525628
Feb 24 16:20:34 daemon warn kernel: ^[[0;36;44mBroadcom Packet Flow Cache flushing the flows^[[0m
Feb 24 16:20:34 user info syslog: l3wanFailover: system default wan is set to eth0.1
Feb 24 16:20:38 user info syslog: ddnsd: xxxxxxxxxx.dyndns.biz (eth0.1) IP has changed from 88.105.xxx.xxx to 86.5.xxx.xxx
Feb 24 16:20:38 user info syslog: ddnsd: update xxxxxxxxxxxxx.dyndns.biz request successfully
Feb 24 16:29:20 daemon warn kernel: wl0: received packet with own address as source address
Feb 24 16:30:50 user info syslog: l3wanFailover: failover to interface pppoa0
Feb 24 16:33:50 daemon crit kernel: eth0 (switch port: 4) Link DOWN.
Feb 24 16:33:54 daemon info syslog: Received SIGTERM
Feb 24 16:33:54 daemon info kernel: device eth0 left promiscuous mode
Feb 24 16:33:54 user info syslog: l3wanFailover: system default wan is set to pppoa0
Feb 24 16:33:57 user info syslog: ddnsd: xxxxxxxx.dyndns.biz (pppoa0) IP has changed from 86.5.xxx.xxx to 88.105.xx.xx
Feb 24 16:33:58 user info syslog: ddnsd: update xxxxxxx.dyndns.biz request successfully
Feb 24 16:34:23 daemon crit kernel: eth0 (switch port: 4) Link UP 1000 mbps full duplex
Feb 24 16:34:23 daemon warn kernel: eth0.1 MAC address set to 60:03:47:09:xx:xx
Feb 24 16:34:23 daemon warn kernel: netdev path : eth0.1 -> eth0
Feb 24 16:34:23 daemon warn kernel: BCMVLAN : eth0 mode was set to RG
Feb 24 16:34:23 daemon info kernel: device eth0 entered promiscuous mode
Feb 24 16:34:23 daemon info syslog: udhcp client (v0.9.6) started
Feb 24 16:34:26 daemon info syslog: Lease of 192.168.100.2 obtained, lease time 30
Feb 24 16:34:28 user info syslog: ddnsd: xxxxxxxxxxxxxxx.dyndns.biz (eth0.1) IP has changed from 88.105.xx.xx to 192.168.100.2
Feb 24 16:34:28 user info syslog: ddnsd: update xxxxxxxxxxxxxxxxxx.dyndns.biz request successfully
Feb 24 16:34:31 daemon warn kernel: ^[[0;36;44mBroadcom Packet Flow Cache flushing the flows^[[0m
Feb 24 16:34:31 user info syslog: l3wanFailover: change default wan to master eth0.1
Feb 24 16:34:42 daemon info syslog: Lease of 192.168.100.2 obtained, lease time 30
Feb 24 16:34:58 daemon info syslog: Lease of 192.168.100.2 obtained, lease time 30
Feb 24 16:35:27 daemon info syslog: Lease lost, entering init state
Feb 24 16:35:28 daemon info syslog: Lease of 86.5.xxx.xxx obtained, lease time 524728
Feb 24 16:35:34 user info syslog: l3wanFailover: system default wan is set to pppoa0
Feb 24 16:35:38 user info syslog: ddnsd: xxxxxxxxxxxxxx.dyndns.biz (pppoa0) IP has changed from 192.168.100.2 to 88.105.xx.xx
Feb 24 16:35:39 user info syslog: ddnsd: update xxxxxxxxxxxxx.dyndns.biz request successfully
Feb 24 16:35:40 daemon warn kernel: ^[[0;36;44mBroadcom Packet Flow Cache flushing the flows^[[0m
Feb 24 16:35:41 user info syslog: l3wanFailover: system default wan is set to eth0.1
Feb 24 16:35:49 user info syslog: ddnsd: xxxxxxxxxx.dyndns.biz (eth0.1) IP has changed from 88.105.xx.xx to 86.5.xxx.xxx
Feb 24 16:35:49 user info syslog: ddnsd: update xxxxxxxxxxxxx.dyndns.biz request successfully
Thanks
Regards
Peter
Re: Failover not detecting dropped connection
Posted: Tue Feb 24, 2015 5:09 pm
by billion_fan
petersharon wrote:Hi
have tried with static ip
it works it will fail over to ADSL and im now getting internet on all equipment but dyndns does not update my ip
heres a log before i changed it to a static dns server
Here`s the Sys lo
Feb 24 16:20:28 user info syslog: ddnsd: update xxxxxxxxxx.dyndns.biz request successfully
Feb 24 16:20:28 daemon info syslog: Lease of 86.5.xxx.xxx obtained, lease time 525628
Feb 24 16:20:34 daemon warn kernel: ^[[0;36;44mBroadcom Packet Flow Cache flushing the flows^[[0m
Feb 24 16:20:34 user info syslog: l3wanFailover: system default wan is set to eth0.1
Feb 24 16:20:38 user info syslog: ddnsd: xxxxxxxxxx.dyndns.biz (eth0.1) IP has changed from 88.105.xxx.xxx to 86.5.xxx.xxx
Feb 24 16:20:38 user info syslog: ddnsd: update xxxxxxxxxxxxx.dyndns.biz request successfully
Feb 24 16:29:20 daemon warn kernel: wl0: received packet with own address as source address
Feb 24 16:30:50 user info syslog: l3wanFailover: failover to interface pppoa0
Feb 24 16:33:50 daemon crit kernel: eth0 (switch port: 4) Link DOWN.
Feb 24 16:33:54 daemon info syslog: Received SIGTERM
Feb 24 16:33:54 daemon info kernel: device eth0 left promiscuous mode
Feb 24 16:33:54 user info syslog: l3wanFailover: system default wan is set to pppoa0
Feb 24 16:33:57 user info syslog: ddnsd: xxxxxxxx.dyndns.biz (pppoa0) IP has changed from 86.5.xxx.xxx to 88.105.xx.xx
Feb 24 16:33:58 user info syslog: ddnsd: update xxxxxxx.dyndns.biz request successfully
Feb 24 16:34:23 daemon crit kernel: eth0 (switch port: 4) Link UP 1000 mbps full duplex
Feb 24 16:34:23 daemon warn kernel: eth0.1 MAC address set to 60:03:47:09:xx:xx
Feb 24 16:34:23 daemon warn kernel: netdev path : eth0.1 -> eth0
Feb 24 16:34:23 daemon warn kernel: BCMVLAN : eth0 mode was set to RG
Feb 24 16:34:23 daemon info kernel: device eth0 entered promiscuous mode
Feb 24 16:34:23 daemon info syslog: udhcp client (v0.9.6) started
Feb 24 16:34:26 daemon info syslog: Lease of 192.168.100.2 obtained, lease time 30
Feb 24 16:34:28 user info syslog: ddnsd: xxxxxxxxxxxxxxx.dyndns.biz (eth0.1) IP has changed from 88.105.xx.xx to 192.168.100.2
Feb 24 16:34:28 user info syslog: ddnsd: update xxxxxxxxxxxxxxxxxx.dyndns.biz request successfully
Feb 24 16:34:31 daemon warn kernel: ^[[0;36;44mBroadcom Packet Flow Cache flushing the flows^[[0m
Feb 24 16:34:31 user info syslog: l3wanFailover: change default wan to master eth0.1
Feb 24 16:34:42 daemon info syslog: Lease of 192.168.100.2 obtained, lease time 30
Feb 24 16:34:58 daemon info syslog: Lease of 192.168.100.2 obtained, lease time 30
Feb 24 16:35:27 daemon info syslog: Lease lost, entering init state
Feb 24 16:35:28 daemon info syslog: Lease of 86.5.xxx.xxx obtained, lease time 524728
Feb 24 16:35:34 user info syslog: l3wanFailover: system default wan is set to pppoa0
Feb 24 16:35:38 user info syslog: ddnsd: xxxxxxxxxxxxxx.dyndns.biz (pppoa0) IP has changed from 192.168.100.2 to 88.105.xx.xx
Feb 24 16:35:39 user info syslog: ddnsd: update xxxxxxxxxxxxx.dyndns.biz request successfully
Feb 24 16:35:40 daemon warn kernel: ^[[0;36;44mBroadcom Packet Flow Cache flushing the flows^[[0m
Feb 24 16:35:41 user info syslog: l3wanFailover: system default wan is set to eth0.1
Feb 24 16:35:49 user info syslog: ddnsd: xxxxxxxxxx.dyndns.biz (eth0.1) IP has changed from 88.105.xx.xx to 86.5.xxx.xxx
Feb 24 16:35:49 user info syslog: ddnsd: update xxxxxxxxxxxxx.dyndns.biz request successfully
Thanks
Regards
Peter
From the logs it seems you are able to update your DynDNS
Feb 24 16:35:38 user info syslog: ddnsd: xxxxxxxxxxxxxx.dyndns.biz (pppoa0) IP has changed from 192.168.100.2 to 88.105.xx.xx
Feb 24 16:35:39 user info syslog: ddnsd: update xxxxxxxxxxxxx.dyndns.biz request successfully
The above is for your ADSL connection, so it should of updated
Then again it updated within 10 seconds to your Virgin connection
Feb 24 16:35:49 user info syslog: ddnsd: xxxxxxxxxx.dyndns.biz (eth0.1) IP has changed from 88.105.xx.xx to 86.5.xxx.xxx
Feb 24 16:35:49 user info syslog: ddnsd: update xxxxxxxxxxxxx.dyndns.biz request successfully
So what you are saying now is that it updated before but no internet connection, but now you have a internet connection and Dyndns is not updating??
Starnge, have you got a update to date system log?? Maybe try waiting for 5 -10 minutes to see if the IP address is updated on your dyndns account
Re: Failover not detecting dropped connection
Posted: Wed Feb 25, 2015 9:49 am
by petersharon
hi
So what you are saying now is that it updated before but no internet connection, but now you have a internet connection and Dyndns is not updating??
Starnge, have you got a update to date system log?? Maybe try waiting for 5 -10 minutes to see if the IP address is updated on your dyndns account
yes that`s exactly what`s happening
i did wait about 10 minutes for it to update
i have sorted it out by having a different piece of equipment update my dydns
Regards
Peter
Re: Failover not detecting dropped connection
Posted: Wed Feb 25, 2015 1:17 pm
by billion_fan
petersharon wrote:hi
So what you are saying now is that it updated before but no internet connection, but now you have a internet connection and Dyndns is not updating??
Starnge, have you got a update to date system log?? Maybe try waiting for 5 -10 minutes to see if the IP address is updated on your dyndns account
yes that`s exactly what`s happening
i did wait about 10 minutes for it to update
i have sorted it out by having a different piece of equipment update my dydns
Regards
Peter
Very strange I just setup a 'Dynamic DNS' account with 'freedns.afraid.org' and once I failover to ADSL, I checked 'freedns.afraid.org' web site and my IP address has been updated to my ADSL IP, then I attempt to login using remote access with my freedns.afraid.org account and it redirected me to the ADSL connection.
So it seems it's all working here
Have you checked your Dynamic DNS page (within the router) to ensure your PPPOA account is added to the 'Selected WAN Interface'