From nobody Sun Sep 14 18:12:44 2025 X-Original-To: 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 4cPx8r0Ljbz67F6G for ; Sun, 14 Sep 2025 18:12:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 "mxrelay.nyi.freebsd.org", Issuer "R12" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4cPx8q6lsZz3hp7 for ; Sun, 14 Sep 2025 18:12:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1757873564; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=qK6coIKQmoO+33jG9S7nReq/SeHq2/R6X35OQdAOAtE=; b=cWYWoOzkGTTa1ZVX3eqt0AAW9dhoFiESe/HHWCMawAVt3BOfIhxuW5w4RON6WaPRUUo9Rt M0f3tt0PdK2Be3fa43wUcysN3iN4liwTrp8fNVSh5XIzQiz5Y8/wBhtRusUDEL82VtyTc6 WdQtLzN/cCVNxWpeqDT6obF/KIy0O0hwAksgL3h2ZJr2W8aqNrfodsREAeCXVYltHMmzMm YlNmwJd9vMFA9Oq8DIBolLjHc2vfNrrj07xfjwnlFuqiT00PmX2PzYRYkLEu4GgpqGklKy uCXLmx3DcBUcq2qbdnHwRsGTF+Q8v71jeYIn4Uw/DQKi8gE2aq4bEWNJR6kFyQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1757873564; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=qK6coIKQmoO+33jG9S7nReq/SeHq2/R6X35OQdAOAtE=; b=PRRutOCaRVtOxlCxd4BdQ3ijVLr1Dm1JttXD1Ou7eH6BwqdJE8fjPwpmT+Crsgwdja7T3g VgGlO0y/aOj1nloBbx6mT2JrKlkMbV35opZOeE4jS98WOQYBkzA+gEEzko428RugCs+kvH xFgWO20uMrLSyVUBPgg98NIawtUrdhYZqleU8j71wmCWcnzbXx6E+/oMvkQ+HbEuYe9HBN BqVnLBdZEJyh9g2OpSwq8cdXk6C1DQZezd82hCUqoX26T2UXRQzWbwM6x8DOnvwQW+es8w /POt2cfsD9VPT3/37G+XNuQC+Bgpz/fTIWSmtjnVI4oWK+SnT7Jr6EzaYV7PZQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1757873564; a=rsa-sha256; cv=none; b=EVxsmG2TKw9XwSkZsFagFGJHpRWp4JoIye87RsoAObkcXuM9hL/h8FATub+bhMAmzDno4h vIqJJmoYbOGJzTGfVqs13kd6lW1HpL2cSq6mf+aP7dFJ+o+Vgb/mVT9ylZj9qnygEuX+Yv hxEZAmHsEhjOF+57BvpXjG85+JwedHSXYNNzueEAKwjlx0E6ntW8Ufz6nIcSqjLcT7+fqP ViMyOwGL0TotNADdgxXFWUMviM6oBm99c0OZlSai3RVg/bTE7ujyQ0DqJSbQA1VjXD2wGx OJYwha2PtTtBA0baUIS8LJKDNZ1cij4Qye9a4lVQtIOXFF1BrAFZ6sDLXVDNOQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4cPx8q68YQz4Qq for ; Sun, 14 Sep 2025 18:12:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 58EIChd6006598 for ; Sun, 14 Sep 2025 18:12:43 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 58EIChgQ006597 for net@FreeBSD.org; Sun, 14 Sep 2025 18:12:43 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 289545] No option to disable NOMAP leads to network down/up with em0 when starting bridge. Date: Sun, 14 Sep 2025 18:12:44 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.5-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: bicknell@ufp.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D289545 --- Comment #3 from Leo Bicknell --- I think saying "the bug" is a bit ambiguous. There appear to be multiple components to this problem: #1 Some Intel NICs drop link when particular capabilities are changed, like hardware offload. I have never seen clear documentation if this is a probl= em with the FreeBSD driver, or if this is firmware inside the NIC that is the responsibility of Intel. The attitude in several bug reports is "that's ju= st the way it is with those NICs", but no one has ever documented WHY in any of the posts I have seen. #2 When a bridge is brought up it has to force all component interfaces to = have the same set of capabilities. It appears in older code this was not documented, but somewhere along the way was documented and is now spelled o= ut in the man 4 bridge page. While the paragraph is clear, I suspect many peo= ple would not understand the implications from just reading the man page.=20=20 #3 A workaround for the combination of #1 and #2 is to manually disable the capabilities on one or more interfaces so that when the bridge starts up everything matches and the bridge code does not need to change them. This seems like a mostly reasonable workaround to me, and was the one I was tryi= ng to implement. It was in the process of implementing that I found this capability "NOMAP" which there appears to be no cli way to turn off, appear= s to be virtually undocumented, but which bridge must turn off, which means the entire workaround does not work. #4 An unstated workaround is to replace the Intel card with a non-Intel NIC that does not have this problem. In this bug report my main goal is to get an argument to ifconfig to disable "NOMAP" so the workaround is a functional workaround again. That would mak= e me happy. However I can see how other people would prefer that #1 be fixed, either by fixing the FreeBSD driver or by getting Intel to fix their card.= =20 Given Intel generally produces high quality NIC cards that people like I can see how getting it fixed could be a priority for some. --=20 You are receiving this mail because: You are the assignee for the bug.=