Date: Mon, 18 Apr 2011 15:26:52 -0700 From: Garrett Cooper <yanegomi@gmail.com> To: Maxim Sobolev <sobomax@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, Gleb Smirnoff <glebius@freebsd.org>, src-committers@freebsd.org Subject: Re: svn commit: r220736 - head/sbin/natd Message-ID: <BANLkTi=mCdmg9Hi-qfENdc90vKXNP=aDww@mail.gmail.com> In-Reply-To: <4DACB0C3.6000804@FreeBSD.org> References: <201104170605.p3H65cab028890@svn.freebsd.org> <20110418181314.GL16958@FreeBSD.org> <4DACB0C3.6000804@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2011/4/18 Maxim Sobolev <sobomax@freebsd.org>: > 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. I've seen the problem that you've attempted to fix here before at home, and it actually occurred between 8.1 and 8.2. I merely hacked things to work at home in the rc script because I didn't want to muck around with natd's C sources. > 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. If it does this when backgrounded, that seems ok. If it blocks foregrounded like this, that's not acceptable. Thanks, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTi=mCdmg9Hi-qfENdc90vKXNP=aDww>