Date: Mon, 22 Nov 1999 08:06:22 -0200 From: Capriotti <capriotti@geocities.com> To: freebsd-questions@FreeBSD.ORG Cc: capriotti@geocities.com Subject: NATd and diverting a port Message-ID: <3.0.6.32.19991122080622.0096fb40@pop.mpcnet.com.br>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.6.32.19991122080622.0096fb40>