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@lists.xensource.com http://lists.xensource.com/xen-users