[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] 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@xxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxx] On Behalf Of Alexandre Kouznetsov Sent: Mittwoch, 14. August 2013 21:02 To: xen-users@xxxxxxxxxxxxx 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@xxxxxxxxxxxxx http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |