Project

General

Profile

Actions
Copy link

Bug #4082

closed

Adding to Captive Portal Allowed Hostnames list gives error (exit code 71) in System Logs

Added by David Goldstrom over 10 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Very Low
Assignee:
-
Category:
Captive Portal
Target version:
-
Start date:
12/07/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1.5
Affected Architecture:
All

Description

Adding a web address to the Captive Portal's Allowed Hostnames list consistently gives this error in the system logs:
php: /services_captiveportal_hostname_edit.php: The command '/sbin/ipfw -x cpzone /tmp/hostname_rules' returned exit code '71', the output was 'Line 3: setsockopt(IP_FW_TABLE_ADD): File exists'

System as a nanobsd (4g) running on a Watchguard Firebox (1386) and has been upgraded through various versions, and been running pfSense for almost 4 years.

Actions
Copy link
 #1

Updated by Chris Buechler over 10 years ago

  • Category set to Captive Portal
  • Status changed from New to Confirmed
  • Priority changed from Normal to Very Low
  • Affected Architecture All added
  • Affected Architecture deleted (i386)

that's just cosmetic, when it tries to add something that's already there.

Actions
Copy link
 #2

Updated by David Goldstrom over 10 years ago

Thanks; so when I add pfsense.org , which is not already there :o), it gives the same error.
Currently, that pass through feature is not working at all on my setup; there are a couple of reasons I can think of that the "Allowed Hostnames" feature isn't working right now, in addition to the error I posted. I'll do some troubleshooting with a spare pfsense box and see if I can get it to work.

Actions
Copy link
 #3

Updated by A FL almost 7 years ago

I can not reproduce this.

Could this bug have been fixed by https://github.com/pfsense/pfsense/commit/517b893eec63ce7695bc91b3a0e82882136e8ef5 ?

Actions
Copy link
 #4

Updated by A FL almost 7 years ago

After further investigation, i confirm that this bug has been fixed in commit 517b893 (precisely here : https://github.com/pfsense/pfsense/commit/517b893eec63ce7695bc91b3a0e82882136e8ef5#diff-764cc5453dc616c068ba7adeb68ba73eL1196 )

The root cause of this bug was that captiveportal_allowedhostname_configure() was restarting filterdns, which caused IP to be added twice in ipfw tables (fist add was done by filterdns, second add by pfSense GUI...)

This has been fixed 2 years ago. This issue can be marked as resolved.

Actions
Copy link
 #5

Updated by Jim Pingle almost 7 years ago

  • Status changed from Confirmed to Resolved
Actions
Copy link

Also available in: Atom PDF