Project

General

Profile

Actions

Bug #6110

closed

Default gateway switching not always working with PPP

Added by Greg M about 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Gateways
Target version:
-
Start date:
04/11/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
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.

Actions #1

Updated by Chris Buechler about 6 years ago

  • 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
Actions #2

Updated by robi robi about 6 years ago

+1 for this !!!!

Actions #3

Updated by Jim Thompson about 6 years ago

  • Assignee set to Chris Buechler
Actions #4

Updated by Chris Buechler about 6 years ago

  • Target version changed from 2.3.1 to 2.3.2
Actions #5

Updated by Greg M about 6 years ago

Hi!
Has this been fixed with latest snap?
I can`t repro it anymore and it works correctly now.

Actions #6

Updated by Chris Buechler about 6 years ago

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.

Actions #7

Updated by Greg M about 6 years ago

Yeah it`s for ipv4.
I don`t get it what changed. We can close it?

Actions #8

Updated by Chris Buechler about 6 years ago

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.

Actions #10

Updated by Chris Buechler almost 6 years ago

  • 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.

Actions #11

Updated by Greg M almost 6 years ago

Hi!

Nope, all fine here.
Tested multiple times...

Actions #12

Updated by Chris Buechler almost 6 years ago

  • 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.

Actions

Also available in: Atom PDF