Author Topic: Internal & Exteral IP, Connection Issues  (Read 3598 times)

0 Members and 1 Guest are viewing this topic.

Offline fakemoonlanding

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Internal & Exteral IP, Connection Issues
« on: 15 September, 2006, 21:29:52 »
Okayyyyyyyyyy.
So, I'm on a cable line and I have the server setup with an internal static IP. Users outside of our household (like my computer at work, etc) can connect using our ONE external IP associated with our Cable Modem. Port forwarding setup on our router so that it port forwards default to the hub.

1. Two internal ip addresses (192.168.1.xxx) can connect and transfer files to one another
2. Two external ip addresses (blah.blah.blah.blah) can connect and transfer files to one another
3. One external ip address and one internal ip address cannot communicate with one another over the hub, though they are both able to connect simultaneously.

There are no conflictions with user names. Any ideas?

PtokaX forum

Internal & Exteral IP, Connection Issues
« on: 15 September, 2006, 21:29:52 »

Offline bastya_elvtars

  • Forum God
  • ****
  • Posts: 3 752
  • Karma: +173/-7
  • The rock n' roll doctor
    • The FreshStuff3 Site
Re: Internal & Exteral IP, Connection Issues
« Reply #1 on: 15 September, 2006, 21:48:18 »
3. One external ip address and one internal ip address cannot communicate with one another over the hub, though they are both able to connect simultaneously.

This is how it's meant to be. RFC1918-addresses are not routable. The only solution is to bind the clients to the external IP (Bind address) and connect to the hub using the ext. IP as well (even better: the hostname), thus allowing all their packets to communicate with the 'outer world'.
Everything could have been anything else and it would have just as much meaning.

Offline sotsa

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Re: Internal & Exteral IP, Connection Issues
« Reply #2 on: 26 October, 2006, 21:22:18 »
Hello !

It would seem I have the same kind of problem BUT I use the external hostname for the hub.

If I understand this correctly :
MyUserName (192.168.0.254) > $ConnectToMe ExternalUserName 192.168.0.254:1201
that means external clients see my internal IP.
No wait, 192.168.0.254 is the internal address of my router...

Is this the source of the problem ?
What do you mean by "bind address" ?
« Last Edit: 26 October, 2006, 21:24:31 by sotsa »

Offline dannyboyrulesman

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Re: Internal & Exteral IP, Connection Issues
« Reply #3 on: 27 October, 2006, 06:32:32 »
So are you guys saying that if I am running the PtokaX hub and also running the dc++ client on the same computer I will be unable to search for files?  Will other users in the wider internet be able to see my file list?

Offline bastya_elvtars

  • Forum God
  • ****
  • Posts: 3 752
  • Karma: +173/-7
  • The rock n' roll doctor
    • The FreshStuff3 Site
Re: Internal & Exteral IP, Connection Issues
« Reply #4 on: 27 October, 2006, 11:26:07 »
So are you guys saying that if I am running the PtokaX hub and also running the dc++ client on the same computer I will be unable to search for files?  Will other users in the wider internet be able to see my file list?

1) No, you'll be able using public IPs.
2) Yes.
Everything could have been anything else and it would have just as much meaning.

Offline Tw?sT?d-d?v

  • Lord
  • ***
  • Posts: 436
  • Karma: +79/-2
    • EURO-OP
Re: Internal & Exteral IP, Connection Issues
« Reply #5 on: 28 October, 2006, 15:34:50 »
I have the same Cable & Router  .... just connect to hub via Routers internal ip     192.168.*.*:port
and in DC++ Client put in External ip address 

No probs here with that     hub runs fine and search works fine  :)

i have 3 pc's set up on that router and they work fine across each other .. if i need files from other pc using dc++ i just alter the ip addy in dc settings to internal ip 192.168.*.*

PtokaX forum

Re: Internal & Exteral IP, Connection Issues
« Reply #5 on: 28 October, 2006, 15:34:50 »