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

[Xen-devel] Networking in Xen


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Girish V" <girish.xen@xxxxxxxxx>
  • Date: Tue, 6 May 2008 11:49:47 -0400
  • Delivery-date: Tue, 06 May 2008 08:50:08 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=bmMvskzu7wEVd0qiH5l7Bt4rIV2r10mshJunT4p51yrYTy4iVk+jxxKlNkomyHRQJpoAkhwucQWUMV2wJf2h5R6pMuC/EiVHTYICYUGvNGHV3FREZUA10NRzUMbOWIsQWbVpgcwW8Selz9DCE9jrgbfoaSqvHB2iP2qzzZRnqqs=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hello,

I have computer which is not connected to the internet (its eth0 is
assigned 10.10.0.13 statically and is UP). I am running Xen 3.0.2 on
it.

I want my domU to be able to ping the dom0 and vice versa (I am
assigning 10.10.0.14 to the domU).

I tried a bridged connection, but when I tried to ping 10.10.0.13 from
the domU I get the message "connect: Network is unreachable". When I
pinged the domU from dom0 I got "Destination Host Unreachable"


What sort of a networking should I set up to achieve this? (I have
shown ifconfig, route and iptabes below).

Any help is appreciated

Thanks,
Girish


my ifconfig from dom0 looks like
----------------------------------------------------
eth0 Link encap:Ethernet HWaddr 10:10:10:10:10:26
 inet addr:10.10.0.13 Bcast:0.0.0.0 Mask:255.255.255.0
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 RX packets:26 errors:0 dropped:0 overruns:0 frame:0
 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:2270 (2.2 KiB) TX bytes:1468 (1.4 KiB)

lo Link encap:Local Loopback
 inet addr:127.0.0.1 Mask:255.0.0.0
 inet6 addr: ::1/128 Scope:Host
 UP LOOPBACK RUNNING MTU:16436 Metric:1
 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:0 (0.0 KiB) TX bytes:0 (0.0 KiB)

peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
 inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
 UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
 RX packets:15 errors:2 dropped:0 overruns:0 frame:0
 TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:1000
 RX bytes:2483 (2.4 KiB) TX bytes:4137 (4.0 KiB)
Interrupt:10Base address:0x3080

vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
 inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
 UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
 RX packets:12 errors:0 dropped:0 overruns:0 frame:0
 TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:1468 (1.4 KiB) TX bytes:2668 (2.6 KiB)

vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
 inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
 UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
 RX packets:15 errors:0 dropped:0 overruns:0 frame:0
 TX packets:1 errors:0 dropped:203 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:846 (846.0 b) TX bytes:42 (42.0 b)

xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
 UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
 RX packets:208 errors:0 dropped:0 overruns:0 frame:0
 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
RX bytes:860 (860.0 b) TX bytes:468 (468.0 b)
---------------------------------------------------------------------
route on dom0 shows
-----------------------------------------------------------------------
Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.10.0.0       *               255.255.255.0         U       0
 0        0   eth0
default           10.10.0.1  0.0.0.0                    UG     0
  0        0   eth0
-------------------------------------------------------------------------

iptables -L on dom0 shows
---------------------------------------------------------------------
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
ACCEPT  all    --  10.10.0.13          anywhere            PHYSDEV
match --physdev-in vif2.0
ACCEPT     udp  --  anywhere             anywhere            PHYSDEV
match --physdev-in vif2.0 udp spt:bootpc dpt:bootps

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
---------------------------------------------------------------------

ifconfig on domU shows
---------------------------------------------------------------------
eth0      Link encap:Ethernet  HWaddr 00:16:3E:3D:D5:18
         inet addr:10.10.0.14  Bcast:10.10.0..255  Mask:255.255.255.0
         inet6 addr: fe80::216:3eff:fe3d:d518/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:1 errors:0 dropped:0 overruns:0 frame:0
         TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:42 (42.0 b)  TX bytes:846 (846.0 b)

lo Link encap:Local Loopback
 inet addr:127.0.0.1 Mask:255.0.0.0
 inet6 addr: ::1/128 Scope:Host
 UP LOOPBACK RUNNING MTU:16436 Metric:1
 RX packets:108 errors:0 dropped:0 overruns:0 frame:0
 TX packets:108 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:0
 RX bytes:7884 (7.6 KiB) TX bytes:7884 (7.6 KiB)
---------------------------------------------------------------------

route on domU shows
-----------------------------------------------------------------------
Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.10.10.0       *               255.255.255.0        U      0
0        0   eth0
169.254.0.0      *               255.255.0.0           U      0
 0        0   eth0
-------------------------------------------------------------------------

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


 


Rackspace

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