You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
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.
The text was updated successfully, but these errors were encountered: