Two default routes are getting installed
-
I'm seeing some confusing behavior.
We have an installation where the WAN interface faces Starlink, and an OPT interface labeled ATT faces AT&T. AT&T is the primary provider, Starlink the backup. Standard routing group configuration.
No matter what we tweak, it seems both default routes are getting installed in the routing table and both connections are being utilized.
Even if I remove WAN from the routing group entirely, the default route over the WAN interface still appears.
The only thing I can hypothesize is that because the default route on the WAN is coming via DHCP, it's still getting injected even though it's unrelated to the gateway group.
We've been doing WAN failover on Pfsense for a really long time...never seen this before. The only thing that's different here than normal is that WAN is the backup, and WAN is DHCP. We've had backup DHCP providers on other interfaces, but never on the WAN port.
This is on 2.7.0, and it's slated to get upgraded, but I don't see anything in the change log or bug reports regarding this behavior.
We're thinking we will rewire and reconfigure the interfaces to determine if that's the cause, but regardless I thought I would post here and see if anybody else has seen this behavior or has any suggestions on things to look at.
-
@andydills said in Two default routes are getting installed:
This is on 2.7.0, ....
@andydills said in Two default routes are getting installed:
We're thinking
Stop thinking, the solution has arrived.
'Years ago'.
Upgrade first. Go to 2.7.2 - and even consider continuing upgrading to "Beta 2.8.0" as is very close to release.Then : reset your questions.
Bye bye old issues.
( Welcome to the new issues - not that I, afaik, 'm aware of any =
