|
|
 
|
|
Author
|
Topic: setting up a web server using Linux
|
|
|
|
|
|
|
Scott Norwood
Film God
Posts: 8146
From: Boston, MA. USA (1774.21 miles northeast of Dallas)
Registered: Jun 99
|
posted 04-09-2002 11:33 AM
What is your goal in doing this? Do you want to get a web server up and running as fast as possible? Do you want it to be primarily a learning experience? Do you want to do this for some other reason?For Linux, I'd recommend the Slackware distribution, which can be found at http://www.slackware.com/ Slackware is less common than various other distributions like Redhat and Mandrake, but it is generally a bit more conservative than the other two and is thus more stable, at least in my experience. The Film-Tech web server runs a hacked-up Slackware installation. The most common web server for Unix and Unix-like systems is Apache -- http://www.apache.org/. The included documentation is pretty good and you should be able to get a basic site up and running fairly quickly if you have any prior Unix knowledge/experience. The BSD variants (FreeBSD, NetBSD, and OpenBSD) are also worth looking into and each offers its own unique benefits. I would tend to recommend Linux for someone without a fair amount of Unix knowledge, though, since the documentation and support that is available online seems to be more abundant and of higher quality (in general). Lastly, when setting up any system that is on a network, take note of security issues. If all you want to do is serve web pages, then you don't need to run services like sendmail, portmap, telnetd, ftpd, rshd, etc. Instructions for turning these services off are specific to your OS and (in the case of Linux) your distribution (Slackware, REdhat, Debian, etc.).
| IP: Logged
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Scott Norwood
Film God
Posts: 8146
From: Boston, MA. USA (1774.21 miles northeast of Dallas)
Registered: Jun 99
|
posted 04-10-2002 08:59 PM
If your address is in the 10.x.x.x range, then you are behind some sort of proxy or NAT (network address translation).The 10-net addresses are among a group of so-called "non-routable" addresses intended for use in private networks and specified in RFC1918: http://www.ietf.org/rfc/rfc1918.txt These RFC1918 address blocks are guaranteed never to be used on the Internet directly and are thus "safe" to use for private networks (i.e. they won't conflict with someone else's address space). Unless you have direct control of the router, firewall, or other device which is doing the NAT or unless you want to get fancy with IP tunneling, etc., it isn't possible to host public services which accept incoming traffic requests on a NAT'ed subnet (except for other users on that network, of course, but we're talking about the Internet at large here). NAT breaks various other things, too. FTP can be made to work, for example, but stuff like videoconferencing often doesn't.
| IP: Logged
|
|
Dave Macaulay
Film God
Posts: 2321
From: Toronto, Canada
Registered: Apr 2001
|
posted 04-10-2002 09:42 PM
Joe:
Take a look at http://www.dyndns.org in the dynamic DNS area. These guys specialize in facilitating what you are trying to do. (Dynamic because most ADSL systems don't assign fixed IP numbers to users; yours may change at any time... if you do have a static IP# things are a bit easier)
The IP# you report may be a red herring. Almost all ADSL systems use "transparent proxy" systems that cache web pages, serving them from their local memory instead of from the "real" internet. Pages are cached for a time depending on how many users are accessing them.
This is called transparent because you can not disable it, cable internet systems typically use a proxy server model that can be disabled by changing your internet settings. You can check in start/settings/control panel/internet/connection/LAN settings: if either of the three main check boxes is checked then you can uncheck it and (possibly) not use the proxy any more. Something is odd - the 10.x.x.x IP# is impossible to use on the internet, as Scott mentioned. It can not be the IP# seen by an internet site when you connect to it. Use the IP reporting tools at www.dyndns.org or www.grc.com
This is a different problem from NAT forwarding/masquerading. With a proxy you still have a "real" IP number that would be seen by more dynamic things like IRC. You can use a service like dyndns.org to map a URL to that IP# and then you could host joeredifer.com from your home machine.
BTW - ISPs hate home web servers. They probably forbid it in the EUA you are bound by. They probably have snoop systems that regularly ask your port 80 whether it is a HTTP server, and you might be disconnected if it says "yes"... just something to consider...Oh... the entire class A address block 12.0.0.0 - 12.255.255.255 is owned by ATT.net! They might be selling some of it to other ISPs though, there are very few single-owner class A blocks...
| IP: Logged
|
|
|
|
All times are Central (GMT -6:00)
|
|
Powered by Infopop Corporation
UBB.classicTM
6.3.1.2
The Film-Tech Forums are designed for various members related to the cinema industry to express their opinions, viewpoints and testimonials on various products, services and events based upon speculation, personal knowledge and factual information through use, therefore all views represented here allow no liability upon the publishers of this web site and the owners of said views assume no liability for any ill will resulting from these postings. The posts made here are for educational as well as entertainment purposes and as such anyone viewing this portion of the website must accept these views as statements of the author of that opinion
and agrees to release the authors from any and all liability.
|
Home
Printer-friendly view of this topic