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

RE: [Xen-users] DHCP problem when changing motherboard

  • To: "Evan Lavelle" <sa212+xen@xxxxxxxxxxx>, "Xen" <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Mon, 13 Jul 2009 23:04:19 +1000
  • Cc:
  • Delivery-date: Mon, 13 Jul 2009 06:05:08 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcoDox1WsFCKvJ8eRBeUEkBroeRJSgAFz28A
  • Thread-topic: [Xen-users] DHCP problem when changing motherboard

> In the new setup, the router isn't seeing a DHCP request from the
> DomU's. Instead, the Dom0 is serving up addresses (in its own subnet;
> 192.168.122, instead of 192.168.1). Xen is presumably handling this
> direct, since there's no DHCP server installed on the Dom0.
> The DomU's can still see the network, but the rest of the network
> see them.
> Any ideas on how I can fix this?

Are you running the 192.168.122 and 192.168.1 networks across the same
'wire'? If so you probably need to isolate them using vlans.


Xen-users mailing list



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