Hi all
Following ipfw rule develop error indicated:
ipfw add 100 fwd 127.0.0.1,1234 tcp from any to any 1234 out via wlan0
Error:
ipfw: getsockopt(IP_FW_ADD): Invalid argument
What I want to do is forward any packet going out of the computer to port 1234
forward back to 127.0.0.1:1234.
There i
Synopsis: ipfw(8) fwd with IPv6 treats input as IPv4
Responsible-Changed-From-To: freebsd-ipfw->bz
Responsible-Changed-By: emaste
Responsible-Changed-When: Tue Jul 5 13:57:09 UTC 2011
Responsible-Changed-Why:
Sandvine has a patch to implement ipv6 fwd that bz@'s going to clean
up and get into the
Hello Unga
On 05.07.2011 12:47, Unga wrote:
Following ipfw rule develop error indicated:
ipfw add 100 fwd 127.0.0.1,1234 tcp from any to any 1234 out via wlan0
Error:
ipfw: getsockopt(IP_FW_ADD): Invalid argument
Does your kernel have 'options IPFIREWALL_FORWARD' (if this is
needed for 8.1,
--- On Tue, 7/5/11, Fabian Wenk wrote:
> From: Fabian Wenk
> Subject: Re: ipfw fwd on FreeBSD 8.1, does it work?
> To: freebsd-ipfw@freebsd.org
> Date: Tuesday, July 5, 2011, 10:00 PM
> Hello Unga
>
> On 05.07.2011 12:47, Unga wrote:
>
> > Following ipfw rule develop error indicated:
> > ipf
On 05.07.2011 21:20, Unga wrote:
> Thanks for the reply.
>
> The 'options IPFIREWALL_FORWARD' is already built in the custom kernel.
>
> Both rules you suggested develop the same error:
> ipfw: getsockopt(IP_FW_ADD): Invalid argument
Hi,
You should add 'options IPFIREWALL' in the your kernel co
--- On Wed, 7/6/11, Andrey V. Elsukov wrote:
> From: Andrey V. Elsukov
> Subject: Re: ipfw fwd on FreeBSD 8.1, does it work?
> To: "Unga"
> Cc: freebsd-ipfw@freebsd.org, "Fabian Wenk"
> Date: Wednesday, July 6, 2011, 1:51 AM
> On 05.07.2011 21:20, Unga wrote:
> > Thanks for the reply.
> >
>
Hello Unga
On 05.07.2011 20:22, Unga wrote:
--- On Wed, 7/6/11, Andrey V. Elsukov wrote:
You should add 'options IPFIREWALL' in the your kernel
config too.
ipfw(8) man page for 'fwd' shows to add only the IPFIREWALL_FORWARD.
I guess the manpage implies that 'options IPFIREWALL' is al
On 05.07.2011 22:46, Fabian Wenk wrote:
>> ipfw(8) man page for 'fwd' shows to add only the IPFIREWALL_FORWARD.
>
> I guess the manpage implies that 'options IPFIREWALL' is already there,
> or the module is loaded, can be done with:
> kldload ipfw
>
> So you do not need to rebuild the kernel.
Hello Andrey
On 05.07.2011 21:04, Andrey V. Elsukov wrote:
fwd does not work when ipfw loaded as module.
Ups, did not know this exactly, thanks for clarify. But it really
makes sense that both options are in the kernel.
After sending out my mail, it somehow crossed my mind that this
eventua
Synopsis: [ipfw] [dummynet] ipfw + dummynet corrupts ipv6 packets
State-Changed-From-To: patched->closed
State-Changed-By: ae
State-Changed-When: Wed Jul 6 05:49:09 UTC 2011
State-Changed-Why:
Merged to stable/8. Thanks!
http://www.freebsd.org/cgi/query-pr.cgi?pr=157239
_
The following reply was made to PR kern/157239; it has been noted by GNATS.
From: dfil...@freebsd.org (dfilter service)
To: bug-follo...@freebsd.org
Cc:
Subject: Re: kern/157239: commit references a PR
Date: Wed, 6 Jul 2011 05:43:13 + (UTC)
Author: ae
Date: Wed Jul 6 05:42:52 2011
New
Synopsis: [ipfw] [patch] fwd reached after skipto in dynamic rules does not
work in every case
State-Changed-From-To: patched->closed
State-Changed-By: ae
State-Changed-When: Wed Jul 6 06:58:11 UTC 2011
State-Changed-Why:
Merged to stable/7 and stable/8. Thanks!
http://www.freebsd.org/cgi/query
Synopsis: [ipfw] ipfw dynamic rules and fwd
State-Changed-From-To: patched->closed
State-Changed-By: ae
State-Changed-When: Wed Jul 6 06:58:55 UTC 2011
State-Changed-Why:
Merged to stable/7 and stable/8. Thanks!
http://www.freebsd.org/cgi/query-pr.cgi?pr=147720
__
13 matches
Mail list logo