On Sun, 2007-04-29 at 10:32 -0500, Yevgeniy Goldberg wrote:
Hi Tim,
The guest that has network issues is suppose to use dhcp and that is
the part that is not working.
When I run ifconfig -a on the xen host OS (Dom0) I get the following:
Your bridge (xenbr0) does not appear to have an IPV4 address.
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:627484 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:29099604 (27.7 Mb) TX bytes:0 (0.0 b)
... nor does your non-enslaved secondary ethernet device (eth1).
Something is telling me you have something wrong with your DHCP
configuration.
Can you paste anything related to dhcp from syslog on the dhcp server
itself?
Better yet, for purposes of eliminating Xen as part of this
problem, can
you assign a static address and subnet to eth0 (which appears to
become
enslaved to xenbr0 via network-bridge), as well as specifying a static
IP and subnet from within the dom-u? From your ifconfig dump, it looks
like network-bridge is doing its job correctly.
Please note, if macs change, you may have to ping outward from within
dom-0 (and the dom-u) prior to either being able to see incoming
traffic. 4.2.2.2 or 4.2.2.3 are good hosts to ping for this purpose.
Best,
--Tim
Home