[Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging?

[David Levinger]

Thanks to both of you guys for helping me out with this! I think I've
gotten the idea and now have eth0 up and functional in the way you
described!

However, I realized that there is one additional thing that I would like
to do and that is have eth0 and eth1 bonded together and have the Xen
machines use that bond just like they are currently using the eth0
device. 

I tried doing this in the way that I normally would, bonding them
together, however, it didn't seem happy afterward. Have either of you
guys done that and if so are there some gotchas I might have missed?

Either way, thank you so much for helping me out with this and
explaining it! It is very much appreciated!

David

-----Original Message-----
From: Dale Bewley [mailto:dlbewley at lib.ucdavis.edu] 
Sent: Friday, November 30, 2007 2:27 PM
To: David Levinger
Cc: fedora-xen at redhat.com
Subject: Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging?

----- "David Levinger" <davidl at matissenetworks.com> wrote:
> Thank Dale for your quick reply! I've definitely started to realize
> that
> libvirt was what was creating the 192.168.122 subnet but I'm still
> unclear on what I'd need to do to go back to something like xenbr0.
> 
> What would I end up putting into /etc/sysconfi/network-scripts after
> changing the line to /bin/true that would allow my xen guests to just
> get IPs on the same subnet that the host is on. Just passing
> communication through.
> 
> Thanks again and my apologies if this sounds like a stupid question
> :-)
> 
> David

I have a bridge on VLAN 6 so I call it br6 you can use xenbr0 is you
like. Mine mostly looks something like this after removing the VLAN
trunk complication:

# cat ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
BRIDGE=br6

# cat ifcfg-br6
DEVICE=br6
TYPE=Bridge
BOOTPROTO=static
ONBOOT=yes
IPADDR=10.10.6.1
NETMASK=255.255.255.0
NETWORK=10.10.6.0
BROADCAST=10.10.6.255

Now your primary IP of your dom0 lives on the br6 interface. Your domU's
will be on the same VLAN and should see your DHCP server. Don't forget
to enable IP forwarding.

# grep phys /etc/sysconfig/iptables
-A FORWARD -m physdev  --physdev-is-bridged -j ACCEPT

# grep forward /etc/sysctl.conf
# Controls IP packet forwarding
net.ipv4.ip_forward = 1

p.s. use 'brctl show' to see your bridges.
--
Dale Bewley - Unix Administrator - Shields Library - UC Davis
GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD  1753 064D 2583 B098 A0F3



************************************************************************
****
            Checked by MailWasher server (www.Firetrust.com)
                WARNING. No FirstAlert account found.
             To reduce spam further activate FirstAlert.
    This message can be removed by purchasing a FirstAlert Account.
************************************************************************
****