From owner-freebsd-current@FreeBSD.ORG Tue Jun 7 18:11:11 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 7B5EE106566B; Tue, 7 Jun 2011 18:11:11 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1271B8FC16; Tue, 7 Jun 2011 18:11:10 +0000 (UTC) Received: by vxc34 with SMTP id 34so5400493vxc.13 for ; Tue, 07 Jun 2011 11:11:10 -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=iZbAAn+5QeLOegf9WnXc4bf0z/buWH9SBTVkXssIHro=; b=GTn/q/iadPq196QnnOSFbU+G1uZYoRIRiOfsd75HZH4TmxL2RPVpFZwPA64F/FB1ES w0/pC9S/6pzTgJ0gAK3kUYMlHsl0BtvPYv+ncAK2gv3JlyM3S++Ww5sbUXAl956OJymD Ze7Iuo6Qlwb3eS3X6gJIkVYFyGTvwJ1/YNTUY= 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=w2Bq2cD2iEm5plsWI4p9+VmucgITHGZUpz/iWBZAhFCguG7HDZW/KmYKUrHN/h0FMd vvbgtGLSxMhskQIKY6YKP4w6Q9x2ILcemgrQvByF96n6jEdZPDSW+a6fSFakkdGLKmJV /EdWPSiiRiz1KwowVuPjAXmwjB8Yp6ZU3EpYs= MIME-Version: 1.0 Received: by 10.220.177.9 with SMTP id bg9mr278342vcb.93.1307470270016; Tue, 07 Jun 2011 11:11:10 -0700 (PDT) Received: by 10.220.189.202 with HTTP; Tue, 7 Jun 2011 11:11:09 -0700 (PDT) In-Reply-To: References: <6D37AF86-9C14-4824-96CA-55C86497DECD@lists.zabbadoz.net> Date: Tue, 7 Jun 2011 11:11:09 -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:11:11 -0000 On Tue, Jun 7, 2011 at 11:00 AM, 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 properl= y, >>> 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 t= he >>> 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 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.. > > Is there a tool I can use (minus banging on the interfaces in C) to > determine what the features are on the machine to diagnose why things > aren't working for me? Answering my own question: sysctl kern.features.inet sysctl kern.features.inet6 Hmmm... they turn up unknown OIDs. Need to do some digging to discover why that's the case.. >> You need an old user land or a new kernel to recover. > > Looks like I need an old userland, because a new kernel/userland combo > doesn't seem to work as advertised :/... > >>> =A0 =A0I have both INET and INET6 built into my kernel and userland, bu= t >>> my immediate upstream router only supports IPv4 right now. I tried >>> building with WITHOUT_INET6=3Dyes to see if it made a difference, and i= t >>> didn't. >>> =A0 =A0I'll test any patches needed to remedy the issue. Thankfully I >>> have flash media I can use in the meantime to push code between my two >>> boxes :) >> >> Welcome to FreeBSD HEAD, being a developer and not following the rule;-) >> >> Sorry for the hassle though. > > It's ok -- that's why I have two near workstations -- one for daily > use and the other for testing :). Thanks, -Garrett