From owner-freebsd-current@FreeBSD.ORG Tue Jun 7 17:29:18 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 6D3DF1065677; Tue, 7 Jun 2011 17:29:18 +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 E85468FC25; Tue, 7 Jun 2011 17:29:17 +0000 (UTC) Received: by vws18 with SMTP id 18so5326621vws.13 for ; Tue, 07 Jun 2011 10:29:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=VtZJIvVhof0DxTTYHt8SykkuB6fau9qe7o3OA8z+yzk=; b=gFtXIhUOIRgsPBOCY4Bcq9p7wAuocOd3YWX2KGK1QH3lQxbA8AhhVaaZhU5ZfCmsoM QoFG+b4lNqU22SOb7dTwcYstPSV3gi21ujA8DjFeuX1ttXBesxwgNS40NMdb9QdK8jhl 6MiKbaXpMh7f8eSXUcP1SzDJr1mf9fArqyVrs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=rAyy07qmE6H1lZ/ZVULocEoC3iQ41adlFouyZCaj5B9FnT5c26ocVP+TmW0zDoSUoH MBf3aW3tMGLXL4JTFTzxXXlAuA/2FQdaqRjUz/xsj4VzydosMyV+Glpdw9NGHqGHft3H /uKuGTaMGOzoyx4KKj4pDAGzhGr2A7+omojb0= MIME-Version: 1.0 Received: by 10.220.213.195 with SMTP id gx3mr1187226vcb.23.1307467757039; Tue, 07 Jun 2011 10:29:17 -0700 (PDT) Received: by 10.220.189.202 with HTTP; Tue, 7 Jun 2011 10:29:17 -0700 (PDT) Date: Tue, 7 Jun 2011 10:29:17 -0700 Message-ID: From: Garrett Cooper To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 Cc: "Bjoern A. Zeeb" Subject: 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 17:29:18 -0000 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 # This unfortunately also breaks 'dhclient re0' (in my case) as it calls ifconfig. Inserting some printfs in link_getaddr it looks like it's trying to test something incorrectly: # ifconfig re0 inet 192.168.20.3 which: 1, ADDR: 1 which: 3, ADDR: 1 ifconfig: can't set link-level netmask or broadcast # Attaching gdb to the process (because the link_getaddr functions are function pointers and I wanted to remove all obscurity), the failing call is originating from setifdstaddr. The abbreviated stack trace is: - af_link.c:77 - ifconfig.c:773 - ifconfig.c:579 - ifconfig.c:346 The actual line count in af_link.c is going to be fuzzed by 2 because of the printf I added. 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). I have both INET and INET6 built into my kernel and userland, but my immediate upstream router only supports IPv4 right now. I tried building with WITHOUT_INET6=yes to see if it made a difference, and it didn't. I'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 :). Thanks, -Garrett