Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
...for the past few years I've run a webserver for a local high school football team out of my home using a computer I purchased for the task. A month ago the power supply and motherboard went and upon fixing, the hard drive an IBM "deathstar" said it's final goodbyes. The site was running well and I also had mailman up and running in order to have a mailing list for the program.
...due to the events above I had the power supply and motherboard replaced and purchased a new harddrive. Yesterday the nice folks over at Duke University that are member of dulug.duke.edu had and install fest and assisted me in getting Fedora 5 up and running. It's been about three plus years since I last went through the set-up for the networking and apache items to get the site up and I'm having a tough go at it now.
This is what I have...
(a) one is a windows box that i use DHCP to grab an IP from and simply use for home use and business
(b) linux box that is being used solely for the website
Internet service is through Roadrunner and comes from the cable to a supplied router.
I have a static IP for use with the webserver.
Prior to the system going down the router and all associated items were working fine, which leads me to believe that all problems I'm experiencing at the moment are due to incomplete set-up issues.
What I have from the Roadrunner folks is a sheet that lists Public network info and Private network info. The public info is 24.172... stuff while the private is 192.168... stuff.
I have a valid hostname and the static IP is listed appropriately with the folks I have the hostname from.
This is what I'm getting...
...on the webserver...if I go to Networking and have the system set for DHCP I can see the outside world and the test page for Apache appears on one of the 192.168... available DHCP addresses, which seems to make sense. I can access this using the address either on the webserver or the other machine in the local network.
On the other hand if I change from DHCP to Static IP on the webserver (which I believe I should be doing) I'm unable to see the outside world from the webserver and does not look as though I'm able to get to the static IP from the other machine in the network, although I can bring up the apache test page from the webserver locally.
Again, I'm sure I simply have some configuration items screwed up and any help would be greatly appreciated.
Also, is there not a command anymore for system-config-httpd in fedora 5? or an equivalent.
PS...the first time through I worked with two friends that helped me through the process and unfortunately I don't have that assistance at this time.
Also when doing a Static IP setup make sure you specify the Default Gateway (the IP address of the Router 192.168...)
And of course you will have to either use the SAME Static IP your Webserver was using before, or you will need to modify the configuratin in the Router to forward the right Ports (80) from the Internet to the Webserver.. Check the User guide for your router for Port Forwarding.
configure the router to have the webserver box in a dmz, outside of the router firewall.
[ the iptables on the serverbox are the same firewall, and won't conflict with the server. ]
you only need one ip address to access the server, the router ip address.
the server box can use a local network ip and the router will mask that to it's public ip address.
I turned off dhcp on my router and just use local network ips that I manually assign, it's not needed to use dhcp.
[ though re installing windows to not use it is a pain, I'm sorry you still use the malware ]
The routershould have the static public ip address as it's exteral ip address,the server should only have a local ip address.
Egads that silly DMZ setting in the routers is the worst feature they put in them..
There is no reason you should ever use that DMZ feature. If you need ONE port forwarded, Forward ONE port.. to put the entire system outside the NAT box by using the DMZ option is just silly, and also it throws away what extra security the NAT box may provide.. (covering your tail for a misconfigured iptables for instance..)
Sure use iptables on the Server, but if you can't forward ONLY the ports you need from the router using the simple web interface, I sure as heck have to question wether you can configure iptables properly.. Don't solve a small problem with a sledge hammer, and Don't use the DMZ option in Broadband routers..
it's handy to make sure you have the actual server working right.
when you have 2 firewalls between your server and the internet either one can kill connectivity.
removing one is a means to make sure it isn't the problem.