[RADIATOR] 4.29 EAP issue - failed socket

[Hugh Irvine]

Hello Cassidy -

This is very odd - it looks like the socket has not been created properly.

I don't understand how you could receive a packet on a socket and not be 
able to send?

What do the startup messages from Radiator look like?

And what is shown before the log below when the request is received - is 
it the same socket number?

thanks

Hugh


On 17/7/2024 07:37, Cassidy B. Larson via radiator wrote:
> Seeing this after upgrading from a few releases to 4.29 and trying EAP 
> with my same hosts/clients on my in-office wifi:
>
> Tue Jul 16 15:31:05 2024: ERR: sendTo: send to 10.40.176.98 port 60389 
> failed: Socket operation on non-socket
>
>
> We're now running FreeBSD 14.1-RELEASE on this.
>
>
> Here's the last bit of a Trace 5 output..
>
>
> Tue Jul 16 15:31:05 2024: DEBUG: Handling with Radius::AuthFILE:
>
> Tue Jul 16 15:31:05 2024: DEBUG: AuthFILE Handling EAP type 1 
> (Identity), code: 2 (Response), identifier: 22, length: 24
>
> Tue Jul 16 15:31:05 2024: DEBUG: Initialised SSL library: Net::SSLeay 
> 1.94, OpenSSL 3.0.13 30 Jan 2024
>
> Tue Jul 16 15:31:05 2024: DEBUG: TLS: Using 0x8 (8) for Net::SSLeay 
> constant SSL2_MT_CLIENT_CERTIFICATE
>
> Tue Jul 16 15:31:05 2024: DEBUG: TLS: Using 0x3 (3) for Net::SSLeay 
> constant SSL2_MT_CLIENT_FINISHED
>
> Tue Jul 16 15:31:05 2024: DEBUG: TLS: Using 0x2 (2) for Net::SSLeay 
> constant SSL2_MT_CLIENT_MASTER_KEY
>
> Tue Jul 16 15:31:05 2024: DEBUG: TLS: Using 0x0 (0) for Net::SSLeay 
> constant SSL2_MT_ERROR
>
> Tue Jul 16 15:31:05 2024: DEBUG: TLS: Using 0x6 (6) for Net::SSLeay 
> constant SSL2_MT_REQUEST_CERTIFICATE
>
> Tue Jul 16 15:31:05 2024: DEBUG: TLS: Using 0x6 (6) for Net::SSLeay 
> constant SSL2_MT_SERVER_FINISHED
>
> Tue Jul 16 15:31:05 2024: DEBUG: TLS: Using 0x4 (4) for Net::SSLeay 
> constant SSL2_MT_SERVER_HELLO
>
> Tue Jul 16 15:31:05 2024: DEBUG: TLS: Using 0x5 (5) for Net::SSLeay 
> constant SSL2_MT_SERVER_VERIFY
>
> Tue Jul 16 15:31:05 2024: DEBUG: TLS: Using 0x2 (2) for Net::SSLeay 
> constant TLSEXT_ERR_ALERT_FATAL
>
> Tue Jul 16 15:31:05 2024: DEBUG: TLS: Using 0x1 (1) for Net::SSLeay 
> constant TLSEXT_ERR_ALERT_WARNING
>
> Tue Jul 16 15:31:05 2024: DEBUG: TLS: Using 0x3 (3) for Net::SSLeay 
> constant TLSEXT_ERR_NOACK
>
> Tue Jul 16 15:31:05 2024: DEBUG: TLS: Using 0x0 (0) for Net::SSLeay 
> constant TLSEXT_ERR_OK
>
> Tue Jul 16 15:31:05 2024: DEBUG: AuthFILE setting EAPTLS_Ciphers to: 
> DEFAULT:!EXPORT:!LOW
>
> Tue Jul 16 15:31:05 2024: DEBUG: EAP result: 3, PEAP Challenge
>
> Tue Jul 16 15:31:05 2024: DEBUG: AuthBy FILE result: CHALLENGE, PEAP 
> Challenge
>
> Tue Jul 16 15:31:05 2024: DEBUG: Access challenged for user at host.com: 
> PEAP Challenge
>
> Tue Jul 16 15:31:05 2024: DEBUG: Packet dump:
>
> *** Sending to 10.40.176.98 port 60389 ....
>
>
> Packet length = 46
>
> 0b 1c 00 2e 67 6a 89 68 86 97 9f 2f c9 ca 99 68
>
> c5 3f 5f 1f 50 12 40 12 4b 21 a4 80 19 29 dc 8e
>
> c9 bc e2 a2 d3 6e 4f 08 01 17 00 06 19 20
>
> Code: Access-Challenge
>
> Identifier: 28
>
> Authentic:gj<137>h<134><151><159>/<201><202><153>h<197>?_<31>
>
> Attributes:
>
> Message-Authenticator = 
> @<18>K!<164><128><25>)<220><142><201><188><226><162><211>n
>
> EAP-Message = <1><23><0><6><25>
>
>
> Tue Jul 16 15:31:05 2024: ERR: sendTo: send to 10.40.176.98 port 60389 
> failed: Socket operation on non-socket
>
>
>
>
> Going to try downgrading to a few previous releases to figure out 
> where the problem started.. but just wondering if anybody had any 
> quick clues while I found time to do that.
>
>
> Thanks!
>
>
> -c
>
>
>
> _______________________________________________
> radiator mailing list
> radiator at lists.open.com.au
> https://lists.open.com.au/mailman/listinfo/radiator
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.open.com.au/pipermail/radiator/attachments/20240717/692e5c53/attachment-0001.html>