New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[defect]: 3.2.x assertion failed while proxying request to home server with radsec #5308
Comments
I've pushed a fix. Please verify. |
no luck unfortunately, still the same behaviour. Crash on status-request after the previously failed proxied request.
|
That's more than a little weird. All of the code paths which reach that assertion call the can you run it with |
well I can't run it with -X because tls requires threading :s I added more "x" which gave some more output
|
You can run in threaded mode with I'll see if I can reproduce this here, but it might take a bit. I'm busy for the next while. |
Yeah that's what I did. |
If you just use tcp or udp, it should work. So yes, please try without radsec. |
Well it was working fine with radius/udp before, but we're in the process to move to radsec with our ftlr and that's when this issue arose. Still I'll try a few more things, and also I'll double check with the NREN if everything is correctly working on their side. |
What type of defect/bug is this?
Crash or memory corruption (segv, abort, etc...)
How can the issue be reproduced?
This was a working configuration of a test IDP eduroam server to test radsec communication with the FTLR servers.
Pulled and compiled a fresh code this morning (
commit cd6534934d1056bac4ad1c01baf99e93fb4d4ed0 (HEAD -> v3.2.x, origin/v3.2.x)
)service started with
sbin/radiusd -fxx -l stdout
sites-available/eduroam-tls as follow :
Log output from the FreeRADIUS daemon
Relevant log output from client utilities
simple eapol_test from local server
Backtrace from LLDB or GDB
The text was updated successfully, but these errors were encountered: