Stop me as soon as I say something that's not accurate.
Okay... so there are three subnets here.
66.x.x.x
[Cayman]
192.168.1.0
[dual-homed host which houses web server]
192.168.2.0
...right?
The DSL router knows about (connects to) 66.x.x.x and 192.168.1.0;
The dual-homed server knows about 192.168.1.0 and 192.168.2.0, and also
is the machine which houses the web daemon.
At this point I think we can safely ignore anything under 192.168.2.0 for
the time being. The Cayman can't see that network directly, so trying to
route packets from the Cayman to the ..2.0 network isn't going to work.
So now I'd like to know if it's possible for a machine on the 192.168.1.0
net to see your web server.
Try this -- on the dual-homed host, take down the interface that touches
192.168.2.0, then try to browse to 192.168.1.10:80 from that system itself
or from another system on the same subnet if there is one.
If you get web pages then we know that Apache is actually serving http to
that network. If not, then you know that you have an Apache problem and not
(exactly) a networking problem.
If I read your setup correctly, you don't actually need to do any port
forwarding at all on the dual-homed system. You just want the httpd process
to be available on the NIC that serves the 192.168.1.0 subnet, so you can
point the Cayman at it.
I suspect that Apache is only binding to the 192.168.2.0 subnet for some
reason.
On Tue, Sep 19, 2000 at 10:01:08AM -0500, Stephen E. Hargrove wrote:
> Sorry for the confusing info in my original post. Let my try to clarify
> based on the questions received.
>
> "Michael R. Jinks" wrote:
> >
> > Does the DSL modem have two associated IP's as well -- 192.168.1.254 and
> > also the 66.x.x.x address you mention below?
>
>
> 192.168.1.254 is the internal IP address of the DSL modem. 66.x.x.x is
> the IP address assigned to the connection between my ISP and the DSL
> modem.
>
> > Are the "internal network" and "connects to DSL" addresses above both residing
> > on one system? (that's what I assume but you don't say explicitly)
>
> Yes.
>
>
> > So in English, you're forwarding 66.x.x.x:80 on the Cayman to either
> > 192.168.2.1:80 or 192.168.1.10:80 on your internal system?
>
> Yes.
>
> > About the internal system -- does it pass those packets on to some other
> > machine, or does it house the web daemon itself? At this point I'm a little
> > confused about your network topology.
>
> The machine has two NICs:
>
> 192.168.1.10 connects to the DSL modem.
> 192.168.2.1 connects to the internal network.
>
> This machine houses the the web daemon.
>
> > The "outside network" in this sentence is The Internet? Or a DMZ between
> > your "home" network and the outside?
>
> Yes. Any connection made from outside my internal network, i.e.,
> someone trying to access Apache from the Internet.
>
>
> > How are 192.168.1.0 and 192.168.2.0 connected?
>
> I don't understand this question.
>
> >
> > > I'm specifically requesting
> > > http://66.xxx.xxx.xxx/index.html, which does exist.
> > >
> > > - If I configure Apache to listen to 192.168.1.10:80, the system responds
> > > that the website is unreachable.
> >
> > Which system?
>
> That's the response received when trying to access the webserver from
> the Internet (i.e., from outside the internal network - from home,
> another office, etc.).
>
>
> > > I'm using IP Masquerade to mask all traffic on the internal network out
> > > through 192.168.1.10 and the router.
> >
> > _and_ the router? Please explain what that means.
>
> Internal requests for external resources route out 192.168.1.10, which
> is connected to the DSL router, which is connected to the Internet.
>
> > Which network -- 192.168.2.0 or 192.168.1.0 -- do you mean by the "internal"
> > network?
>
> 192.168.2.0 is the internal network.
> 192.168.1.0 houses the NIC connecting to the DSL router (192.168.1.10)
> and the DSL router (192.168.1.254).
>
>
> > I think what would help me the most is if you could describe your network
> > layout a little more -- specifically, where does the web server live, how many
> > machines are actually involved, and which network addresses reside where?
>
>
> 192.168.2.1 is a NIC on the server.
> 192.168.2.2 is a workstation.
> 192.168.2.6 is a workstation.
> etc.
>
> 192.168.1.10 is a NIC on the same server previously mentioned.
> 192.168.1.254 is the DSL router. The router connects to 192.168.1.10
> and the Internet.
>
>
> 192.168.2.2---|-----------| |--------------|
> 192.168.2.6---|Server |192.168.1.10| DSL router | 66.x.x.x
> 192.168.2.8---|192.168.2.1|----eth1----| 192.168.1.254|-------------
> Internet
> 192.168.2.9---|___eth0____| |______________|
>
>
> I hope this helps. If I can provide further info, please let me know.
>
> --
> Steve
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
--
Michael Jinks, IB
Systems Administrator, CCCP
finger [EMAIL PROTECTED] for public key
Vote Duke! http://www.entertaindom.com/pages/duke2000/home.jsp
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
