From owner-freebsd-questions@FreeBSD.ORG Tue Jun 21 07:33:13 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 6638C16A41C for ; Tue, 21 Jun 2005 07:33:13 +0000 (GMT) (envelope-from casey@phantombsd.org) Received: from phantombsd.org (dsl231-036-158.sea1.dsl.speakeasy.net [216.231.36.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30DC043D1D for ; Tue, 21 Jun 2005 07:33:13 +0000 (GMT) (envelope-from casey@phantombsd.org) Received: by phantombsd.org (Postfix, from userid 1004) id 810C4102EA7; Tue, 21 Jun 2005 00:33:12 -0700 (PDT) Received: from tomcat.phantombsd.org (tomcat.phantombsd.org [192.168.1.6]) by phantombsd.org (Postfix) with ESMTP id 60615102D50; Tue, 21 Jun 2005 00:33:12 -0700 (PDT) From: Casey Scott To: freebsd-questions@freebsd.org, philip@xms.co.za Date: Tue, 21 Jun 2005 00:33:12 -0700 User-Agent: KMail/1.6.2 References: <1119369916.4660.14.camel@linux.site> In-Reply-To: <1119369916.4660.14.camel@linux.site> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200506210033.12163.casey@phantombsd.org> X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on eagle.phantombsd.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=ALL_TRUSTED,HOT_NASTY autolearn=failed version=3.0.4 Cc: Subject: Re: Sshd problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2005 07:33:13 -0000 Unfortunately, sshd remains bound to the IP it had when it started. This isn't an issue with FBSD, but with OpenSSH. I see this all the time on other UNIX/Linux boxes. A possible solution to it in the future would be to issue a HUP to sshd using "nohup". e.g. root@host# nohup ifconfig xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx; killall -HUP sshd Hope that helps Casey On Tuesday 21 June 2005 09:05 am, Philip Wege wrote: > Things like Allow root login and all that was set because ssh was used > just after the ip change did this happen.