No auth requests through TLS tunnel if connection was checked

Alan DeKok aland at deployingradius.com
Fri Apr 12 16:05:00 UTC 2024


  Thanks.  I've pushed the patch, and another one-line fix which stops that error.

> On Apr 12, 2024, at 11:36 AM, nabble at felix.world wrote:
> 
> That worked! 
> Now the requests are coming through. Thanks! 
> 
> One thing to mention is that every time, the radsec client connects, there is one new error.
> 
> 
> hread 4 got semaphore
> Thread 4 handling request 0, (1 handled so far)
> (0) (TLS) Checking connection to see if it is authorized.
> (0) # Executing group from file /usr/local/etc/raddb/sites-enabled/default
> (0)   Autz-Type New-TLS-Connection {
> (0)     [ok] = ok
> (0)   } # Autz-Type New-TLS-Connection = ok
> (0) (TLS) Connection is authorized
> (0) ERROR: Failed signing packet: ERROR: RADIUS packets must be assigned an Id
> (0) Sent Access-Accept Id 4294967295 from 0.0.0.0:2083 to 192.168.215.1:32993 length 20
> (0) Finished request
> Thread 4 waiting to be assigned a request
> Waking up in 0.2 seconds.
> Waking up in 4.6 seconds.
> 
> - 
> Lineconnect 
> 
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html



More information about the Freeradius-Users mailing list