Date: Wed, 8 Jun 2011 18:59:12 +0400 From: Eir Nym <eirnym@gmail.com> To: Garrett Cooper <yanegomi@gmail.com> Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: IPv4 broken on r222048 Message-ID: <BANLkTinvHNdbh2UOe4jLb_9mYbqLMJztww@mail.gmail.com> In-Reply-To: <BANLkTinCZqZrWBPZZsieoC26fB5w0oJgHg@mail.gmail.com> References: <BANLkTinWSP0ko69qi9Qca7O2=LRpSn19yw@mail.gmail.com> <6D37AF86-9C14-4824-96CA-55C86497DECD@lists.zabbadoz.net> <BANLkTi=PXebdMw9X7=WJ4ygZ6iom=TDJhA@mail.gmail.com> <BANLkTinCZqZrWBPZZsieoC26fB5w0oJgHg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7 June 2011 22:11, Garrett Cooper <yanegomi@gmail.com> wrote: > On Tue, Jun 7, 2011 at 11:00 AM, Garrett Cooper <yanegomi@gmail.com> wrot= e: >> On Tue, Jun 7, 2011 at 10:41 AM, Bjoern A. Zeeb >> <bzeeb-lists@lists.zabbadoz.net> 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= " >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTinvHNdbh2UOe4jLb_9mYbqLMJztww>