-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Running on local network gives empty result #22
Comments
@dominch I don't think it's really needed 😅 |
Looks ugly on those, of course for each You can guess missing information. Is it needed? Sure, the whole point of such service is to get network context. With complicated setup, vpns and security You would like to know which gateway You are using, sometimes for more than one application on same network and vm. It should just give information about network route. |
@dominch It's Internet facing service, not for internal usage though 😱 |
It's network context/ip discovery service, like many others easily found in Internet, but none of them there will return information about internal network routes, and sure - I don't do that locally, but on many networks connected via different protocols and advanced routing. If I would like to know only gateway path - then no point to deploy on Your own. Ok, let's leave that. |
@dominch That's the purpose of the project, yes. But, please feel free to contribute patches, we can get it merged if the complexity is acceptable, no problem. |
Running it in local network gives empty result:
Probably same thing for other IP classes: 10.x.x.x 172.x.x.x,
Also running it locally - 127.0.x.x
Of course address/location for this service is unknown, but this looks empty and even '?' would be better :)
The text was updated successfully, but these errors were encountered: