[CentOS] CentOS 6 bridging problem.
Rafał Radecki
radecki.rafal at gmail.com
Tue Jun 26 07:02:28 UTC 2012
ip route show
192.168.2.0/24 dev vmbr0 proto kernel scope link src 192.168.2.203
193.218.152.0/24 dev vmbr0 proto kernel scope link src 193.218.152.219
10.20.0.0/16 dev vmbr20 proto kernel scope link src 10.20.0.108
169.254.0.0/16 dev vmbr0 scope link metric 1003
169.254.0.0/16 dev vmbr20 scope link metric 1006
default via 193.218.152.1 dev vmbr0
ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 1000
link/ether 00:25:22:0d:c2:2a brd ff:ff:ff:ff:ff:ff
inet6 fe80::225:22ff:fe0d:c22a/64 scope link
valid_lft forever preferred_lft forever
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UNKNOWN
link/ether 00:25:22:0d:c2:2a brd ff:ff:ff:ff:ff:ff
inet 193.218.152.219/24 brd 193.218.152.255 scope global vmbr0
inet 192.168.2.203/24 brd 192.168.2.255 scope global vmbr0:1
inet6 fe80::225:22ff:fe0d:c22a/64 scope link
valid_lft forever preferred_lft forever
4: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc
noqueue state UNKNOWN
link/void
inet6 fe80::1/128 scope link
valid_lft forever preferred_lft forever
5: eth0.20 at eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue state UP
link/ether 00:25:22:0d:c2:2a brd ff:ff:ff:ff:ff:ff
inet6 fe80::225:22ff:fe0d:c22a/64 scope link
valid_lft forever preferred_lft forever
6: vmbr20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UNKNOWN
link/ether 00:25:22:0d:c2:2a brd ff:ff:ff:ff:ff:ff
inet 10.20.0.108/16 brd 10.20.255.255 scope global vmbr20
inet6 fe80::225:22ff:fe0d:c22a/64 scope link
valid_lft forever preferred_lft forever
Any clue?
Best regards,
Rafal Radecki.
2012/6/25 Gordon Messmer <yinyang at eburg.com>:
> On 06/25/2012 05:22 AM, Rafał Radecki wrote:
>> Do you see an error in my configuration? Why is 10.20.0.108 not available?
>
> Not immediately, but check the output of the 'ip' tools. ifconfig and
> route are deprecated:
>
> ip route show
> ip addr show
>
> Finally, see if there's any incoming traffic on the tagged interface:
>
> tcpdump -n -i eth0.20
>
> ... while you ping the assigned address.
>
>
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
More information about the CentOS
mailing list