January 2nd, 2012, 01:44 PM
DNS and private IPs
I am a newbie in this forum, seeking for help......
I am familiar with basic networking procedures, routing, NATing etc, and DDNS services such as No-ip and DynDNS.
Now my question is. I have a workstation running Fedora 14 Linux. This is sitting behind a router which assigns it a private IP in the range 192.168.99.xxx. I have no administrative access to the router. At the moment I access the workstation from the rest of the world using Teamviewer since this does NAT traversal. Hamachi may also be an option, though the current linux version does not seem to be very stable. Is there any way I can get this private IP (which is actually dynamic but has a very very long lease) to map to some publicly available domain such that I can run an ftp server and web server and access them from anywhere simply by pointing to a domain name? DynDNS and No-IP do not work with private IPs, unless you can set up port forwarding from the router, and since I do not have administrative access to the router, that is not possible.
Many thanks !
January 2nd, 2012, 02:37 PM
To run any services behind a router, you need to enable port forwarding. The rest of the world can't see your private IP address, which is why you would need to port forward. Without admin access to the router, there's not much you can do.
"I don't need to get a life. I'm a gamer. I have lots of lives!"
January 2nd, 2012, 03:15 PM
Thanks for your rapid reply. I supposed as much. What I was hoping for was some client that I could install on my Fedora box, which would NAT traverse to a public domain somewhere, which I could then access. Teamviewer (freeware) for example, does an excellent job at providing remote control and file transfer services from any IP to any IP irrespective of whether either or both is private, public and located on any network behind any router or chain of routers.... truly amazing. This is at the expense of a middleman to which each Teamviewer client connects, and therefore there is an expense of bandwith, but I am happy to live with that, if I can use some similar system to map my private IP to a public domain.
Originally Posted by hiker
January 6th, 2012, 07:43 PM
There are techniques that allow point to point connections between hosts that are behind NAT, but they require a middleman server to initiate the connection and it has to be supported by both the client application and the server application. Standard FTP and HTTP clients and servers do not support this.
If you have a server outside of the network that is publicly accessible then you could use that server to make the private workstation accessible to the outside, but you have to consider whether that is even worth doing (you could just host the content directly on that publicly accessible server). Basically your private server would connect to the public server over a VPN, and then the public server would act as a proxy to allow the world to connect to the private server.
January 11th, 2012, 01:16 AM
Originally Posted by afen
i think Logme in and hamachi is the better option for u sir...