Hello
Is there anyone of you that know a console mac-telnet tool for linux users?
Is really stupid that Mikrotik make a fully functionality winbox only for windows and not for linux :-/////
I am wrong or Mikrotik firmware is based on linux kernel?
Unbelievable … I feel a real paradox!
Wine
based on linux kernel doesn’t mean that all the programs are from somewhere else. most of the stuff is made by mikrotik entirely, and we can’t release it for linux for many reasons, including technical.
I know that I would personally LOVE to see a console command that offered mac-telnet from Linux. I have been a strong “defender” of Mikrotik with respect to offering “native” applications in other places, but this particular request isn’t one that is easily worked around. I have asked support for this for a long time, too. So let me just say +1 vote for console mac-telnet client for Linux.
I did some work time ago, basically the authentication part only.
Not useful yet.
Does this mean you know how to encode the password for the client to send to the server?
I can parse and generate everything else required to establish a session and send keystrokes / display output, but I do not know the algorithm to use to encode the password.
It looks like the server sends a random 16 byte key for each session that is to be used when encoding the password.
–
Omni Flux
maybe it’s similar to API authentication? =)
It is exactly the same. I was just missing the leading null character in the string I was calculating the md5 value for.
Thanks, Chupaka.
Does this mean you have a working implementation? Could you share that?
wow great news.. could you provide some information about the initial handshake?? i have problems with that :-/
i see that the first two bytes of each packet are some kind of sequence counter, then follows the mac of the source, then dest mac, and then?? 03 7d 00 15 and at the response packet 00 15 03 7d.. is there any scheme behind this??
it would be very kind if you share your informations 
I do not have a working implementation; I have only hacked enough together to test what I thought I was seeing in my packet captures and haven’t had time to work on it since.
I have posted a write up of what I have found here: http://www.omniflux.com/devel/
–
Omni Flux
wow, thank you very much, that should be helpful!
With help from Omni Flux’ work, I’ve created a Linux native MAC-Telnet client.
Also a native OS X version is in beta stage.
You may find it in the download section at http://github.com/haakonnessjoen/MAC-Telnet
–
Håkon
to make things easier:
use git to get the source
mkdir haakon-mac-telnet && cd haakon-mac-telnet
git clone git://github.com/haakonnessjoen/MAC-Telnet.git
make all
it connects to router, gets the banner, almost gets the prompt and then disconnects.
Good work.
Thanks. Only almost gets the prompt? Really? I have never had any issues with that.
I’ve been using it to Telnet my routers for a while now, with no problems. Could you send me a pcap from when this happens?
Nice porting, i tested it and works fine!
New ideas incoming!! 
Thank you for the app
(installed by .deb package without problems.)
Thank you, thank you, thank you so much!
Please come with ideas
I’ve just uploaded a new commit that enables you to connect to your router by the routers identity name.
It uses the MNDP discovery protocol to find the first router that has the specified name.
Example below:
# mactelnet eth0 Holmenveien -u admin -p mypassword
Searching for 'Holmenveien'...0:c:42:3e:20:c2
Connecting to 0:c:42:3e:20:c2...done
It’s in the current HEAD version, if you download from github. But not as a new .deb package yet. I will do that the next minior version increase.
Wow so we have this quote and then a member of the community comes along and proves you wrong (almost complete). MT should cough up some cash for this guys work and release it because he earned it
Actually, I think normis was answering mostly to the “winbox” part of the first posters request when he said “including technically”. Winbox is not easily created for linux, as it uses windows dll’s for it’s dynamical support for automatically support newer RouterOS devices without upgrading the winbox.exe file.
This would then also require that they would create .so files for linux as well at each update and would need to use the same version of libraries as your linux distribution etc. which could be very different from distribution to distribution, unless you would recreate the winbox interface using the API support. But by using API it would require new versions of the program each time the API changes and each time new elements are added to RouterOS/API.
Anyways, adding linux support for winbox would require extra work that it might not be high enough demand after, to actually afford doing it. If enough customers needed it, they probably would do it. And since winbox works good enough in wine, the need is not that great.