Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Zero-address route incorrectly set for IPv6 #9624

Closed
trevex opened this issue Nov 3, 2024 · 0 comments · Fixed by #9627
Closed

Zero-address route incorrectly set for IPv6 #9624

trevex opened this issue Nov 3, 2024 · 0 comments · Fixed by #9627
Assignees
@smira

Comments

@trevex
Copy link

trevex commented Nov 3, 2024

Bug Report

Description

When adding a static route to the interface eth0 for ::/0, talosctl get routes unexpectedly reports an IPv4 route

The configuration added looks as follows:

machine:
    network:
        interfaces:
            - interface: eth0
              routes:
                - network: ::/0
                  gateway: ""
                  metric: 1000

talosctl get routes for the specified route returns:

fd01:cafe::5054:ff:fe10:9ad   network     RouteStatus   inet4///1000                                                            1                                                                                   eth0         1000

Logs

Environment

  • Talos version: v1.8.2
  • Kubernetes version: v1.30.5
  • Platform: Omni/KubeVirt
@smira smira self-assigned this Nov 4, 2024
smira added a commit to smira/talos that referenced this issue Nov 4, 2024
@smira
fix: make route normalization keep family
341ed88 
When we normalize the route with e.g. IPv6 all addresses (`::/0`), we
were wiping the family information. Keep the information, and also fix
the scope for such routes.

Fixes siderolabs#9624

Signed-off-by: Andrey Smirnov <[email protected]>
@smira smira mentioned this issue Nov 4, 2024
Merged
smira added a commit to smira/talos that referenced this issue Nov 4, 2024
@smira
fix: make route normalization keep family
e1d7e13 
When we normalize the route with e.g. IPv6 all addresses (`::/0`), we
were wiping the family information. Keep the information, and also fix
the scope for such routes.

Fixes siderolabs#9624

Signed-off-by: Andrey Smirnov <[email protected]>
smira added a commit to smira/talos that referenced this issue Nov 13, 2024
@smira
fix: make route normalization keep family
83abb66 
When we normalize the route with e.g. IPv6 all addresses (`::/0`), we
were wiping the family information. Keep the information, and also fix
the scope for such routes.

Fixes siderolabs#9624

Signed-off-by: Andrey Smirnov <[email protected]>
(cherry picked from commit 74b0e8c)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@smira smira

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: make route normalization keep family smira/talos
2 participants
@smira @trevex