[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Has anyone successfully configured Xen to work with...
On Wed, Dec 07, 2005 at 12:40:17AM -0800, Bill Kelly wrote: > Hi, > > Has anyone successfully configured Xen to work with a server having: > > 1 NIC. > Multiple IPs. (e.g. 69.93.218.2, 69.93.218.3, 69.93.218.4, ...) > dom0 using one IP. (e.g. 69.93.218.2) > domU using another IP. (e.g. 69.93.218.3) This is a fairly normal config when bridging, since the eth0 and all vifs are going to be on the same layer 2 network they can all take addresses from the same network. Paste output of: ifconfig -a brctl show ip ro For example: eth0 Link encap:Ethernet HWaddr 00:E0:81:64:1D:07 inet addr:212.13.198.69 Bcast:212.13.198.255 Mask:255.255.255.224 xen-br0 Link encap:Ethernet HWaddr 00:E0:81:64:1D:07 inet addr:212.13.198.69 Bcast:212.13.198.255 Mask:255.255.255.255 $ brctl show bridge name bridge id STP enabled interfaces xen-br0 8000.00e081641d07 no eth0 vif-struggler.0 $ ip ro 212.13.198.64/27 dev xen-br0 proto kernel scope link src 212.13.198.69 default via 212.13.198.65 dev xen-br0 and in the domU connected to vif-struggler.0: eth0 Link encap:Ethernet HWaddr AA:00:00:4B:A0:C1 inet addr:212.13.198.70 Bcast:212.13.198.255 Mask:255.255.255.224 212.13.198.69/27 and 212.13.198.70/27 are obviously both on the same layer 2 network (212.13.198.64 -> 212.13.198.95), nothing special needed to be done to make the bridging work. Make sure you aren't adding the IP of your domU to any interface in dom0. Andy Attachment:
signature.asc _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |