I'm trying to set up a web server on my home machine, which is running Apache on Slackware 7.2 on the 2.2.19 kernel. Unfortunately, I'm using Verizon DSL and Verizon just blocked port 80 in an effort to fight off Code Red (as if my Apache was ever vulnerable). In order to get around this, I set http to port 8080 in /etc/services and told httpd.conf to go to port 8080 as well; since my computer's behind a Linksys router, I had the router forward traffic on port 8080 to it. I also got the domain "foo.bar.com" and dns2go to get around Verizon's forced use of dynamic IPs. I restarted apache and inetd (and then the entire machine just for laughs).

After having done all of this, I can type http://foo.bar.com:8080/ into a browser and get my front page. However, http://foo.bar.com/ eventually times out or just dies immediately because it seems that Apache is still trying to use port 80. And I know this is the only messed up service because ssh, telnet, ftp, finger, and talk seem to be working fine. Have I missed something in the configuration? What else do I need to do (other than switching ISPs) to make the web server work?

Thanks,
cauchy

It doesn't look like anything is wrong to me!! As when you type http://foo.bar.com/ your browser really connects to http://foo.bar.com:80/ hence fails as your httpd is listening on 8080, so you'll need to either ensure that everyone uses the http://foo.bar.com:8080/ or make your route forward any requests that arrive on port 80 to port 8080 on your server (if you can do this).

HTH

Jamie...

Jamie's right.
To confirm this type as root on your Linux box.

#netstat -natp

You should see the httpd service running on your ip on port 8080.

/Raz

you should be able to do this with ipchains,

with -j REDIRECT 8080

all browsers hitting the machine on port 80 will be redirected to 8080 where they will find apache.



ipchains -A input -p TCP -d 0/0 www -j REDIRECT 8080