Possible bug with vmbr* forward eth* in Proxmox 2.0 rc1

maykel535

Active Member
Mar 26, 2012
52
0
26
Hi! I have installed successfully proxmox 2.0 in my server. It has four network cards:
vmbr0 -> eth0 physical network card bridge
vmbr1 -> eth1 physical network card bridge
vmbr2 -> eth2 physical network card bridge
vmbr3 -> eth3 physical network card bridge


root@virtual1:~# brctl show
bridge name bridge id STP enabled interfaces
vmbr0 8000.3c4a927c4db8 yes eth0 ------------> connected
tap100i0
veth101.0
vmbr1 8000.3c4a927c4db9 yes eth1--------------> connected
tap102i0
vmbr2 8000.002655ea3d48 yes eth2--------------> cable not connected, no link
tap100i1
tap102i1
vmbr3 8000.002655ea3d49 yes eth3---------------> cable not connected, no link
tap100i2
tap102i2


PHYSICAL NETWORK CONFIGURATION:


root@virtual1:~# ifconfig
eth0 Link encap:Ethernet HWaddr 3c:4a:92:7c:4d:b8
inet6 addr: fe80::3e4a:92ff:fe7c:4db8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1...




eth1 Link encap:Ethernet HWaddr 3c:4a:92:7c:4d:b9
inet6 addr: fe80::3e4a:92ff:fe7c:4db9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1...




eth2 Link encap:Ethernet HWaddr 00:26:55:ea:3d:48
inet6 addr: fe80::226:55ff:feea:3d48/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1...




eth3 Link encap:Ethernet HWaddr 00:26:55:ea:3d:49
inet6 addr: fe80::226:55ff:feea:3d49/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1...




lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1...




tap100i0 Link encap:Ethernet HWaddr 36:d9:9a:53:66:5b
inet6 addr: fe80::34d9:9aff:fe53:665b/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1...




tap100i1 Link encap:Ethernet HWaddr 0e:a4:2c:55:22:aa
inet6 addr: fe80::ca4:2cff:fe55:22aa/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1...




tap100i2 Link encap:Ethernet HWaddr ba:8b:d0:34:25:8b
inet6 addr: fe80::b88b:d0ff:fe34:258b/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1...


tap102i0 Link encap:Ethernet HWaddr 2a:40:50:6e:03:fc
inet6 addr: fe80::2840:50ff:fe6e:3fc/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1...


tap102i1 Link encap:Ethernet HWaddr 76:8b:74:3c:c3:82
inet6 addr: fe80::748b:74ff:fe3c:c382/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1...


tap102i2 Link encap:Ethernet HWaddr ca:63:34:9d:d8:b0
inet6 addr: fe80::c863:34ff:fe9d:d8b0/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1...


venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::1/128 Scope:Link
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1...


veth101.0 Link encap:Ethernet HWaddr 96:e7:eb:b5:0e:1c
inet6 addr: fe80::94e7:ebff:feb5:e1c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1...


vmbr0 Link encap:Ethernet HWaddr 3c:4a:92:7c:4d:b8
inet addr:10.100.100.7 Bcast:10.100.100.255 Mask:255.255.255.0
inet6 addr: fe80::3e4a:92ff:fe7c:4db8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1..


vmbr1 Link encap:Ethernet HWaddr 3c:4a:92:7c:4d:b9
inet addr:10.116.10.15 Bcast:10.116.255.255 Mask:255.255.0.0
inet6 addr: fe80::3e4a:92ff:fe7c:4db9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1)...


vmbr2 Link encap:Ethernet HWaddr 00:26:55:ea:3d:48
inet addr:10.116.10.26 Bcast:10.116.255.255 Mask:255.255.0.0
inet6 addr: fe80::226:55ff:feea:3d48/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1...


vmbr3 Link encap:Ethernet HWaddr 00:26:55:ea:3d:49
inet addr:10.116.10.27 Bcast:10.116.255.255 Mask:255.255.0.0
inet6 addr: fe80::226:55ff:feea:3d49/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1...




If I throw a ping from another network host, and I do a tcpdump error will look better.


Ping to 10.116.10.15(vmbr1) :


root@virtual1:~# tcpdump -i vmbr1 icmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vmbr1, link-type EN10MB (Ethernet), capture size 65535 bytes


10:08:41.539019 IP 10.116.30.1 > 10.116.10.15: ICMP echo request, id 1, seq 1027, length 40
10:08:41.539057 IP 10.116.10.15 > 10.116.30.1: ICMP echo reply, id 1, seq 1027, length 40


And now, ping to 10.116.10.26(vmbr2) other physical network card in theory:


root@virtual1:~# tcpdump -i vmbr2 icmp ----->>> Not show anything


But in vmbr1 yes...


root@virtual1:~# tcpdump -i vmbr1 icmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vmbr1, link-type EN10MB (Ethernet), capture size 65535 bytes


10:11:48.307929 IP 10.116.30.1 > 10.116.10.26: ICMP echo request, id 1, seq 1058, length 40
10:11:48.307961 IP 10.116.10.26 > 10.116.30.1: ICMP echo reply, id 1, seq 1058, length 40




And now, ping to 10.116.10.27(vmbr3) other physical network card in theroy:


root@virtual1:~# tcpdump -i vmbr3 icmp ----->>> Not show anything


But in vmbr1 yes...


root@virtual1:~# tcpdump -i vmbr1 icmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vmbr1, link-type EN10MB (Ethernet), capture size 65535 bytes
10:14:49.928829 IP 10.116.30.1 > 10.116.10.27: ICMP echo request, id 1, seq 1066, length 40
10:14:49.928864 IP 10.116.10.27 > 10.116.30.1: ICMP echo reply, id 1, seq 1066, length 40


I understand nothing, but the association Proxmox bad physical network card with bridge. The pings to 10.116.10.26 and 10.116.10.27 will must not operate but no link network card...


I think this a bug problem....Can I help me please?? Sorry for my english, thanks un advanced.
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
15,537
920
163
Please do not post your issues on all support channels, this is just a waste of time for all involved people.

so far I you did all this the same time:

- opening support ticket
- posted it via a chat session
- sent the issue to the mailing list
- posted in the forum

please use ONLY one support channel!
 

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 your own in 60 seconds.

Buy now!