Re: [Xen-users] NET Network / Server running on internal Network not reachable

["Christopher Isip" <cmisip@xxxxxxxxx>]

On Wed, Jul 9, 2008 at 2:08 PM, Robert M. Münch <robert.muench@xxxxxxxxxxxxxxx> wrote:

On Wed, 09 Jul 2008 04:34:01 +0200, Christopher Isip <cmisip@xxxxxxxxx> wrote:

The easiest way to do IP masquerade is with shorewall.  Try the two
interface configuration with one interface the external and the other the
internal/bridged interface.

Hi Chris, I took a look into shorewall. I followed the information to setup a simple Xen system. But it doesn't work. I can't connect to the web-server. I always get a "conneciton refused".

Here is some output from the logging and TCPDUMP:


HTTP from DMZ/10.0.0.1 (wget www.robertmuench.de)
Jul  9 16:16:29 FORWARD:REJECT:IN=vif3.0 OUT=eth0 SRC="" href="http://10.0.0.1" target="_blank">10.0.0.1 DST=87.118.120.128 LEN=65 TOS=0x00 PREC=0x00 TTL=63 ID=56283 DF PROTO=UDP SPT=32768 DPT=53 LEN=45

Here I tracked a wget 87.118.120.16 So the requests comes in but is immediatly answered with something that rejects/refuses the connection to be established. Error message on the requester: connection refused.


root@eisxen:~/shorewall-config# tcpdump -i eth0 host 62.141.54.100 and port 80

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on eth0, link-type EN10MB (Ethernet), capture size 68 bytes
16:42:23.415056 IP ns.km1428.keymachine.de.54159 > eisxen.www: S 2049446876:2049446876(0) win 5840 <mss 1460,sackOK,timestamp 2303776659[|tcp]>
16:42:23.416084 IP eisxen.www > ns.km1428.keymachine.de.54159: R 0:0(0) ack 2049446877 win 0


In which mode do I need to run XEN, bridged, routed, nat? I have tried birdged and nat. Same effect, doesn't work.

Best regards.

--
Robert M. Münch
http://www.robertmuench.de

_______________________________________________

Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

Can you access the webserver from within the xen domU?  You can try lynx maybe to see if it would even load.  Also try clearing the firewall between the domU with the web server, dom0  and wherever you are trying to access it from.  What distro is your domU?

 Chris

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users