Capture Player IP Address

[mikldt]

We should capture the player IP address from the API rather than having the user enter it into the form. The UI should then link to the status and configuration pages on the Bandshell server.

Ideally it would only write to the database when the recorded IP address is nil or different from the reported one.

A bonus might be to check whether it is routable from the server (could be a delayed job). This would be informative to the user and possibly useful down the line in a pseudo-push scenario. In this case we could store some serialized data (address, last updated, and routability) rather than just the address.

[kench]

Can you define routability? Also, do we want to log the external IP address as seen by the server of the IP address the client sees assigned to itself?

[mikldt]

@kench By routability I mean that the server can make a request to the recorded IP and reach the bandshell server (no NAT or firewalls in the way). I'm leaning towards the IP seen by the server because it's easy to collect. If the two are different, the IP isn't nearly as useful (exception: port forwarding, in which case you want what the server sees).