- Freeradius-Users - lists.freeradius.org

Re: Freeradius-Users Digest, Vol 122, Issue 104
by firing neurons 22 Jul '15

22 Jul '15

What is the best way to allow radiusd? Will I have to add cutom policy for each type of access that is blocked? Or is there a quick way that doesn't involve disabling SElinux? Message: 1 Date: Thu, 25 Jun 2015 13:34:14 +0000 From: Ben Gatewood <Ben.Gatewood(a)essensys.co.uk> To: FreeRadius users mailing list <freeradius-users(a)lists.freeradius.org> Subject: Re: radiusd not starting at boot. Message-ID: <4B8DA7A1-2801-4D0C-8FC7-1749BFB031EF(a)essensys.co.uk> Content-Type: text/plain; charset="utf-8" "SELinux is preventing radiusd from read access on the file /etc/raddb/dictionary" On 25/06/2015 14:28, "firing neurons" <firingneurons(a)mail.com> wrote: > I am using 3.0.8. > > The result of service radiusd status: > > Redirecting to /bin/systemctl status -l radiusd.service > ● radiusd.service - FreeRADIUS high performance RADIUS server. > Loaded: loaded (/usr/lib/systemd/system/ > radiusd.service; enabled; > vendor preset: disabled) > Active: failed (Result: exit-code) since Fri 2015-06-26 00:08:14 > IST; 5h 24min left > Process: 819 ExecStartPre=/usr/sbin/radiusd -C (code=exited, > status=1/FAILURE) > Process: 794 ExecStartPre=/bin/chown -R radiusd.radiusd > /var/run/radiusd (code=exited, status=0/SUCCESS) > Jun 26 00:08:11 localhost.localdomain systemd[1]: Starting FreeRADIUS > high performance RADIUS server.... > Jun 26 00:08:14 localhost.localdomain systemd[1]: radiusd.service: > control process exited, code=exited status=1 > Jun 26 00:08:14 localhost.localdomain systemd[1]: Failed to start > FreeRADIUS high performance RADIUS server.. > Jun 26 00:08:14 localhost.localdomain systemd[1]: Unit radiusd.service > entered failed state. > Jun 26 00:08:14 localhost.localdomain systemd[1]: radiusd.service > failed. > > result of service radiusd start: > Redirecting to /bin/systemctl start radiusd.service > Job for radiusd.service failed. See "systemctl status radiusd.service" > and "journalctl -xe" for details. > [cleardot.gif] > result of journalctl -xe: > > >Jun 25 18:50:56 localhost.localdomain setroubleshoot[2449]: SELinux is >preventin >g radiusd from read access on the file /etc/raddb/dictionary. For >complete SELin >ux messages. run sealert -l 35e3131e-b329-4326-add0-6fde9b762f14 >Jun 25 18:50:56 localhost.localdomain python[2449]: SELinux is preventing >radius >d from read access on the file /etc/raddb/dictionary. > > ***** Plugin >restorecon (99 >.5 confidence) suggests ************************ > > If you want to fix >the label >. > /etc/raddb/dictionary >defaul >t label should be radiusd_etc_t. > Then you can run >restorecon. > Do > # /sbin/restorecon -v >/etc/r >addb/dictionary > > ***** Plugin >catchall (1.49 > confidence) suggests ************************** > > If you believe that >radiusd >should be allowed read access on the dictionary file by default. > Then you should >report this >as a bug. > You can generate a >local pol >icy module to allow this access. > Do > allow this access for >now by > executing: > # grep radiusd >/var/log/audi >t/audit.log | audit2allow -M mypol > # semodule -i mypol.pp > >Jun 25 18:50:56 localhost.localdomain setroubleshoot[2449]: SELinux is >preventin >g radiusd from read access on the file /etc/raddb/clients.conf. For >complete SEL >inux messages. run sealert -l 35e3131e-b329-4326-add0-6fde9b762f14 >Jun 25 18:50:56 localhost.localdomain python[2449]: SELinux is preventing >radius >d from read access on the file /etc/raddb/clients.conf. > > ***** Plugin >restorecon (99 >.5 confidence) suggests ************************ > > If you want to fix >the label >. > >/etc/raddb/clients.conf defa >ult label should be radiusd_etc_t. > Then you can run >restorecon. > Do > # /sbin/restorecon -v >/etc/r >addb/clients.conf > > ***** Plugin >catchall (1.49 > confidence) suggests ************************** > > If you believe that >radiusd >should be allowed read access on the clients.conf file by default. > Then you should >report this >as a bug. > You can generate a >local pol >icy module to allow this access. > Do > allow this access for >now by > executing: > # grep radiusd >/var/log/audi >t/audit.log | audit2allow -M mypol > # semodule -i mypol.pp > >Jun 25 18:50:56 localhost.localdomain polkitd[660]: Unregistered >Authentication >Agent for unix-process:2678:78843 (system bus name :1.64, object path >/org/freed >esktop/PolicyKit1/AuthenticationAgent, locale en_IN.UTF-8) (disconnected >from bu >s) >Jun 25 18:51:00 localhost.localdomain polkitd[660]: Registered >Authentication Ag >ent for unix-process:2863:79253 (system bus name :1.65 >[/usr/bin/pkttyagent --no >tify-fd 5 --fallback], object path >/org/freedesktop/PolicyKit1/AuthenticationAge >nt, locale en_IN.UTF-8) >Jun 25 18:51:00 localhost.localdomain systemd[1]: Starting FreeRADIUS >high perfo >rmance RADIUS server.... >-- Subject: Unit radiusd.service has begun start-up >-- Defined-By: systemd >-- Support: [1]http://lists.freedesktop.org/mailman/listinfo/systemd-devel >-- >-- Unit radiusd.service has begun starting up. >Jun 25 18:51:00 localhost.localdomain audit[2886]: <audit-1400> avc: >denied { >sys_ptrace } for pid=2886 comm="radiusd" capability=19 >scontext=system_u:syste >m_r:radiusd_t:s0 tcontext=system_u:system_r:radiusd_t:s0 >tclass=capability permi >ssive=0 >Jun 25 18:51:00 localhost.localdomain kernel: ptrace of pid 2885 was >attempted b >y: radiusd (pid 2886) >Jun 25 18:51:00 localhost.localdomain audit[2885]: <audit-1400> avc: >denied { >read } for pid=2885 comm="radiusd" name="dictionary" dev="dm-1" >ino=1711521 sco >ntext=system_u:system_r:radiusd_t:s0 >tcontext=unconfined_u:object_r:user_home_t: >s0 tclass=file permissive=0 >Jun 25 18:51:00 localhost.localdomain audit[2885]: <audit-1400> avc: >denied { >read } for pid=2885 comm="radiusd" name="clients.conf" dev="dm-1" >ino=1711520 s >context=system_u:system_r:radiusd_t:s0 >tcontext=unconfined_u:object_r:user_home_ >t:s0 tclass=file permissive=0 >Jun 25 18:51:00 localhost.localdomain systemd[1]: radiusd.service: >control proce >ss exited, code=exited status=1 >Jun 25 18:51:00 localhost.localdomain systemd[1]: Failed to start >FreeRADIUS hig >h performance RADIUS server.. >-- Subject: Unit radiusd.service has failed >-- Defined-By: systemd >-- Support: [2]http://lists.freedesktop.org/mailman/listinfo/systemd-devel >-- >-- Unit radiusd.service has failed. >-- >-- The result is failed. >Jun 25 18:51:00 localhost.localdomain systemd[1]: Unit radiusd.service >entered f >ailed state. >Jun 25 18:51:00 localhost.localdomain systemd[1]: radiusd.service failed. >Jun 25 18:51:00 localhost.localdomain audit[1]: <audit-1130> pid=1 uid=0 >auid=42 >94967295 ses=4294967295 subj=system_u:system_r:init_t:s0 >msg='unit=radiusd comm= >"systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? >res=failed >' >Jun 25 18:51:00 localhost.localdomain setroubleshoot[2449]: SELinux is >preventin >g radiusd from using the sys_ptrace capability. For complete SELinux >messages. r >un sealert -l cac781eb-1cae-4673-b684-6308a2c7ff2b >Jun 25 18:51:00 localhost.localdomain python[2449]: SELinux is preventing >radius >d from using the sys_ptrace capability. > > ***** Plugin >catchall (100. > confidence) suggests ************************** > > If you believe that >radiusd >should have the sys_ptrace capability by default. > Then you should >report this >as a bug. > You can generate a >local pol >icy module to allow this access. > Do > allow this access for >now by > executing: > # grep radiusd >/var/log/audi >t/audit.log | audit2allow -M mypol > # semodule -i mypol.pp > >Jun 25 18:51:00 localhost.localdomain setroubleshoot[2449]: SELinux is >preventin >g radiusd from read access on the file /etc/raddb/dictionary. For >complete SELin >ux messages. run sealert -l 35e3131e-b329-4326-add0-6fde9b762f14 >Jun 25 18:51:00 localhost.localdomain python[2449]: SELinux is preventing >radius >d from read access on the file /etc/raddb/dictionary. > > ***** Plugin >restorecon (99 >.5 confidence) suggests ************************ > > If you want to fix >the label >. > /etc/raddb/dictionary >defaul >t label should be radiusd_etc_t. > Then you can run >restorecon. > Do > # /sbin/restorecon -v >/etc/r >addb/dictionary > > ***** Plugin >catchall (1.49 > confidence) suggests ************************** > > If you believe that >radiusd >should be allowed read access on the dictionary file by default. > Then you should >report this >as a bug. > You can generate a >local pol >icy module to allow this access. > Do > allow this access for >now by > executing: > # grep radiusd >/var/log/audi >t/audit.log | audit2allow -M mypol > # semodule -i mypol.pp > >Jun 25 18:51:00 localhost.localdomain setroubleshoot[2449]: SELinux is >preventin >g radiusd from read access on the file /etc/raddb/clients.conf. For >complete SEL >inux messages. run sealert -l 35e3131e-b329-4326-add0-6fde9b762f14 >Jun 25 18:51:00 localhost.localdomain python[2449]: SELinux is preventing >radius >d from read access on the file /etc/raddb/clients.conf. > > ***** Plugin >restorecon (99 >.5 confidence) suggests ************************ > > If you want to fix >the label >. > >/etc/raddb/clients.conf defa >ult label should be radiusd_etc_t. > Then you can run >restorecon. > Do > # /sbin/restorecon -v >/etc/r >addb/clients.conf > > ***** Plugin >catchall (1.49 > confidence) suggests ************************** > > If you believe that >radiusd >should be allowed read access on the clients.conf file by default. > Then you should >report this >as a bug. > You can generate a >local pol >icy module to allow this access. > Do > allow this access for >now by > executing: > # grep radiusd >/var/log/audi >t/audit.log | audit2allow -M mypol > # semodule -i mypol.pp > >Jun 25 18:51:01 localhost.localdomain polkitd[660]: Unregistered >Authentication >Agent for unix-process:2863:79253 (system bus name :1.65, object path >/org/freed >esktop/PolicyKit1/AuthenticationAgent, locale en_IN.UTF-8) (disconnected >from bu >s) >- >List info/subscribe/unsubscribe? See >[3]http://www.freeradius.org/list/users.html ------------------------------ References 1. http://lists.freedesktop.org/mailman/listinfo/systemd-devel 2. http://lists.freedesktop.org/mailman/listinfo/systemd-devel 3. http://www.freeradius.org/list/users.html

3 2

configure freeRADIUS with a CHAP "access-challenge" message
by Arul Sundaramoorthy 22 Jul '15

22 Jul '15

Hi, Can anyone please let me know How to configure freeRADIUS server so it replies with a CHAP "access-challenge" message on "access-request" from a client? I am new to the freeradius tool. so it will better if anyone provide the document for above request. Thanks, Arnold

3 2

Re: udp sockets and proxy servers
by Sergey Komarov 22 Jul '15

22 Jul '15

Hello Arran, Alan and colleagues! > Hmmm, well that's problematic. Could you open a GitHub issue. > > -Arran > Ok, done. I opened issue at Github: "FreeRadius 3.0.9 tries to open more and more sockets for proxy server until crash" #1155 I understand thats FR is free software but I hope may be someone helps we with a patch or advise should I try to build 3.1.x or other versions to get CoA proxy stable with lots of home servers. Thank you in advance for your help! Best Regards, Serge Komaroff > > > I'm tring to run 3.0.9 configuration with about ~1500 clients and home > > > servers (as I have about 1500 WLCs in the network and I try to proxy > CoA > > > packet to WLCs via radius). > > > > > > Radius server tries to open as many sockets as possible doing like > that: > > > > > > Info: ... adding new socket proxy address * port 46527 > > > Info: ... adding new socket proxy address * port 38003 > > > > > > It happens slowly or fast and it depends of load as I see it... And > then > > > after about 256 sockets server quits from running with error: > > > > Is that with TLS? Or TCP? We didn't predict that people would use 256 > > or more clients with CoA and TCP. > > > > But it *should* work for UDP. There's no reason for it to open many > > proxy sockets. It just needs one or two. > > > > Alan DeKok. > > > > Hello Alan! The case is that I'm using UDP only, no any TLS now, just > common pap/sql and Acc Req/Accept/CoA Proxy... SQL sockets is ok and no > overflow there (it even close some connections to DB when don't need it). > > But it looks like FR tries to create as many sockets as home servers and it > happen slowly - depends on load. When I limit to 200 home servers - it > stopped to create sockets at number about 153... In case it overcome 256 it > drops soon with that error... > > > Best Regards, Serge Komaroff >

1 0

set up the linelog mod to create a CSV log
by Nash.Paz 22 Jul '15

22 Jul '15

Hi, Running 3.0.4 on Centos 7.1, I've been trying to set up the linelog mod to create a CSV log. Based on what I read here: http://marc.info/?l=freeradius-users&m=133167783813402 http://lists.freeradius.org/pipermail/freeradius-users/2012-March/059283.ht… I added a header, and a stop/start accounting for Acct-Status-Type to the linelog file (attached). Restarted radiusd, but no linelog files are created. Radius is working, the detail file gets updated. The module seems to load when running radiusd -X : # Instantiating module "linelog" from file /etc/raddb/mods-enabled/linelog linelog { filename = "/var/log/radius/linelog" permissions = 384 format = "This is a log message for %{User-Name}" reference = "messages.%{%{Packet-Type}:-default}" } # Instantiating module "log_accounting" from file /etc/raddb/mods-enabled/linelog linelog log_accounting { filename = "/var/log/radius/linelog-accounting" permissions = 384 format = "" reference = "Accounting-Request.%{%{Acct-Status-Type}:-unknown}" } What am I doing wrong? -- -נחשון פז-

2 2

IPv6 coa isn't working having IPv6 NAS IP
by Samir Patel 21 Jul '15

21 Jul '15

Hi Experts, I need your help and expertise with pushing ipv6 coa on the 802.1x sessions. UUT (Switch) and Freeradius are directly connected and can ping each other. Freeradius installed: [root@ott-freerad-7a raddb]# radiusd -X radiusd: FreeRADIUS Version 2.2.8, for host x86_64-unknown-linux-gnu, built on Jul 15 2015 at 13:42:04 Copyright (C) 1999-2015 The FreeRADIUS server project and contributors. Issue: [root@ott-freerad-7a raddb]# /usr/local/bin/radclient -x -t 20 -c 1 -p 20 -f /usr/local/etc/raddb/coa 2020::11:1700 coa cisco radclient: Failed to find IP address for host 2020::11:1700: Success COA push works for IPv4 NAS IP but shows above for IPv6 case. Really appreciate your help with the issue. I am not sure if IPv6 coa push is supported yet with 2.2.8 freeradius version. [root@ott-freerad-7a raddb]# more coa Calling-Station-Id="c414.3c52.900e" Acct-Session-Id="0x0000000b" Cisco-Command-Code=" TEMP_IAF100" [root@ott-freerad-7a raddb]# [root@ott-freerad-7a raddb]# [root@ott-freerad-7a raddb]# [root@ott-freerad-7a raddb]# [root@ott-freerad-7a raddb]# /usr/local/bin/radclient -x -t 20 -c 1 -p 20 -f /usr/local/etc/raddb/coa 2020::11:1700 coa cisco [root@ott-freerad-7a raddb]# ifconfig eth0 Link encap:Ethernet HWaddr 00:50:56:8E:78:33 inet addr:172.16.7.11 Bcast:172.16.255.255 Mask:255.255.0.0 inet6 addr: fe80::250:56ff:fe8e:7833/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:80804 errors:0 dropped:0 overruns:0 frame:0 TX packets:20649 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:14539074 (13.8 MiB) TX bytes:3061296 (2.9 MiB) eth1 Link encap:Ethernet HWaddr 00:50:56:8E:5F:BB inet addr:99.0.7.12 Bcast:99.0.7.255 Mask:255.255.255.0 inet6 addr: 2020::250:56ff:fe8e:5fbb/64 Scope:Global inet6 addr: fe80::250:56ff:fe8e:5fbb/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:47806 errors:0 dropped:0 overruns:0 frame:0 TX packets:138 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3463175 (3.3 MiB) TX bytes:17024 (16.6 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:936 errors:0 dropped:0 overruns:0 frame:0 TX packets:936 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:66843 (65.2 KiB) TX bytes:66843 (65.2 KiB) [root@ott-freerad-7a raddb]# [root@ott-freerad-7a raddb]# ping6 2020::11 PING 2020::11(2020::11) 56 data bytes 64 bytes from 2020::11: icmp_seq=0 ttl=64 time=11.4 ms 64 bytes from 2020::11: icmp_seq=1 ttl=64 time=1.52 ms --- 2020::11 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 1.521/6.463/11.405/4.942 ms, pipe 2 [root@ott-freerad-7a raddb]# [root@ott-freerad-7a raddb]# uname -a Linux ott-freerad-7a 2.6.18-194.8.1.el5 #1 SMP Wed Jun 23 10:52:51 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux [root@ott-freerad-7a raddb]# On UUT: Router#show run int gig2/0/15 Building configuration... Current configuration : 108 bytes ! interface GigabitEthernet2/0/15 no switchport no ip address ipv6 address 2020::11/64 ipv6 enable end Router# Router# Router# Router# Router# Router# Router# Router#show access-sess Interface MAC Address Method Domain Status Fg Session ID -------------------------------------------------------------------------------------------- GigabitEthernet2/0/14 c414.3c52.900e dot1x DATA Auth 000000000000001706794990 Session count = 1 Key to Session Events Blocked Status Flags: A - Applying Policy (multi-line status for details) D - Awaiting Deletion F - Final Removal in progress I - Awaiting IIF ID allocation P - Pushed Session R - Removing User Profile (multi-line status for details) U - Applying User Profile (multi-line status for details) X - Unknown Blocker Router# Router#show access-sess poli Router#show access-sess inter Router#show access-sess interface gig2/0/14 polic Router#show access-sess interface gig2/0/14 policy Interface : GigabitEthernet2/0/14 MAC Address : c414.3c52.900e IPv6 Addres : Unknown IPv4 Addres : Unknown User-Name : client1 Status : Authorized Domain : DATA Oper host mode : multi-host Oper control dir : both Session timeout : N/A Timeout action : Reauthenticate Idle timeout : N/A Common Session ID : 000000000000001706794990 Acct Session ID : 0x0000000b Handle : 0x3c00000d Current Policy : DUAL Blocked On : Method status list: Method State dot1x Authc Success Device Classification Status: ------------------------------------------------------------------------------- Profile Device-Name Device-Class ------------------------------------------------------------------------------- Un Classified Un-Classified Un-Classified

3 7

Auth-Type := ldap
by ST Wong (ITSC) 21 Jul '15

21 Jul '15

Hi all, We're using freeradius 3.0.4-6.el7 on RHEL 7, using LDAP authentication. The server is setup and running without problem. However, I got error when running radwho: -------------- cut here -------------------- ]# radwho Tue Jul 21 18:58:16 2015 : Error: /etc/raddb/sites-enabled/default[384]: Parse error in condition Tue Jul 21 18:58:16 2015 : Error: if ((ok || updated) && User-Password) { Tue Jul 21 18:58:16 2015 : Error: ^ Expected a module return code radwho: Error reading or parsing radiusd.conf -------------- cut here -------------------- I modified /etc/raddb/sites-enabled/default as following as mods-available/ldap mentioned: -------------- mods-available/ldap -------------------- # Note: set_auth_type was removed in v3.x.x # Equivalent functionality can be achieved by adding the following # stanza to the authorize {} section of your virtual server. # # ldap # if ((ok || updated) && User-Password) { # update { # control:Auth-Type := ldap # } # } -------------- cut here -------------------- -------------- /etc/raddb/sites-enabled/default -------------------- # # The ldap module reads passwords from the LDAP database. # -ldap ldap if ((ok || updated) && User-Password) { update { control:Auth-Type := ldap } } -------------- cut here -------------------- Did I miss anything? Besides, I'm new to freeradius 3.x and can't find doc about the meaning of the minus sign before module (e.g. "-ldap"). Would anyone please help? Thanks a lot. Regards, /ST Wong

1 0

Re: udp sockets and proxy servers
by Sergey Komarov 21 Jul '15

21 Jul '15

Hello! > Hmmm, well that's problematic. Could you open a GitHub issue. > > -Arran > Hello Arran. Well, I'm not a developer actually I will try to post it to GitHub in case my credentials is ok for that... > Date: Mon, 20 Jul 2015 19:48:25 +0200 > From: Alan DeKok <aland(a)deployingradius.com> > To: FreeRadius users mailing list > <freeradius-users(a)lists.freeradius.org> > Subject: Re: udp sockets and proxy servers > Message-ID: <56E2A5E4-DFAD-4B47-816E-28CDFF51DACF(a)deployingradius.com> > Content-Type: text/plain; charset=us-ascii > > On Jul 20, 2015, at 7:15 PM, Sergey Komarov <sergey.komaroff(a)gmail.com> > wrote: > > I'm tring to run 3.0.9 configuration with about ~1500 clients and home > > servers (as I have about 1500 WLCs in the network and I try to proxy CoA > > packet to WLCs via radius). > > > > Radius server tries to open as many sockets as possible doing like that: > > > > Info: ... adding new socket proxy address * port 46527 > > Info: ... adding new socket proxy address * port 38003 > > > > It happens slowly or fast and it depends of load as I see it... And then > > after about 256 sockets server quits from running with error: > > Is that with TLS? Or TCP? We didn't predict that people would use 256 > or more clients with CoA and TCP. > > But it *should* work for UDP. There's no reason for it to open many > proxy sockets. It just needs one or two. > > Alan DeKok. > Hello Alan! The case is that I'm using UDP only, no any TLS now, just common pap/sql and Acc Req/Accept/CoA Proxy... SQL sockets is ok and no overflow there (it even close some connections to DB when don't need it). But it looks like FR tries to create as many sockets as home servers and it happen slowly - depends on load. When I limit to 200 home servers - it stopped to create sockets at number about 153... In case it overcome 256 it drops soon with that error... Best Regards, Serge Komaroff

1 0

RLM_Rest and Dynamic Clients
by Nick Cappelletti 20 Jul '15

20 Jul '15

FreeRADIUS version: 3.0.9 I was curious if there was a way to include dynamic-clients via the rest api module in FreeRADIUS. I currently have it setup using LDAP, but we’re looking to use a dedicated server cluster to manage our NAS’s and I’m having a hard time wrapping my head around a way of configuring such an implementation. Any links or previous threads would be extremely helpful. Thanks!

3 8

udp sockets and proxy servers
by Sergey Komarov 20 Jul '15

20 Jul '15

Hello, I'm tring to run 3.0.9 configuration with about ~1500 clients and home servers (as I have about 1500 WLCs in the network and I try to proxy CoA packet to WLCs via radius). Radius server tries to open as many sockets as possible doing like that: Info: ... adding new socket proxy address * port 46527 Info: ... adding new socket proxy address * port 38003 It happens slowly or fast and it depends of load as I see it... And then after about 256 sockets server quits from running with error: "Error: Failed adding event handler for socket: Too many readers ". Server stops after that. I checked under CentOS 6 and under FreeBSD. Its same effect and OS doesn't matter. Does this means I need number of sockets equal to number of home servers and it is impossible to run FR with more than 256 home servers now or I missed something and FR able to reuse/limit udp sockets somehow? In case someone could show me correct idea and how to solve my problem I will be glad to follow. Thank you in advance for your help! Best Regards, Serge Komaroff

3 2

FreeRADIUS & security
by Paul Gunman 20 Jul '15

20 Jul '15

Hello, I would like to know whether FreeRADIUS user SNMPv3 and allow IP filtering for access through SSH. Moreover, is there anything related to PCI compliance? Thanks, P.

3 2