From owner-freebsd-current@FreeBSD.ORG Tue Jun 7 18:15:08 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10CD01065679 for ; Tue, 7 Jun 2011 18:15:08 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id AE84F8FC24 for ; Tue, 7 Jun 2011 18:15:07 +0000 (UTC) Received: by vws18 with SMTP id 18so5378567vws.13 for ; Tue, 07 Jun 2011 11:15:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=0yFnMHdKt3wYFLuBWNHAyXeduKMnt8kpYgyhfTJ4a30=; b=OhnX+LU74erXDQ/K/P6wPotJLkiLUbW8tfDkQEaJfrDdr39y1AoG/vpuecy6d9YvpD a9aFMMRljykApZY8lvIwkHUHzFXinWmk91FSNt//+ZRavL6TwzPj0BNC0uUljJGiCmR/ dGNt2LDByLjd06iXPOLvbr7Y15lfNGNZI/Dp4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=bHLF8nuwi1BEmIy9goQH8atPWoyO0w2xStBblOoNLY+scBo2nJpq1NRrk4ix1lp7x5 KzZg69x4kC5CS+QmyPv/cWhERsb5oZ2jfLK/BYFbqddfyJfB3Of+TYiMLiADehhn0RgQ sixCnpnomI5YN8e7Ny1ivjDpyyYe0JfI8Ayl8= MIME-Version: 1.0 Received: by 10.220.177.9 with SMTP id bg9mr279920vcb.93.1307470506330; Tue, 07 Jun 2011 11:15:06 -0700 (PDT) Received: by 10.220.189.202 with HTTP; Tue, 7 Jun 2011 11:15:06 -0700 (PDT) In-Reply-To: <4434466E-F4B0-47B1-98BF-80E4E495AA4C@lists.zabbadoz.net> References: <6D37AF86-9C14-4824-96CA-55C86497DECD@lists.zabbadoz.net> <4434466E-F4B0-47B1-98BF-80E4E495AA4C@lists.zabbadoz.net> Date: Tue, 7 Jun 2011 11:15:06 -0700 Message-ID: From: Garrett Cooper To: "Bjoern A. Zeeb" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Current Subject: Re: IPv4 broken on r222048 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2011 18:15:08 -0000 On Tue, Jun 7, 2011 at 11:13 AM, Bjoern A. Zeeb wrote: > On Jun 7, 2011, at 6:00 PM, Garrett Cooper wrote: > >> On Tue, Jun 7, 2011 at 10:41 AM, Bjoern A. Zeeb >> wrote: >>> >>> On Jun 7, 2011, at 5:29 PM, Garrett Cooper wrote: >>> >>>> Hi, >>>> =A0 =A0I'm running into an issue where ifconfig isn't executing proper= ly, >>>> and is emitting the following message: >>>> >>>> # ifconfig re0 inet w.x.y.z >>>> ifconfig: can't set link-level netmask or broadcast >>>> # >>> ... >>>> =A0 =A0I haven't traced down what commit exactly is causing this, but = the >>>> issue appears to be a purely userland based problem so far (I >>>> accidentally forgot to swap kernels before booting up the second time >>>> and the symptoms are exactly the same). >>> >>> Yes, you lost. =A0My changes did that. =A0You are the second to hit it. >>> Your kernel does not have "FEATURES()" =A0present and the new user spac= e >>> that came a couple of days later expect it and disable your IPv4 >>> because of that. >>> >>> The real problem is when people update the kernel, then update world >>> and then figure out they need to go back to kernel.old. >>> I'll add an UPDATING entry. >> >> That I would expect, but I just built the kernel last night, installed >> it, and am running it right now and I run into the same issue as I do >> with the older kernel :). Was there any magic foo that I needed to use >> to get FEATURES working properly, or was it supposed to be seamless? I >> don't know because I never had a need to fiddle around with the >> framework.. > > It's supposed to be seamless. =A0Can you check if you have the following = two? > sysctl kern.features.inet > sysctl kern.features.inet6 > > >> Looks like I need an old userland, because a new kernel/userland combo >> doesn't seem to work as advertised :/... > > I think I just found a good "recovery" idea -- I should disable the > features with rescue builds. =A0That should give one a working > /rescue/ifconfig in all cases and should be sufficient to recover? That would be a good backup plan so people could at least avoid painting themselves into a corner by accident. Thanks! -Garrett