From nobody Sun Aug 24 01:31:22 2025 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 4c8bxJ3dvLz64nnk for ; Sun, 24 Aug 2025 01:31:32 +0000 (UTC) (envelope-from rtyler@brokenco.de) Received: from mail-4317.protonmail.ch (mail-4317.protonmail.ch [185.70.43.17]) (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 (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4c8bxJ0tc4z3Lnv for ; Sun, 24 Aug 2025 01:31:32 +0000 (UTC) (envelope-from rtyler@brokenco.de) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brokenco.de; s=protonmail; t=1755999088; x=1756258288; bh=o6gvyjTeii1pCsLFeGboA/KGIkWQhKh4gRhIUKtbnKQ=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=hvbGGmOI4LEjCVV90bhVBKW336BX8VhulSM07YwNPVGUr7DtEnJTkOHmA6A9R6o08 McfVaYXTPhXUXg25BIO9Cy959SSOm5OoonREJLm69W68me5dIW32YTTx6IVz3p65K4 oaIYAAjapOwfBYAn78WNG5PgkqTCjJw9lMWU/bSE= Date: Sun, 24 Aug 2025 01:31:22 +0000 To: Karl Denninger From: R Tyler Croy Cc: freebsd-net@freebsd.org Subject: Re: Intermittent failure of routing/gateway with ix(4) (x86_64) Message-ID: In-Reply-To: <7f463f6f-3a6e-47db-aab8-7817cc6192a5@denninger.net> References: <6HcKz3OxJSnjZdoCr4I0mksk9RemKJflHVgnkYI8-FydM4mDDldzTm8qthQ0iJCftaETOVeQFde4fz5i1703B8Gd2ZBvPmBwF_MMnhuJ8VM=@brokenco.de> <7f463f6f-3a6e-47db-aab8-7817cc6192a5@denninger.net> Feedback-ID: 10207728:user:proton X-Pm-Message-ID: 9e5cf09b546d485f699686fcb773c90a97cfceef 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 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha512; boundary="------f5ba06684df0306e797ff4a9009042ba07ea6efda4ecedbc63fd468d9124a2e7"; charset=utf-8 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4c8bxJ0tc4z3Lnv This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------f5ba06684df0306e797ff4a9009042ba07ea6efda4ecedbc63fd468d9124a2e7 Content-Type: multipart/mixed;boundary=---------------------a04c6e9136ce2b66f1571cc84f03ebed -----------------------a04c6e9136ce2b66f1571cc84f03ebed Content-Transfer-Encoding: quoted-printable Content-Type: text/plain;charset=utf-8 (replies inline) On Saturday, August 23rd, 2025 at 6:24 PM, Karl Denninger wrote: > = > What physical hardware is on that driver? > = > I have a box here with two ix interfaces in it that is my edge router an= d beat the SNOT out of it without problems. This is what the boot messages= are for them in my machine here: These are both identical 10GigE NICs, from dmesg ix0: mem 0xe0400000-0xe05fffff,0xe0600000-0xe0603fff i= rq 18 at device 0.0 on pci1 ix0: Using 2048 TX descriptors and 2048 RX descriptors ix0: Using 2 RX queues 2 TX queues ix0: Using MSI-X interrupts with 3 vectors ix0: allocated for 2 queues ix0: allocated for 2 rx queues ix0: Ethernet address: a0:36:9f:38:44:a8 ix0: PCI Express Bus: Speed 5.0GT/s Width x8 ix0: fw 4.2.0 nvm 4.03.0 eTrack 0x8000037c ix0: netmap queues/slots: TX 2/2048, RX 2/2048 System: FreeBSD 14.2-RELEASE-p4 When I was chasing that arpresolve warning I saw in the console, I did see= some discussion like this (https://be-virtual.net/pfsense-arpresolve-cant= -allocate-llinfo-for-x-x-x-x-on-emx/) about funky routers on the other end= of the link causing trouble. Since this is a newer fiber rollout from my = local ISP (Sonic) I wouldn't be surprised if there was something funky hap= pening there. Since the LAN-side routing goes haywire, I'm thinking that's= a red herring. Cheers -----------------------a04c6e9136ce2b66f1571cc84f03ebed-- --------f5ba06684df0306e797ff4a9009042ba07ea6efda4ecedbc63fd468d9124a2e7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: ProtonMail wsG5BAEBCgBtBYJoqmtaCZDqliUJ0zoEdUUUAAAAAAAcACBzYWx0QG5vdGF0 aW9ucy5vcGVucGdwanMub3JnJlbGHI6RL3umHsmzoiPMyBXPpNjIh4F3eLvy pjKRj6gWIQR7rUKRWE2z4+Kwj8/qliUJ0zoEdQAAnTcP/AkN6JRdVv8eHAHM NKRpLvPMtqOrmAl+r0vaSvFEN9cJ1/uXcK+uJE6/DmJoGixeqZc7R+S8oTRp BJRoeQTsA1dEAw7O5O1bmKbYKzVKLb2Hhm+lOI9WeISMF+IBzs9rNB0dvgwP Au/a9Xuu/1jRCwcZhi5IBJIO0LrhVKv2NpkUKZTUZaEwTvAP/ZNXPKNQL8Nz 07SLEIsm6+ws14mfmv6Js53T3eXK1KDz1FpbOtHyN0Rm/3vN5LX6tuThQ08S Q/dHrb9guD+n66haQntfxL6qQVQA0sf1CXzOz3ApvtMf8hATNy9Fw7u3C+NP 7837v3E6Qa5OiS5eFkkGqeiQ+w8pe/flnOIUYKiZ/93Xn3J4cP7W4oq5b87o xVsQU9HwWF1QK2UC7etgGbld3cwkCAVfMZsFDQgKWkXw04QKVXsvKUbd3xFP 08G7plvogO65E+4SJnjkTXdsdtyH1M7SEBaz28anGN4wdqePuia6SfzxZ/Mu g3oSjZro0orpMzvSMYHDIzs0pIWsKBs1RhwzyNaufafSlwFB20eXuO6dp3C7 lvslFAUhtSalcqU9XLo8i2EtDQjIUVh0ZH6On3d6KuhmHSLQKC3/dRT4GpiM B2RiwcbZkRInyx7FqTwFrzTrquq0Dbr6wV7AUT1djyMaK1y+1CYXAzYuac1c zmKHwkXq =UOVL -----END PGP SIGNATURE----- --------f5ba06684df0306e797ff4a9009042ba07ea6efda4ecedbc63fd468d9124a2e7--