Re: [Xen-devel] [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

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Sander Eikelenboom writes ("Re: [Xen-devel] [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"):
> Good point, although I don't have a config with an old enough
> iptables/kernel to test what happens in that case ..

On lenny:

$ iptables --physdev-is-bridged 
iptables v1.4.2: Unknown arg `(null)'
Try `iptables -h' or 'iptables --help' for more information.
$

What I want to know, though, is what happens if you have a new
iptables and an old kernel.

Ian.

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