From owner-svn-src-head@FreeBSD.ORG Mon Apr 18 22:04:48 2011 Return-Path: Delivered-To: svn-src-head@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CF63106566C; Mon, 18 Apr 2011 22:04:48 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail.sippysoft.com (mail.sippysoft.com [4.59.13.245]) by mx1.freebsd.org (Postfix) with ESMTP id 12CD48FC13; Mon, 18 Apr 2011 22:04:47 +0000 (UTC) Received: from [4.59.13.245] (helo=[192.168.1.79]) by mail.sippysoft.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QBwFI-00085T-5P; Mon, 18 Apr 2011 14:44:36 -0700 Message-ID: <4DACB0C3.6000804@FreeBSD.org> Date: Mon, 18 Apr 2011 14:44:35 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: Gleb Smirnoff References: <201104170605.p3H65cab028890@svn.freebsd.org> <20110418181314.GL16958@FreeBSD.org> In-Reply-To: <20110418181314.GL16958@FreeBSD.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Sender: sobomax@sippysoft.com X-ssp-trusted: yes Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: svn commit: r220736 - head/sbin/natd X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2011 22:04:48 -0000 On 4/18/2011 11:13 AM, Gleb Smirnoff wrote: > This looks like a hack and better place for this hack would be shell > scripts rather than nat daemon. Well, I am not sure how would you apply shell script in such case. The problem with the original code is that natd just silently exits, leaving machine without a network connection. For some reason this problem started after upgrade from 7.4 to 8.2, perhaps there is some changes in the dhclient which allows it to run is parallel with other start-up activity. And I don't see any problem with natd waiting indefinitely on the interface to acquire IP address, it's no better and no worse than the current behavior when the natd simply bails out. -Maxim