-
Notifications
You must be signed in to change notification settings - Fork 399
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
Long time to authorize #262
Comments
Can you get a tcpdump/wireshark capture of the failed session? My first thoughts would be either DNS or network MTU has problems. |
dump3.zip |
Dropbear delays 5 seconds from accepting the connection and sending the first packet. Did you compile Dropbear, or where is the package from? DNS seems a likely reason if it's different from different networks, but the default config for Dropbear is to disable host lookups ( Another possibility is that session key exchange crypto is slow. When you were connecting from different networks (which were fast), was it a different SSH client? What kind of device is Dropbear running on?
|
I compiled dropbear with default options (as I understood with disable host lookups) |
What hardware and OS is Dropbear running on? What client are you using from each network? |
The device based on ARMv7 and buildroot. |
About clients: |
Can you send "ssh -vvv" output from both the fast and the slow networks?
Thanks
|
This comment was marked as duplicate.
This comment was marked as duplicate.
As I understood all logs are identical. |
It looks like the newlines got broken, can you try paste it differently? |
The same network C:\Users\framegrabber>ssh [email protected] -vvv |
The different network C:\Users\framegrabber>ssh [email protected] -vvv |
OK, nothing obvious there. Are there any other connections being made to the SSH server at the same time by chance? (Wondering if it's the pre-auth per-IP limit. Seems unlikely). |
No. The client PC moved from one network to another. |
If I connect from another network, I will timeout before success authorization up to 9 seconds.
If I connect from the same network, all will work correctly.
As example device have IP 192.168.223.40:
root@Decoder:/etc/dropbear# dropbear -F -E -r dropbear_ed25519_host_key [26237] Nov 30 08:58:03 Not backgrounding [26319] Nov 30 08:58:12 Child connection from 192.168.223.1:37902 [26319] Nov 30 08:58:14 Password auth succeeded for 'root' from 192.168.223.1:37902 [26319] Nov 30 08:58:18 Exit (root) from <192.168.223.1:37902>: Disconnect received [26416] Nov 30 08:58:22 Child connection from 192.168.59.17:56442 [26416] Nov 30 08:58:31 Pubkey auth succeeded for 'root' with ssh-rsa key SHA256:26OBMOgzbiRQj8cF6I3MM714tse/ag/dz7Lb4TkvPNE from 192.168.59.17:56442 [26416] Nov 30 08:58:36 Exit (root) from <192.168.59.17:56442>: Disconnect received [26237] Nov 30 08:58:40 Early exit: Terminated by signal
As result I can input pass during 2 seconds from the same network
And authorize from another network take 9 seconds (without time to type pass).
dropbear 2017.75 without this problem but too old
The text was updated successfully, but these errors were encountered: