Wired network behavior (packet loss/timeout)

[tahala]

Dear Proxmox Community,

I just migrated my homelab from esxi6 to proxmox5.


Unfortunately I have got some issues with the network already on the Host itself.
Currently I have two Network Cards attached and the an adapted setup from the wiki.

auto lo
iface lo inet loopback

auto enp0s25 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.252
        netmask 255.255.255.0
        gateway 192.168.1.254
        bridge_ports enp0s25
        bridge_stp off
        bridge_fd 0
#Bridge for VM/CT

iface vmbr0 inet6 static
        address fd86:xx:x:x:xxx:ff:fe:xx
        netmask 48


iface enp3s0 inet manual

auto vmbr1
iface vmbr1 inet static
        address 192.168.1.40
        netmask 255.255.255.0
        gateway 192.168.1.254
        bridge_ports enp3s0
        bridge_stp off
        bridge_fd 0
#Bridge for VM/CT

iface vmbr1 inet6 static
        address fd86:xx:x::xx
        netmask 48

I have several unprivileged Containers configured, some with UFW configured.
They are currently all off (shutdown). The firewall on the Host is disabled.

On the Host is SMB installed. And it is listening on 192.168.1.40.
When trying to connect to 192.168.1.40:445 I often get an Timeout (SYN send, but no response).
Yesterday it was working shortly, but with I had a lot of package Losts while pinging 192.168.1.40 or "(broken pipe)" with SMB.

Further, I'm not able to get a stable network connection from the host to the internet.
Running apt-get update often does not work (timeout) or does not even resolve the networkadress: "
Temporärer Fehlschlag beim Auflösen von »download.proxmox.com«"

ip route
default via 192.168.1.254 dev vmbr0 onlink
192.168.42.0/24 dev enp0s25 proto kernel scope link src 192.168.1.40
192.168.42.0/24 dev vmbr0 proto kernel scope link src 192.168.1.252

When looking at ip addr show:

ip addr show
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: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether d0:50:99:xx:xx:xx brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.40/24 brd 192.168.1.255 scope global enp0s25
       valid_lft forever preferred_lft forever
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether d0:50:99:x:x:x brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.252/24 brd 192.168.1.255 scope global vmbr0
       valid_lft forever preferred_lft forever

I just realized that "lo" is in state UNKNOWN. Is it possible that my network card is not fully supported? Or am I missing something?

Intel OnbordCard:
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V (rev 05)


Thanks and Kind Regards,
Tahala

 

[dcsapak]

i do not understand your configuration:

you have 2 nics but only one shows up in 'ip addr show'
you did not set an ip on enp0s25 but it shows up in 'ip addr show'

the config is not right, you should only set a gateway on one interface
also why do you have 2 ips in the same subnet on 2 nics ?

 

[tahala]

Thanks for reviewing the config.
I have already tried different network options, including giving the ip address directly to a single network card as im used to to it under linux.

ip a now shows:

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: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether d0:50:99:x:x:x brd ff:ff:ff:ff:ff:ff
3: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UP group default qlen 1000
    link/ether 00:13:3b:x:x:x brd ff:ff:ff:ff:ff:ff
4: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:13:3b:x:x:x brd ff:ff:ff:ff:ff:ff
5: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:13:3b:x:x:x brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.40/24 brd 192.168.1.255 scope global vmbr1
       valid_lft forever preferred_lft forever
    inet6 fd86:x:x::x1/48 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::x:ff:fe:xxx/64 scope link
       valid_lft forever preferred_lft forever
6: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether d0:50:99:x:x:x brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.252/24 brd 192.168.42.255 scope global vmbr0
       valid_lft forever preferred_lft forever
8: veth4100i0@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP group
default qlen 1000
    link/ether fe:ba:0c:x:x:x brd ff:ff:ff:ff:ff:ff link-netnsid 0
10: veth4200i0@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP group default qlen 1000
    link/ether fe:c3:ea:x:x:x brd ff:ff:ff:ff:ff:ff link-netnsid 1
12: veth4400i0@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP group default qlen 1000
    link/ether fe:2a:d6:x:x:x brd ff:ff:ff:ff:ff:ff link-netnsid 2

Addionaly I have commentet out the gateway in /etc/network/interfaces file from the initial post.

To answer your question regarding the sense of two ip addresses in the same subnet.
I would like to make usage of my two Ethernet Cards. So I use one Address for the Host (like SMB and Management) and the other Address for the VMs.

 

[tahala]

Update:
I just changed the network configuration to only one IP address since networking in VM/CT is working nevertheless (they get IP addresses)
I will monitor if this setup is more stable in relation to the original behavior.