From owner-freebsd-questions Mon Nov 22 2: 9:18 1999 Delivered-To: freebsd-questions@freebsd.org Received: from server4.mpcbbs.com.br (server4.mpc.com.br [200.246.0.252]) by hub.freebsd.org (Postfix) with ESMTP id A07BF14DFD for ; Mon, 22 Nov 1999 02:08:54 -0800 (PST) (envelope-from capriotti@geocities.com) Received: from bb3ce4 (d2p148.mpcnet.com.br [200.246.29.122]) by server4.mpcbbs.com.br (8.8.8/8.8.6) with SMTP id IAA03265; Mon, 22 Nov 1999 08:06:32 -0200 (EDT) Message-Id: <3.0.6.32.19991122080622.0096fb40@pop.mpcnet.com.br> X-Sender: capriotti@pop.mpcnet.com.br X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 22 Nov 1999 08:06:22 -0200 To: freebsd-questions@FreeBSD.ORG From: Capriotti Subject: NATd and diverting a port Cc: capriotti@geocities.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, all. We had to remove the NT security hole from its "gateway" position on the network, for obvious questions. Of course, iin its place wwe installed FreeBSD 3.3-Release. Problem is that, to keep things going, w/o too much effort for local sysadmins, the email still has to be handled by the NT box. Not a big deal. Problem is: address 206.1.1.1, which was the gateway's, is now the FBSD's. Email server was responding to 206.1.1.1 I was trying to use NATd to forward any traffic to ports 25 and 110 to the NT box like this: (called from .../rc.d/nats.sh during boot) natd -n ed1 -redirect_port 192.16.1.100:25 25 natd -n ed1 -redirect_port 192.16.1.100:110 110 Of course all the requirements to run NATd - kernel, etc - were followed. Sometimes, when using trafshow to see what is going on, I can see packets being diverted, but the target machine does not reply at all. Repeating the experience in the lab, w/ 3 computers, I did: server 192.168.1.100 running qpopper server 192.168.1.153 running natd -n ed1 -redirect_port 192.16.1.100:110 110 machine 192.168.1.152 running win95 and Eudora, checking email from 192.168.1.153 Still not working. What is wrong here ? What is the correct way of doing this w/ NATd ? Is there any other way to handle this packet divertion ? Please, include me in your CC list, for faster feedback. Thank you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message