Project

General

Profile

Actions
Copy link

Bug #7547

closed
CM

Static routes using aliases are not automatically updated when alias content changes

Bug #7547: Static routes using aliases are not automatically updated when alias content changes

Added by Chris Macmahon over 9 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Routing
Target version:
2.6.0
Start date:
05/12/2017
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
22.01
Release Notes:
Affected Version:
2.4.5-p1
Affected Architecture:

Description

When adding a new static route into an Alias group the route does not populate until a resave.
Steps to reproduce:
Create alias with static routes in it
Set static route with a static gateway
Add new route into the alias, check diagnostics routes, is enters as a /32, not as a full route.
Click static routes and resave
Route populates.

Related issues 2 (0 open — 2 closed)

Related to Bug #9743: Missing dependency check(s) on aliases in static routesDuplicate09/11/2019

Actions
Has duplicate Bug #11672: when setup Static Routes use aliases,cannot automatically learn that the aliases ip list has changedDuplicate03/13/2021

Actions

DK Updated by Dave Kobel about 8 years ago Actions
Copy link
 #1

Also, when you delete a subnet from the alias editing and saving the static alias route doesn't remove the route.
You either have to add the route manually, save and then go back and delete it, or reboot.
If the route is in a CARP, it's a bit better in that you can reboot the slave. At this point the slave shows the route deleted. The master still shows the route. On the master, enter maintenance in CARP and then reboot the master. When it comes back up you can remove the maintenance on the CARP.
Both issues has been this way since 2.0.3 (earliest I have run). Currently on 2.4.3p1

JP Updated by Jim Pingle almost 6 years ago Actions
Copy link
 #2

See also: #9743, #11038

KP Updated by Kris Phillips almost 6 years ago Actions
Copy link
 #3

I can confirm this issue is present in 2.4.5p1. The alias needs to be edited and resaved for the changes to take effect in routing.

VG Updated by Viktor Gurov almost 6 years ago Actions
Copy link
 #4

  • Affected Version set to 2.4.5-p1

JP Updated by Jim Pingle over 5 years ago Actions
Copy link
 #5

  • Has duplicate Bug #11672: when setup Static Routes use aliases,cannot automatically learn that the aliases ip list has changed added

JP Updated by Jim Pingle over 5 years ago Actions
Copy link
 #6

  • Related to Bug #9743: Missing dependency check(s) on aliases in static routes added

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

  • Status changed from New to Pull Request Review
  • Target version set to CE-Next
  • Plus Target Version set to Plus-Next

MM Updated by Marcos M almost 5 years ago Actions
Copy link
 #9

See notes on #11599.

VG Updated by Viktor Gurov almost 5 years ago Actions
Copy link
 #10

  • Status changed from Pull Request Review to Feedback
  • % Done changed from 0 to 100

Applied in changeset commit:332052b8bd2a5d35662be2dba773b7a9f0d50681.

DZ Updated by Danilo Zrenjanin almost 5 years ago Actions
Copy link
 #11

  • Status changed from Feedback to Resolved

Tested against:

2.6.0-DEVELOPMENT (amd64)
built on Tue Nov 30 06:19:18 UTC 2021
FreeBSD 12.3-PRERELEASE

It works as expected. Ticket resolved.

JP Updated by Jim Pingle almost 5 years ago Actions
Copy link
 #12

  • Subject changed from Static routing with Aliases to Static routes using aliases are not automatically updated when alias content changes
  • 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

Also available in: Atom