by Guest on 2026/02/09 03:38:45 PM
Actually, if you have a dedicated public IP address on the interface, you will be able to connect to yourself, and see yourself as a peer (with “Self connect” as peer status). Same for certain types of NAT that allow hairpinning. In some cases, you would notice your own public address twice, with different ports. That's because NAT may assign external ports in different ways. One is probably assumed by the client, the other is reported by some external participant. Either one of them can be used for self-connection, or none (if there is no hairpinning).
So peer list really tells you whether your client can connect to itself.
If you want to learn what your external IP address and port are, you need to figure out the network situation. In case of dedicated public IP address on a local network interface or a home router, it's that address, and port number from the settings (or the one you manually forwarded it to, if you deliberately changed it). In case of NAT, it should be the same address you see on address checking websites, but different peers might see different port numbers depending on your NAT type (in that case, choosing a specific one makes no sense, as you can't send packets to it from other network locations). Some people have multiple addresses or interfaces available, and some of the peers can only connect to some of them (IPv4 and IPv6 dual-stack connections are like that, for example).
