On 21 Aug 2009, at 2:55am, Dave Koelmeyer wrote:
Thanks David, here we are:
dkoe...@turrican:~# dladm show-link
LINK CLASS MTU STATE OVER
bge0 phys 1500 up --
xvm2_0 vnic 1500 up bge0
dkoe...@turrican:~# snoop -d xvm2_0 turrican
Using device xvm2_0 (promiscuous mode)
If I run the above and ping dom0 from domU, with the domU in its
default as-installed configuration, I see nothing - no feedback, no
activity picked up with snoop. On the domU running the ping command
it reports "Destination host unreachable".
If in the domU I configure a fixed IP address/netmask/DNS server
(using the correct settings as I would for the same network the dom0
is on) I see from snoop on the dom0:
techsetup -> turrican ICMP Echo request (ID: 512 Sequence
number: 256)
turrican -> techsetup ICMP Echo reply (ID: 512 Sequence number:
256)
I can ping dom0 OK, and dom0 can ping domU. I cannot however ping
any other device from the domU, nor can I connect to any other
network resource (regardless of using DNS).
I might add that the dom0 is also in an as-installed state, aside
from updating to snv_118 and disabling NWAM, I haven't fiddled with
it at all really.
Dave, given that dom0 <-> domU connectivity seems to be working, I'm
puzzled.
Is it possible that the switch port to which bge0 is connected could
be filtering traffic?
_______________________________________________
xen-discuss mailing list
[email protected]
