Project

General

Profile

Bug #3174

Re: ipfw3 check-state doesn't work

Added by aly 8 months ago. Updated 8 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/15/2019
Due date:
% Done:

0%

Estimated time:

Description

Hi Nima,

I can confirm this issue. I believe this is a bug in IPFW3.

Hi Bill, would you please have a look? Actually, "ipfw3" cannot add any rules,
complaining "ipfw3: getsockopt(IP_FW_ADD): Invalid argument". Thanks.

Cheers,
Aaron

On Mon, 11 Feb 2019 17:09:04 +0330
Nima Azizzadeh <> wrote:

> Hi Aaron
> Thanks for the response. Yes, all modules was loaded. It doesn't solve the
> problem!
>
> Regards,
> Nima
>
> On Thu, Feb 7, 2019 at 2:54 PM Aaron LI <> wrote:
>
> > Quoting Nima Azizzadeh (2019-02-07 17:18:55)
> > > Hello,
> > > We are working on a project that includes DragonFlyBSD and IPFW3. On
> > > this phase of project we are trying to test all features. Based on
> > > official DragonFlyBSD
> > > documents(https://www.dragonflybsd.org/docs/ipfw3/) for
> > using
> > > stateful firewall and checking every traffic state, we must use "ipfw3
> > add
> > > check-state" rule. When I use the syntax I got this error :
> > > # ipfw3 add check-state
> > > ipfw3: getsockopt(IP_FW_ADD): Invalid argument
> > >
> >
> > Hi Nima,
> >
> > Did you load the necessary modules? If not, try and load all IPFW3
> > modules, i.e., "ipfw3", "ipfw3_basic", "ipfw3_layer2", "ipfw3_layer4",
> > and "ipfw3_nat".
> >
> > Hope this solves your problem.
> >

History

#1

Updated by liweitianux 8 months ago

  • Status changed from New to Resolved

The fix was commit in 72ce8e08d0708ac9f09d9cda56e3308ad8dcec48 .

Also available in: Atom PDF