From owner-freebsd-questions Tue Mar 5 14: 3:24 2002 Delivered-To: freebsd-questions@freebsd.org Received: from dns1.digitalglobe.com (dns1.digitalglobe.com [205.166.175.34]) by hub.freebsd.org (Postfix) with ESMTP id 9FE8837B400 for ; Tue, 5 Mar 2002 14:03:16 -0800 (PST) Received: from lohr.digitalglobe.com (lohr.digitalglobe.com [10.10.11.18]) by dns1.digitalglobe.com (8.11.6/8.11.4) with ESMTP id g25M3Bv55518; Tue, 5 Mar 2002 15:03:11 -0700 (MST) Subject: Re: Wierd network issues on LAN - hard to describe From: John-David Childs To: Scott Stevens Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <006301c1c388$05d7ec90$6401a8c0@tenchi> References: <006301c1c388$05d7ec90$6401a8c0@tenchi> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2-4mdk Date: 05 Mar 2002 15:03:11 -0700 Message-Id: <1015365791.14114.73.camel@lohr> Mime-Version: 1.0 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I had a situation at one of my employers where I *can't* (administratively) resolve DNS (forward or reverse) for internal hosts (yeah, I could always set up a separate DMZ/outside DNS...which is in the works), and adding an entry to /etc/hosts is completely unfeasible. The solution, therefore, was to add entries in /etc/hosts.allow for those services which depend on DNS lookups (and which are linked with the tcpwrapper library). In addition, the version of OpenSSH distributed with 4.5-RELEASE (2.9p2, I believe), does NOT honor the "ReverseMappingCheck off" directive in /etc/ssh/sshd_config...I had to install 3.0.2 from the ports. For small networks, /etc/hosts is the way to go...for larger networks, using tcpwrapper's /etc/hosts.{allow,deny} and service configuration files is the better thing to do. On Mon, 2002-03-04 at 07:22, Scott Stevens wrote: > I've recently started having some interesting network issues with my machine > and was hoping someone here could help me out. > > I'm having trouble connecting to my machine running FreeBSD from any of the > other machines on my lan (2 win2k machines and an Ibook). When I use telnet > or ftp, the connection takes an obscene amount of time to connect, I would > probably say almost 2 minutes and ssh and pop3 won't connect at all. Other > things like web traffic and connecting to my shoutcast streams works fine. > If I connect to the machine from anywhere outside my LAN, say from work or a > friends house, everything works properly. > > My lan is set up as such; I have adsl which comes in via a Cisco 675, that > is fed into a Linksys Cable/DSL router and then pushed out to each of the > machines. At first I thought something was wonky with the linksys router so > I double checked the port forwarding setup and then ultimately removed it > from the mix all together when the problem didn't go away. Then I switched > out network cards thinking the card might have gone bad (it was pretty old > and needed to be swapped for a 10/100 anyway). Currently there is a Linksys > LNE100TX (v5.1) in the machine, but that didn't seem to make any difference > either. > > This problem just came out of the blue the other day and I have no idea > what's up. Any ideas? Keep in mind the problem is only on my local network, > everything works 100% if I connect to the machine from the outside. > > thanks in advance, > scott. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message