linuxdcpp-team team mailing list archive

[eMTee <748623@xxxxxxxxxxxxxxxxxx>]

>Yes, however this is not a practical solution
I didn't offered this as a solution but for test only, to see if really the binding is your problem. But the screenshot tells that something's not ok, indeed.

My tests show that even if I set my DC++ binding to a virtual (VMWare)
network interface, MiniUPnPc still finds my router so I guess its either
using the inaddr_any interface or discovering UPnP in every existing
interface. Both cases are bad, it should find UPnP capable devices
through and map ports only to the interface DC++ is bound to.


** Changed in: dcplusplus
       Status: Incomplete => Confirmed

** Changed in: dcplusplus
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/748623

Title:
  upnp uses wrong IP address

Status in DC++:
  Confirmed

Bug description:
  I use LogMeIn Hamachi to connect to a friend's computer to play
  Minecraft. The Hamachi VPN device's IP address is 5.227.153.183, I set
  DC++ to bind to 192.168.1.7 which is my motherboard's LAN chip.
  Despite setting the bind address, DC++ still uses my VPN device's IP
  address in its uPnP configuration with the router instead of the
  physical address preventing me from connecting to others in the hub.