IP address for always-on connections?

[MystaraTheGreat]

Is it possible for the ip address associated with an always-on connection to reflect the IP address of the user that is currently connected to that account?

It seems that when a user connects, they are shown as connecting from the IP 127.0.0.1 (localhost). I'm not even sure how I find out their current IP address :)

[slingamn]

The issue with always-on clients (and multiclient more generally) is that they can be connected from multiple IP addresses. (In the case of always-on clients, they can be connected from no IP addresses.)

As an operator with the relevant permissions, you can get a list of currently connected clients using NS CLIENTS LIST (e.g., /msg NickServ clients list shivaram).

[prdes]

It seems that when a user connects, they are shown as connecting from the IP 127.0.0.1 (localhost)

Hi, even with always-on multi-client enabled the -CONNECT- Server Notice should show you the actual IP address of the source of the connection. Unless of course it is something like a tor listener connection. I am fairly confident that this is the case, please let me know if otherwise.

[MystaraTheGreat]

@slingamn: Understood. But when there's exactly one IP address connected, couldn't it update the 127.0.0.1 hostname to the actual connection hostname (masked as appropriate)? Or alternatively provide this information in the WHOIS for IRC ops?

@mogad0n: True and certainly I see these for other people (I wasn't around when this specific user connected so I didn't see a specific notice for them although I assume it's there). In fact, this user connects via mibbit, so that adds a further level of complexity :)

[slingamn]

Here's the behavior in recent versions of Oragono:

1. If a client becomes always-on (e.g. by registering an account and setting themselves always-on), they keep the IP and cloak they initiated their connection with --- the cloaked hostname appears in message sources and in 311 RPL_WHOISUSER, the original IP appears in 338 RPL_WHOISACTUALLY where applicable --- even if they lose their connection and reconnect
2. If the server restarts, their IP will be 127.0.0.1 for purposes of 338 RPL_WHOISACTUALLY, but their hostname (in message sources, 311 RPL_WHOISUSER, etc.) will be a unique cloaked value derived from their account name

What's your use case? I think the most I can offer is to put one of the actual IPs in RPL_WHOISACTUALLY for operators to see. I don't want to change the cloaked hostname because that obligates us to send CHGHOST, which is a drain on performance (and also I don't really like the privacy implications, even with cloaking).

[MystaraTheGreat]

There isn't really much of a use case except that I couldn't quickly (intuitively) find a user's IP address. They had an always-on account, I did /whois expecting to see their IP and I saw localhost, even though they were only connected from a single connection.

It just seems...odd that there's an unambiguous IP address available and it isn't easily accessed.

[slingamn]

In 2.8, I'll plan to display one of the real IPs in 338 RPL_WHOISACTUALLY. (Not sure whether it will be arbitrarily chosen, or the first IP they logged in with, or the most recent.)