From owner-freebsd-current@FreeBSD.ORG Wed Jun 8 14:59:34 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 D5CA4106564A for ; Wed, 8 Jun 2011 14:59:34 +0000 (UTC) (envelope-from eirnym@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 601D08FC19 for ; Wed, 8 Jun 2011 14:59:33 +0000 (UTC) Received: by bwz12 with SMTP id 12so719429bwz.13 for ; Wed, 08 Jun 2011 07:59:33 -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:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=YWgJ1xpRHTWZiQ5pjWqZcV+LFTb4bx8mDJcmQO5dZes=; b=YX97Uq4jerkQo53eFS26M9m6fgk+iJK/DrpxU2Ia/kyULOAVoy5DTMAh65jxfs7Z/W fGIiPXI11yFo7hGcWpnjhb+2XqGsW1IZrkwDgoUIuysa2FtxNftjSLz8fWO4UZ5u8LaK NP7iMtzE5zYWK4M3VHxNeqwlnBZulgSDCTROo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=U01r5UG+A6lgnWLB+vqizWOusdQAygT/Q+GrMcL4gO8OGAOKvRBRsdfhP0WqVoCrdZ 1IOd6lqobl8KzKGIIT+b0U6HRGojwrzUa0FbrWn/RzZlvHh5YPRMOyKRJbKPIzn7Mh02 rETi1eNTcoya2OFnTHUCsJcn4jP4Lh5X/Oy1g= Received: by 10.204.36.7 with SMTP id r7mr698588bkd.2.1307545173142; Wed, 08 Jun 2011 07:59:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.15.74 with HTTP; Wed, 8 Jun 2011 07:59:12 -0700 (PDT) In-Reply-To: References: <6D37AF86-9C14-4824-96CA-55C86497DECD@lists.zabbadoz.net> From: Eir Nym Date: Wed, 8 Jun 2011 18:59:12 +0400 Message-ID: To: Garrett Cooper Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "Bjoern A. Zeeb" , 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: Wed, 08 Jun 2011 14:59:35 -0000 On 7 June 2011 22:11, Garrett Cooper wrote: > On Tue, Jun 7, 2011 at 11:00 AM, Garrett Cooper wrot= e: >> 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, >>>> =C2=A0 =C2=A0I'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 >>>> # >>> ... >>>> =C2=A0 =C2=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. =C2=A0My changes did that. =C2=A0You are the second to h= it it. >>> Your kernel does not have "FEATURES()" =C2=A0present and the new user s= pace >>> 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.. > Oh... And no UPDATING messages. It's bad practice for this features. >>> 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 :/... >> >>>> =C2=A0 =C2=A0I have both INET and INET6 built into my kernel and userl= and, but >>>> my immediate upstream router only supports IPv4 right now. I tried >>>> building with WITHOUT_INET6=3Dyes to see if it made a difference, and = it >>>> didn't. >>>> =C2=A0 =C2=A0I'll test any patches needed to remedy the issue. Thankfu= lly 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 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " >