Project

General

Profile

Actions

Bug #5406

closed

FreeRADIUS will run with its default conf after being reinstalled by pfsense's upgrade process

Added by Heiler Bemerguy about 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Category:
FreeRADIUS
Target version:
-
Start date:
11/09/2015
Due date:
% Done:

0%

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

Description

Everytime I update pfsense, the freeradius package goes back to its default conf, even though the GUI keeps its previous setup.

It's easily noticed by the errors on the log file:
Mon Nov 9 16:42:04 2015 : Info: Loaded virtual server <default>
Mon Nov 9 16:42:04 2015 : Info: Ready to process requests.
Mon Nov 9 16:42:17 2015 : Error: [ldap] bind to ldap.your.domain:389 failed: Can't contact LDAP server
Mon Nov 9 16:42:17 2015 : Error: [ldap] (re)connection attempt failed

Then after going to its "LDAP" tab clicking on SAVE, everything comes back to normal like it was before upgrading.

Actions #1

Updated by Kill Bill about 6 years ago

That's because freeradius_modulesldap_resync() is not called anywhere on install.

https://github.com/pfsense/pfsense-packages/pull/1149

Actions #2

Updated by Jim Thompson about 6 years ago

  • Assignee set to Renato Botelho
Actions #3

Updated by Kill Bill about 6 years ago

Should be fixed in 1.6.18

Actions #4

Updated by Chris Buechler about 6 years ago

  • Status changed from New to Resolved

thanks

Actions #5

Updated by Chris Buechler about 6 years ago

  • Category set to FreeRADIUS
Actions

Also available in: Atom PDF