Project

General

Profile

Actions

Bug #1531

closed

ipfw broken in 2.0-RC1

Added by Frank Heydlauf over 13 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
05/16/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.0
Affected Plus Version:
Affected Architecture:

Description

using:

8.1-RELEASE-p2 FreeBSD 8.1-RELEASE-p2 #0: Tue Apr 19 23:38:02 EDT 2011
sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386
with IPv6-patch from Seth.

on console I get:

ipfw list
ipfw: getsockopt(IP_FW_GET): Protocol not available

ipfw table all list
ipfw: Warn: Failed to get the max tables number via sysctl. Using the compiled in defaults.
The reason was: No such file or directory
ipfw: getsockopt(IP_FW_TABLE_GETSIZE): Protocol not available

just tried the current snapshot:

FreeBSD 8.1-RELEASE-p3 #0: Sun May 15 21:21:53 EDT 2011 sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386

still same error message

Regards
F.

Actions #1

Updated by Jim Pingle over 13 years ago

  • Status changed from New to Feedback

ipfw isn't loaded by default. If you have a feature enabled that needs IPFW (captive portal, limiters, etc) it will be loaded and then it works. Check kldstat before and after enabling a feature such as captive portal and notice the differences.

Actions #2

Updated by Frank Heydlauf over 13 years ago

sorry for the noise.
I just came across some ipfw commands while digging for IPv6 settings and
haven't had a look at the kernel module :-((
Drop this ticket, plz.

Actions #3

Updated by Jim Pingle over 13 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF