Re: [PATCH] don't require ip_forwarding for reset on a bridge

netdev

Re: [PATCH] don't require ip_forwarding for reset on a bridge

To:	Bart De Schuymer <bdschuym@xxxxxxxxxx>
Subject:	Re: [PATCH] don't require ip_forwarding for reset on a bridge
From:	"David S. Miller" <davem@xxxxxxxxxx>
Date:	Mon, 29 Mar 2004 20:30:25 -0800
Cc:	netdev@xxxxxxxxxxx, netfilter-devel@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<200403292314.12855.bdschuym@xxxxxxxxxx>
References:	<200403292314.12855.bdschuym@xxxxxxxxxx>
Sender:	netdev-bounce@xxxxxxxxxxx

On Mon, 29 Mar 2004 23:14:12 +0200
Bart De Schuymer <bdschuym@xxxxxxxxxx> wrote:

> Currently, to be able to send a reset in the FORWARD chain of iptables
> for bridged traffic, ip forwarding must be enabled. This causes confusion
> and in some situations people really don't want to enable ip forwarding.
> The patch below lets the user send reset packets for bridged frames in
> the FORWARD chain, with ip forwarding disabled (as long as there is a
> route).

I want an ACK from the netfilter folks before applying this one.

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[PATCH] don't require ip_forwarding for reset on a bridge, Bart De Schuymer Re: [PATCH] don't require ip_forwarding for reset on a bridge, David S. Miller <=

Previous by Date:	Re: BUG in tcp_timer.c:tcp_retransmit_timer(), David S. Miller
Next by Date:	Re: route cache DoS testing and softirqs, Srivatsa Vaddagiri
Previous by Thread:	[PATCH] don't require ip_forwarding for reset on a bridge, Bart De Schuymer
Next by Thread:	[ANNOUNCE] sch_dup - duplicate packet queue discipline [2.6], Catalin BOIE
Indexes:	[Date] [Thread] [Top] [All Lists]