Project

General

Profile

Actions
Copy link

Bug #12536

closed

Setting a default gateway of "None" does not remove the default gateway from the routing table

Added by Alhusein Zawi about 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Viktor Gurov
Category:
Routing
Target version:
2.7.0
Start date:
Due date:
% Done:

100%

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

Description

selecting Default gateway as NONE should remove the default route from routing table.

making default GW as "NONE" will not remove the default route.
Mark Gateway as "Down" does not remove the default route.

disabling the interface or using the command route delete 0.0.0.0/0 [gateway ip] are the only way to remove it.

selecting Default gateway as NONE (GUI) should take an effect to remove the default route from the routing table.

Related issues

Related to Bug #11692: ``fixup_default_gateway()`` should not remove a default gateway managed by a dynamic routing daemonResolvedViktor Gurov03/17/2021

Actions
Actions
Copy link
 #1

Updated by Viktor Gurov about 3 years ago

  • Related to Bug #11692: ``fixup_default_gateway()`` should not remove a default gateway managed by a dynamic routing daemon added
Actions
Copy link
 #2

Updated by Viktor Gurov about 3 years ago

removing the default gateway, if set to 'none', may result in the removal of the route of dynamic routing protocols
https://github.com/pfsense/pfsense/blob/master/src/etc/inc/gwlb.inc#L1115-L1117:

    if ($gwdefault == "-") {
        // 'none', dont set the default gateway, useful if routes are managed by frr/bgp/ospf or similar
        return;
    }

Actions
Copy link
 #4

Updated by Jim Pingle about 3 years ago

  • Status changed from New to Pull Request Review
  • Assignee set to Viktor Gurov
  • Target version set to CE-Next
  • Plus Target Version set to Plus-Next
Actions
Copy link
 #5

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
 #6

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
 #7

Updated by Alhusein Zawi almost 3 years ago

making default GW as "NONE" removes the default GW routing table.

But Mark Gateway as Down does not remove the default route.(Status>Gateways shows offline GW)

2.7.0.a.20220226.0600

Actions
Copy link
 #8

Updated by Viktor Gurov almost 3 years ago

  • Status changed from Feedback to New

Alhusein Zawi wrote in #note-7:

making default GW as "NONE" removes the default GW routing table.

But Mark Gateway as Down does not remove the default route.(Status>Gateways shows offline GW)

2.7.0.a.20220226.0600

fix:
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/642

Actions
Copy link
 #9

Updated by Jim Pingle almost 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
Actions
Copy link
 #11

Updated by Alhusein Zawi almost 3 years ago

  • Status changed from Feedback to Resolved

fixed

Mark Gateway as Down/Disable this gateway removes the default GW from the routing table.

22.05.a.20220311.0600

Actions
Copy link
 #12

Updated by Jim Pingle almost 3 years ago

  • Subject changed from Default gateway as "NONE" to Setting a default gateway of "None" does not remove the default gateway from the routing table

Updating subject for release notes.

Actions
Copy link

Also available in: Atom PDF