From nobody Mon Mar 9 15:16:58 2026 X-Original-To: freebsd-arm@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 4fV0sK2c75z6VsW3 for ; Mon, 09 Mar 2026 15:13:57 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "pelorus.zefox.org", Issuer "pelorus.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4fV0sG5Vqjz4LS0; Mon, 09 Mar 2026 15:13:54 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.18.1/8.18.1) with ESMTPS id 629FGxqv062284 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 9 Mar 2026 08:16:59 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.18.1/8.18.1/Submit) id 629FGxt6062283; Mon, 9 Mar 2026 08:16:59 -0700 (PDT) (envelope-from fbsd) Date: Mon, 9 Mar 2026 08:16:58 -0700 From: bob prohaska To: Adrian Chadd Cc: Mark Millard , freebsd-arm@freebsd.org Subject: Re: -current network buffer exhaustion on RPi2 armv7 Message-ID: References: <0b6093e0-400c-4e0d-a674-d7b425e7a910@yahoo.com> <5860d6e0-4961-4725-be71-26769bab9d90@yahoo.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-1.10 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.996]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_WWW(0.50)[]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_TLS_LAST(0.00)[]; MISSING_XM_UA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; R_DKIM_NA(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_CC(0.00)[yahoo.com,freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DMARC_NA(0.00)[zefox.net]; RCPT_COUNT_THREE(0.00)[3] X-Rspamd-Queue-Id: 4fV0sG5Vqjz4LS0 X-Spamd-Bar: - On Sun, Feb 22, 2026 at 09:41:41AM -0800, Adrian Chadd wrote: > I'm telling ya, it's dhclient, trying to send frames when the > interface is up but encryption isn't finished negotiating. It appears that leaving a ping session running with an interval of ten seconds somehow suppresses the network connection drop and wpa_cli chatter. There's a steady stream of "group rekeying" messages, but nothing suggesting an error and the link stays up. Could there be an inactivity timeout that's getting into trouble? Certainly not a fix, but useful as a workaround for now. If this suggests any further experiments I'd be glad to try them. Thanks for reading, bob prohaska