[Xen-bugs] [Bug 753] bonding + vlans + bridging

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=753





------- Comment #13 from kfh.xen@xxxxxx  2006-11-28 05:54 -------
(In reply to comment #12)
> Hi,
> 
> I believe your problem is as follows,
> veth0 sends arp-request for ex. IP 1.2.3.4 to mac broadcast.
> vlanXXX-br forwards the frame and marks "veth0 mac" as belonging to vif0.0
> port.
> bond0 sends the frame through ex. eth0.
> The switch connected to eth0 floods all ports except the incoming port (eth0),
> and marks "veth0 mac" as belonging to eth0 port.
> The flood includes the eth1 port.
> The bridge vlanXXX-br forwards the frame and marks "veth0 mac" as belonging to
> vlanXXX port.
> 
> The destination (1.2.3.4) sends arp reply to "veth0 mac".
> The switch connected to eth0/eth1, sends the reply to the eth0 port.
> The bridge vlanXXX-br blocks the frame as it believes the destination belongs
> to vlanXXX port.

You can verify the above as follows:
Make sure domU net is quiet...

In dom0 "watch -n 1 brctl showmacs vlanXXXX-br".
Note the port containing "vif0.0 mac".
In domU "ping non-existing-addr-on-domU-lan" on other console/xterm/...
If you see "veth0 mac" on other port than "vif0.0 mac", the patches from
comment #12 helps

Regards,
/Kristian Høgh


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs