Remote address for websocket connections?

[goodnewsbear]

Hello -

Is there a technical or design reason the remote address of a connecting websocket client isn't recorded in the Steve database or log files? This would be useful information for debugging, catching "rogue" EVSE that have been misconfigured or are potentially malicious, and within the WebUI to quickly connect to the administrative interface of these devices. Re adding the remote address to the WebUI, there'd be no need for a URL (just there to copy-paste) since these devices often have nonstandard web server ports etc anyway.

Cheers!

[goekay]

Is there a technical or design reason the remote address of a connecting websocket client isn't recorded in the Steve database or log files?

there is no conscious reason really. i did not think of it, and no one mentioned it this far. we can add the IP to the logs easily.

having said that, determination of the real/actual IP can be tricky if and when the request goes through proxies etc. since they need to actively forward the real ip under some http header. therefore, i am not sure how reliable the info would be.