|
Home > Archive > Web Servers on Unix and Linux > October 2007 > accessing apache behind DSL modem
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 |
accessing apache behind DSL modem
|
|
| jim.shephard@gmail.com 2007-10-02, 1:23 pm |
| My Apache server (a Sun Enerprise 4000) is behind a DSL modem with an
unroutable DHCP assigned address (192.160.xxx.xxx) and I would like to
access it from the outside world on a "private" basis by just typing
the I.P. of the DSL modem in to the browser client from outside. In
other words this will be an unpublished web server for myself only,or
whomever I give the I.P. to. At this point I can SSH to the 4000 from
the outside using a Cygwin client, so I have connectivity and also can
access a web page on the 4000 from inside the 192.168.xxx.xxx domain
so the httpd.conf file is set properly and the httpd deamon is
running. How can I accomplish accessing web pages from outside?
| |
| Chris Davies 2007-10-03, 1:24 pm |
| jim.shephard@gmail.com wrote:
> My Apache server (a Sun Enerprise 4000) is behind a DSL modem with an
> unroutable DHCP assigned address (192.160.xxx.xxx) and I would like to
> access it from the outside world on a "private" basis by just typing
> the I.P. of the DSL modem in to the browser client from outside.
Those two statements are mutually exclusive: if it's unroutable then by
definition it can't be reachable from "the outside".
> In other words this will be an unpublished web server for myself
> only,or whomever I give the I.P. to.
Assuming it really is routable and you really can get at it from "the
outside2, you're going to be in for a bit of a shock if you expect it
to remain undiscovered for long.
> At this point I can SSH to the 4000 from the outside using a Cygwin
> client, [...]
Then it's not on an unroutable address.
> [...] so I have connectivity and also can access a web page on the
> 4000 from inside the 192.168.xxx.xxx domain so the httpd.conf file is
> set properly and the httpd deamon is running. How can I accomplish
> accessing web pages from outside?
You can't. See point 1.
Chris
| |
| gerryt 2007-10-03, 1:24 pm |
| On Oct 3, 6:04 am, Chris Davies <chris-use...@roaima.co.uk> wrote:
> jim.sheph...@gmail.com wrote:
>
> Those two statements are mutually exclusive: if it's unroutable then by
> definition it can't be reachable from "the outside".
192.160 is routable
> Assuming it really is routable and you really can get at it from "the
> outside2, you're going to be in for a bit of a shock if you expect it
> to remain undiscovered for long.
> Then it's not on an unroutable address.
Indeed and port 22 is perhaps wide open and presumeably all others.
Definitely an inconsistent lead in here by the OP
> You can't. See point 1.
Hard to tell exactly what the OP is up to but usage of ipfilter rules
on port 80
might do the trick or a
Order deny,allow
Deny from all
Allow from somewhere somewhere_else
set of rules perhaps. ipfilter is probably best as its one change in
one place...
But the way the post is worded it sounds like either there are 2 NICs
or its
some kind of logical interface config. Try again OP
> Chris
| |
| I R A Darth Aggie 2007-10-03, 7:18 pm |
| On Wed, 03 Oct 2007 09:10:30 -0700,
gerryt <lepsysinc@gmail.com>, in
<1191427830.715710.123080@r29g2000hsg.googlegroups.com> wrote:
>+ On Oct 3, 6:04 am, Chris Davies <chris-use...@roaima.co.uk> wrote:
>+ > jim.sheph...@gmail.com wrote:
>+ > > My Apache server (a Sun Enerprise 4000) is behind a DSL modem with an
>+ > > unroutable DHCP assigned address (192.160.xxx.xxx) and I would like to
>+ > Those two statements are mutually exclusive: if it's unroutable then by
>+ > definition it can't be reachable from "the outside".
>+
>+ 192.160 is routable
I think the OP meant the 192.168. unroutable subnet, which is
typically what a DSL modem will assign.
One may think of the DSL modem as a sort of router. It will probably
have to be configured correctly to pass thru port 80 (or 443 or
whatever) requests to the machine running apache.
Depending on the modem's setup, the OP merely needs to point a browser
at http://192.168.0.1/ or similar.
--
Consulting Minister for Consultants, DNRC
I can please only one person per day. Today is not your day. Tomorrow
isn't looking good, either.
I am BOFH. Resistance is futile. Your network will be assimilated.
| |
| Chris Davies 2007-10-04, 1:22 pm |
| gerryt <lepsysinc@gmail.com> wrote:
> 192.160 is routable
No it's not, as it's not been assigned:
$ whois 192.160.0.0
No match found for 192.160.0.0.
# ARIN WHOIS database, last updated 2007-10-03 19:10
Chris
| |
| Chris Davies 2007-10-04, 1:22 pm |
| jim.sheph...@gmail.com wrote:
> My Apache server (a Sun Enerprise 4000) is behind a DSL modem with an
> unroutable DHCP assigned address (192.160.xxx.xxx) and I would like to
On Oct 3, 6:04 am, Chris Davies <chris-use...@roaima.co.uk> wrote:
> Those two statements are mutually exclusive: if it's unroutable then by
> definition it can't be reachable from "the outside".
I R A Darth Aggie <n0b0dy@192.168.10.10> wrote:
> I think the OP meant the 192.168. unroutable subnet, which is
> typically what a DSL modem will assign.
Ah, so the 192.160 wasn't assigned /to/ the DSL router-modem, it was
the internal subnet assigned /by/ the DSL router-modem? That's a big
difference.
Let's wait and see how the OP clarifies this. If they don't then they're
clearly not interested in our help.
Chris
| |
| gerryt 2007-10-05, 1:21 am |
| On Oct 4, 8:53 am, Chris Davies <chris-use...@roaima.co.uk> wrote:
> gerryt <lepsys...@gmail.com> wrote:
> No it's not, as it's not been assigned:
> $ whois 192.160.0.0
> No match found for 192.160.0.0.
> # ARIN WHOIS database, last updated 2007-10-03 19:10
Thats what I thought at first. But I got 50+ answers for
whois *192.160 it quit after 50 as whois is wont to do.
One of which talks merrily away to Mozilla : >
|
|
|
|
|