Apache, almost good to go, but . . .

[Floog]

I've got Apache 1.3.24 successfully installed on my Slackware box.
I did a very basic configuration of httpd.conf.
So far, I can get my bare-bones website to show up using either Mozilla or Opera by entering the following:
http://127.0.0.1 http://localhost http://icecream.com (what can i say, netconfig asks you to supply a domain name, so i did)

Here's the issue:

I connect to the internet by way of dsl. My ethernet card connects to a Linksys 10/100 4-port switch, and then the switch connects to a Linksys DSL Router that uses dhcp to sync up with the ISP.

I created a free dynamic hosting account at no-ip.com and use their linux app. to update my ip address for their service. The domain name i set up with them is-- icecream.no-ip.org

As you can probably guess, the problem is that I can't connect to the apache server and my website when I try to go to http://icecream.no-ip.org

I don't get a refusal or a "no permission" message from the apache server. The browser simply times out after a minute or two trying to locate the address.

Does anyone have experience using this kind of service? Or is there something else you think I should look at?

I'll post my httpd.conf if anyone thinks that would be helpful.

Thanks for your time and patience.

Mike

[revolution]

did you port foward port 80 to your server?

[SuperHornet]

Also is port 80 active on your router (assuming thats the IP you used).

[Floog]

Y'know, I've come too far and spent too much with linux to shy away from a challenge at this point.

I have a Pentium 1 166mhz box with 64 megs of RAM, sittin' around with nuthin' to do. I don't want to be dependent on Linksys and their setup. So, I'm gonna pop a 2nd nic card in it and install the latest stable kernel and build a darn router/firewall box if it kills me.

I know this is gonna set my Apache project way back--- the subject of routers and firewalls represents a huge learning curve for me.
If I really want to control and administer my home network, this is the only logical thing to do.

Wish me luck. I'm sure I'll be posting for your help.

Thanks,

Mike

[Floog]

Originally posted by Floog:
<STRONG>. . . and spent too much with linux to shy away from a challenge . . .</STRONG>

oops, meant to say "too much time." Didn't want you folks to think I meant $$.

Mike

[jcrowe]

you should check out the e-smith distro for gateway/router.

good stuff :)

jcrowe

[SKoL]

I'd learn a real distro, gives you a better shot in the future to acually use it for work/etc..

Getting a firewall/gateway setup and working is tough for people who are newer at linux, but it will give you super experience. Just stick it out.. go slow, make sure you know exactly how a gateway/firewall works, (not linux in a sense.. with networking in general) before you even begin.
http://www.oreilly.com/catalog/fire2/

that book would be a good one..