thr3ads.net - Xen users - xen 4.3 - bridge with bonding under Debian Wheezy [Aug 2013]

If this information is useful, please help other people find it:
Share via:

Walter Robert Ditzler

2013-Aug-14 10:49 UTC

xen 4.3 - bridge with bonding under Debian Wheezy

Hi all,

i have a xen 4.3 installation and would like to have a bridge bond szenario:

***
eth0        eth1
    |              |
        bond0
             |
           br0
             |
vif             = [ ''bridge=br0,mac=xx:xx:xx:xx:xx:xx'' ]
***

With the network script in debian wheezy

***
/etc/network/interfaces
auto bond0
iface bond0 inet manual
  slaves eth0 eth1
  bond-mode 0

auto br0
iface br0 inet static
  address 100.x.x.x
  netmask 255.255.255.0
  network 100.x.x.0
  broadcast 100.x.x.255
  gateway 100.x.x.19
  bridge_ports bond0
  bond-miimon        100
  bond-lacp_rate     1
  bond-downdelay     200
  bond-updelay       200
  address            0.0.0.0
  netmask            0.0.0.0
***

***
/etc/sysctl.conf

#kernel.printk = 3 4 1 3
#net.ipv4.conf.default.rp_filter=1
#net.ipv4.conf.all.rp_filter=1
#net.ipv4.tcp_syncookies=1
net.ipv4.ip_forward=1
#net.ipv4.conf.br0.proxy_arp=1
#net.ipv4.conf.eth0.proxy_arp=1
#net.ipv4.conf.eth1.proxy_arp=1
#net.ipv6.conf.all.forwarding=1
#net.ipv4.conf.all.accept_redirects = 0
#net.ipv6.conf.all.accept_redirects = 0
#net.ipv4.conf.all.send_redirects = 0
#net.ipv4.conf.all.accept_source_route = 0
#net.ipv6.conf.all.accept_source_route = 0
#net.ipv4.conf.all.log_martians = 1
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
***

Any idea what I''m doing wrong here??????

Thanks a lot,

Walter

Alexandre Kouznetsov

2013-Aug-14 19:02 UTC

head link

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Hello.

Some observations.

El 14/08/13 05:49, Walter Robert Ditzler escribió:> Hi all,
>
> i have a xen 4.3 installation and would like to have a bridge bond
szenario:
>
> ***
> eth0        eth1
>      |              |
>          bond0
>               |
>             br0
>               |
> vif             = [ ''bridge=br0,mac=xx:xx:xx:xx:xx:xx'' ]
> ***Looks good, should work.

> With the network script in debian wheezy
>
> ***
> /etc/network/interfaces
> auto bond0
> iface bond0 inet manual
>    slaves eth0 eth1
>    bond-mode 0
>
> auto br0
> iface br0 inet static
>    address 100.x.x.x
>    netmask 255.255.255.0
>    network 100.x.x.0
>    broadcast 100.x.x.255
>    gateway 100.x.x.19
>    bridge_ports bond0
>    bond-miimon        100
>    bond-lacp_rate     1
>    bond-downdelay     200
>    bond-updelay       200
>    address            0.0.0.0
>    netmask            0.0.0.0
> ***
Specifically about br0 section:

You mention "address" and "netmask" parameters twice.

All bond-* parameters don''t belong here, they should be used in the 
section that describes bond0, not br0.

bond-lacp_rate parameter makes sense only for bond mode 4 (aka 802.3ad), 
you seem to be using mode 0 (aka balance-rr).

> ***
> /etc/sysctl.conf
>
> #kernel.printk = 3 4 1 3
> #net.ipv4.conf.default.rp_filter=1
> #net.ipv4.conf.all.rp_filter=1
> #net.ipv4.tcp_syncookies=1
> net.ipv4.ip_forward=1
> #net.ipv4.conf.br0.proxy_arp=1
> #net.ipv4.conf.eth0.proxy_arp=1
> #net.ipv4.conf.eth1.proxy_arp=1
> #net.ipv6.conf.all.forwarding=1
> #net.ipv4.conf.all.accept_redirects = 0
> #net.ipv6.conf.all.accept_redirects = 0
> #net.ipv4.conf.all.send_redirects = 0
> #net.ipv4.conf.all.accept_source_route = 0
> #net.ipv6.conf.all.accept_source_route = 0
> #net.ipv4.conf.all.log_martians = 1
> net.bridge.bridge-nf-call-ip6tables = 0
> net.bridge.bridge-nf-call-iptables = 0
> net.bridge.bridge-nf-call-arptables = 0
> ***Not sure it this net.bridge.bridge-nf-call*=0 are needed.
> Any idea what I''m doing wrong here??????Maybe you are mixing configurations from different reference sources, 
that describes different scenarios?



-- 
Alexandre Kouznetsov

Walter Robert Ditzler

2013-Aug-15 15:13 UTC

head link

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Sorry,

Copy Paste Error here: the interface file looks like that:

 auto bond0
 iface bond0 inet manual
    slaves eth0 eth1
    bond-mode 0
    bond-miimon        100
    bond-lacp_rate     1
    bond-downdelay     200
    bond-updelay       200

 auto br0
 iface br0 inet static
    address 100.x.x.x
    netmask 255.255.255.0
    network 100.x.x.0
    broadcast 100.x.x.255
    gateway 100.x.x.19
    bridge_ports bond0
    address            0.0.0.0
    netmask            0.0.0.0

Plus I think XEN has changed the HVM simulated network card. I moved a Guest
from XEN 4.2.1 to 4.3 and I had a hell with my Windows 2012 Guest, Linux
Debian Guest too!!!!

Can it be possible that XEN 4.3 is still just too buggy?

Thanks Walter.

-----Original Message-----
From: xen-users-bounces@lists.xen.org
[mailto:xen-users-bounces@lists.xen.org] On Behalf Of Alexandre Kouznetsov
Sent: Mittwoch, 14. August 2013 21:02
To: xen-users@lists.xen.org
Subject: Re: [Xen-users] xen 4.3 - bridge with bonding under Debian Wheezy

Hello.

Some observations.

El 14/08/13 05:49, Walter Robert Ditzler escribió:> Hi all,
>
> i have a xen 4.3 installation and would like to have a bridge bond
szenario:>
> ***
> eth0        eth1
>      |              |
>          bond0
>               |
>             br0
>               |
> vif             = [ ''bridge=br0,mac=xx:xx:xx:xx:xx:xx'' ]
> ***Looks good, should work.

> With the network script in debian wheezy
>
> ***
> /etc/network/interfaces
> auto bond0
> iface bond0 inet manual
>    slaves eth0 eth1
>    bond-mode 0
>
> auto br0
> iface br0 inet static
>    address 100.x.x.x
>    netmask 255.255.255.0
>    network 100.x.x.0
>    broadcast 100.x.x.255
>    gateway 100.x.x.19
>    bridge_ports bond0
>    bond-miimon        100
>    bond-lacp_rate     1
>    bond-downdelay     200
>    bond-updelay       200
>    address            0.0.0.0
>    netmask            0.0.0.0
> ***
Specifically about br0 section:

You mention "address" and "netmask" parameters twice.

All bond-* parameters don''t belong here, they should be used in the
section
that describes bond0, not br0.

bond-lacp_rate parameter makes sense only for bond mode 4 (aka 802.3ad), you
seem to be using mode 0 (aka balance-rr).

> ***
> /etc/sysctl.conf
>
> #kernel.printk = 3 4 1 3
> #net.ipv4.conf.default.rp_filter=1
> #net.ipv4.conf.all.rp_filter=1
> #net.ipv4.tcp_syncookies=1
> net.ipv4.ip_forward=1
> #net.ipv4.conf.br0.proxy_arp=1
> #net.ipv4.conf.eth0.proxy_arp=1
> #net.ipv4.conf.eth1.proxy_arp=1
> #net.ipv6.conf.all.forwarding=1
> #net.ipv4.conf.all.accept_redirects = 0
> #net.ipv6.conf.all.accept_redirects = 0
> #net.ipv4.conf.all.send_redirects = 0
> #net.ipv4.conf.all.accept_source_route = 0
> #net.ipv6.conf.all.accept_source_route = 0
> #net.ipv4.conf.all.log_martians = 1
> net.bridge.bridge-nf-call-ip6tables = 0
> net.bridge.bridge-nf-call-iptables = 0
> net.bridge.bridge-nf-call-arptables = 0
> ***Not sure it this net.bridge.bridge-nf-call*=0 are needed.
> Any idea what I''m doing wrong here??????Maybe you are mixing configurations from different reference sources, 
that describes different scenarios?



-- 
Alexandre Kouznetsov

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Walter Robert Ditzler

2013-Aug-15 15:19 UTC

head link

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Sorry,

Copy Paste Error here: the interface file looks like that:

 auto bond0
 iface bond0 inet manual
    slaves eth0 eth1
    bond-mode 0
    bond-miimon        100
    bond-lacp_rate     1
    bond-downdelay     200
    bond-updelay       200
    address            0.0.0.0
    netmask            0.0.0.0

 auto br0
 iface br0 inet static
    address 100.x.x.x
    netmask 255.255.255.0
    network 100.x.x.0
    broadcast 100.x.x.255
    gateway 100.x.x.19
    bridge_ports bond0

Plus I think XEN has changed the HVM simulated network card. I moved a Guest
from XEN 4.2.1 to 4.3 and I had a hell with my Windows 2012 Guest, Linux
Debian Guest too!!!!

Can it be possible that XEN 4.3 is still just too buggy?

Thanks Walter.

-----Original Message-----
From: xen-users-bounces@lists.xen.org
[mailto:xen-users-bounces@lists.xen.org] On Behalf Of Alexandre Kouznetsov
Sent: Mittwoch, 14. August 2013 21:02
To: xen-users@lists.xen.org
Subject: Re: [Xen-users] xen 4.3 - bridge with bonding under Debian Wheezy

Hello.

Some observations.

El 14/08/13 05:49, Walter Robert Ditzler escribió:> Hi all,
>
> i have a xen 4.3 installation and would like to have a bridge bond
szenario:>
> ***
> eth0        eth1
>      |              |
>          bond0
>               |
>             br0
>               |
> vif             = [ ''bridge=br0,mac=xx:xx:xx:xx:xx:xx'' ]
> ***Looks good, should work.

> With the network script in debian wheezy
>
> ***
> /etc/network/interfaces
> auto bond0
> iface bond0 inet manual
>    slaves eth0 eth1
>    bond-mode 0
>
> auto br0
> iface br0 inet static
>    address 100.x.x.x
>    netmask 255.255.255.0
>    network 100.x.x.0
>    broadcast 100.x.x.255
>    gateway 100.x.x.19
>    bridge_ports bond0
>    bond-miimon        100
>    bond-lacp_rate     1
>    bond-downdelay     200
>    bond-updelay       200
>    address            0.0.0.0
>    netmask            0.0.0.0
> ***
Specifically about br0 section:

You mention "address" and "netmask" parameters twice.

All bond-* parameters don''t belong here, they should be used in the
section
that describes bond0, not br0.

bond-lacp_rate parameter makes sense only for bond mode 4 (aka 802.3ad), you
seem to be using mode 0 (aka balance-rr).

> ***
> /etc/sysctl.conf
>
> #kernel.printk = 3 4 1 3
> #net.ipv4.conf.default.rp_filter=1
> #net.ipv4.conf.all.rp_filter=1
> #net.ipv4.tcp_syncookies=1
> net.ipv4.ip_forward=1
> #net.ipv4.conf.br0.proxy_arp=1
> #net.ipv4.conf.eth0.proxy_arp=1
> #net.ipv4.conf.eth1.proxy_arp=1
> #net.ipv6.conf.all.forwarding=1
> #net.ipv4.conf.all.accept_redirects = 0 
> #net.ipv6.conf.all.accept_redirects = 0 
> #net.ipv4.conf.all.send_redirects = 0 
> #net.ipv4.conf.all.accept_source_route = 0 
> #net.ipv6.conf.all.accept_source_route = 0 
> #net.ipv4.conf.all.log_martians = 1 
> net.bridge.bridge-nf-call-ip6tables = 0 
> net.bridge.bridge-nf-call-iptables = 0 
> net.bridge.bridge-nf-call-arptables = 0
> ***Not sure it this net.bridge.bridge-nf-call*=0 are needed.
> Any idea what I''m doing wrong here??????Maybe you are mixing configurations from different reference sources, that
describes different scenarios?



-- 
Alexandre Kouznetsov

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Ian Campbell

2013-Aug-15 15:49 UTC

head link

Re: xen 4.3 - bridge with bonding under Debian Wheezy

On Thu, 2013-08-15 at 17:19 +0200, Walter Robert Ditzler
wrote:> Plus I think XEN has changed the HVM simulated network card. I moved a
Guest
> from XEN 4.2.1 to 4.3 and I had a hell with my Windows 2012 Guest, Linux
> Debian Guest too!!!!
4.3 switched the default device model to use the upstream version of
qemu, which I think emulates a slightly different set of peripherals.

If your guest OSes don''t like this change then you can add 
        device_model_version = "qemu-xen-traditional"
to your xl configuration file to go back to the older version.

Ian

Ian Campbell

2013-Aug-15 15:59 UTC

head link

Re: xen 4.3 - bridge with bonding under Debian Wheezy

On Thu, 2013-08-15 at 17:19 +0200, Walter Robert Ditzler
wrote:> Sorry,
> 
> Copy Paste Error here: the interface file looks like that:
> 
>  auto bond0
>  iface bond0 inet manual
manual? doesn''t that mean you need up and down stanzas to actually do
the work since ifup won''t do anything?

Perhaps you need static here instead?

"ifup -v br0" will show you exactly which commands are run.

Ian.

Alexandre Kouznetsov

2013-Aug-15 23:21 UTC

head link

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Hello.

El 15/08/13 10:59, Ian Campbell escribió:> On Thu, 2013-08-15 at 17:19 +0200, Walter Robert Ditzler wrote:
>> Sorry,
>>
>> Copy Paste Error here: the interface file looks like that:
>>
>>   auto bond0
>>   iface bond0 inet manual
>
> manual? doesn''t that mean you need up and down stanzas to actually
do
> the work since ifup won''t do anything?
This is a copy-paste from my production, Debian Squeeze. Just works:

auto bond0
iface bond0 inet manual
   slaves eth2 eth3 eth4 eth5
   bond-mode 802.3ad
   bond-miimon 100
   bond-updelay 100
   bond-downdelay 200

auto xenbr16
iface xenbr16 inet manual
#  bridge_ports eth0.16
   bridge_ports bond0.16
   bridge_stp off
   bridge_maxwait 0
   bridge_fd 5

If the mode is set to "static", ifupdown scripts get scared because of
lack of IP address and netmask definitions.
As I understand it, the bond is actually assembled due to "slaves" 
keyword and the change to "UP" state is done implicitly somewhere
else.

Walter, note that in your case, you better use "static" in the bridge 
definition, because you do want to specify address and netmask. Those 
parameters are not needed in your bond definition.
Also, it would be nice to know what error do you get when trying to 
bring up the interfaces. Comment out "auto" keyword and bring them up 
manually first, in the correct order. Watch for errors, they shall tell 
you what is wrong. Once it''s working, enable auto back.

Greetings.

-- 
Alexandre Kouznetsov

Shane Johnson

2013-Aug-20 20:40 UTC

head link

Re: xen 4.3 - bridge with bonding under Debian Wheezy

On Thu, Aug 15, 2013 at 5:21 PM, Alexandre Kouznetsov <alk@ondore.com>
wrote:

<snip>> the interfaces. Comment out "auto" keyword and bring them up
manually first,
> in the correct order. Watch for errors, they shall tell you what is wrong.
> Once it''s working, enable auto back.
>
> Greetings.
>
> --
> Alexandre Kouznetsov
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
Did you ever get this resolved?  I have a machine with 4 NICS in it
that I tried to bond and use with the bridging and I found that all
the communication from the DOMU was blocked.  DOM0 was fine.  I was
going to look into this again and was hoping you might have some
insight.

Thanks


-- 
Shane D. Johnson
IT Administrator
Rasmussen Equipment

Alexandre Kouznetsov

2013-Aug-20 21:52 UTC

head link

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Hello.

El 20/08/13 15:40, Shane Johnson escribió:> On Thu, Aug 15, 2013 at 5:21 PM, Alexandre Kouznetsov
<alk@ondore.com> wrote:
>
> <snip>
>> the interfaces. Comment out "auto" keyword and bring them up
manually first,
>> in the correct order. Watch for errors, they shall tell you what is
wrong.
>> Once it''s working, enable auto back.
>>
>> [...]
>
> Did you ever get this resolved?  I have a machine with 4 NICS in it
> that I tried to bond and use with the bridging and I found that all
> the communication from the DOMU was blocked.  DOM0 was fine.  I was
> going to look into this again and was hoping you might have some
> insight.
If you are asking me, I do have a working setup, but on Debian Squeeze 
(see no hurry to upgrade). I would not expect it to be different on Wheezy.

The thing that might be different, is that are at least two ways of 
doing link aggregation with Xen (AFAIK). One is to create the bond with 
ifenslave (ifupdown serves as a nice wrapper to it), and then attach it 
to a bridge, this is the one I use. The other is to incorporate the 
physical interfaces directly to a bridge and manage them via Open 
vSwitch, this is the one I have not played with yet. For example, 
XenServer (and XCP) uses Open vSwitch.

Greetings.

-- 
Alexandre Kouznetsov

Walter Robert Ditzler

2013-Aug-20 21:59 UTC

head link

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Hi,

not solved yet!

I mean bond mode 1 works, but it uses only 1 card at once. What I need is
bond mode 0 or 3, that never worked out for me.

When I am on the console, 1 and 3 works, but not from any guest system via
br0!

Thanks,

Walter.


auto br0
iface br0 inet static
  address            10.41.15.41
  netmask            255.255.255.0
  bridge_ports       bond0
  bridge_maxwait     0
  pre-up             ifup bond0
  post-down          ifdown bond0

iface bond0 inet static
  bond-mode          1
  bond-miimon        100
  bond-lacp_rate     1
  bond-downdelay     200
  bond-updelay       200
  address            0.0.0.0
  netmask            0.0.0.0
  slaves             eth1 eth2

-----Original Message-----
From: xen-users-bounces@lists.xen.org
[mailto:xen-users-bounces@lists.xen.org] On Behalf Of Shane Johnson
Sent: Dienstag, 20. August 2013 22:41
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] xen 4.3 - bridge with bonding under Debian Wheezy

On Thu, Aug 15, 2013 at 5:21 PM, Alexandre Kouznetsov <alk@ondore.com>
wrote:

<snip>> the interfaces. Comment out "auto" keyword and bring them up
manually
> first, in the correct order. Watch for errors, they shall tell you what is
wrong.> Once it''s working, enable auto back.
>
> Greetings.
>
> --
> Alexandre Kouznetsov
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
Did you ever get this resolved?  I have a machine with 4 NICS in it that I
tried to bond and use with the bridging and I found that all the
communication from the DOMU was blocked.  DOM0 was fine.  I was going to
look into this again and was hoping you might have some insight.

Thanks


--
Shane D. Johnson
IT Administrator
Rasmussen Equipment

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Shane Johnson

2013-Aug-21 14:11 UTC

head link

Re: xen 4.3 - bridge with bonding under Debian Wheezy

On Tue, Aug 20, 2013 at 3:52 PM, Alexandre Kouznetsov <alk@ondore.com>
wrote:
<snip>>
> If you are asking me, I do have a working setup, but on Debian Squeeze (see
> no hurry to upgrade). I would not expect it to be different on Wheezy.
>
> The thing that might be different, is that are at least two ways of doing
> link aggregation with Xen (AFAIK). One is to create the bond with ifenslave
> (ifupdown serves as a nice wrapper to it), and then attach it to a bridge,
> this is the one I use. The other is to incorporate the physical interfaces
> directly to a bridge and manage them via Open vSwitch, this is the one I
> have not played with yet. For example, XenServer (and XCP) uses Open
> vSwitch.
>
> Greetings.
>
> --
> Alexandre Kouznetsov
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
Alexandre,
Thank you for the information.
If you don''t mind I have a couple of questions.
What level did you set up your bond for?
Is your DOMU PV or HVM?
Did you have to do anything special to make your method work?
I created my bond and bridge in /etc/network/interfaces with eht0-eth3
in bond0(level 6) and then used bond0 for the bridge.  From what you
said, this sounds like I did it right.  But every time I tried, the
DOMU said it was connected to the internet, but wouldn''t communicate
with anything on the network.  DOM0 worked fine.

Thank you.

-- 
Shane D. Johnson
IT Administrator
Rasmussen Equipment

Alexandre Kouznetsov

2013-Aug-21 15:23 UTC

head link

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Hello.

El 21/08/13 09:11, Shane Johnson escribió:> On Tue, Aug 20, 2013 at 3:52 PM, Alexandre Kouznetsov
<alk@ondore.com> wrote:
> <snip>
>>
>> If you are asking me, I do have a working setup, but on Debian Squeeze
(see
>> no hurry to upgrade). I would not expect it to be different on Wheezy.
>>
>> The thing that might be different, is that are at least two ways of
doing
>> link aggregation with Xen (AFAIK). One is to create the bond with
ifenslave
>> (ifupdown serves as a nice wrapper to it), and then attach it to a
bridge,
>> this is the one I use. The other is to incorporate the physical
interfaces
>> directly to a bridge and manage them via Open vSwitch, this is the one
I
>> have not played with yet. For example, XenServer (and XCP) uses Open
>> vSwitch.
>>
>> Greetings.
>>
>> --
>> Alexandre Kouznetsov
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users
>
> Alexandre,
> Thank you for the information.
> If you don''t mind I have a couple of questions.
> What level did you set up your bond for?Don''t mind at all. I use "mode 4" aka 802.3ad.
> Is your DOMU PV or HVM?It works with PV DomUs, but I recall using HVM DomUs with this setup as 
well.
> Did you have to do anything special to make your method work?Not really, was little bit surprising. There is even another layer on 
top of this, VLAN over bond.
> I created my bond and bridge in /etc/network/interfaces with eht0-eth3
> in bond0(level 6) and then used bond0 for the bridge.  From what you
> said, this sounds like I did it right.  But every time I tried, the
> DOMU said it was connected to the internet, but wouldn''t
communicate
> with anything on the network.  DOM0 worked fine.Sounds like to blame the firewall, but I guess it works with plain 
interfaces without special netfilter configuration. I use a custom 
iptables script to set the policy to DROP and allow only specific 
things. This are the lines relevant for bridge forwarding on my Dom0:
iptables -A FORWARD -m physdev --physdev-in  vif+ -j ACCEPT
iptables -A FORWARD -m physdev --physdev-out vif+ -j ACCEPT
The DomUs has their own firewalling rules.

The console complains about it:
"physdev match: using --physdev-out in the OUTPUT, FORWARD and 
POSTROUTING chains for non-bridged traffic is not supported anymore."
But since it''s intended for bridged traffic, it works fine.

Have you tried to debug your setup with tcpdump?

-- 
Alexandre Kouznetsov

Shane Johnson

2013-Aug-21 15:37 UTC

head link

Re: xen 4.3 - bridge with bonding under Debian Wheezy

On Wed, Aug 21, 2013 at 9:23 AM, Alexandre Kouznetsov <alk@ondore.com>
wrote:> Hello.
>
> El 21/08/13 09:11, Shane Johnson escribió:
>
>> On Tue, Aug 20, 2013 at 3:52 PM, Alexandre Kouznetsov
<alk@ondore.com>
>> wrote:
>> <snip>
>>>
>>>
>>> If you are asking me, I do have a working setup, but on Debian
Squeeze
>>> (see
>>> no hurry to upgrade). I would not expect it to be different on
Wheezy.
>>>
>>> The thing that might be different, is that are at least two ways of
doing
>>> link aggregation with Xen (AFAIK). One is to create the bond with
>>> ifenslave
>>> (ifupdown serves as a nice wrapper to it), and then attach it to a
>>> bridge,
>>> this is the one I use. The other is to incorporate the physical
>>> interfaces
>>> directly to a bridge and manage them via Open vSwitch, this is the
one I
>>> have not played with yet. For example, XenServer (and XCP) uses
Open
>>> vSwitch.
>>>
>>> Greetings.
>>>
>>> --
>>> Alexandre Kouznetsov
>>>
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@lists.xen.org
>>> http://lists.xen.org/xen-users
>>
>>
>> Alexandre,
>> Thank you for the information.
>> If you don''t mind I have a couple of questions.
>> What level did you set up your bond for?
>
> Don''t mind at all. I use "mode 4" aka 802.3ad.
>
>
>> Is your DOMU PV or HVM?
>
> It works with PV DomUs, but I recall using HVM DomUs with this setup as
> well.
>
>
>> Did you have to do anything special to make your method work?
>
> Not really, was little bit surprising. There is even another layer on top
of
> this, VLAN over bond.
>
>
>> I created my bond and bridge in /etc/network/interfaces with eht0-eth3
>> in bond0(level 6) and then used bond0 for the bridge.  From what you
>> said, this sounds like I did it right.  But every time I tried, the
>> DOMU said it was connected to the internet, but wouldn''t
communicate
>> with anything on the network.  DOM0 worked fine.
>
> Sounds like to blame the firewall, but I guess it works with plain
> interfaces without special netfilter configuration. I use a custom iptables
> script to set the policy to DROP and allow only specific things. This are
> the lines relevant for bridge forwarding on my Dom0:
> iptables -A FORWARD -m physdev --physdev-in  vif+ -j ACCEPT
> iptables -A FORWARD -m physdev --physdev-out vif+ -j ACCEPT
> The DomUs has their own firewalling rules.
>
> The console complains about it:
> "physdev match: using --physdev-out in the OUTPUT, FORWARD and
POSTROUTING
> chains for non-bridged traffic is not supported anymore."
> But since it''s intended for bridged traffic, it works fine.
>
> Have you tried to debug your setup with tcpdump?
>
>
> --
> Alexandre Kouznetsov
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
Nope haven''t had time to dig that far into it.  I will see what comes
up when I try it again.  Hopefully I will get to it within the next
day or so.  Thank you for the information.  Wish me luck.


-- 
Shane D. Johnson
IT Administrator
Rasmussen Equipment

Reasonably Related Threads

Search for more possibly parallel threads

Xen users - Aug 2013 - xen 4.3 - bridge with bonding under Debian Wheezy

xen 4.3 - bridge with bonding under Debian Wheezy

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Re: xen 4.3 - bridge with bonding under Debian Wheezy

Reasonably Related Threads