linuxdcpp-team team mailing list archive

[Naka <naka@xxxxxxxxxx>]

Public bug reported:

Users connecting to the hub using an internal IP (192.168.X.X/127.0.0.1)
shows other users that their IP is that internal IP. This means users
connecting externally cannot get files from users connecting locally.
This means I can't access my own hub and share files with users.

 This could be solved in the router so that it redirects requests, but
you need a modded or special router.

ApexDC++ at least has a "External / WAN IP" field under connection
settings that I think is used by some hub software.

EDIT: The minute after I post this I found that there's a checkbox in
apexdc++ for "Don't allow hub/UPnP to override" referring to the
external IP.   Couldn't find anything on Google about this. Set the bug
to invalid, but may be worth looking at. FlexHub's automatically sets
IPs as external, even connecting locally, could be used as an example.

** Affects: adchpp
     Importance: Undecided
         Status: Invalid

** Changed in: adchpp
       Status: New => Invalid

** Description changed:

  Users connecting to the hub using an internal IP (192.168.X.X/127.0.0.1)
  shows other users that their IP is that internal IP. This means users
  connecting externally cannot get files from users connecting locally.
  This means I can't access my own hub and share files with users.
  
-  This could be solved in the router so that it redirects requests, but
+  This could be solved in the router so that it redirects requests, but
  you need a modded or special router.
  
  ApexDC++ at least has a "External / WAN IP" field under connection
  settings that I think is used by some hub software.
+ 
+ EDIT: The minute after I post this I found that there's a checkbox in
+ apexdc++ for "Don't allow hub/UPnP to override" referring to the
+ external IP.   Couldn't find anything on Google about this. Set the bug
+ to invalid, but may be worth looking at.

** Description changed:

  Users connecting to the hub using an internal IP (192.168.X.X/127.0.0.1)
  shows other users that their IP is that internal IP. This means users
  connecting externally cannot get files from users connecting locally.
  This means I can't access my own hub and share files with users.
  
   This could be solved in the router so that it redirects requests, but
  you need a modded or special router.
  
  ApexDC++ at least has a "External / WAN IP" field under connection
  settings that I think is used by some hub software.
  
  EDIT: The minute after I post this I found that there's a checkbox in
  apexdc++ for "Don't allow hub/UPnP to override" referring to the
  external IP.   Couldn't find anything on Google about this. Set the bug
- to invalid, but may be worth looking at.
+ to invalid, but may be worth looking at. FlexHub's automatically sets
+ IPs as external, even connecting locally, could be used as an example.

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

Title:
  Displays internal IP to users when connecting locally

Status in ADCH++:
  Invalid

Bug description:
  Users connecting to the hub using an internal IP
  (192.168.X.X/127.0.0.1) shows other users that their IP is that
  internal IP. This means users connecting externally cannot get files
  from users connecting locally. This means I can't access my own hub
  and share files with users.

   This could be solved in the router so that it redirects requests, but
  you need a modded or special router.

  ApexDC++ at least has a "External / WAN IP" field under connection
  settings that I think is used by some hub software.

  EDIT: The minute after I post this I found that there's a checkbox in
  apexdc++ for "Don't allow hub/UPnP to override" referring to the
  external IP.   Couldn't find anything on Google about this. Set the
  bug to invalid, but may be worth looking at. FlexHub's automatically
  sets IPs as external, even connecting locally, could be used as an
  example.

To manage notifications about this bug go to:
https://bugs.launchpad.net/adchpp/+bug/970317/+subscriptions