Project

General

Profile

Actions

Bug #10193

closed

PPPoE wrong default route

Added by Mark Aradi over 5 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
01/20/2020
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

I'm running newest stable pfSense 2.4.4 in KVM virt (pcie passed through NICs, should be identical to physical/baremetal) and I experience a wrong default route interface selection on every cold boot.
Strangely enough, once rebooted from pfSense itself the route gets fixed.

This is the wrong default route:
default 10.0.0.1UGS lagg0

And this is what it should be:
default 10.0.0.1 UGS pppoe0

Thus need to apply this every single time (or reboot from the webui/cli):
route del -net default
route add default 10.0.0.1

It appears that it selects the LAN interface (lagg0) instead of the WAN (pppoe0). I did even set explicitly the default gateway to be the pppoe one.

This issue may or may not be related to this other one: https://redmine.pfsense.org/issues/9192 , as I only experience it on cold boots. It does resolve with another reboot (from cli/webui) and it doesn't come up again if the pppoe is reconnected.

Actions #1

Updated by Jim Pingle over 5 years ago

  • Category set to Interfaces
  • Status changed from New to Rejected
  • Priority changed from Urgent to Normal

Please post on the forum to discuss and diagnose the issue. It is more likely you have a configuration issue here and not a bug, since this doesn't appear to be happening to others. If an actionable bug can be identified, then an issue with more specific details can be opened.

Actions

Also available in: Atom PDF