No Host Connection with vmbr0

M

Mr-Wagner

New Member
Dec 19, 2016
10
0
1
35
Hello,

I have no connection from and to my host with a bridged interface (no ping from and to the host), but I can ping a VM on that same interface.
Oddly I can get a connection for about 1-2 minutes, after I rebooted the machine.

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

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.3.5
        netmask 255.255.255.0
        gateway 192.168.3.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

Best Regards
Mr-Wagner
 
What kind of NIC you have?
I mean the type.
 
Have you looked in the logs?
Is there are any hints?
 
I can't see anything suspicious.
Here is my syslog:
Code: 
Dec 20 14:30:39 proxmox systemd[1]: Started PVE VM Manager.
Dec 20 14:30:39 proxmox systemd[1]: Starting Multi-User System.
Dec 20 14:30:39 proxmox systemd[1]: Reached target Multi-User System.
Dec 20 14:30:39 proxmox systemd[1]: Starting Graphical Interface.
Dec 20 14:30:39 proxmox systemd[1]: Reached target Graphical Interface.
Dec 20 14:30:39 proxmox systemd[1]: Starting Update UTMP about System Runlevel Changes...
Dec 20 14:30:39 proxmox systemd[1]: Started Update UTMP about System Runlevel Changes.
Dec 20 14:30:39 proxmox systemd[1]: Startup finished in 14.962s (kernel) + 6.320s (userspace) = 21.282s.
Dec 20 14:30:39 proxmox kernel: audit: type=1400 audit(1482240639.877:7): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=1363 comm="(networkd)" flags="rw, rslave"
Dec 20 14:30:39 proxmox kernel: vmbr0: port 2(veth100i0) entered forwarding state
Dec 20 14:30:39 proxmox kernel: vmbr0: port 2(veth100i0) entered forwarding state
Dec 20 14:30:49 proxmox kernel: vmbr0: port 1(eth0) entered forwarding state
Dec 20 14:30:54 proxmox kernel: vmbr0: port 2(veth100i0) entered forwarding state
Dec 20 14:31:00 proxmox sshd[1484]: Accepted password for root from 192.168.3.12 port 52596 ssh2
Dec 20 14:31:00 proxmox sshd[1484]: pam_unix(sshd:session): session opened for user root by (uid=0)
Dec 20 14:31:01 proxmox sshd[1484]: pam_unix(sshd:session): session closed for user root
Dec 20 14:31:11 proxmox systemd-timesyncd[662]: interval/delta/delay/jitter/drift 64s/+0.000s/0.130s/0.000s/+0ppm
Dec 20 14:31:13 proxmox sshd[1509]: Accepted password for root from 192.168.3.12 port 52600 ssh2
Dec 20 14:31:13 proxmox sshd[1509]: pam_unix(sshd:session): session opened for user root by (uid=0)
Dec 20 14:31:14 proxmox sshd[1509]: pam_unix(sshd:session): session closed for user root
Dec 20 14:32:16 proxmox systemd-timesyncd[662]: interval/delta/delay/jitter/drift 128s/+0.001s/0.131s/0.000s/+4ppm
Dec 20 14:32:42 proxmox sshd[1637]: Connection closed by 192.168.3.12 [preauth]
Dec 20 14:33:17 proxmox pvedaemon[1212]: <root@pam> successful auth for user 'root@pam'
Dec 20 14:34:09 proxmox pvedaemon[1212]: update new package list: /var/lib/pve-manager/pkgupdates
Dec 20 14:35:04 proxmox sshd[1851]: Connection closed by 192.168.3.12 [preauth]
 
I just read this here ... please do not cross-post german/english. This is very hard to follow and discuss.

As I wrote on the german entry:

Have you tried stopping all your VMs and testing then? Maybe some MAC or IP collision?
 
Yes, the problem still exists without a VM running. The problem only exists, when I install Proxmox on a normal Debian Image (tested it twice). Everything works fine with the official Proxmox Image. I will use the Proxmox Image for now, but maybe try it again sometime.
 
What about the ifconfig status? Have you installed network-manager-stuff? This influences and it is written do deinstall it because it influences the way Proxmox VE works.

Please run
Code: 
dpkg -l | grep network
 
dpkg -l | grep network:
Code: 
ii  ifenslave                      2.6                            all          configure network interfaces for parallel routing (bonding)
ii  ifupdown                       0.7.53.1                       amd64        high level tools to configure network interfaces
ii  iproute2                       4.4.0-2                        amd64        networking and traffic control tools
ii  iputils-ping                   3:20121221-5+b2                amd64        Tools to test the reachability of network hosts
ii  net-tools                      1.60-26+b1                     amd64        NET-3 networking toolkit
ii  netbase                        5.3                            all          Basic TCP/IP networking system
ii  traceroute                     1:2.0.20-2+b1                  amd64        Traces the route taken by packets over an IPv4/IPv6 network
ifconfig:
Code: 
eth0      Link encap:Ethernet  Hardware Adresse 18:66:da:38:8c:69
          inet Adresse:192.168.3.5  Bcast:192.168.3.255  Maske:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX packets:64478 errors:0 dropped:0 overruns:0 frame:0
          TX packets:34028 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:65129052 (62.1 MiB)  TX bytes:40959497 (39.0 MiB)
          Interrupt:20 Speicher:f7c00000-f7c20000

lo        Link encap:Lokale Schleife
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:65536  Metrik:1
          RX packets:1068 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1068 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1
          RX bytes:393042 (383.8 KiB)  TX bytes:393042 (383.8 KiB)

veth100i0 Link encap:Ethernet  Hardware Adresse fe:bd:d5:c7:05:de
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX packets:8918 errors:0 dropped:0 overruns:0 frame:0
          TX packets:58301 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:35790267 (34.1 MiB)  TX bytes:63313035 (60.3 MiB)

vmbr0     Link encap:Ethernet  Hardware Adresse 18:66:da:38:8c:69
          inet Adresse:192.168.3.5  Bcast:192.168.3.255  Maske:255.255.255.0
          inet6-Adresse: fe80::1a66:daff:fe38:8c69/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX packets:7235 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:1588911 (1.5 MiB)  TX bytes:2296 (2.2 KiB)
This is just a standard debian installation with no special packages.
 
One strange this is that your have eth0 and vmbr0 with the same IP. I'd change that but I do not think this is the mail problem. What about the configuration in your VM? Please also post

Code: 
brctl show
 
brctl show:
Code: 
bridge name     bridge id               STP enabled     interfaces
vmbr0           8000.1866da388c69       no              eth0
                                                        veth100i0
 
The Connection to my VM is working.
hSzmRlg.png
 
@Mr-Wagner

is this a default Debian image or an Image from a Datacenter Provider like HEtzner, OVH, etc?
What PVE Version do you use?
 
You must log in or register to reply here.
Top Bottom