From: Sander Eikelenboom Subject: Re: [PATCH] vif-common.sh prevent physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore Date: Tue, 9 Nov 2010 19:29:07 +0100 Message-ID: <458529433.20101109192907@eikelenboom.it> References: <4010012490.20101108235313@eikelenboom.it> <19673.31871.224226.14651@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <19673.31871.224226.14651@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: "Xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org =0D=0ATuesday, November 9, 2010, 5:53:19 PM, you wrote: > Sander Eikelenboom writes ("[Xen-devel] [PATCH] vif-common.sh prevent phy= sdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chai= ns for non-bridged traffic is not supported anymore"): >> - iptables "$c" FORWARD -m physdev --physdev-in "$vif" "$@" -j ACCEPT \ >> + iptables "$c" FORWARD -m physdev --physdev-is-bridged --physdev-in "$= vif" "$@" -j ACCEPT \ > This will break on earlier iptables and/or earlier kernels. > Is there a way to detect whether --physdev-is-bridged is going to work ? > We could grep the output from iptables but is that sufficient ? I > guess we may need to check for kernel behaviour too somehow. Good point, although I don't have a config with an old enough iptables/kern= el to test what happens in that case .. The option should be available from before 2008 (http://ipset.netfilter.org= /iptables.man.html) though. > Ian. --=20 Best regards, Sander mailto:linux@eikelenboom.it