Netgear FVS318 router failing to connect to apache port 80

Jeff Lawlor lawmen5 at comcast.net
Sun Feb 8 15:14:21 UTC 2004


What is the 318's log telling you?  Post an entry please.

On Sat, 2004-02-07 at 17:44, Brooks Kelley wrote:
> Alexander,
> 
> My firewalls are not on. I can get port 80 to respond when using another
> router brand. 
> 
> The Netgear FVS318 router has built functions for VPN which someone I am
> working with needs so if I can get around this problem, it would be
> great. Else, if I can't solve this problem, I will have to send them
> back.
> 
> Anyway, WAN stands for Wide Area Network, LAN stands for Local Area
> Network. DMZ is a host on a LAN exposed to the WAN by the router.
> 
> When I DMZ my host on a Linksys or a Nexland router, surfers from the
> WAN ( WWW ) can surf pages on my web server located on my LAN without
> any problem.
> 
> What I know is that the packets being passed on by the Netgear router
> are not being parsed by the Apache Daemon because Apache does not think
> the packets are meant for it. The question is why?
> 
> Other programs parse data meant for them on the DMZ host. So, why should
> I be able to use Webmin, SSH, and HTTPS from the web and not HTTP?
> 
> Thanks,
> 
> Brooks Kelley
> Linux+ Certified, A+ Certified
> 
> On Sat, 07 Feb 2004 17:48:12 +0100, Alexander Dalloz wrote:
> 
> 
> > Date: Sat, 07 Feb 2004 17:48:12 +0100
> > From: Alexander Dalloz <alexander.dalloz at uni-bielefeld.de>
> > Subject: Re: Netgear FVS318 router failing to connect to apache port
> > 80
> > To: fedora-list at redhat.com
> > Reply-To: fedora-list at redhat.com
> > 
> > Am Sa, den 07.02.2004 schrieb Brooks Kelley um 16:59:
> > > Afer installing Fedora, I set up a netgear FVS318 to handle my web
> > > pages.
> > > 
> > > I am having trouble with the Netgear FVS318 router getting web pages
> > > from the WAN, but not from the LAN.
> > > 
> > > >From the WAN via DMZ, it can connect to my webmin just fine ( port
> > 10000
> > > ). To SSHD just fine ( Port 22 ). Ironically, to Apache port 443 (
> > > HTTPS: ) just fine. But when it comes to port 80 ( HTTP ), there is
> > no
> > > response from my server.
> > > 
> > > I have sniffed the network with ethereal and the router is trying to
> > > pass the packet along from the WAN to my router and then to my
> > server,
> > > but there is no response from the server. The packet looks to be
> > well
> > > formed.
> > > 
> > > I sniffed my Nexland router ( on another set ) and it responded
> > quite
> > > well.
> > > 
> > > Has anyone a clue as to why this is? And how they solved this
> > problem!
> > > 
> > > BTW, it is the same problem with my Redhat 9.0 server too. I just
> > tested
> > > it en lieu of Fedora.
> > > 
> > > Also, my httpd.conf file is classic and is set to 
> > > Listen 80.
> > > 
> > > But, changing it to Listen 8080 and trying it has not had anymore
> > > success than 80.
> > > 
> > > Thanks in advance,
> > > 
> > > Brooks Kelley
> > > Linux+ Certified, A+ Certified
> > 
> > I do not understand your setup - what is WAN, what is DMZ and what LAN
> > in your setup, which task has the Netgear device - but it seems clear
> > that something is blocking port 80. So check your firewalling.
> > 
> > Alexander
>  
-- 
JL
>From my Linux workstation





More information about the users mailing list