No internet on the pve host

[goelandM]

Good Moring,

My host pve machine, lost internet connection after working for several minutes, but the LXC has internet perfectly. I hope someone can hkep me with it. Here is my interfaces:
auto lo
iface lo inet loopback

iface enp1s0 inet manual

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

source /etc/network/interfaces.d/*

And here is output from my ip a and ip route
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether 40:b0:34:0a:b4:23 brd ff:ff:ff:ff:ff:ff
inet 169.254.96.220/16 brd 169.254.255.255 scope global enp1s0
valid_lft forever preferred_lft forever
inet6 fe80::42b0:34ff:fe0a:b423/64 scope link
valid_lft forever preferred_lft forever
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 7c:b0:c2:4c:55:f4 brd ff:ff:ff:ff:ff:ff
24: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 40:b0:34:0a:b4:23 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.19/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::42b0:34ff:fe0a:b423/64 scope link
valid_lft forever preferred_lft forever

ip route
0.0.0.0 dev enp1s0 scope link
default dev enp1s0 scope link
default via 192.168.0.1 dev vmbr0 proto kernel onlink
169.254.0.0/16 dev enp1s0 proto kernel scope link src 169.254.96.220
192.168.0.0/24 dev vmbr0 proto kernel scope link src 192.168.0.19

I can reset the network by systemctl restart networking, however, it will change back after 1 or 2 minutes.

I really appreciate if anyone can help. Thanks in advance again.

 

[UdoB]

0.0.0.0 dev enp1s0 scope link
default dev enp1s0 scope link
default via 192.168.0.1 dev vmbr0 proto kernel onlink

I am not sure how this was created, but only the last line should be there.

169.254.0.0/16 dev enp1s0 proto kernel scope link src 169.254.96.220

This is additional network that should NOT be there at all. APIPA is an automatism I really hate, though it has some good features. ( https://en.wikipedia.org/wiki/Apipa )

Try to get rid of it! Unfortunately I can not tell which piece of software instantiated it...

Disable the autostart of all containers and reboot. Does "everything" work then? Then start one container after the other...

 

[goelandM]

I am not sure how this was created, but only the last line should be there.


This is additional network that should NOT be there at all. APIPA is an automatism I really hate, though it has some good features. ( https://en.wikipedia.org/wiki/Apipa )

Try to get rid of it! Unfortunately I can not tell which piece of software instantiated it...

Disable the autostart of all containers and reboot. Does "everything" work then? Then start one container after the other...

Thanks. And this is the output without lxc or vm running. And I did delete the route or ip, but the 169.x.x.x will come back just 1 or 2 munitues...