Bug #3634
closedDefault gateway not restored after it comes back online
0%
Description
I have a multi-wan setup with two gateways.
Recently, the primary cable company's connection (the primary gateway) has been spotty. pfSense detects packet loss, disables the primary gateway and all traffic starts flowing through the second gateway. So far so good.
When the connection is restored, pfSense detects it, and shows the primary as being online. However, all traffic keeps flowing through the secondary gateway instead of going back to the primary. A reboot of the firewall is required to fix this.
Steps I've taken:1. Clearing all states through Diagnostics->State: doesn't help.
2. Checking Status->Gateways shows both gateways in green (good). The "Gateway Groups" tab also shows green/online and the gateways in proper order (good).
3. Checking /tmp/rules.debug shows this:
- Gateways
GWWAN_ADSL = " route-to ( pppoe0 206.248.154.122 ) "
GWWAN = " route-to ( rl0 99.238.186.1 ) "
GWWAN_Group_Cable_First = " route-to { ( pppoe0 206.248.154.122 ) } "
GWWAN_Group_ADSL_First = " route-to { ( pppoe0 206.248.154.122 ) } "
The group GWWAN_Group_Cable_First is incorrect as it should read rl0 99.238.186.1.
This feels like it's related to bug #3308.
If there is no immediate fix planned, can you tell me if there is a way to force this rule to regenerate without rebooting?
My pfSense: 2.1.2-RELEASE (i386) built on Thu Apr 10 05:23:34 EDT 2014 FreeBSD 8.3-RELEASE-p15
Updated by Oz Solomon almost 11 years ago
Hey guys, are there any plans to fix this for 2.2? Thanks!
Updated by Chris Buechler almost 11 years ago
- Status changed from New to Rejected