| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] Cannot ping from dom0 to domU and vice versa
On Thu, 2005-09-22 at 16:10 +0000, Srinivasan S wrote:
> Hi
>
> I got a FC4 system running as Host. Within this I loaded Suse 10 as a
> guest OS, the config file is as below:
>
> kernel = "/boot/vmlinuz-2.6.11.12-xenU"
> memory = 100
> name = "suseguest"
> nics = 1
> vif= ['mac=aa:00:10:00:00:10, bridge=xen-br0']
> ip = "192.168.2.2"
> disk = ['file:/dev/hdc3,hdc3,w']
> root = "/dev/hdc3 rw"
> extra = "3"
>
> 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
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2 errors:0 dropped:0 overruns:0 frame:0
> TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:106 (106.0 b) TX bytes:7476 (7.3 Kb)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:6 errors:0 dropped:0 overruns:0 frame:0
> TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:300 (300.0 b) TX bytes:300 (300.0 b)
>
>
> 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
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:3044 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3737 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1667081 (1.5 MiB) TX bytes:443030 (432.6 KiB)
> Interrupt:22 Base address:0xdc00
>
> 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
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:43823 errors:0 dropped:0 overruns:0 frame:0
> TX packets:61268 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:2891263 (2.7 MiB) TX bytes:51117660 (48.7 MiB)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:14135 errors:0 dropped:0 overruns:0 frame:0
> TX packets:14135 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1126732 (1.0 MiB) TX bytes:1126732 (1.0 MiB)
>
> vif8.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:330 errors:0 dropped:0 overruns:0 frame:0
> TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:34066 (33.2 KiB) TX bytes:5241 (5.1 KiB)
>
> xen-br0 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.255
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:3486 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2822 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1428583 (1.3 MiB) TX bytes:339881 (331.9 KiB)
>
>
> Please let me know how I get the two doms to ping each other
>
> Regards
> Srini
>
>
Put your domU's on the same broadcast domain as your dom0, if you need
packet manipulation in or out from dom0 to domU than routing is
preferred.
routing setup with above ip config
On dom0
ifconfig eth0:1 "domU gateway ip here" netmask 255.255.255.0
echo "1" >/proc/sys/net/ipv4/ip_forward (edit /etc/sysctl.conf to make
permanent)
You can combine this setup as well if you like.
Regards,
Ted
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home