UPnP port

No, you didn't do anything wrong, and you're right to be confused. In the announcement I made on the 11th I wrote that the client now connects to port 80 on the server. I did this because I discovered that on some Internet connections, higher port numbers are blocked, and port 80, which is normally used for HTTP (web-browsing) is always open. This created a problem and turned out to be ineffective for what I had intentionally intended. The problem was that port 80 is often interfered on by software like Avast, which entirely takes over web connections to monitor them for dangerous content. In the case of avast, this confuses the UPnP module which uses the socket connected to the server to read our local IP address, as it's now really just connected to a local software component and keeps returning localhost (127.0.0.1) as our IP address. When you use UPnP to forward the client's listening port to that address, it understandably doesn't work. The other problem with connecting to the server on port 80 is that it doesn't really change your situation much overall. If your Internet connection blocks higher port connections, you'll be able to connect to the server but not really do anything else, as all P2P activity takes place over higher port numbers. Not only that, but the whole Avast business made me think port 80, being so important and specifically designated, might be open to interference from all kinds of software. I changed the UPnP module to make an educated guess regarding what may be the best IP address among all the network intefaces on the machine to use in case the server connection socket returns localhost, but also decided to go back on using port 80 altogether, for all of the reasons I've listed.