herb Kornfeld wrote:
>..
> I hope this helps
> Set up:
> I do want my webserver connected to the world.  I have my cable modem 
> connected to my router.  The router is connected to the linux box.  I 
> configured the router to set the linux box's IP address to be in the DMZ (I 
> assume this opens up the ports).  I have other devices connected to the 
> router as well.    

You use the words a bit different than I would, but it does look like
port forwarding to your computer for http access is working, since you
see the apache test page.

In general I would be concerned if you (really) were forwarding any/all
incoming connections to your main computer. That forgoes a major benefit
of having a firewall -- best is to forward only specific ports needed
for specific services (eg, just 80 for http).

> 
> Step1:  When outside of my home and away from my private network I open a 
> browser and type in the public IP of my home system 76.88... and the standard 
> Apache Fedora test page displays on the browser (yay, just as I expected).  
> 
> Step2: I have my wordpress blog located at http://76.88..../wordpress and 
> when I try to access it, the browser trys to open the private IP address of 
> my webserver 192.168.... instead of the public IP 76.88.../wordpress .  I am 
> a newbie and don't understand why it seems to try and redirect the request.

I'm as confused as you are about what's going on here.

How is apache configured to handle the wordpress -- is there a
wordpress-installed configuration file /etc/httpd/conf.d/wordpress.conf,
perhaps? What happens when you access http://localhost/wordpress from
your main computer itself? If this doesn't work, that might be a good
starting point. If it does, I would like to look at the config details
in your gateway's manual -- maybe you inadvertently configured it to do
something you didn't intend. Maybe you could post the manufacturer and
model of your gateway box.


Regards,
..jim

-- 
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie

Reply via email to