Date: Mon, 19 Feb 2001 16:41:25 +1300 From: James Grant <jamesg@xtra.co.nz> To: freebsd-questions@freebsd.org Subject: natd won't redirect ports. Message-ID: <20010219164125.A1234@cyclone.h1>
next in thread | raw e-mail | index | archive | help
Hi,
I've set ipfw and natd up on my firewall machine which has a dial on demand ppp
connection using a dynamic ip. Everything works fine, except for this
problem I'm having with natd. It just seems to ignore the fact I've told it
to redirect a port.
Say for example I start natd with the following command line (just for
debugging purposes):
/sbin/natd -n tun0 -dynamic -same_ports -use_sockets -redirect_port tcp
192.168.1.3:6699 6699 -v
The output pertaining to a connection to port 6699 looks like this:
In [TCP] [TCP] 202.49.64.124:3433 -> 210.55.82.216:6699 aliased to
[TCP] 202.49.64.124:3433 -> 210.55.82.216:6699
Out [TCP] [TCP] 210.55.82.216:6699 -> 202.49.64.124:3433 aliased to
[TCP] 210.55.82.216:6699 -> 202.49.64.124:3433
It doesn't redirect it at all!! Hence my napster client just sits there
waiting for a connection.
But if I specify firewall machine's internet address on the command line
like so:
/sbin/natd -n tun0 -dynamic -same_ports -use_sockets -redirect_port tcp
192.168.1.3:6699 210.55.82.216:6699 -v
... and I get the following output:
In [TCP] [TCP] 202.49.64.124:3450 -> 210.55.82.216:6699 aliased to
[TCP] 202.49.64.124:3450 -> 192.168.1.3:6699
Out [TCP] [TCP] 192.168.1.3:6699 -> 202.49.64.124:3450 aliased to
[TCP] 210.55.82.216:6699 -> 202.49.64.124:3450
and so it works if I specify the IP on the command line, but that isn't
really useful for dial on demand with a dynamic IP.
Ideas anyone?
--
James.
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?20010219164125.A1234>