RE: Reject on a Bridge

["Gilad Benjamini" <gilad.benjamini@gmail.com>]

Following the replies I got I understand this is not supported by the code.
I played around with the code and was able to make this work in some
scenarios but not in others.
If I understand correctly, my main obstacle is the call to
ip_route_me_harder, which is completely wrong for my case, as no routing is
involved.
Anyone has an idea for a simple patch that might solve this ?

In case I wasn't clear, the idea is simple; on the bridge, fake a RST packet
as if it came from the destination of the original packet.

Thanks for any help 

-----Original Message-----
From: netfilter-owner@vger.kernel.org
[mailto:netfilter-owner@vger.kernel.org] On Behalf Of Gilad Benjamini
Sent: Wednesday, September 03, 2008 3:41 PM
To: netfilter@vger.kernel.org
Subject: Reject on a Bridge

I am using iptables to run a firewall on a bridge.
The bridge consists of eth1 and eth2. Neither interface, nor the
bridge itself, have an IP address.
eth0, which is not on the bridge, does have an IP address.

Trying to use the REJECT target with --tcp-reset doesn't work.
If I understand the code correctly, the route for the RST packet is
determined through ip_route_me_harder in the send_reset function,
implying in my case that the RST packet will leave through eth0, which
is not the desired behavior. Theoretically, eth0 might be even
physically disconnected from the bridged network.

Am I missing something, or is this a real problem ?
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html