Date: Sat, 21 Aug 1999 18:41:03 -0400 (EDT) From: Alfred Perlstein <bright@rush.net> To: Roy Bettle <rbettle@criterion-group.com> Cc: "Questions List FreeBSD.org" <freebsd-questions@FreeBSD.ORG> Subject: Re: Resolving NT machine names with NAT Message-ID: <Pine.BSF.3.96.990821184033.20420V-100000@cygnus.rush.net> In-Reply-To: <37BE3E4A.5342BE91@criterion-group.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 20 Aug 1999, Roy Bettle wrote:
> Good evening. We have a Cox Communications cable modem. They use the
> @Home Network. We would like to setup NAT so that both our machines can
> go out. We have tried to use Linux RedHat 6.0 but have not been able to
> get IPMasq to resolve the Windows NT Server host names (we use a static
> IP address, but the @Home Network apparently manages itself with Windows
> NT Server and NT DHCP). This is apparently a known problem with
> IPMasq. Does this problem exists with NAT as well? If so, can we get
> around it? If so, how (URL to help us out perhaps?)?
>
> Thank you for your help!
From the natd manpage: (man natd)
-dynamic If the -n or -interface option is used, natd will monitor the
routing socket for alterations to the interface passed. If
the interfaces IP number is changed, natd will dynamically
alter its concept of the alias address.
good luck,
-Alfred
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?Pine.BSF.3.96.990821184033.20420V-100000>