[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#666386: more info



On Mon, Sep 03, 2012 at 06:27:12PM +0200, Josip Rodin wrote:
> On Sun, Sep 02, 2012 at 02:42:38PM +0100, Ben Hutchings wrote:
> > On Sat, 2012-09-01 at 10:45 +0200, Bastian Blank wrote:
> > > On Fri, Aug 31, 2012 at 05:52:03PM +0200, Josip Rodin wrote:
> > > > auto vlan2
> > > > iface vlan2 inet manual
> > > >   vlan-raw-device xenbr0
> > > 
> > > Is vlan-over-bridge documented to be supported?
> > 
> > If it was not supported then bridge devices would have
> > NETIF_F_VLAN_CHALLENGED and you would not be able to create VLAN devices
> > on top of them.  But I don't expect this to work *well* at present.
> > 
> > Rebooting, however... something is very wrong here.
> > 
> > > Usually I would use:
> > > | iface xenbr2 inet static
> > > |   bridge-ports bond0.2
> > > 
> > > > But as soon as I generate any traffic to or from 192.168.54.0/24 and that
> > > > virtual machine (notice - not the right VLAN), the whole system instantly
> > > > reboots, with no messages in syslog.
> > > 
> > > Does it work without bond?
> 
> Ah, good catch, I do actually seem to want to use the underlying device for
> vlan, rather than the bridge device. All my other setups are like that.

Confirming it works with fixed vlan-raw-device, pointed to eth2. I should
test with bond now, that was probably it...

-- 
     2. That which causes joy or happiness.


Reply to: