Wierd route at incusos system network

IncusOS
1

Hello all,

I’m somewhat lost here. For a few days now I have a problem with my dns. It is a docker container on my incusos host. It did run fine and probably still does. However I can’t access the machine. Ping times out and I can’t reach the web console (it’s technitium dns server). So when I checked the network config of incusos I did find a puzzling route:

incus admin os system network show

WARNING: The IncusOS API and configuration is subject to change

config:
  interfaces:
  - addresses:
    - dhcp4
    - slaac
    hwaddr: d8:5e:d3:8c:cb:42
    name: eno1
    required_for_online: “no”
  time:
    timezone: [...]
state:
  interfaces:
    eno1:
      addresses:
      - 192.168.x.x
      - fd85::x
      hwaddr: d8:5e:d3:8c:cb:42
      mtu: 1500
    roles:
    - management
    - cluster
    routes:
    - to: default
      via: 192.168.x.x
    - to: 10.98.238.22  <-- (?)
      via: 192.168.x.x
    speed: “1000”
    state: routable
    stats:
    [...]
    type: interface

The second route seems wrong. The ip is the ip of the dns server and I can’t figure out how that route got installed. It is completely superfluous

I can’t remove it by editing the networking config. It simply ignores the edit and puts the route back in. Maybe I’m missing something obvious but could someone point me in the right direction please?

2

Given the interface is configured for DHCP, that route was almost certainly advertised by your DHCP. I’ve seen similar behavior on some networks before.

3

Thank you Stéphane. That was my most probable cause as well. Although I couldn’t find a route in the er605 (TP-Link) . It probably is automatically generated since the server is on another subnet. Probably a device that thinks to be more clever than me (or probably is, I don’t know) :slight_smile:

I’m a bit cautious with messing with the network settings in incusos. Can I just remove the dhcp from the settings above and have a static ipv4? I’d need to add a dns section then too I guess?

4

Yeah, you’d need to replace dhcp4 with your IP address and mask, then add a routes section with a default route and then a dns section for the DNS.

Basically something kinda like that:

interfaces:
- hwaddr: XYZ
  name: some-name
  addresses:
  - 192.168.0.100/24
  routes:
  - to: 0.0.0.0/0
    via: 192.168.0.1
dns:
  nameservers:
  - 1.0.0.1
  - 1.1.1.1
5

Thank you again. Of course I did scramble my settings before you answered but was able to connect via ipv6 to revert my ipv4 changes. Now it works with a static address.