-
Notifications
You must be signed in to change notification settings - Fork 71
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
reported internal ip address / docker #70
Comments
Here's the existing logic: https://github.com/flightaware/piaware/blob/master/package/fa_sysinfo.tcl#L292 |
I just went over this, and there's three things you can do, all of them "not recommended" or "not reliable".
Oh, I suppose once IPv6 is everywhere it will be a non-issue. |
As said, an option to define the behaviour and one to define a manual value for the URI could be a fix. I agree IPv6 would most likely be the most handy thing, though a question would be even if you |
Not doing address translation is kind of a religion for v6 promoters. Anyway, yeh, just making it some parameter or setting you pass to the program to override the ip address is the way to go. That way it doesn't matter if it's docker or some other NAT/PAT system that's hiding the address from you. |
Hi!
Piaware reports back the internal IP address and exposes that as a link on the users flightaware page.
https://flightaware.com/adsb/stats/user/ shows the internal IP and port of the local webinterface
under "site information": "Web Interface: View live data (requires local network connection)"
which show something like: http://172.17.0.6:8080/
Especially with using docker this internal address might not even be accessible.
It would be nice if the behaviour could be set / overwritten.
Like behaviour:
default export any internal address)
manual (configure protocol (http/https), host/ip, port as whatever you like)
auto-docker (get the hosts ip/port if this is even possible
The text was updated successfully, but these errors were encountered: