Inbound BitTorrent connection with weird destination address?

Hi, all -

I have CPF My computer is connected to the internet via a NAT router; its LAN IP is It runs Azureus (a BitTorrent client), which is set to listen to TCP/UDP port 16881. I followed the tutorial for setting up CPF for BitTorrent, and the result looks as follows:

Network Control Rules:

Application Control Rules:

Note that TCP port 16885 is for Azureus’ HTML UI.

Later, I get the following “receive a connection” popup from CPF:

…which I allow and remember, thereby changing my Application Control Rules to the following:

And now for the weird bit. My external IP address is nothing like the destination address supplied in the popup. The address looks to be from an ISP in London, and I am in New Zealand (about as far away as you can get while still being on the planet’s surface)!

Why is CPF reporting an inbound TCP connection to a destination address that is not local?

I can get around the popups by changing the Application Control Rules destination address to “any”… But I don’t understand why that is necessary. Does anyone?



Thtats because while using P2P, you are receiving connections from other computers. So Azerus is establishing/receiving connections to/from that IP address.

That popup means, you application is going to accept a connection from that IP address.

From that IP address? Are you sure? I was always led to believe that the “destination” field (in earlier versions it was called “remote”) always represents where the packet is going:

  • for an inbound connection, destination is “me” (my local computer)
  • for an outbound connection, destination is “that other computer out there in internetland”

Certainly, that is what you yourself were talking about here, and there are plenty of other examples on the forums that support this view. Given that the popup looks like it is for an inbound TCP connection, surely the destination address should refer to my computer?

It certainly is the remote host. Popups always show the remote address if applicable. Application rules are a different story and obviously confusing… For application monitor, there is no source/destination difference. Application rules are being redesigned. They will be exactly the same as network rules and act as a server will be a seperate option to solve all these confusions.

That thread is not about application monitor rules but network monitor rules.