Make radius timeout value persistent across updates

Interesting, Darrell - where is the config file for RADIUS?

Cheers - Bob

It is the radius timeout entry in /var/aua/AuaConfig.pm:

# Wait timeouts
#
our $handle_client_timeout   = 5;
our $shutdown_client_timeout = 2;
our $radius_timeout          = 30;
our $tacacs_timeout          = 30;
our $ldap_connection_timeout = 10;
our $ldap_search_timeout     = 10;
our $ldap_bind_timeout       = 10;

It is the radius_timeout I have changed from 3 to 30.  It has been a while since it was an issue, but I would typically not notice until I could not authenticate remotely (home user) :).

Sorry for the slow reply.

Thanks, Darrell - great contribution!

I tried this and found that the file name ends with a .pm instead of .pem so I edited your post to correct that.

Cheers - Bob

Thanks Bob.  Sorry I missed that, too much certificate work lately I guess...

I'm not a linux scripter, but someone with that skill could craft a sed to make that replacement and you could then add it to /etc/crontab-static using @reboot.  As an example, where I have clients with Sophos APs, I added the following line last year to deal with a temporary bug:

@reboot root /sbin/ethtool -K wlan0 tso off && date>/home/ethtoolran

Cheers - Bob

Thanks for this.  I was hoping for something more "official" when I saw someone else's post using the cc commands.  I may look and hacking something together.  It has not been an issue in the last several updates, but that may just be luck that the auth pkgs were included in the updates.  Knowing which crontab will get me to the same place!

Hi Guys,

thanks for the information.