On Mon, Apr 04, 2005 at 01:34:25PM -0400, Mike Tancsa wrote:
> This was only added to RELENG_5. I would cvsup, or wait a few days for the
> 5.4R. I have been using RELENG_5 on a number of production boxes and they
> are very stable and I think 5.4R will be as well. But as always, YMMV
>
Ah ok
At 01:04 PM 04/04/2005, Jamie Heckford wrote:
> Try adding
>
> options IPFIREWALL_FORWARD
> options IPFIREWALL_FORWARD_EXTENDED
Saw this however FreeBSD 5.3-RELEASE-p6 #2: Thu Mar 31 01:50:41 BST
2005 is giving
unknown option "IPFIREWALL_FORWARD_EXTENDED"
This was only
> Saw this however FreeBSD 5.3-RELEASE-p6 #2: Thu Mar 31 01:50:41
> BST 2005 is giving unknown option "IPFIREWALL_FORWARD_EXTENDED"
You need RELENG_5 or RELENG_5_4, not RELENG_5_3.
--
Maxim Konovalov
___
freebsd-stable@freebsd.org mailing list
http
On Mon, Apr 04, 2005 at 12:48:04PM -0400, Mike Tancsa wrote:
> At 12:47 PM 04/04/2005, Jamie Heckford wrote:
> >Hi,
> >
> >Has anyone else had issues with using the fwd/forward feature of IPFW2?
> >
> >As described in below PR, not working for me either since going to 5.3 :(
> >
> >http://lists.fre
At 12:47 PM 04/04/2005, Jamie Heckford wrote:
Hi,
Has anyone else had issues with using the fwd/forward feature of IPFW2?
As described in below PR, not working for me either since going to 5.3 :(
http://lists.freebsd.org/pipermail/freebsd-i386/2004-November/001823.html
Any pointers would be greatly
Hi,
Has anyone else had issues with using the fwd/forward feature of IPFW2?
As described in below PR, not working for me either since going to 5.3 :(
http://lists.freebsd.org/pipermail/freebsd-i386/2004-November/001823.html
Any pointers would be greatly appreciated!
thanks
___
