[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Re: [Xen-users] Cannot ping from dom0 to domU and vice versa



Hi Ernst

Can you please also let me know how do I enslave eth1 to xen-br0

Regards
Srini 


On Thu, 22 Sep 2005 Ernst Bachmann wrote :
>On Thursday 22 September 2005 18:10, Srinivasan S wrote:
>...
> > vif= ['mac=aa:00:10:00:00:10, bridge=xen-br0']
> > ip = "192.168.2.2"
>...
>
> > Boots and allows me to login .. then I tried to ping the dom0 from domU and
> > it didnt work.  Heres the ifconfig from domU:
> >
> > eth0      Link encap:Ethernet  HWaddr AA:00:10:00:00:10
> >          inet addr:192.168.2.2  Bcast:192.168.2.255  Mask:255.255.255.0
>
>...
>
> > Heres the ifconfig from dom0, I have 2 nics one local n/w (eth1) and the
> > other for the internet via router (eth0):
> >
> > eth0      Link encap:Ethernet  HWaddr 00:50:BA:08:43:4C
> >          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
> >
> > eth1      Link encap:Ethernet  HWaddr 00:0E:A6:15:8D:FB
> >          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
> >
> > xen-br0  Link encap:Ethernet  HWaddr 00:50:BA:08:43:4C
> >          inet addr:192.168.1.100  Bcast:192.168.1.255
> >
> > Please let me know how I get the two doms to ping each other
>
>Well, simple routing problem:
>
>your xen-br0 bridge has eth0 enslaved, and thus is in the 192.168.1.* subnet,
>while your domU think it has a 192.168.2.* subnet, and ip inside it.
>
>you'll probably want to enslave eth1 to xen-br0 instead of eth0, but giving
>domU a 192.168.1.x IP address would work, too.
>
>/Ernst



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.