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

High latency bug #47

Open
merlinthemagic opened this issue Sep 21, 2018 · 2 comments
Open

High latency bug #47

merlinthemagic opened this issue Sep 21, 2018 · 2 comments

Comments

@merlinthemagic
Copy link

Hi,

Centos 7 install from RPM, connecting from Linux to Mikrotik hAP-AC2 (RouterOS 6.42.3).

When i connect using mactelnet to Mikrotik with latency <10ms no problems. mactelnet behaves as expected.

When connecting to device that is between 120-140ms away, mactelnet will allow a few commands to be executed then exit with message: "Connection timed out".

I know mac telnet relies on L2 communication and as such is quite unreliable and if the mac-telnet client built into Mikrotik was doing the same thing i would not be bothering you. But the Mikrotik client does not suffer from this problem, it acts as expected even under high latency conditions.

You will see from the pcaps that the terminal size is quite large, the terminal is different and colors have been disabled on login. I have tried configuring the linux terminal to mirror the settings that work when using the Mikrotik native client (term=linux, terminal height/width = actual terminal), but that does not make a difference, connection still times out after a few commands.

This may be related to https://github.com/haakonnessjoen/MAC-Telnet/issues/9, however in that case the roles where reversed and linux was used as the server.

@merlinthemagic
Copy link
Author

pcaps.zip

@merlinthemagic
Copy link
Author

Found a work around, if i inset a 500ms delay between commands everything runs ok.

Not ideal, since a static delay slows down the application, but workable. There has to be some reason the app fails when a command is fired immediately after the last returned to the shell prompt?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant