From owner-freebsd-questions Wed Dec 6 6:36:44 2000 From owner-freebsd-questions@FreeBSD.ORG Wed Dec 6 06:36:42 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from d9168.upc-d.chello.nl (d9168.upc-d.chello.nl [213.46.9.168]) by hub.freebsd.org (Postfix) with ESMTP id CF4D237B400 for ; Wed, 6 Dec 2000 06:36:41 -0800 (PST) Received: by d9168.upc-d.chello.nl (Postfix, from userid 1001) id E0DFE313; Wed, 6 Dec 2000 15:36:40 +0100 (CET) Date: Wed, 6 Dec 2000 15:36:40 +0100 From: Edwin Groothuis To: Jim Freeze Cc: freebsd-questions@freebsd.org Subject: Re: Can no longer ssh Message-ID: <20001206153640.D32018@d9168.upc-d.chello.nl> Mail-Followup-To: Edwin Groothuis , Jim Freeze , freebsd-questions@freebsd.org References: <20001206150418.B32018@d9168.upc-d.chello.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jim@freeze.org on Wed, Dec 06, 2000 at 09:25:29AM -0500 Sender: edwin@d9168.upc-d.chello.nl Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 06, 2000 at 09:25:29AM -0500, Jim Freeze wrote: > On Wed, 6 Dec 2000, Edwin Groothuis wrote: > > > I'm interested in the other lines. :-) euh, if you add the first line again, which made it impossible for you to ssh to the machine, then "ipfw zero" to get rid of everything and then try to login again, that is when there is usefull information in this list. Then we can also have a look at /var/log/security which tells you which packets are being blocked. Edwin -- Edwin Groothuis | Fatal Dimensions: mavetju@chello.nl | http://fataldimensions.nl.eu.org/ ------------------+ telnet://fataldimensions.nl.eu.org:4000 Trenton@FinalFantasy: y r all fucken coders wierd and negative except me? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message