Re: iptables: Distinguishing packets from bridge-nf-call-iptables

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

 



On 5 Feb 2014, at 11:53, Mart Frauenlob wrote:

> On 05.02.2014 12:24, Alex Bligh wrote:
>> I am trying to run two pieces of software X and Y on a linux box.
>> 
>> X assumes /proc/sys/net/bridge/bridge-nf-call-iptables is set to 1. I am not able to modify this.
>> 
>> Y assumes /proc/sys/net/bridge/bridge-nf-call-iptables is set to 0. This is my software and I can modify it.
>> 
>> I want to adapt my rules for Y so that it copes with /proc/sys/net/bridge/bridge-nf-call-iptables=1 by ignoring (in the iptables rule) any traffic which is purely bridged, and simply doing the ebtables rules on these packets.
>> 
>> In the iptables rules, how do I differentiate ip forwarded traffic from bridged traffic? The bridge interfaces may or may not carry IP addresses.
>> 
> 
> -m physdev ... ?

Ah "-m physdev --physdev-is-bridged" - thanks

If I want to return to ebtables checking etc. (i.e. do nothing) I take it -j ACCEPT
will do this (i.e. ACCEPT does not mean 'override ebtables rejection')?

-- 
Alex Bligh




--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux