Bug #6110
closed
Default gateway switching not always working with PPP
Added by Greg M over 8 years ago.
Updated over 8 years ago.
Affected Architecture:
All
Description
As per this post: https://forum.pfsense.org/index.php?topic=109285.0
System with 2 WAN connections, one DHCP and other PPPoE and default GW set to DHCP GW, does not always set it back after connection is lost.
When DHCP goes down it correctly switches to PPPoE GW but then 2-3 times outh of 5 it does not set it back to DHCP GW when it becomes available.
- Subject changed from Default gateway not always set correctly to Default gateway switching not always working with PPP
- Category set to Gateways
- Affected Version changed from 2.3 to All
- Assignee set to Chris Buechler
- Target version changed from 2.3.1 to 2.3.2
Hi!
Has this been fixed with latest snap?
I can`t repro it anymore and it works correctly now.
Greg M wrote:
Hi!
Has this been fixed with latest snap?
I can`t repro it anymore and it works correctly now.
I don't recall anything specifically for this, or directly related. If IPv6, what I fixed a bit ago in #6353 and #6258 will fix (but those scenarios would have never worked at all). I presume you were referring to IPv4 though. I haven't been able to replicate any issues with v4 in that scenario.
Yeah it`s for ipv4.
I don`t get it what changed. We can close it?
It could be fixed as a consequence of one of the other fixes in 2.3.1. It didn't seem like it was reliably replicable to start with, so maybe just not happening at the moment.
I'll leave it here for the moment, if you can provide an update in a couple weeks that you're no longer seeing the issue, then I'll close it.
- Status changed from New to Feedback
- Assignee deleted (
Chris Buechler)
- Target version deleted (
2.3.2)
Greg M: does this still happen for you?
James M: you're referring to something entirely unrelated.
Hi!
Nope, all fine here.
Tested multiple times...
- Status changed from Feedback to Resolved
Thanks Greg. Going to consider this fixed then, one of the other gateway-related tickets target 2.3.1 must have resolved.
Also available in: Atom
PDF