Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Aug 2004 13:01:14 -0700 (PDT)
From:      Kelly Yancey <kbyanc@posi.net>
To:        Patrick Tracanelli <eksffa@freebsdbrasil.com.br>
Cc:        ipfw@freebsd.org
Subject:   Re: FWD under bridged enviroment...
Message-ID:  <20040817125600.I2020@gateway.posi.net>
In-Reply-To: <4120DA69.8080609@freebsdbrasil.com.br>
References:  <4120DA69.8080609@freebsdbrasil.com.br>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 16 Aug 2004, Patrick Tracanelli wrote:

>
> Should the fwd action work with the code revision available today under
> 5_2 branch (5.2.1-RELEASE-p8)?
>
> The enviroment is xl0 and xl1 bridged in the sabe cluster, ahd xl2
> available only to host registered IP and be available online. The fwd
> action fordwards to the same machine...
>
> bridged firewalling is enabled, the interesting thing is that the fwd
> rule counts packets and bytes as usual, but the forwarded port gets no
> action.. (ie, no connection is logged);
>
> other behaviour is that if I get only the fwd rule that fordwards to
> somewhere not available, usually the traffic gets stopped (obviously,
> since they are forwarded to somewhere and gets nothing there) but under
> this bridged setup the traffic stills flows, as if there were no fwd
> rule (but it is still counting packets)...
>
> any clue? :)
>
> I remember code were available to allow fwd under bridged enviroment, I
> want to know if it was commited and is supposed to work :}
>

  I believe I've mentioned having code to implement fwd for IPv4 packets
filtered from ether_input (net.link.ether.ipfw=1).  Unfortunately, the
patches are against 4.10.  If someone else doesn't implement it before
then, I plan on porting the functionality to 6-current (and then backport
to 5-stable) after 5.3 is released.

  Kelly

--
Kelly Yancey  --  kbyanc@{posi.net,FreeBSD.org}  --  kelly@nttmcl.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040817125600.I2020>