[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Dom0 to DomU and reverse works but Outside world to DomU only ping works


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Vikas <kedia.vikas@xxxxxxxxx>
  • Date: Sun, 18 Jan 2009 12:49:05 -0600
  • Delivery-date: Sun, 18 Jan 2009 10:51:19 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=hpSzJnIuwyL7W+T0kOhWngdfzvFikrG611+rMg5eEt6zxFrzXbvryH+uGCHYkSWE+M 6SIKHDvZHEOAYV2rJepN5BikWh+QACJzY2u7GOOP4p7CUoGJrXvdzdziQhLzii/qTUde B/g6AWUvTMe7RGPsbLh28U01W4hDq8qWoImxQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Summary problem description:
What works ?
A. ping, ssh, http access - works from Dom0 to DomU and also from DomU to Dom0
B. ping, ssh, http access - works from outside world to Dom0 and from
Dom0 to outside world
C. ping from outside world to DomU

What does not work ?
A. ssh and http access from outside world to DomU and also from DomU
to outside world

Diagnostics:
>From DomU I gave the command:
> lynx 74.125.19.147
and I got the error message:
Making HTTP connection to 74.125.19.147
Sending HTTP request.
HTTP request sent; waiting for response.
Alert!: Unexpected network read error; connection aborted.
Can't Access `http://74.125.19.147/'
Alert!: Unable to access document.
lynx: Can't access startfile


In Dom0 I had tcpdump running and it gave me the following output:
[root@ps1 ~]# tcpdump -vvvv host 74.125.19.147
tcpdump: WARNING: peth0: no IPv4 address assigned
tcpdump: listening on peth0, link-type EN10MB (Ethernet), capture size 96 bytes
06:43:55.941963 IP (tos 0x0, ttl  64, id 20913, offset 0, flags [DF],
proto: TCP (6), length: 60) 72.52.93.9.51415 >
cf-in-f147.google.com.http: S, cksum 0x249c (correct),
2918592937:2918592937(0) win 5840 <mss 1460,sackOK,timestamp 6774808
0,nop,wscale 7>
06:43:55.944002 IP (tos 0x0, ttl  59, id 61335, offset 0, flags
[none], proto: TCP (6), length: 60) cf-in-f147.google.com.http >
72.52.93.9.51415: S, cksum 0x81ea (correct), 2521226213:2521226213(0)
ack 2918592938 win 5672 <mss 1430,sackOK,timestamp 2113385283
6774808,nop,wscale 6>
06:43:55.944032 IP (tos 0x0, ttl  64, id 20914, offset 0, flags [DF],
proto: TCP (6), length: 52) 72.52.93.9.51415 >
cf-in-f147.google.com.http: ., cksum 0xc691 (correct), 1:1(0) ack 1
win 46 <nop,nop,timestamp 6774808 2113385283>
06:43:55.945897 IP (tos 0x0, ttl  64, id 20915, offset 0, flags [DF],
proto: TCP (6), length: 352) 72.52.93.9.51415 >
cf-in-f147.google.com.http: P 1:301(300) ack 1 win 46
<nop,nop,timestamp 6774809 2113385283>
06:43:56.149909 IP (tos 0x0, ttl  64, id 20916, offset 0, flags [DF],
proto: TCP (6), length: 352) 72.52.93.9.51415 >
cf-in-f147.google.com.http: P 1:301(300) ack 1 win 46
<nop,nop,timestamp 6774860 2113385283>
06:43:56.557931 IP (tos 0x0, ttl  64, id 20917, offset 0, flags [DF],
proto: TCP (6), length: 352) 72.52.93.9.51415 >
cf-in-f147.google.com.http: P 1:301(300) ack 1 win 46
<nop,nop,timestamp 6774962 2113385283>
06:43:57.373983 IP (tos 0x0, ttl  64, id 20918, offset 0, flags [DF],
proto: TCP (6), length: 352) 72.52.93.9.51415 >
cf-in-f147.google.com.http: P 1:301(300) ack 1 win 46
<nop,nop,timestamp 6775166 2113385283>
06:43:59.006087 IP (tos 0x0, ttl  64, id 20919, offset 0, flags [DF],
proto: TCP (6), length: 352) 72.52.93.9.51415 >
cf-in-f147.google.com.http: P 1:301(300) ack 1 win 46
<nop,nop,timestamp 6775574 2113385283>
06:44:02.270294 IP (tos 0x0, ttl  64, id 20920, offset 0, flags [DF],
proto: TCP (6), length: 352) 72.52.93.9.51415 >
cf-in-f147.google.com.http: P 1:301(300) ack 1 win 46
<nop,nop,timestamp 6776390 2113385283>
06:44:05.951449 IP (tos 0x0, ttl  59, id 61336, offset 0, flags
[none], proto: TCP (6), length: 52) cf-in-f147.google.com.http >
72.52.93.9.51415: F, cksum 0x9f4e (correct), 1:1(0) ack 1 win 89
<nop,nop,timestamp 2113395290 6774808>
06:44:05.954517 IP (tos 0x0, ttl  64, id 20921, offset 0, flags [DF],
proto: TCP (6), length: 52) 72.52.93.9.51415 >
cf-in-f147.google.com.http: ., cksum 0x9486 (correct), 301:301(0) ack
2 win 46 <nop,nop,timestamp 6777311 2113395290>
06:44:08.798696 IP (tos 0x0, ttl  64, id 20922, offset 0, flags [DF],
proto: TCP (6), length: 352) 72.52.93.9.51415 >
cf-in-f147.google.com.http: P 1:301(300) ack 2 win 46
<nop,nop,timestamp 6778022 2113395290>
06:44:08.954717 IP (tos 0x0, ttl  64, id 20923, offset 0, flags [DF],
proto: TCP (6), length: 52) 72.52.93.9.51415 >
cf-in-f147.google.com.http: F, cksum 0x9197 (correct), 301:301(0) ack
2 win 46 <nop,nop,timestamp 6778061 2113395290>
06:44:08.956809 IP (tos 0x0, ttl  59, id 61337, offset 0, flags
[none], proto: TCP (6), length: 40) cf-in-f147.google.com.http >
72.52.93.9.51415: R, cksum 0x713d (correct), 2521226215:2521226215(0)
win 0

14 packets captured
30 packets received by filter
0 packets dropped by kernel

Software environment:
Name   : xen x86_64
Version: 3.0.3
Release: 64.el5_2.9

Hardware environment:
Supermicro motherboard-X7DWN+

Things I have tried:
1. Shutting down the IPtables in Dom0
2. Reinstalling CentOS.

How should I debug this problem further ?


Thanks for your time,
-- 
sysadmin
http://www.debtconsolidationcare.com

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.