OpenVZ Forum: Support » venet bridge dont work[CentOS]

Home » General » Support » venet bridge dont work[CentOS]

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

venet bridge dont work[CentOS] [message #21140]

Tue, 02 October 2007 12:37

alxumuk
Messages: 1
Registered: October 2007

Junior Member

[root@router1 ~]# vzlist
VEID NPROC STATUS IP_ADDR HOSTNAME
160 16 running 101.router.net
170 16 running 45.172.234.198 102.router.net
[root@router1 template]# ifconfig
br0 Link encap:Ethernet HWaddr 00:07:E9:09:E1:F7
inet addr:45.172.234.38 Bcast:45.172.234.255 Mask:255.255.255.0
inet6 addr: fe80::207:e9ff:fe09:e1f7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1476173 errors:0 dropped:0 overruns:0 frame:0
TX packets:960941 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1021577455 (974.2 MiB) TX bytes:90374111 (86.1 MiB)

eth0 Link encap:Ethernet HWaddr 00:07:E9:09:E1:F7
inet6 addr: fe80::207:e9ff:fe09:e1f7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1526072 errors:0 dropped:0 overruns:0 frame:0
TX packets:962470 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1054719846 (1005.8 MiB) TX bytes:94427316 (90.0 MiB)
Base address:0xa000 Memory:f4020000-f4040000

eth1 Link encap:Ethernet HWaddr 00:00:6C:B9:C7:73
inet6 addr: fe80::200:6cff:feb9:c773/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:31982 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2876150 (2.7 MiB) TX bytes:7431 (7.2 KiB)
Interrupt:15 Base address:0x2000

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:24296 errors:0 dropped:0 overruns:0 frame:0
TX packets:24296 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3625936 (3.4 MiB) TX bytes:3625936 (3.4 MiB)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:3728 errors:0 dropped:0 overruns:0 frame:0
TX packets:5837 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:331038 (323.2 KiB) TX bytes:320841 (313.3 KiB)

veth160.0 Link encap:Ethernet HWaddr 00:18:51:08:37:32
inet6 addr: fe80::218:51ff:fe08:3732/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4177 errors:0 dropped:0 overruns:0 frame:0
TX packets:219167 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:117180 (114.4 KiB) TX bytes:10437243 (9.9 MiB)

[root@router1 template]# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.0007e909e1f7 no veth160.0
eth0
[root@router1 template]# ip route
45.172.234.197 dev br0 scope link
45.172.234.198 dev venet0 scope link
45.172.234.0/24 dev br0 proto kernel scope link src 45.172.234.38
169.254.0.0/16 dev br0 scope link
default via 45.172.234.1 dev br0
[root@router1 template]#
[root@router1 template]# vzctl enter 160
entered into VE 160
[root@101 /]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:18:51:16:9F:83
inet addr:45.172.234.197 Bcast:0.0.0.0 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:219308 errors:0 dropped:0 overruns:0 frame:0
TX packets:4177 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10443807 (9.9 MiB) TX bytes:117180 (114.4 KiB)

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: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)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
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:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

[root@101 /]# ip route
192.0.2.0/24 dev venet0 scope host
45.172.234.0/24 dev eth0 proto kernel scope link src 45.172.234.197
169.254.0.0/16 dev venet0 scope link
default via 45.172.234.1 dev eth0
[root@101 /]# ping 87.250.251.8
PING 87.250.251.8 (87.250.251. Cool

56(84) bytes of data.
From 82.144.221.197 icmp_seq=1 Destination Host Unreachable
From 82.144.221.197 icmp_seq=2 Destination Host Unreachable
From 82.144.221.197 icmp_seq=3 Destination Host Unreachable

--- 87.250.251.8 ping statistics ---
39 packets transmitted, 0 received, +27 errors, 100% packet loss, time 37993ms
, pipe 4
[root@101 /]# traceroute 87.250.251.8
traceroute to 87.250.251.8 (87.250.251. Cool

, 30 hops max, 38 byte packets
1 82.144.221.197 (82.144.221.197) 3000.325 ms !H 3001.092 ms !H 3001.127 ms !H
[root@101 /]#

Report message to a moderator

Re: venet bridge dont work[CentOS] [message #21143 is a reply to message #21140]

Tue, 02 October 2007 13:25

tomfra
Messages: 28
Registered: September 2007

Junior Member

Do you use iptables? I had a similar problem and had to add some iptables rules to allow traffic forwarding from venet0 to eth0 because by default I had the FORWARD policy set to DROP. My hardware node is running on CentOS 5 x86_64.

Take a look at http://forum.lxlabs.com/index.php?t=msg&goto=13353 . The fact I am using CSF should not really matter as CSF is using iptables anyway.

Tomas

Do you really believe the Internet is a safe place?
IdentityCloaker.com - Take Back Your Privacy!

Report message to a moderator

Previous Topic:	Incorrect load average
Next Topic:	ve with cpanel is not stable

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Dec 23 16:32:35 GMT 2025

Total time taken to generate the page: 0.18222 seconds