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] domU's unreachable over network

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] domU's unreachable over network
From: "Rob Greene" <robgreene@xxxxxxxxx>
Date: Thu, 24 Jul 2008 19:17:39 -0500
Delivery-date: Thu, 24 Jul 2008 17:18:15 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=jF0lptMacko/5rFwJ2cRwnBOxu41dNHAMWd6Xwhg7II=; b=MjhveT8kZCGOd3O9yTg+sEaVFFU2jFjQtM7HYcsV4K33CbCdcwexW/44JZiyn/mPcH NzLeQrSwfYG26MKZ0SPm5Wyu/pZSMoxrwgjrGjI1pcvvmDG0yAQfcfGSG1bKzWDqLBg2 f+tUwsClns+4Dnir2y98s5Uq+8Ol8EWrXEKo0=
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=ZOkhcXjMk5q1MfqevD3iIUSLbWNfL0qcG54CF3h5hfMbd6XAAMCVdlI7I2w9EJAp7g nUv3igwAWqfgsY77KzuyOH9VdMiyEf4bwu63+xug/7duwqS4uVzQ6OaGwUaw3NRfUKBU x92b4iW3uxO5HTZDbnvbX7sZWPmSzL0GPgCM4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I've been futzing with this off and on for the last couple of weeks.
I am running CentOS 5 and have 7 domU's, all of which I assigned an IP
address in the range 192.168.1.210 - .216, and the dom0 with an
address of 192.168.1.200 and .201 (dual NIC).  I have a WRT54G serving
as router/firewall/dhcp/etc and a couple of Windows PCs.

This worked for a while.  At some point (maybe the 5.2 upgrade?), my
network became unreachable from the Windows machines.  I found that
assigning the 192.168.1.x made the domU's unable to communicate out or
in (couldn't ping them nor could they ping out).  I did find that
dnsmasq is magically being run -- it has a command line in ps, which I
cannot find anywhere in /etc:

/usr/sbin/dnsmasq --keep-in-foreground --strict-order
--bind-interfaces --pid-file  --conf-file  --listen-address
192.168.122.1 --except-interface lo
--dhcp-leasefile=/var/lib/libvirt/dhcp-default.leases --dhcp-range
192.168.122.2,192.168.122.254

If I stop and start the service, I just see "/usr/sbin/dnsmasq".  It
then loads options from the config file.

What I *think* is now happening is that dnsmasq is acting as a dhcp
server to my domU's.  They are being assigned in the 192.168.122.x
range.  If I let my domU's be dhcp assigned, I'm ok from within the
domU and dom0 itself -- they can see each other, they can see my
Windows IP addresses, and I can get to the internet.

Unfortunately, I cannot figure out how to get Windows to see them.
Alternatively, I also cannot seem to get the domU's to get 192.168.1.x
IP's -- and don't know where or what I need to do!

Any guidance would be appreciated.

Thanks!
-Rob

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] domU's unreachable over network, Rob Greene <=