Hiya, I''ve got a requirement and I can''t work out the right configuration. I''m running Xen 4.0 on Debian Squeeze. The Dom0 has two physical interfaces, one as an ''access'' port (I''ll be using Cisco terminology) and the other is a .1q trunk for up to 150 VLANs (don''t ask, long story). Some of the VLANs on this trunk are for managing the DomUs and as such I''ve created interfaces and bridges for each. The rest I want to pass on, as a trunk, to a DomU. The DomU will have a management interface which connects to one of the above management bridges and it should also have an interface connected to the trunk. I want to be able to listen to all the broadcast traffic on that trunk. I''ve tried treating each VLAN as an individual interface on the Dom0 but I can only get the DomU to connect to about 30 of them. Thus I''d need 5 DomUs at least to handle all the VLANs, which isn''t a nice solution. I''ve tried various attempts to connect the DomU interface to a bridge to the trunk but without much success. Can anyone help? So... Dom0 eth0 -> local management eth1 -> .1q trunk eth1.1 -> VLAN 1 DomU Ueth0 -> eth1.1 Ueth1 -> eth1 Thanks, Mike -- Mike Richardson Networks (network@manchester.ac.uk) IT Services, University of Manchester *Plain text only please - attachments stripped on arrival* _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mike Richardson wrote:>The Dom0 has two physical interfaces, one as an ''access'' port (I''ll >be using Cisco >terminology) and the other is a .1q trunk for up to 150 VLANs (don''t ask, >long story).I can guess> Some of the VLANs on this trunk are for managing the DomUs and >as such I''ve created interfaces and bridges for each. The rest I want to >pass on, as a trunk, to a DomU. > >The DomU will have a management interface which connects to one of the above >management bridges and it should also have an interface connected to the >trunk. I want to be able to listen to all the broadcast traffic on that >trunk. > >I''ve tried treating each VLAN as an individual interface on the Dom0 but I >can only get the DomU to connect to about 30 of them. Thus I''d need 5 DomUs >at least to handle all the VLANs, which isn''t a nice solution.AFAICT, Linux bridges don''t support tagged traffic. My reading suggests that Open vSwitch does (and lots more). It may be worth looking into that. -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hiya, > > I''ve got a requirement and I can''t work out the right configuration.I''m> running Xen 4.0 on Debian Squeeze. > > The Dom0 has two physical interfaces, one as an ''access'' port (I''ll beusing> Cisco > terminology) and the other is a .1q trunk for up to 150 VLANs (don''task, long> story). Some of the VLANs on this trunk are for managing the DomUs andas> such I''ve created interfaces and bridges for each. The rest I want topass on,> as a trunk, to a DomU. > > The DomU will have a management interface which connects to one of the > above management bridges and it should also have an interfaceconnected> to the trunk. I want to be able to listen to all the broadcast trafficon that> trunk.openvswitch is probably what you want. I just installed this on wheezy. I have a script that can pretend to be brctl (at least enough for the xen vif scripts) when you have openvswitch. Openvswitch comes with some sort of brctl compatibility layer but it doesn''t seem quite right for vlans. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Oct 05, 2011 at 09:28:34PM +1100, James Harper wrote:> > Hiya, > > > > I''ve got a requirement and I can''t work out the right configuration. > I''m > > running Xen 4.0 on Debian Squeeze. > > > > The Dom0 has two physical interfaces, one as an ''access'' port (I''ll be > using > > Cisco > > terminology) and the other is a .1q trunk for up to 150 VLANs (don''t > ask, long > > story). Some of the VLANs on this trunk are for managing the DomUs and > as > > such I''ve created interfaces and bridges for each. The rest I want to > pass on, > > as a trunk, to a DomU. > > > > The DomU will have a management interface which connects to one of the > > above management bridges and it should also have an interface > connected > > to the trunk. I want to be able to listen to all the broadcast traffic > on that > > trunk. > > openvswitch is probably what you want. I just installed this on wheezy. > I have a script that can pretend to be brctl (at least enough for the > xen vif scripts) when you have openvswitch. Openvswitch comes with some > sort of brctl compatibility layer but it doesn''t seem quite right for > vlans.Simon, James, Thanks, much appreciated. I''ll take a look at Open vSwitch, which is an interesting piece of software in its own right. Mike -- Mike Richardson Networks (network@manchester.ac.uk) IT Services, University of Manchester *Plain text only please - attachments stripped on arrival* _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mike Richardson <mike.richardson@manchester.ac.uk> writes:> The Dom0 has two physical interfaces, one as an ''access'' port (I''ll be > using Cisco terminology) and the other is a .1q trunk for up to 150 > VLANs (don''t ask, long story). Some of the VLANs on this trunk are for > managing the DomUs and as such I''ve created interfaces and bridges for > each. The rest I want to pass on, as a trunk, to a DomU. > > The DomU will have a management interface which connects to one of the > above management bridges and it should also have an interface > connected to the trunk. I want to be able to listen to all the > broadcast traffic on that trunk.You forgot to tell your precise problem. However, if you put a trunk interface (eth1) into a bridge, the bridge will suck up ALL packets (tagged and native) unless stopped by an appropriate ebtables rule. This manifests as NO traffic getting to the tagged interface (eth1.1). -- Regards, Feri. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users