Page 1 of 2

Failover not detecting dropped connection

Posted: Sun Jan 18, 2015 5:09 pm
by golightlygl
My primary connection is cable connected through a WAN port. My secondary connection is the DSL.

If I reboot or physically detach the cable modem, then the Billion correctly detects no signal and switches to the DSL. However, if the cable modem just loses connectivity to the Internet the Billion does not detect that and keeps it connected as a primnary connected interface.

So my question is should the Billion be checking for internet connectivity rather than "connected device" and if so, how do I make it do this?

Re: Failover not detecting dropped connection

Posted: Wed Jan 21, 2015 9:39 am
by billion_fan
golightlygl wrote:My primary connection is cable connected through a WAN port. My secondary connection is the DSL.

If I reboot or physically detach the cable modem, then the Billion correctly detects no signal and switches to the DSL. However, if the cable modem just loses connectivity to the Internet the Billion does not detect that and keeps it connected as a primnary connected interface.

So my question is should the Billion be checking for internet connectivity rather than "connected device" and if so, how do I make it do this?
What model do you have?? eg 7800DXL,7800DX??

Re: Failover not detecting dropped connection

Posted: Mon Feb 16, 2015 8:17 am
by golightlygl
Hello,

I'm sorry not to have responded: this forum doesn't seem to notify me of replies. I had since raised a ticket with support who confirmed that the firmware is faulty and will not failover from WAN to DSL. They have since issued a patch for me to try (they ahve tested it successfully) but I am travelling and have been unable to test it. Just keeping you informed.

Re: Failover not detecting dropped connection

Posted: Mon Feb 16, 2015 9:40 am
by billion_fan
golightlygl wrote:Hello,

I'm sorry not to have responded: this forum doesn't seem to notify me of replies. I had since raised a ticket with support who confirmed that the firmware is faulty and will not failover from WAN to DSL. They have since issued a patch for me to try (they ahve tested it successfully) but I am travelling and have been unable to test it. Just keeping you informed.
Keep us posted, it should be fine with the new firmware :D

Re: Failover not detecting dropped connection

Posted: Thu Feb 19, 2015 1:46 am
by petersharon
Good evening
I have same set up and im having exactly the same problem on a 7800DXL failover not detecting dropped connection
i have checked your site and i do have the latest software you have available on Billion download site
thanks you
good night

Re: Failover not detecting dropped connection

Posted: Thu Feb 19, 2015 12:24 pm
by billion_fan
petersharon wrote:Good evening
I have same set up and im having exactly the same problem on a 7800DXL failover not detecting dropped connection
i have checked your site and i do have the latest software you have available on Billion download site
thanks you
good night
Which failover WAN's are you trying?? eg EWAN PPPOE >> ADSL, or ADSL >>> 3G/4G or EWAN IPOE >> 3G/4G/ADSL etc??

Re: Failover not detecting dropped connection

Posted: Thu Feb 19, 2015 6:58 pm
by petersharon
Hi
EWAN PPPOE as main and ADSL as failover
i do not use 3G as you cannot port forward cause they use a private IP

Regards

Peter

Re: Failover not detecting dropped connection

Posted: Fri Feb 20, 2015 9:22 am
by billion_fan
petersharon wrote:Hi
EWAN PPPOE as main and ADSL as failover
i do not use 3G as you cannot port forward cause they use a private IP

Regards

Peter
Please load our latest firmware attached, once done reset back to factory default settings.

Once done setup both WAN's as shown on the attached screen shot.

Then under 'Advanced Setup >> Routing' select your failover/fallback interfaces starting from the top as the Master connection and listed below will be failover WANs in order as shown on the attached screen shot.

When using PPPOE EWAN as master and ADSL as secondary, once the EWAN connection has failed the maximum downtime will 5 minutes, while the router fails over the ADSL. (we are looking to tweak the timing and should have a new firmware release soon)

Re: Failover not detecting dropped connection

Posted: Sun Feb 22, 2015 3:11 am
by petersharon
Hi
followed your exact steps and upgraded to the software on the above post after confirming my ADSL and Ewan was connected and working
i tested the fail over by disconnecting my cable from the Virgin router
i then checked the status of my WAN and it reported ADSL connected and EWAN connected showing ip and all just like before i disconnected the cable from my Virgin router waited about ten minutes with the cable disconnected internet was down and it never failed over to ADSL instead it kept my EWAN ip adress on WAN status as if internet on EWAN was connected all the time
I have to revert to my old router not a happy bunny right now

Regards

Peter

Re: Failover not detecting dropped connection

Posted: Mon Feb 23, 2015 10:11 am
by billion_fan
petersharon wrote:Hi
followed your exact steps and upgraded to the software on the above post after confirming my ADSL and Ewan was connected and working
i tested the fail over by disconnecting my cable from the Virgin router
i then checked the status of my WAN and it reported ADSL connected and EWAN connected showing ip and all just like before i disconnected the cable from my Virgin router waited about ten minutes with the cable disconnected internet was down and it never failed over to ADSL instead it kept my EWAN ip adress on WAN status as if internet on EWAN was connected all the time
I have to revert to my old router not a happy bunny right now

Regards

Peter
You were using IPOE EWAN (Virgin Super Hub connection) then not PPPOE EWAN (BT, Plusnet etc), I have a new firmware now with improved failover detection.

Please upgrade your device and follow the attached screen shots, you will need to make sure both WAN connections are up and running, and static DNS servers set.

You will need to reset back to factory defaults to ensure the failover function changes are implemented correctly, do not restore settings from previous firmware builds.

Once you disconnect your coaxial connection from your super hub, refresh the 'Status' page a couple of times, you should notice that the WAN IP will change, once changed check whatsmyip.org. (failover)

Then plug your coaxial connection back to the virgin modem, wait for the kit to connect, and shortly after your IP address should change (fallback)