From owner-freebsd-net@FreeBSD.ORG Wed Mar 13 13:38:18 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A3DF855A for ; Wed, 13 Mar 2013 13:38:18 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 3F90C39C for ; Wed, 13 Mar 2013 13:38:18 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id u54so1007514wey.16 for ; Wed, 13 Mar 2013 06:38:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=CEwJGXZbrnIV+8vmR6ObVc8fi2sk2FxukgeLGSPciCM=; b=M5a8YkMRtylV4L4jwmI6tmXHpuQU45O/67SocvxdOw2aj/nLBCEYV9CWv182wEYH17 lDIQwOPakRQQeEBkDAzDcv4o6ZliXVy7hMBXtQA/M7e2iAO6ZUCPcC3Yiu/O0ktLiF5Q oabpIqnGBcw4ld2Kp43iQy2BEsimfBDB3blY/Hz0gx4OOmA4M29pyhTgR7v2OYuA7Gw+ saWMpKurP5T7gyXtE7ZAFEGbBci3fWQZ7VOL22YOQduQK9kUHSQrDTwI5D+m2/KgYZEg 7UgW56xvlsUK7VSfcTaZ/JLU38hOhP2qQYRGTkxEdvGTsKuUSJ7ksYx/PAqhBdz0SyWI gFuQ== X-Received: by 10.180.104.225 with SMTP id gh1mr26749657wib.27.1363181897122; Wed, 13 Mar 2013 06:38:17 -0700 (PDT) Received: from dfleuriot-at-hi-media.com ([83.167.62.196]) by mx.google.com with ESMTPS id j4sm2800228wiz.10.2013.03.13.06.38.14 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Mar 2013 06:38:15 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: ntpd bind() failure: Can't assign requested address From: Fleuriot Damien In-Reply-To: <76E2EE0D-B6D3-428E-9112-AF0E04E98DDE@my.gd> Date: Wed, 13 Mar 2013 14:38:12 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <76E2EE0D-B6D3-428E-9112-AF0E04E98DDE@my.gd> To: "M. Schulte" X-Mailer: Apple Mail (2.1499) X-Gm-Message-State: ALoCoQktQXxlf50UCZ/4u0lLr/VzbI4/ZCntMKvIQaU2o3moiUlVlEWQ2X3SoZa6wcxNkOZsill8 Cc: "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 13:38:18 -0000 On Mar 12, 2013, at 11:44 PM, Damien Fleuriot wrote: >=20 > On 12 Mar 2013, at 22:42, "M. Schulte" wrote: >=20 >> Hi! >>=20 >> [First of all, I have posted this question already on the FreeBSD >> forum -- so far without replies -- and now my hope is that the set of >> subscribers here and those of the forum do not completely coincide.] >>=20 >> I have installed FreeBSD 9.1 on my server (it's a virtualized = qemu/kvm >> environment, in case that matters) and during boot the following >> messages appear: >>=20 >> ntpd[766]: ntpd 4.2.4p5-a (1) >> ntpd[767]: bind() fd 23, family AF_INET6, port 123, scope 2, addr = fe80::216:36ff:fe74:2076, mcast=3D0 flags=3D0x11 fails: Can't assign = requested address >> ntpd[767]: unable to create socket on re0 (3) for = fe80::216:36ff:fe74:2076#123 >>=20 >> This happens with a GENERIC kernel. I have not touched any IPv6 >> related configuration after install, so everything should be in the >> default state. Neither have I changed the ntp/ntpd configuration. >>=20 >> Although I could find some threads where people were discussing the >> same problem, none of the mentioned suggestions fixed this for me. >>=20 >> In particular I tried setting >>=20 >> ipv6_activate_all_interfaces=3D"YES" >>=20 >> in rc.conf -- didn't fix the problem. >>=20 >> According to ifconfig, my interfaces, re0 in particular, have IPv6 >> addresses associated to them. So why would it fail that a process >> tries to bind to it? Note that I'm rather unexperienced wrt IPv6. >>=20 >> Would be great if somebody could give me a hint into the right >> direction. Anybody else experiencing this? Thank you very much! >>=20 >> ~ melanie >>=20 >=20 > I'll check tomorrow if we have the same issue at work, although it = doesn't look familiar. >=20 > We've got a 9.1 with a custom kernel (although nothing related to ipv6 = changed) running in KVM. I confirm I have the same issue on 9.1 r247912 , as below: Clearing /tmp (X related). Updating motd:. Starting ntpd. Mar 8 14:57:23 pf1-drt ntpd[938]: bind() fd 23, family AF_INET6, port = 123, scope 2, addr fe80::90bd:54ff:fe55:2d21, mcast=3D0 flags=3D0x11 = fails: Can't assign requested address Mar 8 14:57:23 pf1-drt ntpd[938]: unable to create socket on vlan12 (3) = for fe80::90bd:54ff:fe55:2d21#123 However, ntpd runs fine and is bound to the following addresses: root@pf1-drt:/var/run # sockstat | grep ntp root ntpd 938 3 dgram -> /var/run/logpriv root ntpd 938 20 udp4 *:123 *:* root ntpd 938 21 udp6 *:123 *:* root ntpd 938 22 udp4 195.158.240.37:123 *:* root ntpd 938 23 udp4 192.168.32.253:123 *:* root ntpd 938 24 udp6 fe80:3::a8b0:eeff:fef9:dbb:123 *:* root ntpd 938 25 udp4 192.168.22.254:123 *:* root ntpd 938 26 udp6 fe80:4::6820:e3ff:fe0b:76dc:123 *:* root ntpd 938 27 udp6 ::1:123 *:* root ntpd 938 28 udp6 fe80:7::1:123 *:* root ntpd 938 29 udp4 127.0.0.1:123 *:* root ntpd 938 31 udp6 fe80:2::90bd:54ff:fe55:2d21:123 *:* root ntpd 938 32 udp4 192.168.22.253:123 *:*