AirDC++ 2.72 and port settings for VPN use

edited April 2014 in P2P Support
Hello,

I want to make my DC traffic a little more private. But with AirDC++ it sounds easier than it is.
I got my internet working and I tried different settings all with the same result.

Now i got running PPTP connected to the german VPN. When starting AirDC++ the ONLY way i can connect to hubs is when using the automatic connections setup on both IP4 and IP6. 

Following output:
[17:14:21] Connectivity (IPv4 & IPv6): Determining the best connectivity settings... 
  [17:14:21] Connectivity (IPv6): Public IP address detected, selecting active mode with direct connection 
  [17:14:21] Connectivity (IPv4): Local network with possible NAT detected, trying to map the ports... 
  [17:14:23] Connectivity (IPv4): Port mapping: Successfully created port mappings (Transfers: 53754, Encrypted transfers: 53755, Search: 54321) on the "Compal Broadband Networks, Inc CH6643" device with the MiniUPnP interface 
  [17:14:37] Failed to check for new version: Could not download the version file (Connection timeout (http://version.airdcpp.net/version.xml)) 

When I look at my IP it the german one. I can upload to people, but downloading (files and lists) and searching is completely blocked. Don't really understand what I could do about this. 


Comments

  • DC is still being used?

    Well, since the VPN doesn't support IPv6, I guess you should disable it, otherwise you won't be protected for IPv6 transfers.

    UPnP can leak your IP address. It's already mapping the ports on your router, which isn't involved with the VPN connection, so you could easily leak your ISP IP address that way.
    Also, PIA won't give you more than one port forward, and you can't choose it. If DC really needs different ports for transfers and search, it won't work very well with PIA.

    Don't know what's wrong with the update checking. Can you open that address in your browser?
  • I think my biggest problem is that AirDC choses multiple ports to open through UPnP when connecting. The Search port is the one I setup in TLS port, but the other 2 (transfer and encrypted transfers) are ports completely different from anything I have setup.

    So If I want it to work I should open a range of ports on my router. But that compromises the anonymity ? Or is it the UPnP thingy that is dangerous?

    I shutdown the IPv6 communication as it isnt being used by my hubs anyway. And the update thing I never encountered again.
  • No, UPnP itself isn't dangerous, as long as the implementation is done well. The problem is that your router doesn't know about your VPN connection or the VPN server's IP address (which would be where you'd expect packets for you to go). IT will happily report your ISP IP address if asked for it, which is the problem.

    If DC absolutely needs these ports, you won't be able to use it with PIA.
Sign In or Register to comment.