Im getting a second gateway out of nowhere...?

[demira89]

Hi y'all,

I'm currently trying to get a NodePort going on one external facing node, however the system always uses the internal network and I'm also unable to ping the node using the public network.

The relevant part in the machineconf:

    network: 
        interfaces:
            - interface: enp1s0f0
              addresses:
                - PU.BL.IC.IP/29
              routes:
                - network: 0.0.0.0/0
                  gateway: PU.BL.GA.WY
                  metric: 0
            - interface: enp1s0f1
              addresses:
                - 10.132.7.53/20

Previously I only had one network connection to the node and had it configured with the local gateway 10.132.0.35.
Since adding the public connection, i removed the gateway and route, but the changed machineconf persists across reboots and there is no way of getting the old gateway out of it.

Thanks for any insights, I don't fancy reinstalling the node since that would require physical access for the initial network config.
BTW the search for related issues brought up the MetaKey resources, which contain the old manual configuration from installation time. Are they somehow merged into one effective configuration?

[smira]

It's impossible to guess where things are coming from without any details, but you can figure it out yourself.

See networking resources, specifically for routes you'd want something like talosctl get routespecs --namespace=network-config.

If your problem is the network configuration you put using the dashboard in the console, then see this.

[demira89]

Thanks, the idea with the meta command was right. I simply had to talosctl meta delete 0x0a to purge the old network configuration that was superseded by the new machine config. It might be a good idea in newer realeases to automatically do this after installation or move that into the machine config? Or put a warning somewhere, that the hand config from the installation remains seen.

[zombiemaker]

@smira : Thanks for posting about the Console Dashboard. This solved my problem!