RE: Setting up a LAN to use DSL....

["Dale W Hodge" <dwh@neuralmatrix.org>]

> -----Original Message-----
> From: linux-admin-owner@vger.kernel.org
> [mailto:linux-admin-owner@vger.kernel.org]On Behalf Of Phillp Morgan

> btw: The apache server has been running at all times. This is what the
> problem is. No one can connect to it.
>
> I put "220-224.1.95.61.in-addr-arpa..." in named.conf, and changed the PTR
> records in the reverse lookup file. This made no difference.
>
> I still cannot access the web sites from either internally or externally.
> nslookup still complains it can't resolve the names, though now it fails
> instantly whereas befoer it took two full minutes.
>
> I don't have a subnet. The ISP, who are being particularly uncooperative,
> have given me 4 IP addresses 61.95.1.220 to 61.95.1.223. The first for the
> router, and the other three for each of the servers. As per rc.inet1 the
> actual machine IP is a 192.168.0.0/255.255.255.0 network.
>
> Remember, the router is supposedly handling rotuing between public and
> private IP addresses.

If it is indeed handing the public/private translation, your public
addresses likely stop at the router. It's unlikely that you can route the
additonal address through the router and still have it provide NAT. My
suggestion would be to turn off NAT, route the public address to your Linux
boxes, and have them provide NAT to your internal network.  If you are
paranoid, then you can use a separate firewall box or hardware firewall for
your internal network.

--dwh

---
Dale W Hodge - dwh@neuralmatrix.org
Vice Chairman & Secretary - info@aclug.org
Air Capital Linux User's Group  (ACLUG)
---