Date: 07 Sep 2001 02:16:59 -0400 From: Arcady Genkin <antipode@thpoon.com> To: freebsd-questions@freebsd.org Cc: chat@gtabug.org Subject: Routing / NAT / Apache question Message-ID: <87vgivttic.fsf@tea.thpoon.com>
next in thread | raw e-mail | index | archive | help
Symptom: sometimes can't connect to HTTP server from the local
machines, while it works fine for clients from the outside.
I have the following network topology of three computers:
SOUP:192.168.1.1 -----|
Apache |---- ROUND:192.168.1.4
| 24.42.106.79 ----- Internet
TEA:192.168.1.2 -----| IPNAT,IPF,Port forward
Netscape
ROUND is the gateway for the local computers, and also forwards port
80 from the outside interface to port 80 on SOUP, where Apache runs.
The boxes are interconnected network via a switch on the internal
network.
I cannot browse my HTTP server when I address it by a name which
resolves to the external IP (i.e. when the packets travel through the
router and are then port-forwarded), but can browse it just fine if I
refer to it by its internal name (i.e. `soup').
The problem persisted after I flushed all IPF rules on the firewall.
Neither am I seeing any dropped packages logged with the firewall
active. This makes me think that this is related to routing or NAT.
Adding the external names to /etc/hosts works for *some* software
(Mozilla, Netscape), but not other (lynx, w3m).
Any ideas on how to fight this problem highly appreciated.
Many thanks,
--
Arcady Genkin
i=1; while 1, hilb(i); i=i+1; end
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87vgivttic.fsf>