Project

General

Profile

Actions
Copy link

Bug #11692

closed

``fixup_default_gateway()`` should not remove a default gateway managed by a dynamic routing daemon

Added by yon Liu almost 4 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Viktor Gurov
Category:
Gateways
Target version:
2.7.0
Start date:
03/17/2021
Due date:
% Done:

100%

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

Description

so I using frr bgp router,so I need disable and setup Default gateway IPv6 to none, but I config Default gateway IPv6 none, but it pf2.6 system still setup route Default gateway IPv6 to wan.

Files

Download all files
IMG_20210318_084937.jpg (332 KB) IMG_20210318_084937.jpg yon Liu, 03/17/2021 07:51 PM
IMG_20210318_085543.jpg (406 KB) IMG_20210318_085543.jpg yon Liu, 03/17/2021 07:57 PM

Related issues

Related to Bug #12536: Setting a default gateway of "None" does not remove the default gateway from the routing tableResolvedViktor Gurov

Actions
Related to Bug #14717: A default route can remain after setting the default gateway to NoneResolvedMarcos M

Actions
Actions
Copy link
 #3

Updated by Jim Pingle almost 4 years ago

  • Project changed from pfSense Packages to pfSense
  • Subject changed from Default gateway IPv6 to PPPoE IPv6 gateway set as default even when IPv6 default gateway is set to "
  • Category changed from System Patches to Gateways
  • Release Notes set to Default
Actions
Copy link
 #4

Updated by Jim Pingle almost 4 years ago

  • Subject changed from PPPoE IPv6 gateway set as default even when IPv6 default gateway is set to " to PPPoE IPv6 gateway set as default even when IPv6 default gateway is set to "None"
  • Target version set to 2.6.0

Updating subject for release notes.

Actions
Copy link
 #5

Updated by Jim Pingle about 3 years ago

  • Target version changed from 2.6.0 to CE-Next
  • Plus Target Version set to Plus-Next
Actions
Copy link
 #6

Updated by Viktor Gurov about 3 years ago

  • Related to Bug #12536: Setting a default gateway of "None" does not remove the default gateway from the routing table added
Actions
Copy link
 #8

Updated by Jim Pingle about 3 years ago

  • Assignee set to Viktor Gurov
Actions
Copy link
 #9

Updated by Viktor Gurov about 3 years ago

  • Status changed from New to Pull Request Review
Actions
Copy link
 #10

Updated by Viktor Gurov almost 3 years ago

  • Status changed from Pull Request Review to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #11

Updated by Jim Pingle almost 3 years ago

  • Target version changed from CE-Next to 2.7.0
  • Plus Target Version changed from Plus-Next to 22.05
Actions
Copy link
 #12

Updated by Jim Pingle over 2 years ago

  • Subject changed from PPPoE IPv6 gateway set as default even when IPv6 default gateway is set to "None" to IPv6 gateway obtained from a PPPoE interface ignores configuration and is always set as default

Updating subject for release notes.

Actions
Copy link
 #13

Updated by Jim Pingle over 2 years ago

  • Subject changed from IPv6 gateway obtained from a PPPoE interface ignores configuration and is always set as default to @fixup_default_gateway()@ should not remove a default gateway managed by a dynamic routing daemon
  • Status changed from Feedback to Resolved
Actions
Copy link
 #14

Updated by Jim Pingle over 2 years ago

  • Subject changed from @fixup_default_gateway()@ should not remove a default gateway managed by a dynamic routing daemon to ``fixup_default_gateway()`` should not remove a default gateway managed by a dynamic routing daemon
Actions
Copy link
 #15

Updated by Marcos M over 1 year ago

  • Related to Bug #14717: A default route can remain after setting the default gateway to None added
Actions
Copy link

Also available in: Atom PDF