June 2018 - Freeradius-Users - lists.freeradius.org

Default Certificate Expiration Time
by Mitch Sullivan 05 Jun '18

05 Jun '18

Hi Team I created an Instance of FreeRadius a few months back for my organisation. I followed the user guide for setting up certificates. http://deployingradius.com/documents/configuration/certificates.html Deploying RADIUS: Production Certificates<http://deployingradius.com/documents/configuration/certificates.html> deployingradius.com Production Certificates. Once the initial EAP testing has been performed, it is time to create the real certificates to use in your production network. These certificates will be configured on the end hosts that will be doing PEAP, TTLS, or EAP-TLS authentication. It seems the Certificates have expired, which is fine for OS X and Linux devices, which install new certificates automatically next time you connect while connecting but not for Windows10 that require the certificates be installed manually. Is it possible for me to change the certificates so they last a year? Thanks Mitch.Sullivan mitch.sullivan(a)swarm64.com IT administrator | Swarm64 AS Swarm64 AS Zweigstelle Hive Ullsteinstr. 120 | 12109 Berlin | Germany

3 2

Invalid packet code 1 sent to a accounting port from client : IGNORED
by Saurabh Lahoti 05 Jun '18

05 Jun '18

Dear, Could you please help me with below error whilst radius running in debug mode..? Invalid packet code 1 sent to a accounting port from client port 33393 : IGNORED ---- *Thanks & Kind Regards,* Saurabh LAHOTI.

2 1

RE: TLSMC: MozNSS compatibility interception begins message
by Chris Howley 05 Jun '18

05 Jun '18

Alan, Thank you for the link: https://wiki.freeradius.org/modules/Rlm_ldap The server is using PEAP-MSCHAPv2 and LDAP not LDAPS. The messages are generated only when the server is started. Am I correct in assuming that I can safely ignore the messages? If I want to use LDAPS in the future, is the FR message below telling me that the server has been built with the correct libraries? Tue Jun 5 07:47:57 2018 : Info: Debugger not attached Tue Jun 5 07:47:58 2018 : Info: rlm_ldap: libldap vendor: OpenLDAP, version: 20444 Thank you for your time. Chris Howley

2 1

Compatible device
by rints harry 05 Jun '18

05 Jun '18

Hi Could you share compatible devices with accounting used by freeradius. I want to implement hotspot in public area. Thx again

2 1

Not able to see RADIUS access request in debug mode
by Amit Mittal 04 Jun '18

04 Jun '18

Hi, I have installed freeradius ver. 3.0.13-9.el7_5 on CentOS Linux release 7.5.1804 After setting up the Users and client.conf files (attached) and running the radius server in debug mode (radius -X), I am not able to see the radius access-request packets coming in. I am able to see the access-request packets coming on the ethernet interface using the "tcpdump" utility though. Please let me know if I am doing something wrong in here. TIA Amit Mittal ________________________________ DISCLAIMER: This e-mail and any attachments to it may contain confidential and proprietary material and is solely for the use of the intended recipient. Any review, use, disclosure, distribution or copying of this transmittal is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed.

2 2

TLSMC: MozNSS compatibility interception begins message
by Chris Howley 04 Jun '18

04 Jun '18

Hi, I rebuilt the FreeRDAIUS 3.0.15 packages, but I'm still seeing the same message in /var/log/messages file. The build host is running CentOS Linux release 7.5.1804 (Core). Do I need to use a different FreeRADIUS SPEC file? Any help in fixing this problem would be appreciated. Thanks, Chris Howley Jun 4 08:46:23 XXXXXX radiusd: tlsmc_convert: INFO: cannot open the NSS DB, expecting PEM configuration is present. Jun 4 08:46:23 XXXXXX radiusd: tlsmc_intercept_initialization: INFO: successfully intercepted TLS initialization. Continuing with OpenSSL only. Jun 4 08:46:23 XXXXXX radiusd: TLSMC: MozNSS compatibility interception ends. Jun 4 08:46:23 XXXXXX systemd: Started FreeRADIUS high performance RADIUS server..

4 3

How to include username field at the end of access logs.
by Saurabh Lahoti 02 Jun '18

02 Jun '18

Dear, Could you please help is getting username filed in the access logs post accept or reject of the request..? ---- *Thanks & Kind Regards,* Saurabh LAHOTI. *Mob: +32.499.82.37.88* *Ideas enlighten Innovation**!!!* Please consider the environment before printing this mail..!!

1 0

Re: Error in access_reject
by Saurabh Lahoti 01 Jun '18

01 Jun '18

Thanks Alan for helping in fixing the error. ---- *Thanks & Kind Regards,* Saurabh LAHOTI.

1 0

Compilation Warning - FreeRadius 3.0.16
by Andrea Mucci 01 Jun '18

01 Jun '18

Hi All, we downloaded the source software freeradius 3.0.16 from: git clone https://github.com/FreeRADIUS/freeradius-server.git cd freeradius-server git checkout release_3_0_16 The OS is RHEL 7.4. We will use freeRadius with Oracle 12 DataBase. We compiled with this enviroment variable seting export LD_LIBRARY_PATH=/usr/lib/oracle/12.2/client64/lib:/usr/lib:/usr/lib64 export ORACLE_HOME=/usr/include/oracle/12.2/client64 We had this WARNING: configure: WARNING: securid headers not found. Use --with-rlm-securid-include-dir=<path>. checking for SD_Init in -laceclnt... no checking for SD_Init in -laceclnt in /usr/local/lib... no checking for SD_Init in -laceclnt in /opt/lib... no configure: WARNING: securid libraries not found. Use --with-rlm-securid-lib-dir=<path>. configure: WARNING: silently not building rlm_securid. configure: WARNING: FAILURE: rlm_securid requires: acexport.h libaceclnt. configure: WARNING: silently not building rlm_opendirectory. configure: WARNING: FAILURE: rlm_opendirectory requires: membership.h. configure: WARNING: Oracle version >= 12 needs -laio We would like to know if these warnings can generate incorrect behavior of the software. Thanks Andrea

4 4

Error in access_reject
by Saurabh Lahoti 01 Jun '18

01 Jun '18

Dear, While initializing radius in debug mode getting below error: /usr/app/radius-new2/prod-corp-internal/etc/raddb/mods-config/attr_filter/access_reject[18]: Entry does not begin with a user name Errors reading /usr/app/radius-new2/prod-corp-internal/etc/raddb/mods-config/attr_filter/access_reject /usr/app/radius-new2/prod-corp-internal/etc/raddb/mods-enabled/attr_filter[28]: Instantiation failed for module "attr_filter.access_reject" Coulf you please help..? ---- *Thanks & Kind Regards,* Saurabh LAHOTI.

2 1