From owner-freebsd-questions@FreeBSD.ORG Fri May 14 07:43:09 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C60DF16A4CE for ; Fri, 14 May 2004 07:43:09 -0700 (PDT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D66343D2D for ; Fri, 14 May 2004 07:43:09 -0700 (PDT) (envelope-from johnmills@speakeasy.net) Received: (qmail 22525 invoked from network); 14 May 2004 13:33:45 -0000 Received: from dsl027-162-100.atl1.dsl.speakeasy.net (HELO otter.localdomain) ([216.27.162.100]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 May 2004 13:33:45 -0000 Received: from localhost (jmills@localhost) by otter.localdomain (8.11.6/8.11.6) with ESMTP id i4EDXkd09421; Fri, 14 May 2004 13:33:46 GMT X-Authentication-Warning: otter.localdomain: jmills owned process doing -bs Date: Fri, 14 May 2004 08:33:46 -0500 (EST) From: John Mills X-X-Sender: jmills@otter.localdomain To: FreeBSD-questions In-Reply-To: <16548.42814.515842.247302@hyde.home.loc> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "Walter C. Pelissero" Subject: Re: Dlink DSL router doesn't like FreeBSD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John Mills List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 May 2004 14:43:09 -0000 Walter - On Fri, 14 May 2004, Walter C. Pelissero wrote: > My problem is that ssh and telnet don't work. I get as far as the > Password prompt, I type it in, and then ssh freezes for a couple of > minutes until it probably goes in timeout and gives up. Before we blame the router, a little more information would be good. First, are you coming into your LAN from outside, or going outwards? If it's an outgoing-connection problem, I would look into the firewall setting of the FBSD box. Maybe you set didn't set it up to pass the ports for outgoing telnet and ssh, or maybe you shut off the replies on those same ports. As for the timeout - many ssh setups will attempt to confirm the incoming connection, and many clients come from unconfirmable IP addresses. This usually involves a timeout of a few tens of seconds, but not terminating the connection. On the other hand, if you are discarding reply packets, I would expect the remote server to timeout awaiting your response to its acknowledgement. Second, if incoming, does your DSL account have a static IP address? Does your FBSD box have a static address within your LAN? You need these in order to route to your [FBSD] server. Are you running 'sshd' and 'telnetd' in the FBSD box to accept incoming connections? Try plugging the WindowBox into another of the router's ports, then use PuTTY to telnet and ssh into your FBSD box (using it's LAN address, naturally). If that works, the problem is definitely the router, but possibly a setup issue. Especially since telnet is also involved. (Many people disable incoming telnet, for security reasons.) When you have intra-LAN access working, look into port forwarding in the router's setup: you want incoming traffic from the ports used by ssh and (if you enable it) telnet to be sent to the LAN address of your FBSD box. Knowing what you are looking for may help you find it in the manuals. PuTTY's control panel to set up a connection shows you the default 'telnet' and 'ssh' ports if you are in doubt. My experience with the D-Link router has been outgoing and setting up a local WindowBox with a static IP (so it could server as a printer for the LAN). Keep us posted. Tschuess. - John Mills john.m.mills@alum.mit.edu