Re: [RADIATOR] Debian Bullseye support ?

2021-08-17 Thread Heikki Vatiainen

On 17.8.2021 11.47, Patrik Forsberg wrote:

I recently, today, upgraded one of our radiator machines to Debian 
Bullseye and everything worked as it should except when I tried to start 
Radiator.


It fails for the radiator-radius-utilxs_2.3-1 package with “ 
lib/Radius/UtilXS.c: loadable library and perl binaries are mismatched 
(got handshake key 0xce00080, needed 0xed00080) “.


So.. my question is if you have any plans to release a Debian Bullseye 
package for “utilxs” ?


Yes, we actually talked about that yesterday: add it to testing, make 
sure the non-binary deb packages work with it and then compile the 
binary UtilXS for the new Debian release.


The sources are for UtilXS are available with Radiator downloads, so if 
you are in hurry, you can compile it. Look for Radius-UtilXS-2.3-1.tgz


Thanks,
Heikki

--
Heikki Vatiainen
OSC, makers of Radiator
Visit radiatorsoftware.com for Radiator AAA server software
___
radiator mailing list
radiator@lists.open.com.au
https://lists.open.com.au/mailman/listinfo/radiator

Re: [RADIATOR] AuthBy DUO issue

2021-08-17 Thread Alfred Reibenschuh
hello
 
seams like you are facing the same "uncooperative" upstream system issue i have had in the past.
 
i have had similar problems with radius and other protocols, that radiator
would mark all upstream servers offline and never recovering.
 
i did not follow your complete conversation, but iirc DUO is http-based,
so if your issue is ha-related you could get away with setting CheckTimerInterval to 0
and putting a reverse-proxy between radiator and DUO like NGINX
(the community edition of nginx would be sufficient)
 
Yours sincerelyAlfred Reibenschuh
Network Engineer 
(Management & Monitoring Architect)
Unified Communication Services
Network & Telecommunication AT
 
Value Transformation Services GmbHAn IBM CompanyObere Donaustrasse 951020 Wien
Phone: +43-1-2056320-143Mobile: +43-664-3523820
mail: alfred.reibenschuh_v-tservi...@at.ibm.comwebex: https://ibm.webex.com/meet/alfred.reibenschuh_v-tservicesPlease consider the environment before printing this e-mail.This e-mail is confidential and may also contain privileged information. If you are not the intended recipient you are not authorized to read, print, save, process or disclose this message. If you have received this message by mistake, please inform the sender immediately and delete this e-mail, its attachments and any copies.Any use, distribution, reproduction or disclosure by any person other than the intended recipient is strictly prohibited and the person responsible may incur penalties. 
Thank you!
 
 
Message: 1
Date: Mon, 16 Aug 2021 16:23:45 +From: To: , Subject: Re: [RADIATOR] AuthBy DUO issueMessage-ID:Content-Type: text/plain; charset="windows-1252"Hi,that sounds like a sane solution.A simpler might be to mark Duo dead for a configurable number of seconds after which it's marked as alive again without a check. The next authentication would then either work or again trigger marking it as dead.Thanks, AlexT-SYSTEMS AUSTRIA GESMBHPU Cyber SecurityNetwork ArchitectureOperation Manager AuthenticationRennweg 97-99, A-1030 Vienna+43 57057 4320 (phone)+43 676 8642 4320 (mobile)E-mail: alexander.hartma...@t-systems.comInternet: www.t-systems.atBlog: blog.t-systems.atSocial Media: Facebook, Linkedin, TwitterBIG CHANGES START SMALL ? CONSERVE RESOURCES BY NOT PRINTING EVERY E-MAIL.T-Systems Austria GesmbH, Rennweg 97-99, A-1030 ViennaCommercial Court Vienna, FN 79340bNotice: This transmittal and/or attachments may be privileged or confidential. It isintended solely for the addressee named above. If you received this transmittal in error,please notify us immediately by reply and delete this message and all its attachments.Thank you.Von: radiator  im Auftrag von Heikki Vatiainen Gesendet: Mittwoch, 14. Juli 2021 20:26An: radiator@lists.open.com.au Betreff: Re: [RADIATOR] AuthBy DUO issueOn 13.7.2021 18.05, alexander.hartma...@t-systems.com wrote:> We've encountered another issue today: when CheckTimerInterval is> configured to 0, to disable the periodic DUO API check which fills our> log and generated unnecessary traffic and load, the API never recovers> when marked as dead.That seems to be correct, but likely not expected.> Do you have a suggestion how to solve this besides configuring> CheckTimerInterval for something else?Currently there is nothing to solve this. A strategy, such as startingthe poll timer when the API is down and letting it poll until it's up,would be needed.If you have a preferred idea, please let us know.Thanks,Heikki--Heikki Vatiainen Radiator: the most portable, flexible and configurable RADIUS serveranywhere. SQL, proxy, DBM, files, LDAP, TACACS+, PAM, Active Directory,EAP, TLS, TTLS, PEAP, WiMAX, RSA, Vasco, Yubikey, HOTP, TOTP,DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, etc.___

___
radiator mailing list
radiator@lists.open.com.au
https://lists.open.com.au/mailman/listinfo/radiator

[RADIATOR] Debian Bullseye support ?

2021-08-17 Thread Patrik Forsberg
Hello,
I recently, today, upgraded one of our radiator machines to Debian Bullseye and 
everything worked as it should except when I tried to start Radiator.
It fails for the radiator-radius-utilxs_2.3-1 package with “ 
lib/Radius/UtilXS.c: loadable library and perl binaries are mismatched (got 
handshake key 0xce00080, needed 0xed00080) “.

So.. my question is if you have any plans to release a Debian Bullseye package 
for “utilxs” ?

---
Best Regards,
Patrik Forsberg

___
radiator mailing list
radiator@lists.open.com.au
https://lists.open.com.au/mailman/listinfo/radiator