From owner-freebsd-net Mon Jul 24 7: 9: 4 2000 Delivered-To: freebsd-net@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 9BB1E37B914 for ; Mon, 24 Jul 2000 07:09:00 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id IAA80971; Mon, 24 Jul 2000 08:08:49 -0600 (MDT) Date: Mon, 24 Jul 2000 08:08:49 -0600 (MDT) From: Nick Rogness To: "Roberto Nunnari, AGIE" Cc: net@freebsd.org Subject: Re: gateway strange behaviour for telnet and ftp In-Reply-To: <397C340E.98B471AA@agie.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 24 Jul 2000, Roberto Nunnari, AGIE wrote: > > Here's the network configuration: > - host1 192.168.1.1 gateway to my isp > - host2 192.168.1.2 workstation > - host3 192.168.1.3 workstation > - host4 192.168.1.4 workstation > > host1 also acts as a master DNS for the local network > > other host have host1 as the default router and DNS. > > all workstation can reach each other and also access the > internet through host1 > > Every thing works just marveillous until I try to > telnet or ftp or nfs host1 from any other host on the local > network. Here, the initiating host don't get a login prompt > until host1 has made a connection to the isp. This is DNS related. More than likely, it is trying to do a reverse lookup on your 192.168.1.0/24 network hosts. Add that network's IN_ADDR_ARPA in your name server (host1), add corresponding A pointers as well for all host on the local network. Nick Rogness - Drive defensively. Buy a tank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message