OpenVZ Forum


Home » General » Support » veth bridge not forwarding virtual client sources (forwarding through a virtual VE router)
veth bridge not forwarding virtual client sources [message #39142] Thu, 18 March 2010 17:07 Go to next message
nubjub is currently offline  nubjub
Messages: 2
Registered: March 2010
Location: Oregon
Junior Member
In short I've set up a container as a router, masquerading clients connected on internal br1 to external br0, when the client is a real computer everything works fine, but when the client is virtual the router is forwarding the packets to the veth in br0 but they are not forwarded to the physical iface.

Details:

bridge_name__bridge_id____________STP___interfaces
br0__________8000.00185173f3bd____no____eth0
________________________________________veth131.0
br1__________8000.000fb588832d____no____eth1
________________________________________veth131.1
________________________________________veth201.1

in container router 131.conf:
NETIF=" ifname=eth0,bridge=br0,mac=00:18:51:83:CC:DF,host_ifname=vet h131.0,host_mac=00:18:51:74:F3:BD;ifname=eth1,bridge=br1,mac =00:18:51:EB:D9:CD,host_ifname=veth131.1,host_mac=00:18:51:0 B:A8:C1 "
CAPABILITY="NET_ADMIN:on "

131 ifconfig:
eth0 Link encap:Ethernet HWaddr 00:18:51:83:cc:df
inet addr:216.99.207.218 Bcast:216.99.207.255 Mask:255.255.255.192
eth1 Link encap:Ethernet HWaddr 00:18:51:eb:d9:cd
inet addr:10.0.0.6 Bcast:10.0.255.255 Mask:255.255.0.0

tcpdump:
from a computer connected to eth1:
veth131.0:
09:36:50.660471 00:18:51:83:cc:df > 00:10:67:00:41:d7, ethertype IPv4 (0x0800), length 98: 216.99.207.218 > 216.99.207.254: ICMP echo request, id 34369, seq 128, length 64
09:36:50.699939 00:10:67:00:41:d7 > 00:18:51:83:cc:df, ethertype IPv4 (0x0800), length 98: 216.99.207.254 > 216.99.207.218: ICMP echo reply, id 34369, seq 128, length 64
br0:
09:36:50.660471 00:18:51:83:cc:df > 00:10:67:00:41:d7, ethertype IPv4 (0x0800), length 98: 216.99.207.218 > 216.99.207.254: ICMP echo request, id 34369, seq 128, length 64
09:36:50.699939 00:10:67:00:41:d7 > 00:18:51:83:cc:df, ethertype IPv4 (0x0800), length 98: 216.99.207.254 > 216.99.207.218: ICMP echo reply, id 34369, seq 128, length 64
eth0:
09:36:50.660471 00:18:51:83:cc:df > 00:10:67:00:41:d7, ethertype IPv4 (0x0800), length 98: 216.99.207.218 > 216.99.207.254: ICMP echo request, id 34369, seq 128, length 64
09:36:50.699939 00:10:67:00:41:d7 > 00:18:51:83:cc:df, ethertype IPv4 (0x0800), length 98: 216.99.207.254 > 216.99.207.218: ICMP echo reply, id 34369, seq 128, length 64

From a container such as the one with veth201.1 in br1
tcpdump; requests looks the same from veth131.0:
10:16:55.790264 00:18:51:83:cc:df > 00:10:67:00:41:d7, ethertype IPv4 (0x0800), length 98: 216.99.207.218 > 216.99.207.254: ICMP echo request, id 55304, seq 1105, length 64
10:16:56.790323 00:18:51:83:cc:df > 00:10:67:00:41:d7, ethertype IPv4 (0x0800), length 98: 216.99.207.218 > 216.99.207.254: ICMP echo request, id 55304, seq 1106, length 64

but nothing on br0 or eth0

Apologies if this topic is already covered I'm not quite sure what I'm looking for.

[Updated on: Thu, 18 March 2010 17:25]

Report message to a moderator

Re: veth bridge not forwarding virtual client sources [message #39153 is a reply to message #39142] Fri, 19 March 2010 20:43 Go to previous message
nubjub is currently offline  nubjub
Messages: 2
Registered: March 2010
Location: Oregon
Junior Member
I upgraded to kernel 2.6.32 this morning to get new wireless drivers. I'm not sure what else has changed yet but whatever was causing this behavior is fixed now. If i find it in the near future I'll post on it. But consider this one closed.

Report message to a moderator

Previous Topic: Network down
Next Topic: vzmigrate - shared storage
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Tue Dec 24 03:44:30 GMT 2024

Total time taken to generate the page: 0.02867 seconds
Powered by FUDforum Powered by Virtuozzo Containers