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.
I installed the rc.firewall and then I set up a webserver using Apache. Using ShieldsUp I checked the status of my ports. Knowing the Port 80 needs to be open in order for the webserver to work correctly, I am wondering if it is OK that that status of Port 80 is Stealth? So do I need to open Port 80? Also, since my computer is behind a router, would configuring port forwarding on the router solve this issue for me instead of opening up any ports?
Is that a masquerading router for your network? If so, and the Web server is on a different box to the one doing the routing, yes, I would just port forward tcp/80 to the appropriate machine.
OK, I'm having trouble with port forwarding. I have a LinkSys EtherFast Cable/DSL Router with 4-Port Switch (Model # BEFSR41). I go into the router config and go to the Forwarding tab. I click on the UPnP Forwarding button. For HTTP I make sure that TCP is selected, that the Internal External Ports are both 80, and I set the IP Address to the address of my computer within my local network (192.168.1.102). My IP Address outside the network is 151.199.115.99. I can get to my website using http://localhost/ and I can get to it using http://192.168.1.102 but I can't get to it using http://151.199.115.99. I checked the status of my ports again and Port 80 is still listed as Stealth. What am I doing wrong?
Originally posted by glevine Something to add to that....
My Apache webserver is running on 127.0.0.1. Could this be my problem? Do I need to configure the webserver to run on 192.168.1.102?
Some isp's block port 80, so if you're apache webserver is listening to port 80 it may not be getting any traffic. Try editing your httpd.conf file and having apache listen to port 8080 or some other high port that is not being used by any other processes. Then get into your router and route all traffic on port 8080 to your computer. When accessing your computer type http://some_address:8080/. Be sure to restart apache after making changes to the httpd.conf file. Also, I don't think apache is supposed to run on 127.0.0.1, i could be wrong, but that doesnt make much sense to me for apache to run on the loopback address.
Also, I don't think apache is supposed to run on 127.0.0.1, i could be wrong, but that doesnt make much sense to me for apache to run on the loopback address.
Actually, that is the address of localhost, which is where you access your site from the server itself when the site is not in production, so there is no problem with it being on 127.0.0.1. That IP address is each computer's IP address that it gives to itself, so everyone's local host is 127.0.0.1, unless you can change it I guess.
If I configure Apache to listen to port 8080 or something like that, then my site would be located at http://LAN_IP_Address:8080 but if I used a service like dyndns.com or public-dns.org, would they be able to access my server correctly so that my page gets displayed using the domain that I registered?
Also, would using port 443 (SHTML) work the same as 80, or is that another way of by-passing the listening port problem with port 80?
Originally posted by glevine Actually, that is the address of localhost, which is where you access your site from the server itself when the site is not in production, so there is no problem with it being on 127.0.0.1. That IP address is each computer's IP address that it gives to itself, so everyone's local host is 127.0.0.1, unless you can change it I guess.
If I configure Apache to listen to port 8080 or something like that, then my site would be located at http://LAN_IP_Address:8080 but if I used a service like dyndns.com or public-dns.org, would they be able to access my server correctly so that my page gets displayed using the domain that I registered?
Also, would using port 443 (SHTML) work the same as 80, or is that another way of by-passing the listening port problem with port 80?
It works the same whether you have a domain or not. When you register your domain it simply aliases your ip address to a name so when a user queries a name server for your_domain that nameserver will know about your ip address from higher level nameservers. In this case the ip address of your router is aliased to your_domain and you still have to specify the port 8080 because the router wont know where to route the traffic, also your isp may be blocking port 80 and by default all http requests use port 80.
As for the shtml, im not sure if isp's even block that port, so you may be able to just leave that alone. You wont have to add the :443 to the end of your domain because by default shtml protocols will use that port number.
Thanks bleunuit, you've been a big help. I understand the process now, but I have to wait until I'm back at home to actually try to implement it.
Just out of curiosity, if someone cares to answer, are most people on this and some of the other linux messages boards students or are they programmers, network admins, etc. in the actual workforce? I myself am a CS student at Virginia Tech and are using these message boards for the first time, so I am wondering where the majority of this information on these boards is coming from.
I'm a student during the school year and I will be graduating with a BS in computer enginnering from a Tech school in Vermont. I scored a linux system admin internship for the summer so I guess I'm kinda workforce/student.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.