Project

General

Profile

Bug #1508

Wan Fai lback

Added by Phil Parris about 8 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Gateways
Target version:
Start date:
05/05/2011
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.0
Affected Architecture:

Description

When the WAN interface has a static ip and the system fails over the gateway to a tier2 opt1 interface it will not failback to the tier1 interface's gateway when it comes back up.
If the Wan interface has a dhcp ip address it fails back properly.

I have notifications enabled and do not receive any notification when the wan1 interface comes back up if it has a static ip.
Status - Gateway shows the tier1 Wan interface as being up.

Associated revisions

Revision b7d56b64 (diff)
Added by Ermal Luçi about 8 years ago

Fixes #1508. When an interface is configured as static and an up event comes manually trigger rc.newwanip so gateway and other services get restarted properly.

History

#1 Updated by Phil Parris about 8 years ago

Subject should say "Wan Fail Back"

#2 Updated by Phil Parris about 8 years ago

Changing anything in the web interface to do with gateways makes the system failback but this is a manual process.

Also, the Wan interface is set as the default in the web interface before testing.

#3 Updated by Perry Mason about 8 years ago

Could be the same thing I see on my wan2. When I look in /tmp/rules.debug gateways hasn't recovered. In a shell script I reload filters with /usr/local/sbin/pfSctl -c 'filter reload' to correct it.

#4 Updated by Phil Parris about 8 years ago

I see in the logs "Filter Reload" when wan comes back up. I've also ran the PfSctl -c 'filter reload' manually and it will not switch back to tier1.

More detail is that I have wan set as default, priority is 1 and it is tier1.

When I stated that it will fail back with dhcp that was with me pulling the cable. If I leave the link up and down the monitor ip then it will not come back up.

#5 Updated by Phil Parris about 8 years ago

For anyone watching this bug report, i've created a workaround until it gets officially fixed.
create a file /root/failback.php with the following code:
include("/etc/inc/system.inc");
include("/etc/inc/interfaces.inc");
include("/etc/inc/gwlb.inc");
include("/etc/inc/util.inc");
include("/etc/inc/config.inc");
system_routing_configure("wan");
exec("/usr/local/sbin/pfSctl -c 'filter reload'");
?>

then in /etc/inc/gwlb.inc
change the line:
command off "/usr/local/sbin/pfSctl -c 'filter reload'"
to
command off "/usr/local/bin/php /root/failback.php"

#6 Updated by Chris Buechler about 8 years ago

  • Category set to Gateways
  • Target version set to 2.0

#7 Updated by Ermal Luçi about 8 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#8 Updated by Phil Parris almost 8 years ago

Correct me if I'm wrong, but this appears to only resolve the issue of bringing the WAN back up if you physically unplug the cable and plug it back in. This doesn't solve the issue if apinger detects the WAN is down and fails over.

#9 Updated by Ermal Luçi almost 8 years ago

If apinger marks a gateway as down as soon as it is up it will mark it as availble and the pool will switch to it for sure.

I have not seen any report of this not working and if you claim so please provide the system logs on this.
Also a description of how your system is setup.

#10 Updated by Ermal Luçi almost 8 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF