Node + CTs have IPv6, no IPv4 (external) - Lo showing "unknown" status

vulcan

New Member
Jun 15, 2022
1
0
1
Hey all,
I am running into an issue on a home-based node. It just started doing this recently, it was running fine. The node + containers can access IPv6 but not IPv4. The loopback interface is also showing an "unknown" status. New CTs wont even start because they are unable to bring the interfaces up. IPv4 works on internal addresses (10.0.0.1) but not external (1.1.1.1) as I am getting

Code:
root@cubed:~# ping 1.1.1.1
ping: connect: Network is unreachable

Interfaces:

Code:
root@cubed:~# 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 dhcp

auto eno2
iface eno2 inet manual

auto eno3
iface eno3 inet manual

auto eno4
iface eno4 inet manual
        address 10.0.4.1/21

auto vmbr99
iface vmbr99 inet manual
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
#bridge-stp off bridge-fd 0

IP info:

Code:
root@cubed:~# 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 mq master vmbr99 state UP group default qlen 1000
    link/ether d8:9d:67:26:0c:70 brd ff:ff:ff:ff:ff:ff
    altname enp3s0f0
3: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether d8:9d:67:26:0c:71 brd ff:ff:ff:ff:ff:ff
    altname enp3s0f1
4: eno3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether d8:9d:67:26:0c:72 brd ff:ff:ff:ff:ff:ff
    altname enp3s0f2
5: eno4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether d8:9d:67:26:0c:73 brd ff:ff:ff:ff:ff:ff
    altname enp3s0f3
    inet 10.0.4.1/21 scope global eno4
       valid_lft forever preferred_lft forever
    inet6 2600:8800:8380:51:da9d:67ff:fe26:c73/64 scope global dynamic mngtmpaddr
       valid_lft 593sec preferred_lft 593sec
    inet6 fe80::da9d:67ff:fe26:c73/64 scope link
       valid_lft forever preferred_lft forever
6: vmbr99: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether d8:9d:67:26:0c:70 brd ff:ff:ff:ff:ff:ff
    inet6 2600:8800:8380:51:da9d:67ff:fe26:c70/64 scope global dynamic mngtmpaddr
       valid_lft 593sec preferred_lft 593sec
    inet6 fe80::da9d:67ff:fe26:c70/64 scope link
       valid_lft forever preferred_lft forever
7: veth102i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr99 state UP group default qlen 1000
    link/ether fe:f5:af:bb:91:d4 brd ff:ff:ff:ff:ff:ff link-netnsid 0
8: veth102i1@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr102i1 state UP group default qlen 1000
    link/ether fe:a9:15:de:c3:0a brd ff:ff:ff:ff:ff:ff link-netnsid 0
9: fwbr102i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a6:7e:2e:e3:3f:9e brd ff:ff:ff:ff:ff:ff
10: fwpr102p1@fwln102i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr99 state UP group default qlen 1000
    link/ether 86:d3:f7:19:e5:9b brd ff:ff:ff:ff:ff:ff
11: fwln102i1@fwpr102p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr102i1 state UP group default qlen 1000
    link/ether 76:12:5f:42:b8:92 brd ff:ff:ff:ff:ff:ff


Any help is greatly appreciated, I am going mad!
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!