Project

General

Profile

Actions
Copy link

Bug #8561

closed
PB PB

default-route is not always set for a pppoe connection after bootup.

Bug #8561: default-route is not always set for a pppoe connection after bootup.

Added by Pi Ba over 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
High
Assignee:
Pi Ba
Category:
Routing
Target version:
2.4.4
Start date:
06/09/2018
Due date:
% Done:

0%

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

Description

It seems the dynamic pppoe gateway does not have a status yet when it hasn’t connected before… And the code assumes its a gatewaygroup as it cannot find the status a normal gateway normally does have

Issue description:
https://forum.netgate.com/topic/131149/no-internet-connection-after-upgrade-from-april-20-snapshot-to-may-19

Fix:
https://github.com/pfsense/pfsense/pull/3947

JP Updated by Jim Pingle about 8 years ago Actions
Copy link
 #1

  • Status changed from New to Feedback

PR has been merged

PB Updated by Pi Ba about 8 years ago Actions
Copy link
 #2

Sorry, forgot the '!', new PR added: https://github.com/pfsense/pfsense/pull/3956

JP Updated by Jim Pingle about 8 years ago Actions
Copy link
 #3

  • Status changed from Feedback to New
  • Assignee set to Pi Ba
  • % Done changed from 100 to 0

JP Updated by Jim Pingle about 8 years ago Actions
Copy link
 #4

  • Status changed from New to Feedback

PR merged

PB Updated by Pi Ba about 8 years ago Actions
Copy link
 #5

Fix confirmed, issue can be closed.

https://forum.netgate.com/post/775465
@w0w said in [No internet connection after upgrade from April 20 snapshot to May 19](/post/775465):

As expected, latest snapshot containing this PR boots normally.

RB Updated by Renato Botelho about 8 years ago Actions
Copy link
 #6

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom