From owner-freebsd-net@freebsd.org Wed Jan 6 03:19:18 2021 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4FE5A4DB83A for ; Wed, 6 Jan 2021 03:19:18 +0000 (UTC) (envelope-from vas@sibptus.ru) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4D9ZN51JVmz4Yv5 for ; Wed, 6 Jan 2021 03:19:16 +0000 (UTC) (envelope-from vas@sibptus.ru) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=I2uCPKXI05/mpC9SMm/8mohVLX6SFEAc5alLMshZFhw=; b=bmv8UgajFDG+SnuBvyejBX3m0i JTx0loQiwBXborc0ZoRKeefk40MLDA+Pp0zP7iscc8NSEgELec51ykFy5akuK+00ROf2HKgnSCmY9 r2Ev9/uhSLad5QxmW97lL3lDogLnJbl0Hqivk3XhcSO0vmxvxPylmAujN5HX3fulfZOA=; Received: from vas by admin.sibptus.ru with local (Exim 4.94 (FreeBSD)) (envelope-from ) id 1kwzLp-000AMW-42 for freebsd-net@freebsd.org; Wed, 06 Jan 2021 10:19:09 +0700 Date: Wed, 6 Jan 2021 10:19:09 +0700 From: Victor Sudakov To: freebsd-net@freebsd.org Subject: Re: FreeBSD does not reply to IPv6 Neighbor SolicitationsNUD Message-ID: <20210106031909.GA39200@admin.sibptus.ru> References: <00d901d6e382$5c3db590$14b920b0$@donnerhacke.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline In-Reply-To: <00d901d6e382$5c3db590$14b920b0$@donnerhacke.de> X-PGP-Key: http://admin.sibptus.ru/~vas/ X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 X-Rspamd-Queue-Id: 4D9ZN51JVmz4Yv5 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=sibptus.ru header.s=20181118 header.b=bmv8Ugaj; dmarc=pass (policy=none) header.from=sibptus.ru; spf=pass (mx1.freebsd.org: domain of vas@sibptus.ru designates 2001:19f0:5001:21dc::10 as permitted sender) smtp.mailfrom=vas@sibptus.ru X-Spamd-Result: default: False [-6.10 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:19f0:5001:21dc::10:from]; R_DKIM_ALLOW(-0.20)[sibptus.ru:s=20181118]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2001:19f0:5001:21dc::10:from:127.0.2.255]; DKIM_TRACE(0.00)[sibptus.ru:+]; DMARC_POLICY_ALLOW(-0.50)[sibptus.ru,none]; NEURAL_HAM_SHORT(-1.00)[-0.999]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:5000::/38, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-net] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.34 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, 06 Jan 2021 03:19:18 -0000 --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Lutz Donnerhacke wrote: > > $ ifconfig re1 > > re1: flags=3D8843 metric 0 mtu = 1500 > > > options=3D8209b NKSTATE> > > ether c4:12:f5:33:c9:7c > > inet 192.168.170.5/24 broadcast 192.168.170.255 > > inet6 fe80::c612:f5ff:fe33:c97c%re1/64 scopeid 0x2 > > inet6 2001:470:ecba:3::5/64 > > media: Ethernet autoselect (1000baseT ) > > status: active > > nd6 options=3D21 >=20 > There is another possibility: The address could be in a tentative or > duplicate state. > In such a state the device SHOULD/MUST NOT respond to solicitation messag= es. >=20 > This can be caused by a "proxy arp/nd" device, which responds to an addre= ss > in > the local neighbour cache with its own solication message. It might be ev= en > a loop. > We had such cases in the past, so that the device does not activate the I= Pv6 > address without disabling the NUD (was a windows server). For fixed > addresses it > should be save to disable the flag. >=20 > But this state should be reported by ifconfig. I expect it should. >=20 > So, did you try the latest stable? Not yet.=20 When the situation occurs again, I'll turn on net.inet6.icmp6.nd6_debug=3D0xff as Bjoern A. Zeeb has suggested, maybe I'll see something useful. Then I'll think of updating the system. --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJf9SwtAAoJEA2k8lmbXsY0VTUIAKOdNyw0ZAby8jPwvOUMmdCg ICCChOz1PjorVJZiNtf3yGWitswYjXu5kNo60wrltr4LC1XWdICKgKTOUkAuDNPb WDHp7GqtPz2maoFPZOPQsL3M6fLXiO8YLDy9Y7PCIga6uKhMjPGBMnWZnT0+BZ5T 4UiJw5HTLsc0amR+ykIdOe7vzQ0STB5mckq6i8JYKCr6XD4Vl08ZJSTcB3GbIEiG SzCeGTzgrotDx7ED13oUS/0exsPuRM2jTOvnZ3BUx3wDrCd9wTgiZXcWznBS8Yyi ep5KMubXvNcjKQVT+ljay8UNyKhjVsJgJQCAeNEETiZA4pQYpJlBAHXmk9xvJuA= =GiMJ -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV--