Skip to content
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]: wrong timeout in parallel mode #5106

Open
ef-end-y opened this issue Jul 12, 2023 · 0 comments
Open

[defect]: wrong timeout in parallel mode #5106

ef-end-y opened this issue Jul 12, 2023 · 0 comments
Labels
defect category: a defect or misbehaviour

Comments

@ef-end-y
Copy link

What type of defect/bug is this?

Unexpected behaviour (obvious or verified by project member)

How can the issue be reproduced?

file.txt contains 15 attributes separated by empty lines. I run:

radclient -x -t5 -r1 -p15 -f file.txt xx.xx.xx.xx:3799 coa password

xx.xx.xx.xx - any host that ignores requests on port 3799

tcpdump shows all 15 attributes were actually sent at the same time. The host does not respond. radclient waits 5 seconds for a response for the first packet, then 5 seconds for the 2nd one and ... all takes 15 * 5 = 1 minute 15 seconds. The last packet was sent a minute ago, why does radclient have to wait 1 minute for a response?

Log output from the FreeRADIUS daemon

freeradius -v
radiusd: FreeRADIUS Version 3.0.26, for host x86_64-pc-linux-gnu, built on Jan  4 2023 at 03:23:09
FreeRADIUS Version 3.0.26

Relevant log output from client utilities

(0) No reply from server for ID 52 socket 3
(1) No reply from server for ID 240 socket 3
(2) No reply from server for ID 241 socket 3
(3) No reply from server for ID 136 socket 3
(4) No reply from server for ID 113 socket 3
(5) No reply from server for ID 247 socket 3
(6) No reply from server for ID 154 socket 3
(7) No reply from server for ID 37 socket 3
(8) No reply from server for ID 239 socket 3
(9) No reply from server for ID 126 socket 3
(10) No reply from server for ID 168 socket 3
(11) No reply from server for ID 16 socket 3
(12) No reply from server for ID 50 socket 3
(13) No reply from server for ID 75 socket 3
(14) No reply from server for ID 107 socket 3

Backtrace from LLDB or GDB

No response

@ef-end-y ef-end-y added the defect category: a defect or misbehaviour label Jul 12, 2023
alandekok added a commit that referenced this issue Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect category: a defect or misbehaviour
Projects
None yet
Development

No branches or pull requests

1 participant