Project

General

Profile

Actions

Bug #12721

closed

IPv6 gateway group using link local addresses incorrectly logs a gateway change because it not including interface scope properly

Added by Loren McQuade about 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Gateways
Target version:
Start date:
Due date:
% Done:

0%

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

Description

Change `get_gwgroup_memebers()` to include the interface in link-local IPv6 addresses. This way, the `gwip` value will match the return value of `route_get_default()`. The mismatch was causing `fixup_default_gateway()` to spam "Gateway, switch to: XXX" when default IPv6 gateway was set to a Gateway Group.

Actions #2

Updated by Jim Pingle about 2 years ago

  • Target version set to 2.7.0
  • Plus Target Version set to 22.05
Actions #3

Updated by Viktor Gurov about 2 years ago

  • Status changed from Pull Request Review to Feedback
Actions #4

Updated by Jim Pingle almost 2 years ago

  • Subject changed from Change get_gwgroup_members to include interface in link-local IPv6 addresses to IPv6 gateway group using link local addresses incorrectly logs a gateway change because it not including interface scope properly

Updating subject for release notes.

Actions #5

Updated by Jim Pingle almost 2 years ago

  • Assignee set to Loren McQuade
Actions #6

Updated by Loren McQuade almost 2 years ago

I see you have assigned this back to me, but I am unsure of what further action is needed on my part. I can verify after 22.05 ships, but that seems like it could be too late.

Actions #7

Updated by Jim Pingle almost 2 years ago

It lacked an assignee before, mostly it's for tracking who fixed the issue.

Ideally we'd like feedback from someone who could reproduce the problem before to know if it's fixed, but they'd have to be testing it on a 22.05 (or recent 2.7.0) snapshot.

If you could give some guidance about how to reproduce the issue and confirm that it's working properly now, others may be able to test it if you cannot.

Actions #8

Updated by Loren McQuade almost 2 years ago

How to verify that this change is working:

1) Create gateway group "WAN_IPv6" which contains:

Tier 1: WAN1 (my gateway has a link-local fe80:: address)
Tier 2: WAN2

2) Set "Default gateway IPv6" to "WAN_IPv6" group

3) Go to "System Logs/Gateways" and verify not getting spammed with gateway switch messages, even when gateway is not changing:

"Gateway, switch to: XXX"
Actions #9

Updated by Jim Pingle almost 2 years ago

  • Status changed from Feedback to Resolved

Seems to be OK on the latest snapshot. I can't reproduce the problem there. Failover group with two IPv6 tiers, both are fe80 gateways, Group set as default. Gateways show online, group shows online, no log messages about the gateway switching.

Actions

Also available in: Atom PDF