PROXMOX host unable connect to the internet

francly · Dec 16, 2021

Hi, my VM access to the network no issue, however the host have issue access internet, I cannot update the proxmox, on my server only have one NIC.

any idea what is the problem?

Bash:

root@proxmox:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.201/24
        gateway 192.168.1.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

iface wlp6s0 inet static
        address 192.168.1.208/24
        wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
#        wpa-ssid xxxx
#        wpa-psk xxxx
root@proxmox:~# apt-get update
0% [Working]^C
root@proxmox:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 33ms

root@proxmox:~# ip route list
default dev eno1 scope link
default via 192.168.1.1 dev vmbr0 onlink
169.254.0.0/16 dev eno1 proto kernel scope link src 169.254.159.61
169.254.0.0/16 dev tap102i0 proto kernel scope link src 169.254.134.7
169.254.0.0/16 dev tap102i1 proto kernel scope link src 169.254.49.61
169.254.0.0/16 dev tap106i0 proto kernel scope link src 169.254.248.89
169.254.0.0/16 dev tap120i0 proto kernel scope link src 169.254.31.177
169.254.0.0/16 dev tap121i0 proto kernel scope link src 169.254.234.147
192.168.1.0/24 dev vmbr0 proto kernel scope link src 192.168.1.201
root@proxmox:~#
root@proxmox:~# 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
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether c4:34:6b:54:6b:ad brd ff:ff:ff:ff:ff:ff
    inet 169.254.159.61/16 brd 169.254.255.255 scope global eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::c634:6bff:fe54:6bad/64 scope link
       valid_lft forever preferred_lft forever
3: wlp6s0: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 10:4a:7d:d2:23:b9 brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether c4:34:6b:54:6b:ad brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.201/24 brd 192.168.31.255 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fdab:6815:5d57:41f7:c634:6bff:fe54:6bad/64 scope global dynamic mngtmpaddr
       valid_lft 1658sec preferred_lft 1658sec
    inet6 fe80::c634:6bff:fe54:6bad/64 scope link
       valid_lft forever preferred_lft forever
8: tap102i0: <BROADCAST,MULTICAST,PROMISC,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether ca:50:62:af:65:62 brd ff:ff:ff:ff:ff:ff
    inet 169.254.134.7/16 brd 169.254.255.255 scope global tap102i0
       valid_lft forever preferred_lft forever
    inet6 fe80::c850:62ff:feaf:6562/64 scope link
       valid_lft forever preferred_lft forever
9: tap102i1: <BROADCAST,MULTICAST,PROMISC,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether b2:19:fa:52:1b:c0 brd ff:ff:ff:ff:ff:ff
    inet 169.254.49.61/16 brd 169.254.255.255 scope global tap102i1
       valid_lft forever preferred_lft forever
    inet6 fe80::b019:faff:fe52:1bc0/64 scope link
       valid_lft forever preferred_lft forever
10: tap106i0: <BROADCAST,MULTICAST,PROMISC,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether c6:d5:df:b4:de:e2 brd ff:ff:ff:ff:ff:ff
    inet 169.254.248.89/16 brd 169.254.255.255 scope global tap106i0
       valid_lft forever preferred_lft forever
    inet6 fe80::c4d5:dfff:feb4:dee2/64 scope link
       valid_lft forever preferred_lft forever
11: tap120i0: <BROADCAST,MULTICAST,PROMISC,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether 52:f8:7e:63:db:fb brd ff:ff:ff:ff:ff:ff
    inet 169.254.31.177/16 brd 169.254.255.255 scope global tap120i0
       valid_lft forever preferred_lft forever
12: tap121i0: <BROADCAST,MULTICAST,PROMISC,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether be:fb:56:42:d2:ae brd ff:ff:ff:ff:ff:ff
    inet 169.254.234.147/16 brd 169.254.255.255 scope global tap121i0
       valid_lft forever preferred_lft forever
root@proxmox:~#

Dunuin · Dec 16, 2021

You eno1 is using "169.254.159.61" but your vmbr0 attached to it is using "192.168.1.201/24". So you are basically bridging your public and private subnets. And your wifi also got a IP in the same subnet as your vmbr0. A host shouldn't have two IPs in the same subnet.

Why is your NIC using the 169.254.159.61 at all? Thats not defined in your /etc/network/interfaces so I guess you are running some non PVE packages on that host like network-manager that screws up your network config?

You also might want to disable IPv6 in your sysconf if you don't plan to use it. If you got that enabled you got double the work because you need to manage and secure it too.

francly · Dec 20, 2021

Dunuin said:
You eno1 is using "169.254.159.61" but your vmbr0 attached to it is using "192.168.1.201/24". So you are basically bridging your public and private subnets. And your wifi also got a IP in the same subnet as your vmbr0. A host shouldn't have two IPs in the same subnet.

Why is your NIC using the 169.254.159.61 at all? Thats not defined in your /etc/network/interfaces so I guess you are running some non PVE packages on that host like network-manager that screws up your network config?

You also might want to disable IPv6 in your sysconf if you don't plan to use it. If you got that enabled you got double the work because you need to manage and secure it too.

Thanks for the response, let me check and come back.

robb01 · Nov 26, 2022

If I can be forgiven for re-opening this, I have almost the identical problem.

Code:

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
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 94:c6:91:17:f9:72 brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
    inet 169.254.185.138/16 brd 169.254.255.255 scope global eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::96c6:91ff:fe17:f972/64 scope link
       valid_lft forever preferred_lft forever
3: wlp58s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether d4:25:8b:91:06:ef brd ff:ff:ff:ff:ff:ff
6: tap103i0: <BROADCAST,MULTICAST,PROMISC,DYNAMIC> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 1e:b9:0b:e2:af:bd brd ff:ff:ff:ff:ff:ff
12: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 94:c6:91:17:f9:72 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.163/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::96c6:91ff:fe17:f972/64 scope link
       valid_lft forever preferred_lft forever
13: veth102i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:98:4c:14:4f:fa brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet 169.254.54.153/16 brd 169.254.255.255 scope global veth102i0
       valid_lft forever preferred_lft forever
    inet6 fe80::fc98:4cff:fe14:4ffa/64 scope link
       valid_lft forever preferred_lft forever
     
ip route list
default dev eno1 scope link
default via 192.168.1.1 dev vmbr0 proto kernel onlink
169.254.0.0/16 dev eno1 proto kernel scope link src 169.254.185.138
169.254.0.0/16 dev veth102i0 proto kernel scope link src 169.254.54.153
169.254.0.0/16 dev vmbr0 scope link metric 1000
192.168.1.0/24 dev vmbr0 proto kernel scope link src 192.168.1.163

My proxmox was built on top of debian bullseye not from PM image install but there is no network-manager running or installed. Any clues on how to interrogate my system to see why eno1 is using 169.254.185.138/16 ? Maybe some other network package?

Code:

root@proxmox7node01:~# dpkg -l | grep network
ii  avahi-autoipd                          0.8-5+deb11u1                    amd64        Avahi IPv4LL network address configuration daemon
ii  dirmngr                                2.2.27-2+deb11u2                 amd64        GNU privacy guard - network certificate management service
ii  glib-networking:amd64                  2.66.0-2                         amd64        network-related giomodules for GLib
ii  glib-networking-common                 2.66.0-2                         all          network-related giomodules for GLib - data files
ii  glib-networking-services               2.66.0-2                         amd64        network-related giomodules for GLib - D-Bus services
rc  ifupdown                               0.8.36+pve2                      amd64        high level tools to configure network interfaces
ii  iproute2                               5.10.0-4                         amd64        networking and traffic control tools
ii  iputils-ping                           3:20210202-1                     amd64        Tools to test the reachability of network hosts
ii  libnet1:amd64                          1.1.6+dfsg-3.1                   amd64        library for the construction and handling of network packets
ii  libqt5network5:amd64                   5.15.2+dfsg-9                    amd64        Qt 5 network module
ii  net-tools                              1.60+git20181103.0eebece-1       amd64        NET-3 networking toolkit
ii  netbase                                6.3                              all          Basic TCP/IP networking system

Thanks for any help.

Dunuin · Nov 26, 2022

What is cat /etc/network/interfaces returning?

robb01 · Nov 26, 2022

Thanks for your reply. Very standard file.

Code:

cat /etc/network/interfaces

auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.163/24
        gateway 192.168.1.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

robb01 · Nov 26, 2022

This section of the syslog follows a restart of networking.

Code:

Nov 27 07:23:19 proxmox7node01.rb.test systemd[1]: Finished Network initialization.
Nov 27 07:23:21 proxmox7node01.rb.test avahi-daemon[538]: Joining mDNS multicast group on interface vmbr0.IPv6 with address fe80::96c6:91ff:fe17:f972.
Nov 27 07:23:21 proxmox7node01.rb.test avahi-daemon[538]: New relevant interface vmbr0.IPv6 for mDNS.
Nov 27 07:23:21 proxmox7node01.rb.test avahi-daemon[538]: Registering new address record for fe80::96c6:91ff:fe17:f972 on vmbr0.*.
Nov 27 07:23:22 proxmox7node01.rb.test connmand[543]: eno1 {update} flags 102467 <UP,RUNNING,LOWER_UP>
Nov 27 07:23:22 proxmox7node01.rb.test connmand[543]: eno1 {newlink} index 2 address 94:C6:91:17:F9:72 mtu 1500
Nov 27 07:23:22 proxmox7node01.rb.test connmand[543]: eno1 {newlink} index 2 operstate 6 <UP>
Nov 27 07:23:22 proxmox7node01.rb.test kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Nov 27 07:23:22 proxmox7node01.rb.test kernel: vmbr0: port 1(eno1) entered blocking state
Nov 27 07:23:22 proxmox7node01.rb.test kernel: vmbr0: port 1(eno1) entered forwarding state
Nov 27 07:23:22 proxmox7node01.rb.test connmand[543]: eno1 {newlink} index 2 address 94:C6:91:17:F9:72 mtu 1500
Nov 27 07:23:22 proxmox7node01.rb.test connmand[543]: eno1 {newlink} index 2 operstate 6 <UP>
Nov 27 07:23:22 proxmox7node01.rb.test connmand[543]: eno1 {RX} 1316250 packets 321799183 bytes
Nov 27 07:23:22 proxmox7node01.rb.test connmand[543]: eno1 {TX} 970919 packets 192470150 bytes
Nov 27 07:23:22 proxmox7node01.rb.test connmand[543]: eno1 {newlink} index 2 address 94:C6:91:17:F9:72 mtu 1500
Nov 27 07:23:22 proxmox7node01.rb.test connmand[543]: eno1 {newlink} index 2 operstate 6 <UP>
Nov 27 07:23:22 proxmox7node01.rb.test connmand[543]: vmbr0 {RX} 0 packets 0 bytes
Nov 27 07:23:22 proxmox7node01.rb.test connmand[543]: vmbr0 {TX} 1 packets 150 bytes
Nov 27 07:23:22 proxmox7node01.rb.test connmand[543]: vmbr0 {update} flags 69699 <UP,RUNNING,LOWER_UP>
Nov 27 07:23:22 proxmox7node01.rb.test connmand[543]: vmbr0 {newlink} index 16 address 94:C6:91:17:F9:72 mtu 1500
Nov 27 07:23:22 proxmox7node01.rb.test connmand[543]: vmbr0 {newlink} index 16 operstate 6 <UP>
Nov 27 07:23:22 proxmox7node01.rb.test connmand[543]: eno1 {add} route fe80:: gw :: scope 0 <UNIVERSE>
Nov 27 07:23:23 proxmox7node01.rb.test avahi-daemon[538]: Joining mDNS multicast group on interface eno1.IPv6 with address fe80::96c6:91ff:fe17:f972.
Nov 27 07:23:23 proxmox7node01.rb.test avahi-daemon[538]: New relevant interface eno1.IPv6 for mDNS.
Nov 27 07:23:23 proxmox7node01.rb.test avahi-daemon[538]: Registering new address record for fe80::96c6:91ff:fe17:f972 on eno1.*.
Nov 27 07:23:53 proxmox7node01.rb.test pvedaemon[439498]: <root@pam> starting task UPID:proxmox7node01:00104B99:005B1CEC:638275D9:aptupdate::root@pam:
Nov 27 07:23:55 proxmox7node01.rb.test pvedaemon[1067929]: update new package list: /var/lib/pve-manager/pkgupdates
Nov 27 07:23:57 proxmox7node01.rb.test pvedaemon[439498]: <root@pam> end task UPID:proxmox7node01:00104B99:005B1CEC:638275D9:aptupdate::root@pam: OK
Nov 27 07:24:08 proxmox7node01.rb.test avahi-daemon[538]: Joining mDNS multicast group on interface eno1.IPv4 with address 169.254.123.211.
Nov 27 07:24:08 proxmox7node01.rb.test avahi-daemon[538]: New relevant interface eno1.IPv4 for mDNS.
Nov 27 07:24:08 proxmox7node01.rb.test avahi-daemon[538]: Registering new address record for 169.254.123.211 on eno1.IPv4.
Nov 27 07:24:08 proxmox7node01.rb.test connmand[543]: eno1 {add} address 169.254.123.211/16 label eno1 family 2
Nov 27 07:24:08 proxmox7node01.rb.test connmand[543]: eno1 {add} route 169.254.0.0 gw 0.0.0.0 scope 253 <LINK>
Nov 27 07:24:08 proxmox7node01.rb.test connmand[543]: eno1 {add} route 0.0.0.0 gw 0.0.0.0 scope 253 <LINK>

All looks well until

Code:

Nov 27 07:24:08 proxmox7node01.rb.test avahi-daemon[538]: Joining mDNS multicast group on interface eno1.IPv4 with address 169.254.123.211.

Should I uninstall avahi-daemon? I notice that Proxmox installed from the image file does not include avahi.

Search

Search

PROXMOX host unable connect to the internet

francly

New Member

Dunuin

Distinguished Member

francly

New Member

robb01

Member

Dunuin

Distinguished Member

robb01

Member

robb01

Member

We value your privacy