Re: [RADIATOR] Auth by LDAP Ubuntu 12.04 & Radiator 4.10
On 07/03/2013 11:42 PM, John Goubeaux wrote: > Are there specific libraries ( other than those specified in the > Radiator 4.10 docs ) that I need in order to support LDAP binds to the > Sun Directory from Ubuntu ? I have included the config that I am > speaking about below. Your config looks quite fine. Sometimes HTTPS connection and/or a bind by admin user, see AuthDN in the reference manual, is needed to for queries. I'd say per-ldap aka Net::LDAP should be enough for plain LDAP connections. I recommend turning on AuthBy LDAP2 Debug option and running radiusd from the command line with Trace 4 enabled. Something like: radiusd -trace 4 -log_stdout -foreground -config ... This lets you see the LDAP library messages that are printed to STDOUT and can not be logged by Radiator. > OR another way of asking the question : Is anyone successfully running > Radiator 4.10 on Ubuntu 12.04 AND authing against an Oracle DS and IF > so were there any caveats to the build ? If these provide a standard LDAP interface, I would be quite sure they work. It really depends on Net::LDAP module and I'd be surprised if it did not support the ex Sun now Oracle LDAP server. Thanks, Heikki -- Heikki Vatiainen Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc. ___ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
Re: [RADIATOR] Status-Server changes in patches for Radiator 4.11
On 06/19/2013 10:35 AM, Heikki Vatiainen wrote: > The patch set for Radiator 4.11 now has changes to make Status-Server > based detection of failed Hosts more reliable especially when there is > more than one Host defined for AuthBy RADIUS or its subclasses. These changes are now available for AuthBy RADSEC too. Status-Server based alive checking should now work similarly for both AuthBy RADIUS and its subclasses and AuthBy RADSEC when UseStatusServerForFailureDetect is enabled. > Comments and test reports are welcome! Indeed. Especially reports against different RadSec implementations. Currently Proxy-State attribute is used in Status-Server probes, just as with any other requests over RadSec, and it would be good to hear if this is compatible with other RadSec implementations too. Thanks, Heikki -- Heikki Vatiainen Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc. ___ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
[RADIATOR] tacacs unlimited badlogins count
Hi I have radiator setup for tacacs.Default BADLOGINS value is 0.If BADLOGINS value reach 5, account is locked.I want to make this BADLOGINS such a value,so that nobodies account is locked. ___ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
Re: [RADIATOR] Radiator & Debian Wheezy = memory problem?
Hi Sami, Sami Keski-Kasari schrieb: > Hello Kurt, > > I think that you updated to Radiator 4.11 when you updated to Debian 7? yes, breaking the basic rule to never change more than one thing at a time ;-) > > We found memory leak in AuthRADSEC module which was caused by the > change done in 4.10 patches (Special Thanks to Paul Dekkers @SURFnet > for helping us to debug this). > > The change is reverted now in the latest 4.11 patch set. > > Could you try if it helps to your problem? I applied the latest patch set yesterday and can confirm, that the memory leak problem went away. Radiusd is now using about 4% of memory, not increasing for about 20h now. Thanks a lot for the fix, best regards, Kurt > > The change was related to fix some issues in > UseStatusServerForFailureDetect. > > We have done proper fix to AuthByRADIUS as Heikki Vatiainen announced > 2013-06-19: > http://www.open.com.au/pipermail/radiator/2013-June/019148.html > > We are currently integrating those changes to AuthRADSEC and in > meantime I would advice not to use UseStatusServerForFailureDetect in > AuthBy RADSEC. > > Best Regards, > Sami > > > On 06/19/2013 12:04 PM, Kurt Bauer wrote: >> Hi, >> >> since upgrading one of our radius-servers to Debain 7 (Wheezy) we >> expierence serious memory problems, namely Radiator eating up all the >> available memory over time (see attached graph). We have a few Radiator >> installations running and the ones on Debian Squeeze behave fine. >> Radiator 4.11 plus latest patches >> Perl v5.14.2 (as packaged in Wheezy) >> >> Any similar experiences or hints why this could be? Restarting Radiator >> every few days rectifies the situation but is not the way we want to run >> the service ;-) >> >> Thanks for your help, >> best regards, >> Kurt >> >> >> >> >> >> >> -- >> Kurt Bauer >> Vienna University Computer Center - ACOnet - VIX >> Universitaetsstrasse 7, A-1010 Vienna, Austria, Europe >> Tel: ++43 1 4277 - 14070 (Fax: - 814070) KB1970-RIPE >> >> >> >> ___ >> radiator mailing list >> radiator@open.com.au >> http://www.open.com.au/mailman/listinfo/radiator >> > > smime.p7s Description: S/MIME Cryptographic Signature ___ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
