From nobody Mon Aug 21 08:46:57 2023 X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RTmLb2W7yz4qT0g for ; Mon, 21 Aug 2023 08:47:03 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward502c.mail.yandex.net (forward502c.mail.yandex.net [178.154.239.210]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4RTmLZ0Z48z4F3b for ; Mon, 21 Aug 2023 08:47:01 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yandex.ru header.s=mail header.b=I+gaODyH; spf=pass (mx1.freebsd.org: domain of bu7cher@yandex.ru designates 178.154.239.210 as permitted sender) smtp.mailfrom=bu7cher@yandex.ru; dmarc=pass (policy=none) header.from=yandex.ru Received: from mail-nwsmtp-smtp-production-main-39.myt.yp-c.yandex.net (mail-nwsmtp-smtp-production-main-39.myt.yp-c.yandex.net [IPv6:2a02:6b8:c12:2891:0:640:3c15:0]) by forward502c.mail.yandex.net (Yandex) with ESMTP id E9A105E854 for ; Mon, 21 Aug 2023 11:46:58 +0300 (MSK) Received: by mail-nwsmtp-smtp-production-main-39.myt.yp-c.yandex.net (smtp/Yandex) with ESMTPSA id vkDDsNcWrOs0-dpAh0yr4; Mon, 21 Aug 2023 11:46:58 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1692607618; bh=1AUgL/SoMv5jws9a+4s0oL4ID34qYxvFrvSlWVod7d0=; h=In-Reply-To:Subject:From:Date:References:To:Message-ID; b=I+gaODyHI2l8L6a3KfgAoZ2nT+Fqalc9RXdhcadmKeJUA5ZGmIix5GRZeO/7OkJog 9nl6GuB6VbX1hUVeWmQw5iWzbN5GdP4RR/27aSv0N/xOMUYG/fP7bX4MF7Ivnq7QrC cQOGbJxq56pgTNoswmnhk47YwF5e/Jkmv6Q45NSw= Message-ID: <4ce02d1b-3a27-1910-a9f6-2fc2938bc04d@yandex.ru> Date: Mon, 21 Aug 2023 11:46:57 +0300 List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.14.0 Content-Language: ru, en-US To: freebsd-net@freebsd.org References: <503561ece3e7201318c298c2d5b91eb5@mail.yourbox.net> From: "Andrey V. Elsukov" Subject: Re: em0: No buffer space available for IPv6 traffic but IPv4 is OK In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-4.30 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[yandex.ru,none]; R_SPF_ALLOW(-0.20)[+ip4:178.154.239.208/28]; R_DKIM_ALLOW(-0.20)[yandex.ru:s=mail]; RWL_MAILSPIKE_VERYGOOD(-0.20)[178.154.239.210:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[2a02:6b8:c12:2891:0:640:3c15:0:received]; RCPT_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-net@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-net@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DWL_DNSWL_NONE(0.00)[yandex.ru:dkim]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[yandex.ru:+]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[yandex.ru]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[yandex.ru]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:200350, ipnet:178.154.224.0/19, country:RU]; RCVD_COUNT_TWO(0.00)[2] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4RTmLZ0Z48z4F3b On 19.08.2023 00:54, Kevin Oberman wrote: > Interestingly, there is incoming IPv6 local broadcast traffic as > sniffed > by > # tcpdump -n -i em0 ip6 > (ICMP6, neighbor solicitation, UDP from LAN link local addresses). > > Has anyone seen this before and can suggest a fix? > > Reboot did not solve, no software updates made, no config changes, just > stop working from one day to the next. > > Oddly, ENOBUFS is the error I get when my firewall is blocking transmit > traffic. There may well be other causes. Yes, network stack returns this error usually when it is unable to send data. And this could be due to many different causes. First of check that prefixes and masks are correctly configured. Then check that your IPv6 default gateway is directly reachable and its layer 2 address is known. Also you can check `netstat -s` to find what counter grows when you try to use IPv6. Make sure your firewall doesn't block ICMPv6 types needed for IPv6 to work. Check that multicast functions correctly. # ifconfig # ndp -an # netstat -s # ifmstat -- WBR, Andrey V. Elsukov