On 07/06/10 14:21, Fajar A. Nugraha wrote:
> On Tue, Jul 6, 2010 at 8:51 PM, Net Warrior <netwarrior863@xxxxxxxxx> wrote:
>
>>> IF, like you said:
>>> - eth0 on dom0 is configured via DHCP
>>> - domU is on eth0 bridge
>>>
>>> Then domU should be configured using DHCP as well. It should end up in
>>> the SAME network address as dom0, AND have the same DNS/gateway
>>> parameters. In other words, domU will behave like ANOTHER physical
>>> host on the same network as dom0.
>>>
>
>> Well, no luck yet.
>>
>
>> Dom0
>> netwarrior xen # ifconfig
>> eth0 Link encap:Ethernet HWaddr 00:21:86:94:c5:c0
>> inet addr:186.18.132.141 Bcast:0.0.0.0 Mask:255.255.252.0
>>
>
>> ubuntu904 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
>> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
>>
> Okay, lets's try some experiments.
> First, make sure that /proc/sys/net/ipv4/ip_forward is set to 1 on dom0.
> Next, your dom0 is using 186.18.132.141, with netmask of
> 255.255.252.0. Therefore, your domU IP address should also be in that
> IP range. Try using static configuration on domU first, something like
> 186.18.132.142 (ping from dom0 first to make sure the address is
> unused). Then test pinging dom0 -> domU and domU -> dom0. If it
> doesn't work, while pinging, do a "tcpdump -n -i eth0 host
> 186.18.132.142" on both dom0 and domU. That should at least give some
> idea of what's going on.
>
>
Sorry for the delay, had some personal issues.
Well, after all I had some issues with my router which I was able to
solve, now I can connect the DomU to internet via
dhcp as you mentioned before.
Thanks for your time and support!!!
Regards
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|