-
Notifications
You must be signed in to change notification settings - Fork 128
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
Comments
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. |
What is latest version is supported? |
Now it supports all versions. What was the reason for specifying -i? it always tries every available interface. |
Being able to choose the interface can be very useful not only in discovery but also in connecting the client. I think that being able to choose the specific interface would reduce the time to a few seconds, so it would be very useful. |
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? |
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?
The text was updated successfully, but these errors were encountered: