|
Home > Archive > Apache Server configuration support > July 2006 > apache, port 80, linksys, and suscom
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
apache, port 80, linksys, and suscom
|
|
| uncleclinto 2006-07-23, 1:23 pm |
| Hey kids,
I recently switched ISP's. I am suspicious that Suscom is blocking incoming
requests on port 80 because folks have commented that they cannot get to my
page (http://www.walterswebdesign.org). I found out that I can apparently
subvert this by having apache listen on another port, like 6010, and simply
ofrward http requests to this port in my router. I still can't get my page
this way (yes, I am typing http://www.walterswebdesign:6010 when I test
this).
What am I missing? Does anyone here use suscom? Do they block 80? What
ports don't they block?
Please help...
| |
| Stuart Miller 2006-07-23, 1:23 pm |
|
"uncleclinto" <qwalters@suscom.net> wrote in message
news:78KdnXIMDsbLGV7ZnZ2dnUVZ_omdnZ2d@su
scom.com...
> Hey kids,
>
> I recently switched ISP's. I am suspicious that Suscom is blocking
> incoming
> requests on port 80 because folks have commented that they cannot get to
> my
> page (http://www.walterswebdesign.org). I found out that I can apparently
> subvert this by having apache listen on another port, like 6010, and
> simply
> ofrward http requests to this port in my router. I still can't get my
> page
> this way (yes, I am typing http://www.walterswebdesign:6010 when I test
> this).
>
> What am I missing? Does anyone here use suscom? Do they block 80? What
> ports don't they block?
>
> Please help...
>
A bit more information will be helpful
ping to walters... shows 71.207.21.97 is this correct?
whois shows that is a comcast address, but traceroute shows this as a subset
of suscom. Which is correct?
what is the full address that you isp is giving your server or router? is
71.207.21.97.hsd1.pa.comacst.net correct?
Who is you use for dns forwarding? Are they forwarding requests to :80 or to
:6010?
Can you access apache at 6010 when you run on your lan?
Is your router allowing access through 6010? Try putting the server in the
'dmz' so all requests can be seen, rather that filtered by your firewall.
If you can tell me (e-mail if you want) how you are configured at a specific
time I can take another look from here.
I am allowed two ip addresses here, so I have the web server outside of the
router. Perhaps you could try this approach.
Stuart
| |
|
| "uncleclinto" <qwalters@suscom.net> schreef in bericht
news:78KdnXIMDsbLGV7ZnZ2dnUVZ_omdnZ2d@su
scom.com...
> I recently switched ISP's. I am suspicious that Suscom is blocking
incoming
> requests on port 80 because folks have commented that they cannot get to
my
> page (http://www.walterswebdesign.org). I found out that I can apparently
> subvert this by having apache listen on another port, like 6010, and
simply
> ofrward http requests to this port in my router.
Routers are commonly able to forward from any port on the public IP to any
other or the same port on a local IP. No need to change config of apache.
You even can have a router forward multiple ports to a single port on your
webserver without apache having a clue.
> I still can't get my page this way
> (yes, I am typing http://www.walterswebdesign:6010 when I test this).
The missing '.org' is assumed a typo ...
> What am I missing?
You are using mydyndns.org. Confirm their records match your current comcast
ip, otherwise your request is redirected to a place you're not listening. If
their services include wrapping your site in some way, the DNS record for
your domain will point to their server. This server is likely NOT to listen
to the port you add to the request ...
So first, try to reach your apache by addressing its IP directly, like in
http://your-suscom-ip or http://your-suscom-ip:aport.
You may need to have your browser set to use a proxy, as many routers cann't
handle their ougoing request as incoming directly. If the latter is working,
go back to dyndns.org to set up port masqurades.
Last thing to do from here is to set up continious monitoring of your public
IP and update the records at dyndns with each change.
HansH
| |
| uncleclinto 2006-07-23, 7:21 pm |
| Yes, my current ip is 71.207.21.97. I have my server listening on port 80
right now. I have my router forwarding requests to port 80. I use
DYNDNS.org. I didn't set them up to forward to 6010 with webhop yet,
because I wanted to make sure it worked to go to mydns:6010 first.
Do you in fact get a site or an error when you go to
http://www.walterswebdesign.org?
"Stuart Miller" <stuart_miller@shaw.ca> wrote in message
news:yXOwg.222511$Mn5.32730@pd7tw3no...
>
> "uncleclinto" <qwalters@suscom.net> wrote in message
> news:78KdnXIMDsbLGV7ZnZ2dnUVZ_omdnZ2d@su
scom.com...
apparently[vbcol=seagreen]
What[vbcol=seagreen]
> A bit more information will be helpful
>
> ping to walters... shows 71.207.21.97 is this correct?
> whois shows that is a comcast address, but traceroute shows this as a
subset
> of suscom. Which is correct?
> what is the full address that you isp is giving your server or router? is
> 71.207.21.97.hsd1.pa.comacst.net correct?
> Who is you use for dns forwarding? Are they forwarding requests to :80 or
to
> :6010?
> Can you access apache at 6010 when you run on your lan?
> Is your router allowing access through 6010? Try putting the server in the
> 'dmz' so all requests can be seen, rather that filtered by your firewall.
>
> If you can tell me (e-mail if you want) how you are configured at a
specific
> time I can take another look from here.
>
> I am allowed two ip addresses here, so I have the web server outside of
the
> router. Perhaps you could try this approach.
>
> Stuart
>
>
|
|
|
|
|