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

Re: [Xen-users] iptables and state matches (established, related)


  • To: "Tomas Lund" <tlund@xxxxxx>
  • From: "John Hannfield" <hal9020@xxxxxxxxx>
  • Date: Sat, 28 Apr 2007 13:49:58 +0100
  • Cc: Andrey Oreshnikov <elride@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sat, 28 Apr 2007 05:48:36 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=X/KUlnw/fBXNBa9admCWKDdKExiMTRGUEc3wvFcpIiSQKxZ6vFxa7gNr4BzCvCNsXB2jSxrv+PKAjsL0bJ19Jqv4N64hTrinokWH8/nvheZMSywkHgXJl+e6ooZ8zfulKxfYyb1TpJSAjB+RVZs9Yh/Kk21VRSZB6YzWvKpJgng=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

This is a known problem with Xen 3.0.x  and iptables connection tracking.
Connection tracking and state filtering only works as long as xen is
not running.
Try doing this:

echo "0" >/proc/sys/net/bridge/bridge-nf-call-iptables

That fixed it for me.


--

John

_______________________________________________
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®.