From: "Y. D." <duyuyang@gmail.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: domU is unreachable to and from outside xen
Date: Fri, 31 Oct 2008 21:42:52 +0800 [thread overview]
Message-ID: <200810312142512510332@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1450 bytes --]
The domU can ping dom0, but not outside Xen, and vice versa.
I test in domU:
#ping 10.0.0.150 /*10.0.0.150 is an external IP in LAN*/
>From 10.0.0.36 icmp_seq=303 Destination Host Unreachable
>From 10.0.0.36 icmp_seq=304 Destination Host Unreachable
>From 10.0.0.36 icmp_seq=305 Destination Host Unreachable
>From 10.0.0.36 icmp_seq=306 Destination Host Unreachable
>From 10.0.0.36 icmp_seq=307 Destination Host Unreachable
>From 10.0.0.36 icmp_seq=308 Destination Host Unreachable
I test in dom0:
#tcpdump -i peth0 | grep "10.0.0.36" /*10.0.0.36 is domu's IP*/
16:21:10.181977 arp who-has 10.0.0.150 tell 10.0.0.36
16:21:11.181961 arp who-has 10.0.0.150 tell 10.0.0.36
16:21:11.841972 arp who-has 10.0.0.150 tell 10.0.0.36
16:21:12.181974 arp who-has 10.0.0.150 tell 10.0.0.36
16:21:12.841953 arp who-has 10.0.0.150 tell 10.0.0.36
16:21:13.841997 arp who-has 10.0.0.150 tell 10.0.0.36
16:21:14.848934 arp who-has 10.0.0.150 tell 10.0.0.36
16:21:15.181945 arp who-has 10.0.0.150 tell 10.0.0.36
16:21:15.845963 arp who-has 10.0.0.150 tell 10.0.0.36
16:21:16.181962 arp who-has 10.0.0.150 tell 10.0.0.36
#brctl show
bridge name bridge id STP enabled interfaces
eth0 8000.000fea0247e6 no peth0
vif82.0
It seems everything is all right.
I don't know what is wrong. Can anyone help?
Thanks in advance,
Shawn
[-- Attachment #1.2: Type: text/html, Size: 3794 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2008-10-31 13:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200810312142512510332@gmail.com \
--to=duyuyang@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.