IP Port 80

[Brad De Vries]

On 5/18/06, Rick Sivernell <res005ru at verizon.net> wrote:
> On Wed, 17 May 2006 16:36:45 -0500 (EST)
> Net Llama! <netllama at linux-sxs.org> wrote:
>
> > On Wed, 17 May 2006, Rick Sivernell wrote:
> > > On Wed, 17 May 2006 10:28:02 -0600
> > > "Michael Hipp" <michael at hipp.com> wrote:
> > >
> > > > > Now this last one seems to indicate that my web server is not listening
> > > > > to 8080 or something else is not set. Using FC4.
> > > >
> > > > I tried a couple of quick nmap's of that address and didn't see anything open. Could you disable the firewall temporarily. Since you're behind NAT anyway the risk is negligible. I've found strange interactions between NAT and the Firewall on some of these commodity router boxes.
> > > >
> > >
> > > Mike
> > >
> > >    I get the following from no-ip port checker:
> > > Error: I could not see your service on 71.252.218.83 on port (8080)
> > > Reason: Connection timed out
> > >
> > > I have set /etc/services to use 8080 tcp www. What I do not know if my
> > > services have opened port 8080. using fc4 what checks or sets ports
> > > open or closed? I can not turn of firewall rules in router, some are
> > > not allowed.
> >
> > "netstat -an | grep 8080"
> >
> >
>
> Well then it must be open:
> netstat -an | grep 8080<return>
> 0   0 192.168.0.50:8080  0.0.0.0:*  LISTEN
>
> If 192.168.0.50:8080 is open then that means that verizon has many more
> ports blocked or my router is blocking.
>
>  --
> Rick Sivernell
> Dallas, Texas  75287
> 972 306-2296
> ricksivernell at verizon.net
> Registered Linux User

Rick, it seems to me that this has become more complex than it needs
to be.  Why not just leave the Linux services where they were, leave
the HTTP server listening on port 80 and make one change to the router
to port-forward/redirect all incoming requests on port xyz to port 80
on the Linux server.  That way you can change port xyz quickly and
easily to anything you want by just changing the router's settings and
you can pick any unused incoming port for your test.

If, for example, you allow SSH into your Linux server from the outside
world, you are probably port-forwarding/redirecting port 22 from the
outside to port 22 on your SSH server.  If that works, temporarily try
port 22 being redirected to port 80.

For a more permanent solution, any port not currently being allowed in
will work but I would recommend something greater than 30 (mainly
because that's getting a little to close to Lonnie's age.)

HTH,
Brad.