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.

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

Default gateway route misassignment to VLAN instead of physical interface #8709

Open
kvaps opened this issue May 6, 2024 · 1 comment
Open

Comments

@kvaps
Copy link
Contributor

kvaps commented May 6, 2024

Bug Report

Description

I came across another interesting bug, or rather a peculiarity. A configuration of this type does not work:

interfaces:
  - deviceSelector:
      hardwareAddr: 9c:6b:00:47:06:6c
    addresses:
      - 11.22.33.206/26
    routes:
      - network: 0.0.0.0/0
        gateway: 11.22.33.193
    vlans:
      - addresses:
          - 192.168.100.12/24
        vlanId: 4006
        vip:
          ip: 192.168.100.10

This is because the deviceSelector matches all interfaces by MAC address, and the default gateway route is assigned to the VLAN interface, not the physical one:

NODE             NAMESPACE   TYPE          ID                         VERSION   DESTINATION GATEWAY        LINK              METRIC
192.168.100.12   network     RouteStatus   inet4/11.22.33.193//1024   1                     11.22.33.193   enp1d74731.4006   1024

The solution: explicitly specify the driver option for deviceSelector.

Logs

Environment

  • Talos version: v1.7.1
  • Kubernetes version: 1.30
  • Platform: metal
@frezbo
Copy link
Member

frezbo commented May 6, 2024

you could also use physical: true

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants