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

Interface option for discovery #53

Open
vetash opened this issue Feb 8, 2019 · 5 comments
Open

Interface option for discovery #53

vetash opened this issue Feb 8, 2019 · 5 comments

Comments

@vetash
Copy link

vetash commented Feb 8, 2019

Its would be great if there wil be option like -i for discovery on machines that have more than one network interface. Do you have any plans on it?

@haakonnessjoen
Copy link
Owner

I must admit that I have stopped planning until we have solved the big problem that we cannot support newer RouterOS versions, since they have changed out the authentication process, and do not want to give us any help, and I have no time to try to reverse engineer it.

Even though they are a company built upon open source software. They are really hostile against open source.

@vetash
Copy link
Author

vetash commented Feb 12, 2019

What is latest version is supported?

@haakonnessjoen
Copy link
Owner

Now it supports all versions. What was the reason for specifying -i? it always tries every available interface.

@miquelmartos
Copy link

Being able to choose the interface can be very useful not only in discovery but also in connecting the client.
We have an "accel-ppp" server, this creates an "ipoe" interface for each connected user. There are thousands of users connected, "mactelnet" takes a long time to find the correct interface, tens of minutes in some cases.

I think that being able to choose the specific interface would reduce the time to a few seconds, so it would be very useful.

@haakonnessjoen
Copy link
Owner

Sure, but that is weird, it shouldn't even take a second to send a udp packet each on a thousand interfaces. Have you tried with -n? It could potentially work better.

Are you connecting to the mac address, or using the identity name?

It would be interesting to see some packet capture of the interface you are trying to connect via, and then do mactelnet, and wait until you get a connection. And share the pcap with me?

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

3 participants