Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
of course, internal IP's are exactly what their name suggests in turn wouldn't get you very far out in the internet world
your internal ip would work internally and your external ip (what you call public i am assuming) would work outside your home.
It doesn't matter if it's the ip address of your router, which could then forward through to your apache / ftp server, or if you have a direct dial connection from your apache / ftp server.
The main point here is: You can't get on the web without a public ip address. This is what your ISP gives you when you connect.
You may have an ISP then assignes you a permenant address, in which case it's easy to remember, or you may be given a different one each time you dial up, in which case you would have to make a note of it each time you connect.
Thats is exactly what I'm asking about, I'm not an English native speaker I'm From El Salvador and we call Public IP (external Ip I think), to an Ip that allow to you to have access to you web server (for example) from anywhere,
But It's there any other way to avoid this, or is requirement?
I tried to setup a web server before, but just me and other terminal from the same ISP network that provides Internet to me could see it.
If you're connected to the internet then you have a public IP address already. However with a lot of internet connections sold to consumers (ie. not to businesses) this IP address can change every time you connect, or even every so often, dependening on how your ISP sets it up. If you really want to do web hosting then contact your ISP about signing up for a business connection with a static IP.
There is a way to get around the changing IP problem - register your domain name with a dynamic DNS place like http://www.dyndns.com/ and then run ddclient (http://ddclient.sourceforge.net/) to update your IP address whenever it changes. That way you can have a domain name that will always point to the right IP address.
Originally posted by the-roseman Thanks DrOzz, Thanks Mike,
Thats is exactly what I'm asking about, I'm not an English native speaker I'm From El Salvador and we call Public IP (external Ip I think), to an Ip that allow to you to have access to you web server (for example) from anywhere,
But It's there any other way to avoid this, or is requirement?
I tried to setup a web server before, but just me and other terminal from the same ISP network that provides Internet to me could see it.
What about an FTP server?
To find out what the public IP assigned to you by your ISP is, you can go to this little mivascript I wrote:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.