[PVE-User] Problem proxmox 2.0 to forward vmbr1 to eth0, eth1, eth2 VM
maykel at maykel.sytes.net
maykel at maykel.sytes.net
Mon Mar 26 10:21:13 CEST 2012
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 at 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 at virtual1:~# ifconfig
-a
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
RX packets:3360633 errors:0 dropped:0 overruns:0
frame:0
TX packets:2125379 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:655234176 (624.8 MiB) TX
bytes:416357864 (397.0 MiB)
Interrupt:16
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
RX
packets:1182567 errors:0 dropped:0 overruns:0 frame:0
TX packets:764372
errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:248530497 (237.0 MiB) TX bytes:243084204 (231.8 MiB)
Interrupt:17
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
RX packets:85937 errors:0 dropped:0
overruns:0 frame:0
TX packets:69887 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:1000
RX bytes:8129685 (7.7 MiB) TX
bytes:6451674 (6.1 MiB)
Interrupt:16 Memory:df920000-df940000
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
RX packets:20463 errors:0 dropped:0 overruns:0
frame:0
TX packets:1067 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1931022 (1.8 MiB) TX bytes:70316
(68.6 KiB)
Interrupt:17 Memory:df960000-df980000
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
RX packets:2952899
errors:0 dropped:0 overruns:0 frame:0
TX packets:2952899 errors:0
dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX
bytes:489113942 (466.4 MiB) TX bytes:489113942 (466.4 MiB)
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
RX packets:4 errors:0 dropped:0 overruns:0
frame:0
TX packets:580326 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:300 (300.0 B) TX bytes:42505700
(40.5 MiB)
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
RX packets:67053 errors:0 dropped:0
overruns:0 frame:0
TX packets:88147 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:500
RX bytes:6289538 (5.9 MiB) TX
bytes:8216188 (7.8 MiB)
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
RX packets:0
errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0
overruns:1 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B)
TX bytes:0 (0.0 B)
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
RX packets:223
errors:0 dropped:0 overruns:0 frame:0
TX packets:44189 errors:0
dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX
bytes:23620 (23.0 KiB) TX bytes:6179099 (5.8 MiB)
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
RX packets:22 errors:0 dropped:0 overruns:0
frame:0
TX packets:2979 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1356 (1.3 KiB) TX bytes:208892
(203.9 KiB)
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
RX packets:20 errors:0
dropped:0 overruns:0 frame:0
TX packets:2988 errors:0 dropped:0
overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1272 (1.2
KiB) TX bytes:210292 (205.3 KiB)
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
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX
packets:0 errors:0 dropped:3 overruns:0 carrier:0
collisions:0
txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
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
RX packets:7480 errors:0 dropped:0 overruns:0
frame:0
TX packets:567384 errors:0 dropped:19844 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:619369 (604.8 KiB) TX
bytes:33869184 (32.3 MiB)
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
RX packets:3028501
errors:0 dropped:0 overruns:0 frame:0
TX packets:2079838 errors:0
dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX
bytes:413810936 (394.6 MiB) TX bytes:402997699 (384.3 MiB)
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
RX packets:1164860 errors:0 dropped:0 overruns:0
frame:0
TX packets:717396 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:223145708 (212.8 MiB) TX
bytes:236019310 (225.0 MiB)
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
RX packets:18199 errors:0
dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:0
RX bytes:1519712 (1.4 MiB) TX
bytes:468 (468.0 B)
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
RX packets:18192 errors:0 dropped:0
overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:0
RX bytes:1519190 (1.4 MiB) TX
bytes:468 (468.0 B)
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 at 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
10:08:42.545551 IP 10.116.30.1 > 10.116.10.15: ICMP
echo request, id 1, seq 1028, length 40
10:08:42.545578 IP 10.116.10.15
> 10.116.30.1: ICMP echo reply, id 1, seq 1028, length
40
10:08:43.546448 IP 10.116.30.1 > 10.116.10.15: ICMP echo request, id
1, seq 1029, length 40
10:08:43.546476 IP 10.116.10.15 > 10.116.30.1:
ICMP echo reply, id 1, seq 1029, length 40
And now, ping to
10.116.10.26(vmbr2) other physical network card in
theory:
root at virtual1:~# tcpdump -i vmbr2 icmp ----->>> Not show
anything
But in vmbr1 yes...
root at 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
10:11:49.320005
IP 10.116.30.1 > 10.116.10.26: ICMP echo request, id 1, seq 1059, length
40
10:11:49.320031 IP 10.116.10.26 > 10.116.30.1: ICMP echo reply, id 1,
seq 1059, length 40
10:11:50.314017 IP 10.116.30.1 > 10.116.10.26: ICMP
echo request, id 1, seq 1060, length 40
10:11:50.314048 IP 10.116.10.26
> 10.116.30.1: ICMP echo reply, id 1, seq 1060, length
40
10:11:51.328958 IP 10.116.30.1 > 10.116.10.26: ICMP echo request, id
1, seq 1061, length 40
10:11:51.328987 IP 10.116.10.26 > 10.116.30.1:
ICMP echo reply, id 1, seq 1061, length 40
And now, ping to
10.116.10.27(vmbr3) other physical network card in
theroy:
root at virtual1:~# tcpdump -i vmbr3 icmp ----->>> Not show
anything
But in vmbr1 yes...
root at 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
10:14:50.931331
IP 10.116.30.1 > 10.116.10.27: ICMP echo request, id 1, seq 1067, length
40
10:14:50.931356 IP 10.116.10.27 > 10.116.30.1: ICMP echo reply, id 1,
seq 1067, length 40
10:14:51.928864 IP 10.116.30.1 > 10.116.10.27: ICMP
echo request, id 1, seq 1068, length 40
10:14:51.928893 IP 10.116.10.27
> 10.116.30.1: ICMP echo reply, id 1, seq 1068, length
40
10:14:52.926669 IP 10.116.30.1 > 10.116.10.27: ICMP echo request, id
1, seq 1069, 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
when installed the VM ClearOS(based in Centos) and I have associated the
follow networks cards via web interface proxmox in the VM:
physical
network card bridge vmbr1 -> eth0 in Centos VM(ClearOS)
physical
network card bridge vmbr2 -> eth1 in Centos VM(ClearOS)
physical
network card bridge vmbr3 -> eth2 in Centos VM(ClearOS)
Network card
configuration VM Centos:
eth0 Link encap:Ethernet HWaddr
9A:25:9F:53:7B:3D
inet addr:10.116.10.18 Bcast:10.116.255.255
Mask:255.255.0.0
inet6 addr: fe80::9825:9fff:fe53:7b3d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20530
errors:0 dropped:0 overruns:0 frame:0
TX packets:188 errors:0 dropped:0
overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2122419
(2.0 MiB) TX bytes:17250 (16.8 KiB)
Interrupt:10 Base address:0xa000
eth1 Link encap:Ethernet HWaddr F6:2E:25:63:3C:AA
inet
addr:10.116.10.17 Bcast:10.116.255.255 Mask:255.255.0.0
inet6 addr:
fe80::f42e:25ff:fe63:3caa/64 Scope:Link
UP BROADCAST RUNNING MULTICAST
MTU:1500 Metric:1
RX packets:582 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
txqueuelen:1000
RX bytes:28439 (27.7 KiB) TX bytes:636 (636.0 b)
Interrupt:11 Base address:0x4000
eth2 Link encap:Ethernet HWaddr
E2:C1:6C:7E:55:B4
inet addr:10.116.10.16 Bcast:10.116.10.255
Mask:255.255.255.0
inet6 addr: fe80::e0c1:6cff:fe7e:55b4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2010
errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0
overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:94545 (92.3
KiB) TX bytes:636 (636.0 b)
Interrupt:11 Base address:0x6000
imq0
Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:16000
Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX
packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
txqueuelen:11000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
imq1 Link
encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:16000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0
frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
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
RX packets:375 errors:0 dropped:0 overruns:0 frame:0
TX packets:375
errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX
bytes:516514 (504.4 KiB) TX bytes:516514 (504.4 KiB)
sit0 Link
encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0
dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0
b)
And all OK but the problem is when I doing ping to host
10.116.10.18, 10.116.10.17 and 10.116.10.16, the all pings have the same
TTL that vmbr1. The TTL host 10.116.10.18, 10.116.10.17 and 10.116.10.16
must be +1.
I think this a bug problem....
Can I help me please??
Sorry for my english, thanks un advanced.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-user/attachments/20120326/f5efd48c/attachment.htm>
More information about the pve-user
mailing list