Linux - Networking This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
11-12-2005, 08:38 PM
|
#1
|
Member
Registered: Oct 2005
Location: Seattle, WA
Distribution: Fedora Core 4
Posts: 67
Rep:
|
How do I set my Apache server to be seen in the Internet?
Hello Gurus!!!!
I need your help once again. I just finished setting up Linux with Apache, MySQL, and PHP. Everything seem to be working fine, using my system as localhost. Now I would like my web server to be seen in the internet. Here is my setup at home:
1) My server's operating system is Fedora Core 4 and uses wireless networking.
2) I have a cable modem (ISP provider: Comcast).
3) The cable modem is connected to a Linksys wireless router. The router is configured to have WEP encryption with keys.
4) My network's config is DHCP. My computers and router IP addresses are generic 192.168.*.*.
Do I really need to buy a Domain Name and/or IP address? If so, which company do you recommend? Which files do I need to edit? Do I need to change anything in my router? Please provide detail steps for I am still new at this.
Thanks in advance!!!!
Jun
|
|
|
11-12-2005, 10:27 PM
|
#2
|
Senior Member
Registered: Nov 2004
Location: Third rock from the Sun
Distribution: NetBSD-2, FreeBSD-5.4, OpenBSD-3.[67], RHEL[34], OSX 10.4.1
Posts: 1,197
Rep:
|
This has been covered *many* times before. Try the search button or google.
Also, Comcast will be unhappy with you if you put a webserver on a residential cable line.
|
|
|
11-12-2005, 10:42 PM
|
#3
|
Member
Registered: Oct 2005
Location: Seattle, WA
Distribution: Fedora Core 4
Posts: 67
Original Poster
Rep:
|
hi sigsegv,
thanks for replying. i'll go search it out here and in google. i saw it before but could not seem to find it again. should have bookmarked it.
i don't expect a big traffic happening for my webserver. this is just a small project for myself using linux, apache. mysql, and php. but would love to actually see working in the outside world.
for those who knows the site where i can find the info, please send me the address or link. i'll continue looking for the time being.
thank you!!
|
|
|
11-13-2005, 06:41 AM
|
#4
|
Senior Member
Registered: Jan 2002
Location: St Louis, MO
Distribution: Ubuntu
Posts: 1,284
Rep:
|
You need to look at configuring a dynamic naming service such as DynDNS or No-IP to point through to your computer, and configure your cable modem to forward port 80 to your computer running Apache. As stated before, there are one or two threads on this already.
|
|
|
11-13-2005, 11:59 AM
|
#5
|
Member
Registered: Oct 2005
Location: Seattle, WA
Distribution: Fedora Core 4
Posts: 67
Original Poster
Rep:
|
hello fouldsy,
thanks for helping out. i saw the thread. could you or anyone please help me understand the basics of it though so i know at least some on how it works?
this is how i understand it:
1) i make a domain name, say www.test.net. i get this domain name, if its available, from dyndns. they'll give me also an ip address, say 25.24.23.22.
2) i change my /etc/hosts file to have my new domain name and ip address and "keeping" my servers 192.168.5.5 localhost.
3) i change my router setting to forward port 80 from 25.24.23.22 to 192.168.5.5.
i have a linksys router. i could not find the area where i can do this forwarding. i see a port range forward with the following fields/columns:
Application Start End Protocol IP Address Enable
well i'll go read some more. thanks guys.....
|
|
|
11-13-2005, 12:27 PM
|
#6
|
Senior Member
Registered: Jan 2002
Location: St Louis, MO
Distribution: Ubuntu
Posts: 1,284
Rep:
|
Not sure about that router, would need read the associated docs for it. But, you shouldn't need to change your hosts file. Basically, you set one of the DynDNS clients to update their services when the IP address of your router changes. This means when someone enters the domain name, DynDNS take it, query their database to find your IP, and forward the request to your router. The router then points it to your computer. Some routers (again, check your docs) have a client built-in, so you don't have to do anything on your machine other than have Apache running and serving requests.
|
|
|
11-13-2005, 11:59 PM
|
#7
|
LQ Newbie
Registered: Oct 2004
Posts: 7
Rep:
|
application should be apache, start & end should be 80, you might need to make it 81 depending, im not sure. but try 80 first. protocol should be TCP. and address should be your computer's address. set that address on your machine to be a static address. your default gateway should be 192.168.1.1, unless you have changed it, and the subnet mask is 255.255.255.0 unless you'e changed it. if it is a dynamic address, it changes, and might be the same, or it might be different, it all depends. with a static address, it will remain that same address always.. btw, that is a private address on your own network, there is a public address that your router has that it uses and it routes al;l traffic to your computer through complex algorithms. if you would like to learn more, get books on CCNA certification. you can get certified afterwards.
|
|
|
11-14-2005, 03:04 AM
|
#8
|
Senior Member
Registered: Jan 2002
Location: St Louis, MO
Distribution: Ubuntu
Posts: 1,284
Rep:
|
Quote:
if you would like to learn more, get books on CCNA certification. you can get certified afterwards. [/B]
|
Not being disrepectful, but that's a little extreme for learning basic networking 
|
|
|
11-14-2005, 02:13 PM
|
#9
|
Member
Registered: Oct 2005
Location: Seattle, WA
Distribution: Fedora Core 4
Posts: 67
Original Poster
Rep:
|
hi guys,
thanks so much for your input!!!
fouldsy, i am now setup with dyndns. woohooooo! everything works great now and to top everything off, its free!
ab2kgj, thanks for the help on the router. just did that and im in business!
i just need to find out how to secure this server from outside attack. any suggestions?
|
|
|
11-14-2005, 02:35 PM
|
#10
|
Senior Member
Registered: Jan 2002
Location: St Louis, MO
Distribution: Ubuntu
Posts: 1,284
Rep:
|
Best write something to get off 666 posts
Now onto something useful! Glad you got everything working and is playing quite nicely across the Internet with a DynDNS address. Well done! As for security, you should be looking at the machine as a whole, the usual basic stuff. Turn off services you don't need. Remove software you don't need. Close ports that don't need to be open. Ensure permissions on the directories aren't set to 777. Ensure your passwords are strong. With Apache, maybe look at enabling SSL, preventing images being linked off site, limiting FTP access and/or upload size limits, etc.
|
|
|
All times are GMT -5. The time now is 02:01 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|