From owner-freebsd-questions Sat Aug 21 15:33: 2 1999 Delivered-To: freebsd-questions@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 442C114D11 for ; Sat, 21 Aug 1999 15:32:50 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id SAA09589; Sat, 21 Aug 1999 18:41:05 -0400 (EDT) Date: Sat, 21 Aug 1999 18:41:03 -0400 (EDT) From: Alfred Perlstein To: Roy Bettle Cc: "Questions List FreeBSD.org" Subject: Re: Resolving NT machine names with NAT In-Reply-To: <37BE3E4A.5342BE91@criterion-group.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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