WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Xen bridge swallowing packets?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen bridge swallowing packets?
From: Geoff Meakin Acid <geoffmeakin@xxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 18 Aug 2011 00:19:15 +0100
Delivery-date: Wed, 17 Aug 2011 16:20:40 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi, can anyone help me with this (weirdest problem Ive ever seen)

I have the latest Debian Squeeze vendor xen dom0 kernel and 1 domU succesfully installed on it using bridged networking. From dom0, I can ping/telnet etc. to anywhere on the web

WHAT IS WORKING >
* From my domU I can successfully ping google.com and telnet to 8.8.8.8:53 (googles dns server)
* tcpdump vif1.0 and I see SYNs and ACKs
* tcpdump peth0 and I see corresponding SYNs and ACKs

WHAT IS NOT WORKING >
* However I cannot telnet to google.com:80 - connection refused
* When I TCPDump vif1.0 I see SYNs followed by RST,ACK sent from dom0
* There are no packets leaving or entering on peth0 at all - so they dont get out onto the network

All my iptables rules are all ACCEPT rules, and the policys are all ACCEPT. IE there is no iptables rule in either INPUT, FORWARD, OUTPUT, PREROUTING or POSTROUTING that does anything other than accept. This is the case for both dom0 and domU

Can anyone shed any light on this mysterious behaviour? Why would googles dns server work but http server not? Is there something I've forgotten?


--

Geoff Meakin





_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>