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

Re: [Xen-users] Re: DomU network configuration problem


  • To: shubham <shubham.sharma@xxxxxx>
  • From: Tej <bewith.tej@xxxxxxxxx>
  • Date: Mon, 11 Aug 2008 15:00:01 +0530
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 11 Aug 2008 02:30:38 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=gEmtGjDtwV7phZ4K+o3CgSkXjfpL5vuBnWyxYTo4lgSFtlytE7inyvIlCXYGGCFg71 +xbv08UohLKaH7AVLxXhB7GTb9zAp+GVL5XkJX6aDbgbw8F2/tarrMzQW/3E9W+t+Pqb +dqbWoFOxv+Fm3juAW4BuuO9j/4KLl8+uFDGA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On 8/11/08, shubham <shubham.sharma@xxxxxx> wrote:
> ---------------8<------------------
>>
>> You can do following steps:
>>
>> 1. Assign any private IP to your DomU
>> 2. Assign the subnet gateway to the domU, above vuf configuration is
>> fine i guess.
>>
>> 3. Now as dom0 is on different subnet, create the eth0 (i assume here
>> that eth0 domU and eth0 of dom0 is connected to xenbr0 ) alias as a
>> gateway for domU.
>>     In dom0:
>>     ifconfig eth0 add domU-gateway netmask.
>> 4. Now that gateway should be pingable
>> 5. Now add the forwarding rules
>>     echo 1 >/procsys/net/ipv4/ip_forward
>>    Now you should be able to ping the eth0 on dom0.
>> 6. Add the masq rule as above.
>>    iptables -t nat -A POSTROUTING -j MASQUERADE (use the eth0 address)
>> 7. Now you should be able to ping google.com
>>
>> HTH
>>
>> -tej
> -------------------8<--------------
>
> i tried these instructions but i could not proceed till step 4.
> i was not able to ping the gateway from domU.

only one reason i could see xenbridge is not connecting dom0 and domU

ensure this connectivity using brctl show:

xenbr0           8000.xxxxx     no                vif0.0
                                                               peth0
                                                               vif<domU-id>.0
if not eth0.0 will not be pingable.

try this if still problem  post following
1. domU ifconfig & route -n
2. dom0 ifconfig & route -n
3. brctl show

-tej


>
> is there any method to know that the eth0 of domU is connected to xenbr0
>
> one more information that i missed out last time was that i am using full
> virtualization. so i just want to confirm that are the above steps fine
> for full virtualization as well?
>
>
>
>
>> > _______________________________________________
>> > Xen-users mailing list
>> > Xen-users <at> lists.xensource.com
>> > http://lists.xensource.com/xen-users
>> >
>>
>
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

_______________________________________________
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®.