WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] FC5 -- Xen 3.0.2 -- networking with dom0 and domU

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] FC5 -- Xen 3.0.2 -- networking with dom0 and domU
From: dgreen@xxxxxxxxxxx
Date: Wed, 10 Jan 2007 17:08:02 -0500 (EST)
Delivery-date: Wed, 10 Jan 2007 14:07:59 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
Importance: Normal
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.6
Situation:

Trying to ping from one VM on one physical machine to another VM on a
different physical machine (different subnets).

--------------------------------------------

My environment:

(machine1) domU 192.168.1.101 <-> (machine1) dom0 192.168.1.100
<-network-> (machine2) dom0 192.168.2.100 <-> (machine2) domU
192.168.2.101

dom0s -- FC5  (2.6.17-1.2157_FC5xen0, using 512MB RAM)
domUs -- FC5  (2.6.17-1.2157_FC5xen0, using 256MB RAM)
scripts (network-bridge, vif-bridge) are used on bootup
I have disabled selinux and firewall

I can:
-ping and ssh between dom0s and their respective domUs
-ping between dom0s (which are on different subnets)

-------------------------------------------------

My routing table on 192.168.1.100 dom0:
Destination   Gateway       Genmask       Flags Metric Ref  Use Iface
192.168.1.0   0.0.0.0       255.255.255.0   U     0      0   0 eth0
169.254.0.0   0.0.0.0       255.255.0.0     U     0      0   0 eth0
0.0.0.0       192.168.1.1   0.0.0.0         UG    0      0   0 eth0

-------------------------------------------------

ifconfig output from 192.168.1.100 dom0 (took out loopback):

eth0      Link encap:Ethernet  HWaddr 00:E0:81:5D:B1:70
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2e0:81ff:fe5d:b170/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:145 errors:0 dropped:0 overruns:0 frame:0
          TX packets:154 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:20100 (19.6 KiB)  TX bytes:15611 (15.2 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 MULTICAST  MTU:1500  Metric:1
          RX packets:17 errors:0 dropped:0 overruns:0 frame:0
          TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2073 (2.0 KiB)  TX bytes:10222 (9.9 KiB)
          Interrupt:18 Base address:0xe000

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 MULTICAST  MTU:1500  Metric:1
          RX packets:154 errors:0 dropped:0 overruns:0 frame:0
          TX packets:146 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:15611 (15.2 KiB)  TX bytes:20190 (19.7 KiB)

vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:126 errors:0 dropped:0 overruns:0 frame:0
          TX packets:149 errors:0 dropped:6 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:16233 (15.8 KiB)  TX bytes:14581 (14.2 KiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:72 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:7293 (7.1 KiB)  TX bytes:468 (468.0 b)

----------------------------------

iptables --list output for 192.168.1.100 dom0:
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

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

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

----------------------------------

I would like to keep a VMM and its respective VMs on the same subnet.  Can
anyone help with this configuration?  Thanks for your help in advance.

Vince

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] FC5 -- Xen 3.0.2 -- networking with dom0 and domU, dgreen <=