From owner-freebsd-security Tue Mar 28 4:38:55 2000 Delivered-To: freebsd-security@freebsd.org Received: from ns1.via-net-works.net.ar (ns1.via-net-works.net.ar [200.10.100.10]) by hub.freebsd.org (Postfix) with ESMTP id CA87237BE30 for ; Tue, 28 Mar 2000 04:38:30 -0800 (PST) (envelope-from fpscha@ns1.via-net-works.net.ar) Received: (from fpscha@localhost) by ns1.via-net-works.net.ar (8.9.3/8.9.3) id JAA07237; Tue, 28 Mar 2000 09:38:37 -0300 (GMT) From: Fernando Schapachnik Message-Id: <200003281238.JAA07237@ns1.via-net-works.net.ar> Subject: Re: natd question In-Reply-To: from "owner-freebsd-security@FreeBSD.ORG" at "Mar 27, 0 09:45:43 pm" To: vikashb@my-Deja.com Date: Tue, 28 Mar 2000 09:38:37 -0300 (GMT) Cc: freebsd-security@FreeBSD.ORG Reply-To: Fernando Schapachnik X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You might want to tcpdump each interface to see what kind of traffic is being generated. Also, make sure your firewall rules aren't dropping the packets (figuring the right rules is sometimes very tricky). I have had success in the past using redirect_port tcp internal_address Regards. En un mensaje anterior, owner-freebsd-security@FreeBSD.ORG escribió: > Greetings > > Could some one please assist me with a natd configuration ? [...] > Fernando P. Schapachnik Administración de la red VIA NET.WORKS ARGENTINA S.A. fernando@via-net-works.net.ar (54-11) 4323-3333 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message