Hello,
I forwarded the ports but I think the time out is set too long. Here is what I get now.
Problem loading page
The connection has timed out The server at pilotalk.dyndns.biz is taking too long to respond. list of 3 items . The site could be temporarily unavailable or too busy. Try again in a few moments. . If you are unable to load any pages, check your computer's network connection. . If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web. list end
Scott
On Fri, 2007-05-25 at 17:02 -0500, Scott Berry wrote:
I forwarded the ports but I think the time out is set too long.
How? What have you done?
I was told to forward port 712 to 80 on the linux box. So what I did is I went in to my router which is a Linksys Wrt54G and I went to the ip address of 192.168.1.1 and I went under Applications and Gaming and went to the port forwarding tab and I set in the router port 80 on the linux box forwarded to port 712. I also looked at the httpd time out directive and set that to 300 just for curiosity which has made Apache not work so I am going to set the timeout back to 100.
Scott
----- Original Message ----- From: "Tim" ignored_mailbox@yahoo.com.au To: "For users of Fedora" fedora-list@redhat.com Sent: Friday, May 25, 2007 9:22 PM Subject: Re: Apache problems
On Fri, 2007-05-25 at 17:02 -0500, Scott Berry wrote:
I forwarded the ports but I think the time out is set too long.
How? What have you done?
-- (This box runs FC6, my others run FC4 & FC5, in case that's important to the thread.)
Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
-- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.8.0/819 - Release Date: 5/26/2007 10:47 AM
On Sat, 2007-05-26 at 10:59 -0500, Scott Berry wrote:
I was told to forward port 712 to 80 on the linux box. So what I did is I went in to my router which is a Linksys Wrt54G and I went to the ip address of 192.168.1.1 and I went under Applications and Gaming and went to the port forwarding tab and I set in the router port 80 on the linux box forwarded to port 712. I also looked at the httpd time out directive and set that to 300 just for curiosity which has made Apache not work so I am going to set the timeout back to 100.
That sounds backwards, but that might just be in the description.
From the public IP, forward port 712 (or whatever you want to use), to the private IP (e.g. 192.168.1.1) port 80, and run your Apache listening to port 80.
If you find that you cannot use port 80, because your ISP blocks it. You can run your Apache on that port, and forward the same port to the same port (i.e. public IP port 712 to private IP port 712, with Apache listening to port 712).
Bear in mind that if your ISP prohibits running a web server, as some do, you may get your account terminated. Some just block port 80 because the old code red exploit (which is so old that it's a stupid thing to do - what about everything else that's still a problem, but not blocked?), and don't care if you run a server some other way.
From the public IP, forward port 712 (or whatever you want to use), to the private IP (e.g. 192.168.1.1) port 80, and run your Apache listening to port 80.
Tim,
If I understand you correctly you say for instance forward "pilotalk.dyndns.biz" or forward something like 269.281.101.136 to 192.168.1.5 or whatever the local address is on the network. Am I foloowing you correctly here?
Scott
----- Original Message ----- From: "Tim" ignored_mailbox@yahoo.com.au To: "For users of Fedora" fedora-list@redhat.com Sent: Saturday, May 26, 2007 8:44 PM Subject: Re: Apache problems
On Sat, 2007-05-26 at 10:59 -0500, Scott Berry wrote:
I was told to forward port 712 to 80 on the linux box. So what I did is I went in to my router which is a Linksys Wrt54G and I went to the ip address of 192.168.1.1 and I went under Applications and Gaming and went to the port forwarding tab and I set in the router port 80 on the linux box forwarded to port 712. I also looked at the httpd time out directive and set that to 300 just for curiosity which has made Apache not work so I am going to set the timeout back to 100.
That sounds backwards, but that might just be in the description.
From the public IP, forward port 712 (or whatever you want to use), to the private IP (e.g. 192.168.1.1) port 80, and run your Apache listening to port 80.
If you find that you cannot use port 80, because your ISP blocks it. You can run your Apache on that port, and forward the same port to the same port (i.e. public IP port 712 to private IP port 712, with Apache listening to port 712).
Bear in mind that if your ISP prohibits running a web server, as some do, you may get your account terminated. Some just block port 80 because the old code red exploit (which is so old that it's a stupid thing to do - what about everything else that's still a problem, but not blocked?), and don't care if you run a server some other way.
-- (This box runs FC6, my others run FC4 & FC5, in case that's important to the thread.)
Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
-- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.8.0/820 - Release Date: 5/27/2007 12:31 PM
On Sun, 2007-05-27 at 19:05 -0500, Scott Berry wrote:
If I understand you correctly you say for instance forward "pilotalk.dyndns.biz" or forward something like 269.281.101.136 to 192.168.1.5 or whatever the local address is on the network. Am I foloowing you correctly here?
Pretty much. Forward port 712 from 269.281.101.136 through to port 80 on 192.168.1.5.