From: mixer_ <mixer_@scurvydogs.org>
To: xen-devel@lists.xensource.com
Subject: Xen 3.2.0 - domU cannot reach the internet
Date: Wed, 13 Feb 2008 10:42:21 +0100 [thread overview]
Message-ID: <47B2BB7D.2040808@scurvydogs.org> (raw)
hi, i recently updated to xen 3.2 and now networking has stopped working.
i have a configuration with 2 nics: eth1 (internet) and eth0 (lan)
when i start xend i get peth{0,1} with no ip, and xenbr{0,1} with the
right addresses
the server running xen is also the lan gw
the routing table seems ok
192.168.0.0 * 255.255.255.0 U 0
0 0 xenbr0
1.232.xx.0 * 255.255.240.0 U 0
0 0 xenbr1
default 1.232.xx.1 0.0.0.0 UG 0
0 0 xenbr1
connections coming from the lan are all ok and the nat works well, but
the ones coming from the domUs cannot transmit any data.
the domUs are on the same subnet of dom0 (192.168.0.0/24), gw and ns are ok
i use iptables with MASQUERADE for nat and tried the NOTRACK solution
but it's not working for me
from domUs i can ping the outside if i use an ip as parameter for ping,
and when dumping traffic on dom0 i see some ACKs ..looks like the
connection is established, but no data comes back
ie.
telnet $google's_ip 80
get index.php
i get connected but i receive no data, in traffic dump i can see the
packet containing "get index.php" going out and then the connection goes
timeout
the firewall is completely empty and in ACCEPT, the only rules i used
are MASQUERADE for nat and NOTRACK in raw table
has anyone found a solution with xen 3.2?
thanks in advance for help
reply other threads:[~2008-02-13 9: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=47B2BB7D.2040808@scurvydogs.org \
--to=mixer_@scurvydogs.org \
--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.