Project

General

Profile

Actions
Copy link

Bug #11599

closed

Modifying static routes results in a logged error, changes are not reflected in routing table

Added by Roland Volkmann almost 4 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Routing
Target version:
2.6.0
Start date:
03/02/2021
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
22.01
Release Notes:
Default
Affected Version:
2.5.0
Affected Architecture:
All

Description

When modifying an existing static route, e.g. changing subnet to be routed, the modified route is added to the current routing table instead of replacing the existing route. To get the correct routing table, you have to reboot pfSense.

Example:
Have an existing static route "Destination = 10.0.0.0/8, Gateway = 10.100.0.1, Flags = UGS, netif = hn0", then modify the Destination to 10.0.0.0/24 by GUI "System/Routing/Static Routes", and you will find two entries in routing table (on GUI "Diagnostics/Routes" or on shell "netstat -rn"): The original one and a new one "Destination = 10.0.0.0/24, Gateway = 10.100.0.1, Flags = UGS, netif = hn0".

Actions
Copy link
 #1

Updated by Viktor Gurov almost 4 years ago

  • Affected Version changed from 2.5.x to 2.5.0

see also #7547
we need to keep a cache of the currently applied static routes to compare against when editing/updating

Actions
Copy link
 #3

Updated by Jim Pingle over 3 years ago

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

Updated by Marcos M about 3 years ago

Tested this on 22.01.a.20211108.0600.
  • Deleting a static route does not prompt for an "Apply Changes" confirmation.
  • Deleting a static route entry does not remove it from the route table.
  • Removing an entry from a network IP alias being used in a static route entry does not remove it from the route table.
  • Changing an entry from a network IP alias being used in a static route entry adds the new route but does not delete the old one.

Related issues:
#11599 #11895 #7547

Actions
Copy link
 #5

Updated by Viktor Gurov about 3 years ago

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

Updated by Alhusein Zawi about 3 years ago

I added a static route 192.168.254.0/24 ,the route is added to routing table.

after modifying it to be 192.0.0.0/8 the new route is added to routing table and old one has not been removed .

192.0.0.0/8 10.100.100.1 UGS 0 1500 em1
192.168.254.0/24 10.100.100.1 UGS 0 1500 em1

22.01.a.20211130.0600

Actions
Copy link
 #7

Updated by Viktor Gurov about 3 years ago

Alhusein Zawi wrote in #note-6:

I added a static route 192.168.254.0/24 ,the route is added to routing table.

after modifying it to be 192.0.0.0/8 the new route is added to routing table and old one has not been removed .

192.0.0.0/8 10.100.100.1 UGS 0 1500 em1
192.168.254.0/24 10.100.100.1 UGS 0 1500 em1

22.01.a.20211130.0600

This fix is still not merged to 22.01

Actions
Copy link
 #8

Updated by Jim Pingle about 3 years ago

  • Subject changed from Error on updating routing table after modifying static routes to Modifying static routes results in a logged error, changes are not reflected in routing table
  • Target version changed from CE-Next to 2.6.0
  • Plus Target Version changed from Plus-Next to 22.01

Updating subject for release notes and fixing targets.

Actions
Copy link
 #9

Updated by Jim Pingle almost 3 years ago

  • Status changed from Feedback to Resolved

Working as expected on current 22.01 RC and 2.6.0 RC snapshots.

Actions
Copy link

Also available in: Atom PDF