From owner-freebsd-current@FreeBSD.ORG Tue Jun 7 18:13:21 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 B501C106564A for ; Tue, 7 Jun 2011 18:13:21 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) by mx1.freebsd.org (Postfix) with ESMTP id 6BC528FC16 for ; Tue, 7 Jun 2011 18:13:21 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 9B27B25D3870; Tue, 7 Jun 2011 18:13:20 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id D6B5515A130C; Tue, 7 Jun 2011 18:13:19 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id 2aGV81ZLqE7w; Tue, 7 Jun 2011 18:13:18 +0000 (UTC) Received: from orange-en1.sbone.de (orange-en1.sbone.de [IPv6:fde9:577b:c1a9:31:cabc:c8ff:fecf:e8e3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 37E2015A12F8; Tue, 7 Jun 2011 18:13:18 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "Bjoern A. Zeeb" In-Reply-To: Date: Tue, 7 Jun 2011 18:13:16 +0000 Content-Transfer-Encoding: 7bit Message-Id: <4434466E-F4B0-47B1-98BF-80E4E495AA4C@lists.zabbadoz.net> References: <6D37AF86-9C14-4824-96CA-55C86497DECD@lists.zabbadoz.net> To: Garrett Cooper X-Mailer: Apple Mail (2.1084) 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:13:21 -0000 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, >>> I'm running into an issue where ifconfig isn't executing properly, >>> and is emitting the following message: >>> >>> # ifconfig re0 inet w.x.y.z >>> ifconfig: can't set link-level netmask or broadcast >>> # >> ... >>> I 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. My changes did that. You are the second to hit it. >> Your kernel does not have "FEATURES()" present and the new user space >> 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. Can 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. That should give one a working /rescue/ifconfig in all cases and should be sufficient to recover? Bjoern -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family.