Host can't access internet with bogus routing but VMs can

[Noa Himesaka]

I have been running Proxmox for a while but now the host gets wrong routing and can't access the internet. The VMs can access the internet fine though.
`ip route`:
```
0.0.0.0 via 192.168.0.1 dev vmbr0
0.0.0.0 dev fwpr101p0 scope link
0.0.0.0 dev tap100i0 scope link
0.0.0.0 dev fwln100i0 scope link
0.0.0.0 dev fwpr100p0 scope link
0.0.0.0 dev eno2 scope link
default dev fwln101i0 scope link
default dev tap101i0 scope link
default dev fwpr101p0 scope link
default via 192.168.0.1 dev vmbr0 src 192.168.0.6
default dev eno2 scope link
default via 192.168.0.1 dev vmbr0 proto kernel onlink
169.254.0.0/16 dev fwpr100p0 proto kernel scope link src 169.254.26.18
169.254.0.0/16 dev fwln100i0 proto kernel scope link src 169.254.25.104
169.254.0.0/16 dev tap100i0 proto kernel scope link src 169.254.149.134
169.254.0.0/16 dev fwpr101p0 proto kernel scope link src 169.254.43.41
169.254.0.0/16 dev tap101i0 proto kernel scope link src 169.254.158.192
169.254.0.0/16 dev fwln101i0 proto kernel scope link src 169.254.68.113
192.168.0.0/24 dev vmbr0 proto kernel scope link src 192.168.0.6
```

`cat /etc/network/interfaces`:
```
auto lo
iface lo inet loopback

iface eno2 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.0.6/24
gateway 192.168.0.1
bridge-ports eno2
bridge-stp off
bridge-fd 0

iface eno1 inet manual


source /etc/network/interfaces.d/*
```

`ip route get 1.1.1.1`:
```
1.1.1.1 dev fwln101i0 src 169.254.68.113 uid 0
cache
```

The internet gets routed to bogus interface instead of vmbr0 which is the correct interface to be routed to.

 

[shanreich]

It seems like your interfaces are getting IPv4LL addresses for some reason, which messes up the routing table. Have you installed anything that configures this, as this does not happen by defauly (e.g. avahi zeroconfg)

 

[Noa Himesaka]

It seems like your interfaces are getting IPv4LL addresses for some reason, which messes up the routing table. Have you installed anything that configures this, as this does not happen by defauly (e.g. avahi zeroconfg)

The result was yes, it got installed for some reason (likely when I was trying to install other packages) so I just removed it. What should I do now to make routing table get fixed?

 

[shanreich]

The easiest way would probably be to just reboot your machine, then everything should work as expected. Otherwise, you will need to manually remove IPs from all interfaces via ip addr del. Possibly, you will also have to remove the leftover routes.