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 ma
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 docume
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
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?
Usually I would use:
| iface xenbr2 inet static
| bridge-ports bond0.2
> But as soon as I generate any traffic to or fr
Hi,
I had removed the igb-based eth0 from the bonding interface, and the machine
was running fine with it, but when the time had come to get some Xen domUs
running on it, it failed miserably on me once again.
The updated setup is:
auto bond0
iface bond0 inet manual
slaves eth2
bond_mode acti
5 matches
Mail list logo