From owner-freebsd-net@freebsd.org Mon Oct 16 10:16:18 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05577E355D5 for ; Mon, 16 Oct 2017 10:16:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 E761C75BFF for ; Mon, 16 Oct 2017 10:16:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GAGHlt029244 for ; Mon, 16 Oct 2017 10:16:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attatching vxlan interfaces to a bridge stops all traffic on it Date: Mon, 16 Oct 2017 10:16:18 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mav@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 10:16:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 Alexander Motin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mav@FreeBSD.org --- Comment #1 from Alexander Motin --- I've tried to reproduce this, and all I see is an uplink interface flap for several seconds due to bridge need to disable/restore of interface offload flags. After NIC reinitialize the link, operation is restored. Do I repro= duce your issue, or you mean something different? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 10:54:34 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9FA8E364C8 for ; Mon, 16 Oct 2017 10:54:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 AB58A76F94 for ; Mon, 16 Oct 2017 10:54:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GAsYD6032774 for ; Mon, 16 Oct 2017 10:54:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attatching vxlan interfaces to a bridge stops all traffic on it Date: Mon, 16 Oct 2017 10:54:34 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: heinz@project-fifo.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 10:54:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 --- Comment #2 from Heinz N. Gies --- Hi, first of all, thanks for looking into this! It does sound like an explanation for what I'm seeing. I sadly know little about the internals of= the network stack, but the symptoms seem to fit. Adding an interface leads to a reproducible drop of connectivity/delay for a few seconds. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 11:00:18 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2ABF6E36632 for ; Mon, 16 Oct 2017 11:00:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 18549770E7 for ; Mon, 16 Oct 2017 11:00:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GB0HqR046716 for ; Mon, 16 Oct 2017 11:00:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attatching vxlan interfaces to a bridge stops all traffic on it Date: Mon, 16 Oct 2017 11:00:18 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mav@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Works As Intended X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 11:00:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 Alexander Motin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Works As Intended --- Comment #3 from Alexander Motin --- Then I tend to say that it behaves correctly, even though not very nice. If you wish to avoid the flaps on bridge reconfiguration, you may explicitly disable some capabilities of uplink interface before bridge configuration, = to avoid them modified by bridge later on epair interface addition/removal. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 11:24:23 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67EA9E37130 for ; Mon, 16 Oct 2017 11:24:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 562B877D97 for ; Mon, 16 Oct 2017 11:24:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GBONNo018447 for ; Mon, 16 Oct 2017 11:24:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attatching vxlan interfaces to a bridge stops all traffic on it Date: Mon, 16 Oct 2017 11:24:23 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: heinz@project-fifo.net X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 11:24:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 Heinz N. Gies changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|Works As Intended |--- Status|Closed |Open --- Comment #4 from Heinz N. Gies --- I understand that it acts as implemented i.e. is not a code bug. Before we close this I'd like to make a case that is not working as intended but rath= er working as accepted. The VNET system is rather new in FreeBSD, bridges, on the other hand, exist= for a lot longer. Historically bridges were used in a rather static manner, to bridge physical interfaces (they don't change often), or bridge between physical interfaces= and tunnels or other virtual but too rather static interfaces. This kind of use is often a one-time configuration that happens on system startup or in the case of tunnels in an incredibly rare basis. At those tim= es the loss of connectivity for a few seconds either has no impact (during startup), or the impact is neglectable (i.e. adding tunnel interfaces as no= one is connected to a nonexisting interface anyway). I suspect that when the decision was made to implement it this way all that= was taken into consideration and (rightfully so) it wasn't worth the work for finding an alternative as it was working good enough for its use. VNET and more so VNET jails change things a bit, they make network configuration more dynamic. It becomes required to add and remove interface= s to a bridge dynamically - something that I suspect wasn't foreseen. Features do not exist in a void, they exist in relation to their environmen= t. The environment for bridges changed and while it was fine before it becomes problematic in this changed environment. I agree it's not a 'bug' in the bridge driver. But we can not look at a sin= gle component in isolation and on a system level, I'm sure that 'starting/stopp= ing a vnet jail means all other vnet jails loose connectivity' is intended behavior. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 11:26:59 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7F9FE372CC for ; Mon, 16 Oct 2017 11:26:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 A67B97C127 for ; Mon, 16 Oct 2017 11:26:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GBQxM2023165 for ; Mon, 16 Oct 2017 11:26:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attatching vnet interfaces to a bridge stops all traffic on it Date: Mon, 16 Oct 2017 11:26:59 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: heinz@project-fifo.net X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 11:26:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 Heinz N. Gies changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Attatching vxlan interfaces |Attatching vnet interfaces |to a bridge stops all |to a bridge stops all |traffic on it |traffic on it --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 11:30:14 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9F648E373BA for ; Mon, 16 Oct 2017 11:30:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 8D8F77C226 for ; Mon, 16 Oct 2017 11:30:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GBUEHo029425 for ; Mon, 16 Oct 2017 11:30:14 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attatching vnet interfaces to a bridge stops all traffic on it Date: Mon, 16 Oct 2017 11:30:14 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc see_also Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 11:30:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eugen@freebsd.org See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 143 | |59 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 11:32:02 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 467F0E3745D for ; Mon, 16 Oct 2017 11:32:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 353107C50F for ; Mon, 16 Oct 2017 11:32:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GBW1Ru038474 for ; Mon, 16 Oct 2017 11:32:02 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attatching vnet interfaces to a bridge stops all traffic on it Date: Mon, 16 Oct 2017 11:32:02 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mav@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 11:32:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 --- Comment #5 from Alexander Motin --- OK, we call it any way you like, but it does not change the facts: to be ab= le bridge interfaces with different hardware capabilities, some of those capabilities has to be disabled, and changing capabilities for Intel NICs e= nds up in NIC reinit, that takes time and invasive. Before this was introduced, bridging was just not working correctly in number of scenarios, including V= NET jails also, especially for modern NICs with more offload capabilities. If somebody see alternative way to handle that -- be my guest. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 11:35:43 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97E87E37680 for ; Mon, 16 Oct 2017 11:35:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 857607C65F for ; Mon, 16 Oct 2017 11:35:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GBZhpA046729 for ; Mon, 16 Oct 2017 11:35:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attatching vnet interfaces to a bridge stops all traffic on uplink NIC for few seconds Date: Mon, 16 Oct 2017 11:35:43 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mav@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 11:35:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 Alexander Motin changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Attatching vnet interfaces |Attatching vnet interfaces |to a bridge stops all |to a bridge stops all |traffic on it |traffic on uplink NIC for | |few seconds --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 11:36:38 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 267A7E37721 for ; Mon, 16 Oct 2017 11:36:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 14EDA7C728 for ; Mon, 16 Oct 2017 11:36:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GBabTf048309 for ; Mon, 16 Oct 2017 11:36:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds Date: Mon, 16 Oct 2017 11:36:38 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mav@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 11:36:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 Alexander Motin changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Attatching vnet interfaces |Attaching interface to a |to a bridge stops all |bridge stops all traffic on |traffic on uplink NIC for |uplink NIC for few seconds |few seconds | --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 11:40:01 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04E28E3781D for ; Mon, 16 Oct 2017 11:40:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 DF9937C806 for ; Mon, 16 Oct 2017 11:40:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GBe0fB054265 for ; Mon, 16 Oct 2017 11:40:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attatching vnet interfaces to a bridge stops all traffic on it Date: Mon, 16 Oct 2017 11:40:00 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 11:40:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Attaching interface to a |Attatching vnet interfaces |bridge stops all traffic on |to a bridge stops all |uplink NIC for few seconds |traffic on it --- Comment #6 from Eugene Grosbein --- (In reply to Heinz N. Gies from comment #4) Addition of first member to the bridge is quite different from addition of others. Why do you think it interfers with traffic flow every time? Also, you did not show your actions (commands) and has not been quite speci= fic describing what ill effects those actions bring thereafter. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 11:41:15 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5CA39E37902 for ; Mon, 16 Oct 2017 11:41:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 4AEDF7C94E for ; Mon, 16 Oct 2017 11:41:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GBfEBW058013 for ; Mon, 16 Oct 2017 11:41:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds Date: Mon, 16 Oct 2017 11:41:15 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 11:41:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Attatching vnet interfaces |Attaching interface to a |to a bridge stops all |bridge stops all traffic on |traffic on it |uplink NIC for few seconds --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 11:55:55 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83474E37F16 for ; Mon, 16 Oct 2017 11:55:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 707C47D245 for ; Mon, 16 Oct 2017 11:55:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GBttba003468 for ; Mon, 16 Oct 2017 11:55:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds Date: Mon, 16 Oct 2017 11:55:55 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: heinz@project-fifo.net X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 11:55:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 --- Comment #7 from Heinz N. Gies --- (In reply to Eugene Grosbein from comment #6) > Addition of first member to the bridge is quite different from addition o= f others. Why do you think it interferes with traffic flow every time? Mostly because I could not find any documentation regarding this so all I h= ad to go by was what I observed and it never occurred to me to try a second or third interface after seeing the problem with the first. The actions/commands in the initial bug report, along with a diagram of the setup, and hardware specifications. The ill effect is losing network connectivity for a few seconds, for a serv= er that can be quite problematic. Perhaps I'm approaching this all wrong and trying to squeeze s square peg through a round hole. Are bridge/epairs the wrong tools for vnet jails, is there a better alternative? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 12:06:53 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80174E38D92 for ; Mon, 16 Oct 2017 12:06:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 6E6427DD14 for ; Mon, 16 Oct 2017 12:06:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GC6rKJ085076 for ; Mon, 16 Oct 2017 12:06:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds Date: Mon, 16 Oct 2017 12:06:53 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mav@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 12:06:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 --- Comment #8 from Alexander Motin --- (In reply to Heinz N. Gies from comment #7) Bridge+epair are the right tools, unless you wish to dedicate one NIC completely to specific VNET Jail. I've already told you how to workaround the problem: when configuring upli= nk interface, you can explicitly disable its capabilities that bridge try to disable otherwise (TSO, LRO, TOE, TXCSUM, TXCSUM6). In that case bridge sh= ould be happy from the beginning and not modify capabilities any more. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 12:33:54 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7699E3998F for ; Mon, 16 Oct 2017 12:33:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 958227EFC1 for ; Mon, 16 Oct 2017 12:33:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GCXsw1007874 for ; Mon, 16 Oct 2017 12:33:54 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds Date: Mon, 16 Oct 2017 12:33:54 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 12:33:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 --- Comment #9 from commit-hook@freebsd.org --- A commit references this bug: Author: mav Date: Mon Oct 16 12:32:57 UTC 2017 New revision: 324659 URL: https://svnweb.freebsd.org/changeset/base/324659 Log: Update details of interface capabilities changed by bridge(4). PR: 221122 MFC after: 1 week Changes: head/share/man/man4/bridge.4 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 12:38:58 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5BD4CE39AFE for ; Mon, 16 Oct 2017 12:38:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 4A7BB7F10D for ; Mon, 16 Oct 2017 12:38:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GCcwFr005608 for ; Mon, 16 Oct 2017 12:38:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds Date: Mon, 16 Oct 2017 12:38:58 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 12:38:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 --- Comment #10 from Eugene Grosbein --- (In reply to Heinz N. Gies from comment #7) Please repeat your tests being more thorough: 1. Verify if you still have the problem while adding second and next bridge members after uplink interface already added as first bridge member. 2. Compare output of ifconfig $uplink before and after it added to the brid= ge. Then destroy the bridge and use ifconfig for uplink to disable features that bridge disables automatically. Then repeat creation of the bridge and verif= y if addition of uplink as first bridge member still leads to uplink reset. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 12:41:08 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0C454E39C1E for ; Mon, 16 Oct 2017 12:41:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 EBEA67F31F for ; Mon, 16 Oct 2017 12:41:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GCf718044496 for ; Mon, 16 Oct 2017 12:41:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds Date: Mon, 16 Oct 2017 12:41:07 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: heinz@project-fifo.net X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 12:41:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 --- Comment #11 from Heinz N. Gies --- Yes I read that, and I've been going through the man pages trying to figure= out which those are is there a list of settings supported by epairs. Just saw t= he updated info bridge I think that's what I was looking for. I was worried that the delta (RXCSUM, TXCSUM, TSO4) is not exhaustive - and= it seems it wasn't. Weeding through ifconfig(8), will LRO also be affected? I'm not trying to be dense. I've spent quite some time building tooling aro= und jails and am trying to understand this good enough to write up the steps for someone (like me) who don't know how bridges are implemented to get things working in a way that can be used in a production environment without unpleasant surprises. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 12:42:44 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA5C9E39E45 for ; Mon, 16 Oct 2017 12:42:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 C839B7F5F0 for ; Mon, 16 Oct 2017 12:42:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GCgi7U080703 for ; Mon, 16 Oct 2017 12:42:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds Date: Mon, 16 Oct 2017 12:42: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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 12:42:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 --- Comment #12 from Eugene Grosbein --- (In reply to Heinz N. Gies from comment #7) > 2. Compare output of ifconfig $uplink before and after it added to the br= idge. ... after it AND other members added to the bridge. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 12:49:18 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2526E39F6E for ; Mon, 16 Oct 2017 12:49:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 B0D367F738 for ; Mon, 16 Oct 2017 12:49:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9GCnIB3097696 for ; Mon, 16 Oct 2017 12:49:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds Date: Mon, 16 Oct 2017 12:49:18 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: heinz@project-fifo.net X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 12:49:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 --- Comment #13 from Heinz N. Gies --- (In reply to Eugene Grosbein from comment #12) ifconfig em0 (no bridge interfaces) em0: flags=3D8943 metric 0 = mtu 1500 =20=20=20=20=20=20=20 options=3D4219b ether 00:25:90:a6:3b:c7 hwaddr 00:25:90:a6:3b:c7 inet 192.168.1.22 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=3D29 media: Ethernet autoselect (1000baseT ) status: active adding first bridge interface: 64 bytes from 192.168.1.22: icmp_seq=3D22 ttl=3D64 time=3D1.325 ms Request timeout for icmp_seq 23 Request timeout for icmp_seq 24 Request timeout for icmp_seq 25 Request timeout for icmp_seq 26 Request timeout for icmp_seq 27 Request timeout for icmp_seq 28 Request timeout for icmp_seq 29 64 bytes from 192.168.1.22: icmp_seq=3D30 ttl=3D64 time=3D1.261 ms ifconfig em0 (after adding bridge interface)=20 em0: flags=3D8943 metric 0 = mtu 1500 options=3D42098 ether 00:25:90:a6:3b:c7 hwaddr 00:25:90:a6:3b:c7 inet 192.168.1.22 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=3D29 media: Ethernet autoselect (1000baseT ) status: active adding second interface: 64 bytes from 192.168.1.22: icmp_seq=3D132 ttl=3D64 time=3D1.432 ms 64 bytes from 192.168.1.22: icmp_seq=3D133 ttl=3D64 time=3D1.332 ms 64 bytes from 192.168.1.22: icmp_seq=3D134 ttl=3D64 time=3D1.146 ms (no drops) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 16 14:22:14 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB622E3BBF6 for ; Mon, 16 Oct 2017 14:22:14 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from mail.mimar.rs (tazar.mimar.rs [193.53.106.132]) (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 98665828CE for ; Mon, 16 Oct 2017 14:22:13 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from tazar.mimar.rs (localhost [127.0.2.132]) by mail.mimar.rs (Postfix) with ESMTP id BC248620BD5C for ; Mon, 16 Oct 2017 16:22:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mimar.rs; h= content-transfer-encoding:content-type:content-type:mime-version :x-mailer:organization:message-id:subject:subject:from:from:date :date:received:received; s=mimar-0901; t=1508163725; x= 1509978126; bh=eoCZgUsnlYZ99Iufwf6Rwy0Om9BAt/cE/XxHUIbPX/c=; b=K 2vuIoWLlL3FzYyi6yPXXYrdgg6SuxoSECVscZHZ2D1EUv0+DcMOeZ+K4XmYhA932 T6vwYNC4A/BX0cpSKGmXZFAnT55OZuY/ECajNiEHoXvpuKE0KEylOiRDOrD05Pey IqCdur/apABe8W80N4qyh7oKqus3yxB2oaIpFS3Cj8= X-Virus-Scanned: amavisd-new at mimar.rs Received: from mail.mimar.rs ([127.0.2.132]) by tazar.mimar.rs (amavis.mimar.rs [127.0.2.132]) (amavisd-new, port 10026) with LMTP id cupeZrZLOjMj for ; Mon, 16 Oct 2017 16:22:05 +0200 (CEST) Received: from efreet-freebsd.kappastar.com (nat-nat.kappastar.com [193.53.106.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: marko.cupac) by mail.mimar.rs (Postfix) with ESMTPSA id 8F96D620BD58 for ; Mon, 16 Oct 2017 16:22:05 +0200 (CEST) Date: Mon, 16 Oct 2017 16:22:04 +0200 From: Marko =?UTF-8?B?Q3VwYcSH?= To: freebsd-net@freebsd.org Subject: setfib (ez)jails and wierd routing Message-ID: <20171016162204.5d01a1b1@efreet-freebsd.kappastar.com> Organization: Mimar X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 14:22:15 -0000 Hi, I have already asked this on -jail two weeks ago, but perhaps this is better place to ask. I notice wierd routing in my setfib (ez)jails setup. I have a server with multiple NICs. setfib should ensure that LAN jails (setfib 1) can not talk to DMZ jails (setfib 2) over loopbacks, but need to go through firewalls as though they were physical boxes. pacija@warden3:~ % sudo setfib 1 netstat -rn Routing tables (fib: 1) Internet: Destination Gateway Flags Netif Expire default 10.30.19.190 UGS bce0 10.30.19.160/27 00:1c:c4:de:0a:86 US bce0 127.0.0.1 lo0 UHS lo0 127.0.1.0/24 lo1 US lo1 pacija@warden3:~ % sudo setfib 2 netstat -rn Routing tables (fib: 2) Internet: Destination Gateway Flags Netif Expire default 193.53.106.254 UGS bce1 127.0.0.1 lo0 UHS lo0 127.0.2.0/24 lo2 US lo2 193.53.106.0/24 00:1c:c4:de:0a:84 US bce1 Host has the same default route as fib 1: pacija@warden3:~ % sudo netstat -rn Routing tables Internet: Destination Gateway Flags Netif Expire default 10.30.19.190 UGS bce0 ... If I ssh from the Internet into DMZ jail, everything works as expected. But if I ping DMZ jail from the Internet, I see reply packets leaving not the interface they came from (bce1, public address space, DMZ), but another one (bce0, private address space, LAN). This is kinda understandable, because jail on fib2 does not have ICMP enabled, so it is not DMZ jail, but the host (which is in fib 0) who replies to packets via its default gateway (router on a private LAN). Is there an easy and elegant way to solve this? Like binding IP address to fib? I wouldn't like to have to fire up pf on host and meddle with reply-to rules in order to achieve this, I'd rather revert to old setup of separate physical servers for each network. Thank you in advance, --=20 Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupa=C4=87 https://www.mimar.rs/ From owner-freebsd-net@freebsd.org Mon Oct 16 14:37:13 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25A13E3C083 for ; Mon, 16 Oct 2017 14:37:13 +0000 (UTC) (envelope-from kfodil-lemelin@xiplink.com) Received: from smtp97.iad3a.emailsrvr.com (smtp97.iad3a.emailsrvr.com [173.203.187.97]) (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 E6BA482D6D for ; Mon, 16 Oct 2017 14:37:12 +0000 (UTC) (envelope-from kfodil-lemelin@xiplink.com) Received: from smtp13.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp13.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 7CF4D5676; Mon, 16 Oct 2017 10:37:03 -0400 (EDT) X-Auth-ID: kfodil-lemelin@xiplink.com Received: by smtp13.relay.iad3a.emailsrvr.com (Authenticated sender: kfodil-lemelin-AT-xiplink.com) with ESMTPSA id 27C8657D2; Mon, 16 Oct 2017 10:37:03 -0400 (EDT) X-Sender-Id: kfodil-lemelin@xiplink.com Received: from [10.10.1.188] ([UNAVAILABLE]. [192.252.130.194]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA) by 0.0.0.0:465 (trex/5.7.12); Mon, 16 Oct 2017 10:37:03 -0400 Subject: Re: m_move_pkthdr leaves m_nextpkt 'dangling' To: Gleb Smirnoff References: <59567148.1020902@xiplink.com> <31535133-f95a-5db6-a04c-acc0175fa287@yandex.ru> <59DFD3CC.2000401@xiplink.com> <20171013211026.GB1055@FreeBSD.org> Cc: Adrian Chadd , FreeBSD Net , "Andrey V. Elsukov" From: Karim Fodil-Lemelin Message-ID: <59E4C40E.9060103@xiplink.com> Date: Mon, 16 Oct 2017 10:37:02 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <20171013211026.GB1055@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 14:37:13 -0000 On 2017-10-13 5:10 PM, Gleb Smirnoff wrote: > On Fri, Oct 13, 2017 at 12:59:47AM -0700, Adrian Chadd wrote: > A> >>>> When doing so m_move_pkthdr is called to copy the current PKTHDR fields > A> >>>> (tags and flags) to the mbuf that was prepended. The function also does: > A> >>>> > A> >>>> to->m_pkthdr = from->m_pkthdr; > A> >>>> > A> >>>> This, for the case I am interested in, essentially leaves the 'from' > A> >>>> mbuf > A> >>>> with a dangling pointer m_nextpkt pointing to the next fragment. While > A> >>>> this > A> >>>> is mostly harmless because only mbufs of pkthdr types are supposed to > A> >>>> have > A> >>>> m_nextpkt it triggers some panics when running with INVARIANTS in > A> >>>> NetGraph > A> >>>> (see ng_base.c :: CHECK_DATA_MBUF(m)): > A> >>>> > A> >>>> ... > A> >>>> if (n->m_nextpkt != NULL) > A> >>>> \ > A> >>>> panic("%s: m_nextpkt", __func__); > A> >>>> \ > A> >>>> } > A> >>>> ... > A> >>>> > A> >>>> So I would like to propose the following patch: > A> >>>> > A> >>>> @@ -442,10 +442,11 @@ m_move_pkthdr(struct mbuf *to, struct mbuf *from) > A> >>>> if ((to->m_flags & M_EXT) == 0) > A> >>>> to->m_data = to->m_pktdat; > A> >>>> to->m_pkthdr = from->m_pkthdr; /* especially tags */ > A> >>>> SLIST_INIT(&from->m_pkthdr.tags); /* purge tags from src > A> >>>> */ > A> >>>> from->m_flags &= ~M_PKTHDR; > A> >>>> + from->m_nextpkt = NULL; > A> >>>> } > > Not only mbufs of M_PKTHDR may have m_nextpkt set. However, I tend to agree > with the patch. But shouldn't we first copy the m_nextpkt to the new mbuf: > > + to->m_nextpkt = from->m_nextpkt; > + from->m_nextpkt = NULL; > > Same way as we deal with tags. > > Hi Gleb, I think you are correct. If we look at the 'spirit' of m_move_pkthdr(); In my mind, it is to deep copy all fields related to a packet header and since m_nextpkt should only be carried by packet headers, it makes sense to copy it within m_move_pkthdr(). This also raises the question (my apologies in advance from bringing this up...) of weather or not m_nextpkt belongs in struct m_hdr and not in struct pkthdr. In our case we are copying it explicitly outside the function as most of users of m_move_pkthdr() do. Thanks for looking in to this. Karim. From owner-freebsd-net@freebsd.org Mon Oct 16 17:57:46 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1700BE40B02 for ; Mon, 16 Oct 2017 17:57:46 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (glebi.us [96.95.210.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F02AE662A3 for ; Mon, 16 Oct 2017 17:57:45 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.15.2/8.15.2) with ESMTPS id v9GHvcRY024695 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 Oct 2017 10:57:39 -0700 (PDT) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id v9GHvcZ5024694; Mon, 16 Oct 2017 10:57:38 -0700 (PDT) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 16 Oct 2017 10:57:38 -0700 From: Gleb Smirnoff To: Karim Fodil-Lemelin Cc: Adrian Chadd , FreeBSD Net , "Andrey V. Elsukov" Subject: Re: m_move_pkthdr leaves m_nextpkt 'dangling' Message-ID: <20171016175738.GA1100@FreeBSD.org> References: <59567148.1020902@xiplink.com> <31535133-f95a-5db6-a04c-acc0175fa287@yandex.ru> <59DFD3CC.2000401@xiplink.com> <20171013211026.GB1055@FreeBSD.org> <59E4C40E.9060103@xiplink.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <59E4C40E.9060103@xiplink.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 17:57:46 -0000 Karim, On Mon, Oct 16, 2017 at 10:37:02AM -0400, Karim Fodil-Lemelin wrote: K> > Not only mbufs of M_PKTHDR may have m_nextpkt set. However, I tend to agree K> > with the patch. But shouldn't we first copy the m_nextpkt to the new mbuf: K> > K> > + to->m_nextpkt = from->m_nextpkt; K> > + from->m_nextpkt = NULL; K> > K> > Same way as we deal with tags. K> > K> > K> K> I think you are correct. If we look at the 'spirit' of m_move_pkthdr(); K> In my mind, it is to deep copy all fields related to a packet header and K> since m_nextpkt should only be carried by packet headers, it makes sense K> to copy it within m_move_pkthdr(). K> K> This also raises the question (my apologies in advance from bringing K> this up...) of weather or not m_nextpkt belongs in struct m_hdr and not K> in struct pkthdr. K> K> In our case we are copying it explicitly outside the function as most of K> users of m_move_pkthdr() do. Moving m_nextpkt from m_hdr to m_pkthdr would be much more intrusive change, we can't handle that. I think an mbuf with m_nextpkt and no M_PKTRHDR is a valid one. In a datagram socket buffer that could hold a record. (didn't check that, just guessing). So, any objections on commiting this addition to m_move_pkthdr? + to->m_nextpkt = from->m_nextpkt; + from->m_nextpkt = NULL; -- Gleb Smirnoff From owner-freebsd-net@freebsd.org Mon Oct 16 18:37:20 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF193E41ADD for ; Mon, 16 Oct 2017 18:37:20 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [89.188.221.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plan-b.pwste.edu.pl", Issuer "plan-b.pwste.edu.pl" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 132576797F for ; Mon, 16 Oct 2017 18:37:19 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (zarychtam@localhost [127.0.0.1]) by plan-b.pwste.edu.pl (8.15.2/8.15.2) with ESMTPS id v9GI7Tcm034214 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 Oct 2017 20:07:29 +0200 (CEST) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: (from zarychtam@localhost) by plan-b.pwste.edu.pl (8.15.2/8.15.2/Submit) id v9GI7SDf034209; Mon, 16 Oct 2017 20:07:28 +0200 (CEST) (envelope-from zarychtam) Date: Mon, 16 Oct 2017 20:07:28 +0200 From: Marek Zarychta To: Marko =?utf-8?B?Q3VwYcSH?= Cc: freebsd-net@freebsd.org Subject: Re: setfib (ez)jails and wierd routing Message-ID: <20171016180728.GA32726@plan-b.pwste.edu.pl> References: <20171016162204.5d01a1b1@efreet-freebsd.kappastar.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline In-Reply-To: <20171016162204.5d01a1b1@efreet-freebsd.kappastar.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 18:37:20 -0000 --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 16, 2017 at 04:22:04PM +0200, Marko Cupa=C4=87 wrote: > Hi, >=20 > I have already asked this on -jail two weeks ago, but perhaps this is > better place to ask. >=20 > I notice wierd routing in my setfib (ez)jails setup. >=20 > I have a server with multiple NICs. setfib should ensure that LAN jails > (setfib 1) can not talk to DMZ jails (setfib 2) over loopbacks, but > need to go through firewalls as though they were physical boxes. >=20 > pacija@warden3:~ % sudo setfib 1 netstat -rn > Routing tables (fib: 1) >=20 > Internet: > Destination Gateway Flags Netif Expire > default 10.30.19.190 UGS bce0 > 10.30.19.160/27 00:1c:c4:de:0a:86 US bce0 > 127.0.0.1 lo0 UHS lo0 > 127.0.1.0/24 lo1 US lo1 >=20 > pacija@warden3:~ % sudo setfib 2 netstat -rn > Routing tables (fib: 2) >=20 > Internet: > Destination Gateway Flags Netif Expire > default 193.53.106.254 UGS bce1 > 127.0.0.1 lo0 UHS lo0 > 127.0.2.0/24 lo2 US lo2 > 193.53.106.0/24 00:1c:c4:de:0a:84 US bce1 >=20 > Host has the same default route as fib 1: >=20 > pacija@warden3:~ % sudo netstat -rn > Routing tables >=20 > Internet: > Destination Gateway Flags Netif Expire > default 10.30.19.190 UGS bce0 > ... >=20 > If I ssh from the Internet into DMZ jail, everything works as expected. > But if I ping DMZ jail from the Internet, I see reply packets leaving > not the interface they came from (bce1, public address space, DMZ), but > another one (bce0, private address space, LAN). This is kinda > understandable, because jail on fib2 does not have ICMP enabled, so > it is not DMZ jail, but the host (which is in fib 0) who replies to > packets via its default gateway (router on a private LAN). >=20 > Is there an easy and elegant way to solve this? Like binding IP address > to fib? I wouldn't like to have to fire up pf on host and meddle with > reply-to rules in order to achieve this, I'd rather revert to old setup > of separate physical servers for each network. >=20 Hi, try after to set "ifconfig bce1 fib 2" after disabling PF.=20 This should do the work. --=20 Marek Zarychta --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEMOqvKm6wKvS1/ZeCdZ/s//1SjSwFAlnk9V0ACgkQdZ/s//1S jSzT7ggAmoEMMLJkCdiaRfPUWNnt5Kqs9M2Ui/msaZhCVn9aMCWC5J6w37aNGE1A To2sizmtITiQA46hKhjA4govkPmCyCtvs2IWOb5mL0ctpe54EeGfgeojHnkN8K5Y +nC1ne45O8dkMjijIMzq54I2q2jnAc+7LzBLgzBQwhwBsb7kTmItdoCGDY9ovuCw e0xjFnVQugNAG1lZ/nTwLF/iLBusY9xvK1Idx/tl31n3dA/U2X/3DKhlf1+kBU4S 9sj08XhoS/lHfbHa4MVtEXKF1FSiwTVMTniKufwHUhfWByEXsr2KU8lav2jH6GMb rocPS3iDjEqsOteG35h0v3BdSUqVZQ== =i8c6 -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+-- From owner-freebsd-net@freebsd.org Mon Oct 16 21:46:29 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA162E46173 for ; Mon, 16 Oct 2017 21:46:29 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id 7E1046E810 for ; Mon, 16 Oct 2017 21:46:29 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id 40F0920D8C; Mon, 16 Oct 2017 21:46:29 +0000 (UTC) Date: Mon, 16 Oct 2017 21:46:29 +0000 To: freebsd-net@freebsd.org From: Phabricator Reply-to: D4090+325+3b0e398d354b0e86@reviews.freebsd.org Subject: [Differential] D4090: mbuf(9): unbreak m_fragment() Message-ID: X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , Thread-Topic: D4090: mbuf(9): unbreak m_fragment() X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NGMzZGUyODg0ODA5ZmU5NDFmYjZkMzllMWJlIFnlKLU= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="b1_c6109793872a4bb4263df0009757192f" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 21:46:29 -0000 --b1_c6109793872a4bb4263df0009757192f Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: base64 VGhpcyByZXZpc2lvbiB3YXMgYXV0b21hdGljYWxseSB1cGRhdGVkIHRvIHJlZmxlY3QgdGhlIGNv bW1pdHRlZCBjaGFuZ2VzLgpDbG9zZWQgYnkgY29tbWl0IHJTMzI0NjczOiBtYnVmKDkpOiB1bmJy ZWFrIG1fZnJhZ21lbnQoKSAoYXV0aG9yZWQgYnkgYXZvcywgY29tbWl0dGVkIGJ5ICkuCgpDSEFO R0VEIFBSSU9SIFRPIENPTU1JVAogIGh0dHBzOi8vcmV2aWV3cy5mcmVlYnNkLm9yZy9ENDA5MD92 cz05OTczJmlkPTM0MDM4I3RvYwoKUkVQT1NJVE9SWQogIHJTIEZyZWVCU0Qgc3JjIHJlcG9zaXRv cnkKCkNIQU5HRVMgU0lOQ0UgTEFTVCBVUERBVEUKICBodHRwczovL3Jldmlld3MuZnJlZWJzZC5v cmcvRDQwOTA/dnM9OTk3MyZpZD0zNDAzOAoKUkVWSVNJT04gREVUQUlMCiAgaHR0cHM6Ly9yZXZp ZXdzLmZyZWVic2Qub3JnL0Q0MDkwCgpBRkZFQ1RFRCBGSUxFUwogIGhlYWQvc3lzL2tlcm4vdWlw Y19tYnVmLmMKCkVNQUlMIFBSRUZFUkVOQ0VTCiAgaHR0cHM6Ly9yZXZpZXdzLmZyZWVic2Qub3Jn L3NldHRpbmdzL3BhbmVsL2VtYWlscHJlZmVyZW5jZXMvCgpUbzogczNlcmlvc19nbWFpbC5jb20s IGZyZWVic2QtbmV0LWxpc3QsIGdsZWJpdXMsIGFkcmlhbgpDYzogaW1wCg== --b1_c6109793872a4bb4263df0009757192f Content-Type: text/x-patch; charset=utf-8; name="D4090.34038.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="D4090.34038.patch" ZGlmZiAtLWdpdCBhL2hlYWQvc3lzL2tlcm4vdWlwY19tYnVmLmMgYi9oZWFkL3N5cy9rZXJuL3Vp cGNfbWJ1Zi5jCi0tLSBhL2hlYWQvc3lzL2tlcm4vdWlwY19tYnVmLmMKKysrIGIvaGVhZC9zeXMv a2Vybi91aXBjX21idWYuYwpAQCAtMTQ0OSw2MiArMTQ0OSw1OSBAQAogc3RydWN0IG1idWYgKgog bV9mcmFnbWVudChzdHJ1Y3QgbWJ1ZiAqbTAsIGludCBob3csIGludCBsZW5ndGgpCiB7Ci0Jc3Ry dWN0IG1idWYgKm1fbmV3ID0gTlVMTCwgKm1fZmluYWwgPSBOVUxMOwotCWludCBwcm9ncmVzcyA9 IDA7CisJc3RydWN0IG1idWYgKm1fZmlyc3QsICptX2xhc3Q7CisJaW50IGRpdmlzb3IgPSAyNTUs IHByb2dyZXNzID0gMCwgZnJhZ2xlbjsKIAogCWlmICghKG0wLT5tX2ZsYWdzICYgTV9QS1RIRFIp KQogCQlyZXR1cm4gKG0wKTsKIAotCWlmICgobGVuZ3RoID09IDApIHx8IChsZW5ndGggPCAtMikp CisJaWYgKGxlbmd0aCA9PSAwIHx8IGxlbmd0aCA8IC0yKQogCQlyZXR1cm4gKG0wKTsKKwlpZiAo bGVuZ3RoID4gTUNMQllURVMpCisJCWxlbmd0aCA9IE1DTEJZVEVTOworCWlmIChsZW5ndGggPCAw ICYmIGRpdmlzb3IgPiBNQ0xCWVRFUykKKwkJZGl2aXNvciA9IE1DTEJZVEVTOworCWlmIChsZW5n dGggPT0gLTEpCisJCWxlbmd0aCA9IDEgKyAoYXJjNHJhbmRvbSgpICUgZGl2aXNvcik7CisJaWYg KGxlbmd0aCA+IDApCisJCWZyYWdsZW4gPSBsZW5ndGg7CiAKIAltX2ZpeGhkcihtMCk7IC8qIE5l ZWRlZCBzYW5pdHkgY2hlY2sgKi8KIAotCW1fZmluYWwgPSBtX2dldGNsKGhvdywgTVRfREFUQSwg TV9QS1RIRFIpOwotCi0JaWYgKG1fZmluYWwgPT0gTlVMTCkKKwltX2ZpcnN0ID0gbV9nZXRjbCho b3csIE1UX0RBVEEsIE1fUEtUSERSKTsKKwlpZiAobV9maXJzdCA9PSBOVUxMKQogCQlnb3RvIG5v c3BhY2U7CiAKLQlpZiAobV9kdXBfcGt0aGRyKG1fZmluYWwsIG0wLCBob3cpID09IDApCisJaWYg KG1fZHVwX3BrdGhkcihtX2ZpcnN0LCBtMCwgaG93KSA9PSAwKQogCQlnb3RvIG5vc3BhY2U7CiAK LQltX25ldyA9IG1fZmluYWw7CisJbV9sYXN0ID0gbV9maXJzdDsKIAotCWlmIChsZW5ndGggPT0g LTEpCi0JCWxlbmd0aCA9IDEgKyAoYXJjNHJhbmRvbSgpICYgMjU1KTsKLQogCXdoaWxlIChwcm9n cmVzcyA8IG0wLT5tX3BrdGhkci5sZW4pIHsKLQkJaW50IGZyYWdsZW47Ci0KLQkJaWYgKGxlbmd0 aCA+IDApCi0JCQlmcmFnbGVuID0gbGVuZ3RoOwotCQllbHNlCi0JCQlmcmFnbGVuID0gMSArIChh cmM0cmFuZG9tKCkgJiAyNTUpOworCQlpZiAobGVuZ3RoID09IC0yKQorCQkJZnJhZ2xlbiA9IDEg KyAoYXJjNHJhbmRvbSgpICUgZGl2aXNvcik7CiAJCWlmIChmcmFnbGVuID4gbTAtPm1fcGt0aGRy LmxlbiAtIHByb2dyZXNzKQogCQkJZnJhZ2xlbiA9IG0wLT5tX3BrdGhkci5sZW4gLSBwcm9ncmVz czsKIAotCQlpZiAoZnJhZ2xlbiA+IE1DTEJZVEVTKQotCQkJZnJhZ2xlbiA9IE1DTEJZVEVTOwot Ci0JCWlmIChtX25ldyA9PSBOVUxMKSB7Ci0JCQltX25ldyA9IG1fZ2V0Y2woaG93LCBNVF9EQVRB LCAwKTsKKwkJaWYgKHByb2dyZXNzICE9IDApIHsKKwkJCXN0cnVjdCBtYnVmICptX25ldyA9IG1f Z2V0Y2woaG93LCBNVF9EQVRBLCAwKTsKIAkJCWlmIChtX25ldyA9PSBOVUxMKQogCQkJCWdvdG8g bm9zcGFjZTsKKworCQkJbV9sYXN0LT5tX25leHQgPSBtX25ldzsKKwkJCW1fbGFzdCA9IG1fbmV3 OwogCQl9CiAKLQkJbV9jb3B5ZGF0YShtMCwgcHJvZ3Jlc3MsIGZyYWdsZW4sIG10b2QobV9uZXcs IGNhZGRyX3QpKTsKKwkJbV9jb3B5ZGF0YShtMCwgcHJvZ3Jlc3MsIGZyYWdsZW4sIG10b2QobV9s YXN0LCBjYWRkcl90KSk7CiAJCXByb2dyZXNzICs9IGZyYWdsZW47Ci0JCW1fbmV3LT5tX2xlbiA9 IGZyYWdsZW47Ci0JCWlmIChtX25ldyAhPSBtX2ZpbmFsKQotCQkJbV9jYXQobV9maW5hbCwgbV9u ZXcpOwotCQltX25ldyA9IE5VTEw7CisJCW1fbGFzdC0+bV9sZW4gPSBmcmFnbGVuOwogCX0KIAlt X2ZyZWVtKG0wKTsKLQltMCA9IG1fZmluYWw7CisJbTAgPSBtX2ZpcnN0OwogCXJldHVybiAobTAp Owogbm9zcGFjZToKLQlpZiAobV9maW5hbCkKLQkJbV9mcmVlbShtX2ZpbmFsKTsKKwlpZiAobV9m aXJzdCkKKwkJbV9mcmVlbShtX2ZpcnN0KTsKIAkvKiBSZXR1cm4gdGhlIG9yaWdpbmFsIGNoYWlu IG9uIGZhaWx1cmUgKi8KIAlyZXR1cm4gKG0wKTsKIH0KCg== --b1_c6109793872a4bb4263df0009757192f-- From owner-freebsd-net@freebsd.org Tue Oct 17 01:48:30 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8BCA5E4D2F1 for ; Tue, 17 Oct 2017 01:48:30 +0000 (UTC) (envelope-from lew@perftech.com) Received: from smtp-gw.pt.net (smtp-gw.pt.net [206.210.194.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp-gw.pt.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 562F97716F for ; Tue, 17 Oct 2017 01:48:29 +0000 (UTC) (envelope-from lew@perftech.com) X-ASG-Debug-ID: 1508203932-09411a0f9b3265b0001-Pd2ruv Received: from mail.pt.net (mail.pt.net [206.210.194.11]) by smtp-gw.pt.net with ESMTP id Igi4P1zpxaI9Xq2Z (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 16 Oct 2017 20:32:12 -0500 (CDT) X-Barracuda-Envelope-From: lew@perftech.com X-Barracuda-Effective-Source-IP: mail.pt.net[206.210.194.11] X-Barracuda-Apparent-Source-IP: 206.210.194.11 Received: from localhost (localhost [IPv6:::1]) by mail.pt.net (Postfix) with ESMTP id 8DA8784265B for ; Mon, 16 Oct 2017 20:32:12 -0500 (CDT) Received: from mail.pt.net ([IPv6:::1]) by localhost (mail.pt.net [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id QaWyaJYsZ6Cd for ; Mon, 16 Oct 2017 20:32:12 -0500 (CDT) Received: from localhost (localhost [IPv6:::1]) by mail.pt.net (Postfix) with ESMTP id 1A21784265C for ; Mon, 16 Oct 2017 20:32:12 -0500 (CDT) X-Virus-Scanned: amavisd-new at pt.net Received: from mail.pt.net ([IPv6:::1]) by localhost (mail.pt.net [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id sPp0OaJ5QpYP for ; Mon, 16 Oct 2017 20:32:12 -0500 (CDT) Received: from lewhome-dhcp-179.pt.net (lewhome-dhcp-179.pt.net [206.210.207.179]) (Authenticated sender: lew@pt.net) by mail.pt.net (Postfix) with ESMTPSA id E4D4184265B for ; Mon, 16 Oct 2017 20:32:11 -0500 (CDT) From: Lewis Donzis Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [Bug 221385] [Regression] v6 mapped v4 addresses not working in 11.1 Date: Mon, 16 Oct 2017 20:32:11 -0500 X-ASG-Orig-Subj: Re: [Bug 221385] [Regression] v6 mapped v4 addresses not working in 11.1 References: To: freebsd-net@FreeBSD.org In-Reply-To: Message-Id: <490283D6-C663-46BE-9125-CCD9C49CD0BF@perftech.com> X-Mailer: Apple Mail (2.3273) X-Barracuda-Connect: mail.pt.net[206.210.194.11] X-Barracuda-Start-Time: 1508203932 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://smtp-gw.pt.net:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at pt.net X-Barracuda-Scan-Msg-Size: 3549 X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.82 X-Barracuda-Spam-Status: No, SCORE=0.82 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=HTML_MESSAGE, MIME_QP_LONG_LINE, MIME_QP_LONG_LINE_2 X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.43956 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 HTML_MESSAGE BODY: HTML included in message 0.00 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars 0.82 MIME_QP_LONG_LINE_2 RAW: Quoted-printable line longer than 76 chars Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 01:48:30 -0000 Would appreciate some guidance on this. It seems like a reasonably = serious regression, so I=E2=80=99m surprised it hasn=E2=80=99t already = been fixed. Since all of our code binds a particular library, we were able to work = around it by overriding the weak referenced socket() with our own = version that creates the socket and explicitly turns off the V6ONLY = option, but that doesn=E2=80=99t help with third-party applications. Thanks, lew > On Sep 13, 2017, at 7:47 AM, Lewis Donzis wrote: >=20 > Hello. >=20 > This particular bug is a real problem in our embedded system, and = we=E2=80=99re trying to decide whether to go back to 11.0 or wait for a = patch for 11.1. >=20 > We downloaded just the one file containing the fix, but it wouldn=E2=80=99= t compile, so we downloaded -CURRENT and verified that it works fine. = But it=E2=80=99s unclear to me whether the code in -CURRENT is slated = for an 11.1 patch, or if it won=E2=80=99t show up until 11.2 or even = 12.0. I see the "mfc-stable11 = =E2=80=9D = flag on the bug set to a value of =E2=80=9C?=E2=80=9D. Is that = significant? >=20 > Perhaps someone can help us understand how to determine when and in = which version a fix will show up. >=20 > Thanks, > lew >=20 From owner-freebsd-net@freebsd.org Tue Oct 17 08:05:43 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 793D7E3222A for ; Tue, 17 Oct 2017 08:05:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 670B9633B6 for ; Tue, 17 Oct 2017 08:05:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9H85gQi039071 for ; Tue, 17 Oct 2017 08:05:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds Date: Tue, 17 Oct 2017 08:05:43 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 08:05:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 --- Comment #14 from Eugene Grosbein --- (In reply to Heinz N. Gies from comment #13) Have you tried to use /etc/rc.conf to disable these features of em0 that an= yway got disabled by the bridge? And then create the bridge and try to add membe= rs to it to make sure that it does not affect traffic this way. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Oct 17 08:35:19 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B1522E32E7D for ; Tue, 17 Oct 2017 08:35:19 +0000 (UTC) (envelope-from Michael.Tuexen@lurchi.franken.de) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 774EF6426E for ; Tue, 17 Oct 2017 08:35:19 +0000 (UTC) (envelope-from Michael.Tuexen@lurchi.franken.de) Received: from [47.73.226.174] (unknown [47.73.226.174]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 2B06E70F8FC11; Tue, 17 Oct 2017 10:35:11 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\)) Subject: Re: [Bug 221385] [Regression] v6 mapped v4 addresses not working in 11.1 From: Michael Tuexen In-Reply-To: <490283D6-C663-46BE-9125-CCD9C49CD0BF@perftech.com> Date: Tue, 17 Oct 2017 10:35:09 +0200 Cc: freebsd-net@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <490283D6-C663-46BE-9125-CCD9C49CD0BF@perftech.com> To: Lewis Donzis X-Mailer: Apple Mail (2.3445.1.7) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 08:35:19 -0000 > On 17. Oct 2017, at 03:32, Lewis Donzis wrote: >=20 > Would appreciate some guidance on this. It seems like a reasonably = serious regression, so I=E2=80=99m surprised it hasn=E2=80=99t already = been fixed. >=20 > Since all of our code binds a particular library, we were able to work = around it by overriding the weak referenced socket() with our own = version that creates the socket and explicitly turns off the V6ONLY = option, but that doesn=E2=80=99t help with third-party applications. I can check later today to tomorrow if the patch is already MFCed to = stable/11. If not done already, I can MFC it to stable/11. Best regards Michael >=20 > Thanks, > lew >=20 >=20 >> On Sep 13, 2017, at 7:47 AM, Lewis Donzis wrote: >>=20 >> Hello. >>=20 >> This particular bug is a real problem in our embedded system, and = we=E2=80=99re trying to decide whether to go back to 11.0 or wait for a = patch for 11.1. >>=20 >> We downloaded just the one file containing the fix, but it wouldn=E2=80= =99t compile, so we downloaded -CURRENT and verified that it works fine. = But it=E2=80=99s unclear to me whether the code in -CURRENT is slated = for an 11.1 patch, or if it won=E2=80=99t show up until 11.2 or even = 12.0. I see the "mfc-stable11 = =E2=80=9D = flag on the bug set to a value of =E2=80=9C?=E2=80=9D. Is that = significant? >>=20 >> Perhaps someone can help us understand how to determine when and in = which version a fix will show up. >>=20 >> Thanks, >> lew >>=20 >=20 > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Tue Oct 17 12:53:15 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52DEFE39B46 for ; Tue, 17 Oct 2017 12:53:15 +0000 (UTC) (envelope-from Michael.Tuexen@lurchi.franken.de) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 194AA6BB51 for ; Tue, 17 Oct 2017 12:53:15 +0000 (UTC) (envelope-from Michael.Tuexen@lurchi.franken.de) Received: from [47.73.226.174] (unknown [47.73.226.174]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id EDD1170F8FC17; Tue, 17 Oct 2017 14:53:02 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\)) Subject: Re: [Bug 221385] [Regression] v6 mapped v4 addresses not working in 11.1 From: Michael Tuexen In-Reply-To: <490283D6-C663-46BE-9125-CCD9C49CD0BF@perftech.com> Date: Tue, 17 Oct 2017 14:52:59 +0200 Cc: freebsd-net@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <490283D6-C663-46BE-9125-CCD9C49CD0BF@perftech.com> To: Lewis Donzis X-Mailer: Apple Mail (2.3445.1.7) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 12:53:15 -0000 > On 17. Oct 2017, at 03:32, Lewis Donzis wrote: >=20 > Would appreciate some guidance on this. It seems like a reasonably = serious regression, so I=E2=80=99m surprised it hasn=E2=80=99t already = been fixed. I just MFCed the fix to stable/11: https://svnweb.freebsd.org/base?view=3Drevision&revision=3D324686 Does this help? Best regards Michael >=20 > Since all of our code binds a particular library, we were able to work = around it by overriding the weak referenced socket() with our own = version that creates the socket and explicitly turns off the V6ONLY = option, but that doesn=E2=80=99t help with third-party applications. >=20 > Thanks, > lew >=20 >=20 >> On Sep 13, 2017, at 7:47 AM, Lewis Donzis wrote: >>=20 >> Hello. >>=20 >> This particular bug is a real problem in our embedded system, and = we=E2=80=99re trying to decide whether to go back to 11.0 or wait for a = patch for 11.1. >>=20 >> We downloaded just the one file containing the fix, but it wouldn=E2=80= =99t compile, so we downloaded -CURRENT and verified that it works fine. = But it=E2=80=99s unclear to me whether the code in -CURRENT is slated = for an 11.1 patch, or if it won=E2=80=99t show up until 11.2 or even = 12.0. I see the "mfc-stable11 = =E2=80=9D = flag on the bug set to a value of =E2=80=9C?=E2=80=9D. Is that = significant? >>=20 >> Perhaps someone can help us understand how to determine when and in = which version a fix will show up. >>=20 >> Thanks, >> lew >>=20 >=20 > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Tue Oct 17 12:58:47 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0950BE39CCE for ; Tue, 17 Oct 2017 12:58:47 +0000 (UTC) (envelope-from lew@perftech.com) Received: from smtp-gw.pt.net (smtp-gw.pt.net [206.210.194.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp-gw.pt.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CD7A56BDA2 for ; Tue, 17 Oct 2017 12:58:46 +0000 (UTC) (envelope-from lew@perftech.com) X-ASG-Debug-ID: 1508245045-09411a0f99337440001-Pd2ruv Received: from mail.pt.net (mail.pt.net [206.210.194.11]) by smtp-gw.pt.net with ESMTP id Gay9KrCDrRF521Dl (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 17 Oct 2017 07:57:25 -0500 (CDT) X-Barracuda-Envelope-From: lew@perftech.com X-Barracuda-Effective-Source-IP: mail.pt.net[206.210.194.11] X-Barracuda-Apparent-Source-IP: 206.210.194.11 Received: from localhost (localhost [IPv6:::1]) by mail.pt.net (Postfix) with ESMTP id C2DAC84266D; Tue, 17 Oct 2017 07:57:25 -0500 (CDT) Received: from mail.pt.net ([IPv6:::1]) by localhost (mail.pt.net [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id 88XenErOOUdK; Tue, 17 Oct 2017 07:57:25 -0500 (CDT) Received: from localhost (localhost [IPv6:::1]) by mail.pt.net (Postfix) with ESMTP id 6CDFC84265A; Tue, 17 Oct 2017 07:57:25 -0500 (CDT) X-Virus-Scanned: amavisd-new at pt.net Received: from mail.pt.net ([IPv6:::1]) by localhost (mail.pt.net [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id g9qQkuYoqPx5; Tue, 17 Oct 2017 07:57:25 -0500 (CDT) Received: from lewhome-dhcp-179.pt.net (lewhome-dhcp-179.pt.net [206.210.207.179]) (Authenticated sender: lew@pt.net) by mail.pt.net (Postfix) with ESMTPSA id 343D1842653; Tue, 17 Oct 2017 07:57:25 -0500 (CDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [Bug 221385] [Regression] v6 mapped v4 addresses not working in 11.1 From: Lewis Donzis X-ASG-Orig-Subj: Re: [Bug 221385] [Regression] v6 mapped v4 addresses not working in 11.1 In-Reply-To: Date: Tue, 17 Oct 2017 07:57:24 -0500 Cc: freebsd-net@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <490283D6-C663-46BE-9125-CCD9C49CD0BF@perftech.com> To: Michael Tuexen X-Mailer: Apple Mail (2.3273) X-Barracuda-Connect: mail.pt.net[206.210.194.11] X-Barracuda-Start-Time: 1508245045 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://smtp-gw.pt.net:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at pt.net X-Barracuda-Scan-Msg-Size: 483 X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.43968 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 12:58:47 -0000 > On Oct 17, 2017, at 7:52 AM, Michael Tuexen = wrote: >=20 >> On 17. Oct 2017, at 03:32, Lewis Donzis wrote: >>=20 >> Would appreciate some guidance on this. It seems like a reasonably = serious regression, so I=E2=80=99m surprised it hasn=E2=80=99t already = been fixed. > I just MFCed the fix to stable/11: >=20 > https://svnweb.freebsd.org/base?view=3Drevision&revision=3D324686 >=20 > Does this help? Yes it does. Thanks very much! lew= From owner-freebsd-net@freebsd.org Tue Oct 17 14:36:40 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1DBA5E3BBDE for ; Tue, 17 Oct 2017 14:36:40 +0000 (UTC) (envelope-from lew@perftech.com) Received: from smtp-gw.pt.net (smtp-gw.pt.net [206.210.194.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp-gw.pt.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E76DD6F03C for ; Tue, 17 Oct 2017 14:36:39 +0000 (UTC) (envelope-from lew@perftech.com) X-ASG-Debug-ID: 1508250963-09411a0f9b33b730001-QdxwpM Received: from mail.pt.net (mail.pt.net [206.210.194.11]) by smtp-gw.pt.net with ESMTP id Pv1AHiZHwa8eVHen (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 17 Oct 2017 09:36:03 -0500 (CDT) X-Barracuda-Envelope-From: lew@perftech.com X-Barracuda-Effective-Source-IP: mail.pt.net[206.210.194.11] X-Barracuda-Apparent-Source-IP: 206.210.194.11 Received: from localhost (localhost [IPv6:::1]) by mail.pt.net (Postfix) with ESMTP id 9C1C384268E for ; Tue, 17 Oct 2017 09:36:03 -0500 (CDT) Received: from mail.pt.net ([IPv6:::1]) by localhost (mail.pt.net [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id 8fvNqJQfdA3Q for ; Tue, 17 Oct 2017 09:36:03 -0500 (CDT) Received: from localhost (localhost [IPv6:::1]) by mail.pt.net (Postfix) with ESMTP id 66A30842687 for ; Tue, 17 Oct 2017 09:36:03 -0500 (CDT) X-Virus-Scanned: amavisd-new at pt.net Received: from mail.pt.net ([IPv6:::1]) by localhost (mail.pt.net [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id 3v0Br-rT7Mvs for ; Tue, 17 Oct 2017 09:36:03 -0500 (CDT) Received: from dhcp-221-110.perftech.com (dhcp-221-110.perftech.com [206.210.221.110]) (Authenticated sender: lew@pt.net) by mail.pt.net (Postfix) with ESMTPSA id 5714A84268E for ; Tue, 17 Oct 2017 09:36:03 -0500 (CDT) From: Lewis Donzis Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: vmxnet3 driver bug? Message-Id: <0536294F-3709-4E38-AD7C-1A809AAD13A6@perftech.com> X-ASG-Orig-Subj: vmxnet3 driver bug? References: <398971232.399523.1508250252244.JavaMail.zimbra@perftech.com> To: freebsd-net@freebsd.org Date: Tue, 17 Oct 2017 09:36:02 -0500 X-Mailer: Apple Mail (2.3273) X-Barracuda-Connect: mail.pt.net[206.210.194.11] X-Barracuda-Start-Time: 1508250963 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://smtp-gw.pt.net:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at pt.net X-Barracuda-Scan-Msg-Size: 698 X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.43969 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 14:36:40 -0000 The VMXNET3 driver appears to have a bug that prevents it from correctly = reporting when the link goes down. There are two lines of code that should be deleted in = /usr/src/sys/dev/vmware/vmxnet3/if_vmx.c: @@ -3619,8 +3619,6 @@ vmxnet3_media_status(struct ifnet *ifp, struct = ifmediareq *ifmr) VMXNET3_CORE_LOCK(sc); if (vmxnet3_link_is_up(sc) !=3D 0) ifmr->ifm_status |=3D IFM_ACTIVE; - else - ifmr->ifm_status |=3D IFM_NONE; VMXNET3_CORE_UNLOCK(sc); } IFM_NONE doesn=E2=80=99t belong in the status flags and, coincidentally, = is defined with an identical value as IFM_ACTIVE, so it indicates that = link is always active. Thanks, lew= From owner-freebsd-net@freebsd.org Tue Oct 17 15:05:38 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7960CE3C85B for ; Tue, 17 Oct 2017 15:05:38 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2A55170124 for ; Tue, 17 Oct 2017 15:05:38 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-qt0-x22c.google.com with SMTP id f8so4188016qta.5 for ; Tue, 17 Oct 2017 08:05:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=bNzd5/GivIOXGGfuCCgVHwm1NjdZ9gaWAyJ9sjKjNuQ=; b=d2EFvy7ft20f/Zs/CDydFqicLZLTlyzyopFJmc3f4W5eb9xMiprd3IzwccrjG+QO4Q HiLylF4TakdqDepgW3Nx8GHCB7YC7Pop3KYlrhwdkOLrimO9890DeErBVPHGkcWUhPwO x33qNY8/2IblmkaoS/YqJclXlHwkho2u0ccE926AxchNt3Hiy0qLVcH/nKWKr/7ixPCt rfbY8+FZOnM4DRa6IZr4fE8B0aIKD/OBdNMGpU6E4d4zMtsio2a/fn9D8UU4qitlcUQi 1mkAPP8VXL5paz98pd5C24rFfAbFsT+HsGaL2OK4LRtzp2PezI4Dpkrr7511F/daPO1S 7hUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=bNzd5/GivIOXGGfuCCgVHwm1NjdZ9gaWAyJ9sjKjNuQ=; b=UNbssrImeQSSrBbqrHioN+CS97dIwGrjSYXBDg1tL1NM5AC3IxygXrhqAz0Od+Sj00 PgQzVfDK+3ITn4WLx5yzGDe7iBbQ57XvWPSsb3o6SmO0Y9pkmj727Fi4tz92WEh5I3K2 uiFCXZ8i3SgqoHs3yL/Q+EFgqllhdxgFHTJjcS7t0HX2+xX2s5ZXH1ymnLJ/34AsCFsy UM6fICfV2GX9JPG+bH4GKaYcWrriFp7X2Cjtd6weq5ryxIv337OmB5Gvsm77r6E1yEt4 1nTM6qfUUvdz4jjzegestBQF4tvu5jzof/Vo6KZLaqpmH9YEEuiMJOpFMYdzpqW+49AK desg== X-Gm-Message-State: AMCzsaVKeSQGJvuOPqYiJ6w2A72rpBXLn+0Bk+b8SiXbvEGpbBk2U9n6 F/MDpAYhPvDjGPP5kctA62TxMVkVzoqe0vvDCps= X-Google-Smtp-Source: ABhQp+TLj+SRxGC4PD7Ejkff12fIvKtx9l9P+JOKUhWwYGMKDVIKemi8M4Lq1cthu/aRD9Q5Vq5HOIyUnPXdlGk0IJs= X-Received: by 10.200.47.169 with SMTP id l38mr4714623qta.272.1508252736834; Tue, 17 Oct 2017 08:05:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.53.186 with HTTP; Tue, 17 Oct 2017 08:05:36 -0700 (PDT) From: Ryan Stone Date: Tue, 17 Oct 2017 11:05:36 -0400 Message-ID: Subject: Should RO_RTFREE() also free the cached lle entry? To: freebsd-net Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 15:05:38 -0000 About a year back we brought back lle (the ARP/NDP entry) caching back into the network stack. As near as I can tell, the ethernet layer will take a reference on the lle and place a pointer to it in the ro_lle field in the struct route passed down from the upper layer. The upper layer is expected to do something sensible with the lle. This appears to have introduced bugs in code that doesn't perform route caching. For example, ip_forward() passes a struct route down to ip_output(), but never checks if it needs to free an lle. Similarly, if ip_output() is passed NULL for the route, it substitutes a locally allocated one, and again does nothing with the lle. I believe that this means that these code paths now leak a reference on the lle. Both paths do call RO_RTFREE() on the struct route when they are done with it. I am wondering if the easiest path forward is to have that macro also release the reference on the cached lle. Otherwise fixing this is going to require a very invasive change that fixes any caller that ultimately might call into ether_output(). From owner-freebsd-net@freebsd.org Tue Oct 17 15:13:18 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1C793E3CBAE for ; Tue, 17 Oct 2017 15:13:18 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CC41A7054D for ; Tue, 17 Oct 2017 15:13:17 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-qk0-x229.google.com with SMTP id y23so2437041qkb.10 for ; Tue, 17 Oct 2017 08:13:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=kjnk+YK4mzSD8Uu2pAoKrVjgsiDvZ65eGk+4rmZhkvQ=; b=YyJkTVnSkcFXWFe8PSgrE2JVck5aPHp5vlw1K1kH0e1jpyNWwiLbg9d+1w5F/blunQ Nn+z8vpPin8ibNdoFi5rzOqXKG9hD9G1GbOXDww4xRTGJSZ3+9QnMDVNLn1UcBhWAKtm WqUitkMYRpcz00m6jn8Yk7VwU9KuC5Dq6X8xuusLXN8nFinQ02Y7ZlW/lE3+mBAz6/Bi J0o5MV4P75nIE2jQTFtxACDj5zpFMAhZ4fBZhz6btU3t+oKwEubaiEWHFypZWJiD76u+ GxJr+KCoNVksL+BXPtc1eLCNr6GW0FyyFel+A/oC+gATJxqQRtkEzDuOnDtDSD3elqlT KSaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=kjnk+YK4mzSD8Uu2pAoKrVjgsiDvZ65eGk+4rmZhkvQ=; b=lI5EZRwm5on9HwtiiG2e2aGkFv8zn0mVdPTEdCr+gZnFOOvzdj2SEk6QHAk417gAEy yS7VuTN9RXDdxem/AkOfWC3ZbqcSDdWfIIXP1FD482c7Xt1UuZjmi7yYlR4ntZStBAF0 yAtVKfPrORvJlWIe3YEdQBDKsNZLlVXCoDEV0HjgsYl6YZfjDccqheSUdgBZ3R/U7Hm0 Ik5rhn6rNbSnArWn+/NW3U1L59Zon4TiVjKiCOozsLMuEVnBd7hlS3kDkMZC7s8kUTu5 QYxFvybqlwoCS+9VW6i7LFHrXxnhYGE0kIZ0Ztc+i9dD9MYzdUew9QjodlOrGVQCTP// JATA== X-Gm-Message-State: AMCzsaVhmNKUukA37ZfuqMPbRuaJF3marGhIj2HdjaEQsM4Dhq+By/gm LjVG8SgYJSfsT9TVyn7jha3Vrv75UQFW+DX1t+I5HQ== X-Google-Smtp-Source: ABhQp+SC9yKnuZ7MZBmjfeNgX8Fp84k7HjQUNBHqn4gmbj47JNivfjCe5CAGCmTZyFEwprk2O51Vot/nTTtInAqA16M= X-Received: by 10.55.106.132 with SMTP id f126mr18001865qkc.295.1508253196761; Tue, 17 Oct 2017 08:13:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.53.186 with HTTP; Tue, 17 Oct 2017 08:13:16 -0700 (PDT) In-Reply-To: References: From: Ryan Stone Date: Tue, 17 Oct 2017 11:13:16 -0400 Message-ID: Subject: Re: Should RO_RTFREE() also free the cached lle entry? To: freebsd-net Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 15:13:18 -0000 Ah, never mind. When I started to investigate this problem I was looking at an old tree. I tried to verify that it was still a problem on -head, but missed that r315956 fixed the problem in a different way than I was expecting. Sorry for the noise. From owner-freebsd-net@freebsd.org Tue Oct 17 16:17:17 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5ADDE3F143 for ; Tue, 17 Oct 2017 16:17:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 A1B6873679 for ; Tue, 17 Oct 2017 16:17:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9HGHHZ7028452 for ; Tue, 17 Oct 2017 16:17:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds Date: Tue, 17 Oct 2017 16:17:17 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: heinz@project-fifo.net X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 16:17:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 Heinz N. Gies changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |Closed Resolution|--- |Not A Bug --- Comment #15 from Heinz N. Gies --- (In reply to Eugene Grosbein from comment #14) Yes, I did remove the features Alexander recommended, that did solve the downtime issue. He also did submit a patch to document the behavior. While = it isn't ideal we don't live in a perfect world and having it documented proba= bly as good as it gets. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Oct 17 18:28:29 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B78C1E437AD for ; Tue, 17 Oct 2017 18:28:29 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from mail.mimar.rs (tazar.mimar.rs [193.53.106.132]) (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 744567D77B for ; Tue, 17 Oct 2017 18:28:29 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from tazar.mimar.rs (localhost [127.0.2.132]) by mail.mimar.rs (Postfix) with ESMTP id 5F303620BDE8; Tue, 17 Oct 2017 20:28:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mimar.rs; h= content-transfer-encoding:content-type:content-type:mime-version :x-mailer:organization:references:in-reply-to:message-id:subject :subject:from:from:date:date:received:received; s=mimar-0901; t= 1508264898; x=1510079299; bh=ZbcskLJja1kmi7hbPb4LJNoT6U58T7aWxGX IATaMgbA=; b=OnWYzKh7wNNylyTcKjDwHAG6Js91DAam0cC0HlEyYCEJPV+N8qx UBJFgWHp8h46+zRF4fiXFb1BBXBWGtqn8DLwaCW1cA2kFl5lzAxO/tGlFM6NIvbk pabvEEhYWQ/0chTKaC8kVtb7xJSjdUPRSI9wPijKcnPqeO+1G+Sae/Fs= X-Virus-Scanned: amavisd-new at mimar.rs Received: from mail.mimar.rs ([127.0.2.132]) by tazar.mimar.rs (amavis.mimar.rs [127.0.2.132]) (amavisd-new, port 10026) with LMTP id 9ug4PFhZRg_X; Tue, 17 Oct 2017 20:28:18 +0200 (CEST) Received: from efreet-freebsd.kappastar.com (93-86-139-135.dynamic.isp.telekom.rs [93.86.139.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: marko.cupac) by mail.mimar.rs (Postfix) with ESMTPSA id 11414620BDE6; Tue, 17 Oct 2017 20:28:17 +0200 (CEST) Date: Tue, 17 Oct 2017 20:28:16 +0200 From: Marko =?UTF-8?B?Q3VwYcSH?= To: Marek Zarychta Cc: freebsd-net@freebsd.org Subject: Re: setfib (ez)jails and wierd routing Message-ID: <20171017202816.66a1664d@efreet-freebsd.kappastar.com> In-Reply-To: <20171016180728.GA32726@plan-b.pwste.edu.pl> References: <20171016162204.5d01a1b1@efreet-freebsd.kappastar.com> <20171016180728.GA32726@plan-b.pwste.edu.pl> Organization: Mimar X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 18:28:29 -0000 On Mon, 16 Oct 2017 20:07:28 +0200 Marek Zarychta wrote: > Hi, >=20 > try after to set "ifconfig bce1 fib 2" after disabling PF.=20 > This should do the work. Hi Marek, thank you for your advice, it seems to be getting me closer to the solution. PF is not enabled on this host. I've set `ifconfig bce1 fib 2' interactively, and packets with source address of DMZ net disappeared from LAN NIC (bce0 / fib 1). I wanted of course to have this automated, so I changed my rc.conf line for bce1: ifconfig_bce1=3D"inet 193.53.106.7 netmask 255.255.255.0 fib 2" However, after restart I observed another undesirable situation - packets with source address 193.53.106.7 leaving bce0 interface. I found out those are generated by sysutils/py-salt master service running directly on host (fib 0), bound to 193.53.106.7 (on interface bce1, which is now set as fib 2 at boot time). Why is outcome different when bce1 is set with fib 2 at the boot time from rc.conf from setting it at runtime? If setting bce1 with fib2 at the boot time from rc.conf, should I also start services running directly on host and bound to bce1 in fib 2? Would this be the correct rc.conf syntax for starting services in other fibs (for salt): salt_master_enable=3D"YES" salt_master_fib=3D"2" salt_minion_enable=3D"YES" salt_minion_fib=3D"2" Thank you in advance, --=20 Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupa=C4=87 https://www.mimar.rs/ From owner-freebsd-net@freebsd.org Tue Oct 17 19:30:26 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D13CBE45633 for ; Tue, 17 Oct 2017 19:30:26 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [89.188.221.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plan-b.pwste.edu.pl", Issuer "plan-b.pwste.edu.pl" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 542037FBC5 for ; Tue, 17 Oct 2017 19:30:25 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (zarychtam@localhost [127.0.0.1]) by plan-b.pwste.edu.pl (8.15.2/8.15.2) with ESMTPS id v9HJUGrF027311 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 17 Oct 2017 21:30:16 +0200 (CEST) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: (from zarychtam@localhost) by plan-b.pwste.edu.pl (8.15.2/8.15.2/Submit) id v9HJUGf0027309; Tue, 17 Oct 2017 21:30:16 +0200 (CEST) (envelope-from zarychtam) Date: Tue, 17 Oct 2017 21:30:16 +0200 From: Marek Zarychta To: Marko =?utf-8?B?Q3VwYcSH?= Cc: freebsd-net@freebsd.org Subject: Re: setfib (ez)jails and wierd routing Message-ID: <20171017193016.GA19784@plan-b.pwste.edu.pl> References: <20171016162204.5d01a1b1@efreet-freebsd.kappastar.com> <20171016180728.GA32726@plan-b.pwste.edu.pl> <20171017202816.66a1664d@efreet-freebsd.kappastar.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="rwEMma7ioTxnRzrJ" Content-Disposition: inline In-Reply-To: <20171017202816.66a1664d@efreet-freebsd.kappastar.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 19:30:26 -0000 --rwEMma7ioTxnRzrJ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 17, 2017 at 08:28:16PM +0200, Marko Cupa=C4=87 wrote: > On Mon, 16 Oct 2017 20:07:28 +0200 > Marek Zarychta wrote: >=20 > > Hi, > >=20 > > try after to set "ifconfig bce1 fib 2" after disabling PF.=20 > > This should do the work. >=20 > Hi Marek, >=20 > thank you for your advice, it seems to be getting me closer to the > solution. >=20 > PF is not enabled on this host. I've set `ifconfig bce1 fib 2' > interactively, and packets with source address of DMZ net disappeared > from LAN NIC (bce0 / fib 1). >=20 > I wanted of course to have this automated, so I changed my rc.conf line > for bce1: > ifconfig_bce1=3D"inet 193.53.106.7 netmask 255.255.255.0 fib 2" >=20 > However, after restart I observed another undesirable situation - > packets with source address 193.53.106.7 leaving bce0 interface. I > found out those are generated by sysutils/py-salt master service > running directly on host (fib 0), bound to 193.53.106.7 (on interface > bce1, which is now set as fib 2 at boot time). >=20 > Why is outcome different when bce1 is set with fib 2 at the boot time > from rc.conf from setting it at runtime? >=20 > If setting bce1 with fib2 at the boot time from rc.conf, should I also > start services running directly on host and bound to bce1 in fib 2? > Would this be the correct rc.conf syntax for starting services in other > fibs (for salt): >=20 > salt_master_enable=3D"YES" > salt_master_fib=3D"2" > salt_minion_enable=3D"YES" > salt_minion_fib=3D"2" Hi Marko, =20 bounding interface with FIB applies only to packets received on that interface (ifconfig(8)). IMHO py-salt works as expected and as before. If you wish to apply FIB to packets belonging to the connections originating from the host, you should either start service with setfib(1) or use appropriate firewall rules to assist this. With PF(4) it could be route-to or rtable options, see pf.conf(5) Best regards, --=20 Marek Zarychta --rwEMma7ioTxnRzrJ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEMOqvKm6wKvS1/ZeCdZ/s//1SjSwFAlnmWkUACgkQdZ/s//1S jSz+BwgAq9NysO7AjCU7RfyM+53L6/tYOCdV27iRsAGpFHg8A7NsbN4K7eU7TGic Gl9R6o5mTH9eyhJFLT0M5rnJGI75LLpXA7zUbLPfIqUsZT55OLIH65R/XB5bAzc7 5uaBkI3BrpMTesxknKWP0SoRzA+eGyXwIM+RJDvMGhrdvF9GSEy7hkTLW48s/+wV 8DjGvayy66DXhdKAKoZTCrtlZ+D03gug22+YUo1e39VxjGC/l5BfRMB3oN3z57ep spbGwJ52wJM/qrEmcQXPNo6E2s2ehLDB1as++4kluJbWvutuJocyBkwTHLDqzXey OhIYHrEtwyEnc81hGhmrYLuLLdLYbg== =bQyf -----END PGP SIGNATURE----- --rwEMma7ioTxnRzrJ-- From owner-freebsd-net@freebsd.org Wed Oct 18 03:04:51 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A479CE4DC53 for ; Wed, 18 Oct 2017 03:04:51 +0000 (UTC) (envelope-from julian@elischer.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 67A1B679CD for ; Wed, 18 Oct 2017 03:04:51 +0000 (UTC) (envelope-from julian@elischer.org) Received: from Julian-MBP3.local (124-148-79-216.dyn.iinet.net.au [124.148.79.216]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v9I34hjk015447 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 17 Oct 2017 20:04:47 -0700 (PDT) (envelope-from julian@elischer.org) Subject: Re: setfib (ez)jails and wierd routing To: Marek Zarychta , =?UTF-8?Q?Marko_Cupa=c4=87?= Cc: freebsd-net@freebsd.org References: <20171016162204.5d01a1b1@efreet-freebsd.kappastar.com> <20171016180728.GA32726@plan-b.pwste.edu.pl> <20171017202816.66a1664d@efreet-freebsd.kappastar.com> <20171017193016.GA19784@plan-b.pwste.edu.pl> From: Julian Elischer Message-ID: Date: Wed, 18 Oct 2017 11:04:38 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171017193016.GA19784@plan-b.pwste.edu.pl> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 18 Oct 2017 03:04:51 -0000 On 18/10/17 3:30 am, Marek Zarychta wrote: > On Tue, Oct 17, 2017 at 08:28:16PM +0200, Marko Cupać wrote: >> On Mon, 16 Oct 2017 20:07:28 +0200 >> Marek Zarychta wrote: >> >>> Hi, >>> >>> try after to set "ifconfig bce1 fib 2" after disabling PF. >>> This should do the work. >> Hi Marek, >> >> thank you for your advice, it seems to be getting me closer to the >> solution. >> >> PF is not enabled on this host. I've set `ifconfig bce1 fib 2' >> interactively, and packets with source address of DMZ net disappeared >> from LAN NIC (bce0 / fib 1). >> >> I wanted of course to have this automated, so I changed my rc.conf line >> for bce1: >> ifconfig_bce1="inet 193.53.106.7 netmask 255.255.255.0 fib 2" >> >> However, after restart I observed another undesirable situation - >> packets with source address 193.53.106.7 leaving bce0 interface. I >> found out those are generated by sysutils/py-salt master service >> running directly on host (fib 0), bound to 193.53.106.7 (on interface >> bce1, which is now set as fib 2 at boot time). >> >> Why is outcome different when bce1 is set with fib 2 at the boot time >> from rc.conf from setting it at runtime? >> >> If setting bce1 with fib2 at the boot time from rc.conf, should I also >> start services running directly on host and bound to bce1 in fib 2? >> Would this be the correct rc.conf syntax for starting services in other >> fibs (for salt): >> >> salt_master_enable="YES" >> salt_master_fib="2" >> salt_minion_enable="YES" >> salt_minion_fib="2" > Hi Marko, > > bounding interface with FIB applies only to packets received on that > interface (ifconfig(8)). IMHO py-salt works as expected and as before. > > If you wish to apply FIB to packets belonging to the connections > originating from the host, you should either start service with > setfib(1) or use appropriate firewall rules to assist this. With PF(4) > it could be route-to or rtable options, see pf.conf(5) > > Best regards, TO me it sounds a bit like what you want to do is better achieved using Vimage/Vnet on your jail. As for using Fibs, you can make sure that the jail is started with setfib, and that you always use setfib with jexec to ensure that all processes in hte jail inherit the correct fib setting.. The Fib on an interface just assignes that as a default fib for incoming packets. no more..  We did have a set of changes that allowd an incoming packet to attach to a  socket that had no fib and set its fib to that socket. Thet set was never really committed. (basically the server socket would take on the fib for the interface on which the packet had arrived) I still hope to get that change in one day. Julian From owner-freebsd-net@freebsd.org Wed Oct 18 05:49:17 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C4C3E2B87F for ; Wed, 18 Oct 2017 05:49:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 8A61B6B9DE for ; Wed, 18 Oct 2017 05:49:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9I5nHlI055788 for ; Wed, 18 Oct 2017 05:49:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds Date: Wed, 18 Oct 2017 05:49:17 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: julian@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 18 Oct 2017 05:49:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 Julian Elischer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |julian@FreeBSD.org --- Comment #16 from Julian Elischer --- The earlier comment that epair and bridge were the way to go was correct but incomplete. You can also use netgraph to plumb the jails (this was how vim= age was originally done). See the examples in /usr/share/examples. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 18 11:51:09 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 358B7E35BA3 for ; Wed, 18 Oct 2017 11:51:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 23B0A75A0E for ; Wed, 18 Oct 2017 11:51:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9IBp9w8002934 for ; Wed, 18 Oct 2017 11:51:09 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221122] Attaching interface to a bridge stops all traffic on uplink NIC for few seconds Date: Wed, 18 Oct 2017 11:51:09 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: see_also Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 18 Oct 2017 11:51:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221122 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- See Also|https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2143 | |59 | --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 18 11:53:30 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5CF81E35E25 for ; Wed, 18 Oct 2017 11:53:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 4B87075BD4 for ; Wed, 18 Oct 2017 11:53:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9IBrT1c012763 for ; Wed, 18 Oct 2017 11:53:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221317] Netmap issue after ixgbe driver update in r320897 Date: Wed, 18 Oct 2017 11:53:29 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: IntelNetworking, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: peixoto.cassiano@gmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: erj@freebsd.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 18 Oct 2017 11:53:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221317 --- Comment #11 from Cassiano Peixoto --- Hi guys, Any update about this issue? Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 18 11:55:13 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 865CFE35EFC for ; Wed, 18 Oct 2017 11:55:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 74A1475CBB for ; Wed, 18 Oct 2017 11:55:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9IBtDBt016124 for ; Wed, 18 Oct 2017 11:55:13 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219390] [ixgbe] [patch] ixgbe stripping vlan_tag by default Date: Wed, 18 Oct 2017 11:55:13 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: peixoto.cassiano@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 18 Oct 2017 11:55:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219390 Cassiano Peixoto changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-net@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 18 11:55:50 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6042E35F92 for ; Wed, 18 Oct 2017 11:55:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 B471775D75 for ; Wed, 18 Oct 2017 11:55:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9IBtoFl017368 for ; Wed, 18 Oct 2017 11:55:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219390] [ixgbe] [patch] ixgbe stripping vlan_tag by default Date: Wed, 18 Oct 2017 11:55:50 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: peixoto.cassiano@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 18 Oct 2017 11:55:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219390 --- Comment #2 from Cassiano Peixoto --- Please, can some committer take care of this? It's a quite simple patch. Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 18 13:08:31 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 82076E3875D for ; Wed, 18 Oct 2017 13:08:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 7078B7CB05 for ; Wed, 18 Oct 2017 13:08:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9ID8VHP082398 for ; Wed, 18 Oct 2017 13:08:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219390] [ixgbe] [patch] ixgbe stripping vlan_tag by default Date: Wed, 18 Oct 2017 13:08:31 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: jeffrey.e.pieper@intel.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 18 Oct 2017 13:08:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219390 Jeff Pieper changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffrey.e.pieper@intel.com --- Comment #3 from Jeff Pieper --- This is against 10.3-STABLE. The driver has been refactored quite a bit sin= ce this was filed. Have you retested this against a current -STABLE branch? --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 18 13:54:41 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B288DE3994A for ; Wed, 18 Oct 2017 13:54:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 99D6B7E652 for ; Wed, 18 Oct 2017 13:54:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9IDsfFj021110 for ; Wed, 18 Oct 2017 13:54:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219390] [ixgbe] [patch] ixgbe stripping vlan_tag by default Date: Wed, 18 Oct 2017 13:54:41 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: halfling@halfling.com.br X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 18 Oct 2017 13:54:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219390 Charles Goncalves changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #182723|0 |1 is obsolete| | --- Comment #4 from Charles Goncalves --- Created attachment 187278 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D187278&action= =3Dedit Patch for FreeBSD 11.1-STABLE --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 18 14:02:20 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 750B1E39B1A for ; Wed, 18 Oct 2017 14:02:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 632CC7EB13 for ; Wed, 18 Oct 2017 14:02:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9IE2KFC050548 for ; Wed, 18 Oct 2017 14:02:20 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219390] [ixgbe] [patch] ixgbe stripping vlan_tag by default Date: Wed, 18 Oct 2017 14:02:20 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: halfling@halfling.com.br X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: version Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 18 Oct 2017 14:02:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219390 Charles Goncalves changed: What |Removed |Added ---------------------------------------------------------------------------- Version|10.3-STABLE |11.1-STABLE --- Comment #5 from Charles Goncalves --- (In reply to Jeff Pieper from comment #3) Hello Jeff! I have tested on FreeBSD 11.1-STABLE and the same error happened. In fact I updated my patch to FreeBSD 11.1-STABLE. Can you check that? --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 18 15:34:25 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 679E8E3C4AE for ; Wed, 18 Oct 2017 15:34:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 5362682E04 for ; Wed, 18 Oct 2017 15:34:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9IFYOf0053907 for ; Wed, 18 Oct 2017 15:34:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219390] [ixgbe] [patch] ixgbe stripping vlan_tag by default Date: Wed, 18 Oct 2017 15:34:24 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: peixoto.cassiano@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 18 Oct 2017 15:34:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219390 --- Comment #6 from Cassiano Peixoto --- (In reply to Charles Goncalves from comment #5) Same here. I just tested and the patch still needed. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 18 16:38:43 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 42558E3DD04 for ; Wed, 18 Oct 2017 16:38:43 +0000 (UTC) (envelope-from tony.liu@chinaregistrar.org) Received: from us2-ob2-7.mailhostbox.com (us2-ob2-7.mailhostbox.com [208.91.199.208]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 241CE1DF for ; Wed, 18 Oct 2017 16:38:42 +0000 (UTC) (envelope-from tony.liu@chinaregistrar.org) Received: from 163.com (unknown [117.60.207.41]) (Authenticated sender: tony.liu@chinaregistrar.org) by us2.outbound.mailhostbox.com (Postfix) with ESMTPA id 426C8781174 for ; Wed, 18 Oct 2017 16:30:33 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chinaregistrar.org; s=20160924; t=1508344237; bh=kHYZUs988ec9uNRoiOtEEk8UY0Hrzbj9v7x+hRiAJ8Q=; h=Date:From:To:Subject; b=OkqNln5KNvBIvaSXzAxCp0EzJhaPMgtfceTA1Jo6iAXcGd7Oq0vUY3lgfv5KFqsBM zjrLs50DRQydc+MUmXeNvV5ytMnibTTbybPldQEKaRp4jJx7mSEc0kcVQVopdrCimH pKIOFR+pqOKMmjsKk5/asPhtkASVknKvL50YzO2k= Date: Thu, 19 Oct 2017 00:29:06 +0800 From: "Tony Liu" To: Subject: Confirm: About freebsd Registration Message-ID: <20171019002917157510@chinaregistrar.org> X-mailer: Foxmail 6, 13, 102, 15 [cn] Mime-Version: 1.0 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=LqTi8jVc c=1 sm=1 tr=0 a=HtsoVcCuE1CxeUoBkkJksA==:117 a=HtsoVcCuE1CxeUoBkkJksA==:17 a=r77TgQKjGQsHNAKrUKIA:9 a=eM8GnQ37fcCt0Adyq74A:9 a=vd3EqFg4hB1rOKno:21 a=UbkGGWrHNaleXsLZ:21 a=mFyHDrcPJccA:10 a=vPC6YCEeDZK88YgTCNsA:9 a=-SKoznOhtWkFvbzt:21 a=_W_S_7VecoQA:10 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 18 Oct 2017 16:38:43 -0000 RGVhciBNYW5hZ2VyLA0KKFBsZWFzZSBmb3J3YXJkIHRoaXMgdG8geW91ciBDRU8sIGJlY2F1c2Ug dGhpcyBpcyB1cmdlbnQuIFRoYW5rcykNClRoaXMgaXMgVG9ueSBMaXUsIFNlbmlvciBNYW5hZ2Vy IG9mIGEgTmV0d29yayBTZXJ2aWNlIENvbXBhbnkgd2hpY2ggaXMgdGhlIGRvbWFpbiBuYW1lIHJl Z2lzdHJhdGlvbiBjZW50ZXIgaW4gU2hhbmdoYWksIENoaW5hLiBPbiBPY3RvYmVyIDE2dGgsIDIw MTcsIHdlIHJlY2VpdmVkIGFuIGFwcGxpY2F0aW9uIGZyb20gUnVuYmFuZyBIb2xkaW5ncyBMdGQg cmVxdWVzdGVkIKGwZnJlZWJzZKGxIGFzIHRoZWlyIGludGVybmV0IGtleXdvcmQgYW5kIENoaW5h IChDTikgZG9tYWluIG5hbWVzKCBmcmVlYnNkLmNuLyBmcmVlYnNkLmNvbS5jbi8gZnJlZWJzZC5u ZXQuY24vIGZyZWVic2Qub3JnLmNuKS4gIEJ1dCBhZnRlciBjaGVja2luZyBpdCwgd2UgZmluZCB0 aGlzIG5hbWUgY29uZmxpY3Qgd2l0aCB5b3VyIGNvbXBhbnkgbmFtZSBvciB0cmFkZW1hcmsuIElu IG9yZGVyIHRvIGRlYWwgd2l0aCB0aGlzIG1hdHRlciBiZXR0ZXIsIGl0oa9zIG5lY2Vzc2FyeSB0 byBzZW5kIGVtYWlsIHRvIHlvdSBhbmQgY29uZmlybSB3aGV0aGVyIHRoaXMgY29tcGFueSBpcyB5 b3VyIGRpc3RyaWJ1dG9yIG9yIGJ1c2luZXNzIHBhcnRuZXIgaW4gQ2hpbmE/DQpCZXN0IFJlZ2Fy ZHMNClRvbnkgTGl1DQpTZW5pb3IgTWFuYWdlcg0KDQoNCkNoaW5hIFJlZ2lzdHJhciBIZWFkcXVh cnRlcnMNCnd3dy5jaGluYXJlZ2lzdHJhci5vcmcNCjgwMDgsIFRpYW5hbiBCdWlsZGluZywgTm8u IDEzOTkgSmlucWlhbyBSb2FkLCANClNoYW5naGFpIDIwMDEyMCwgQ2hpbmENCjAwODYtMjEtNjE5 MS04Njk2KFRlbCkgDQowMDg2LTEzNzctNDQwMC0zNDAoIE1vYmkpDQowMDg2LTIxLTYxOTEtODY5 NyhGYXgp From owner-freebsd-net@freebsd.org Thu Oct 19 13:03:12 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75440E3AC9A for ; Thu, 19 Oct 2017 13:03:12 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [148.251.9.81]) by mx1.freebsd.org (Postfix) with ESMTP id 397A2689B1 for ; Thu, 19 Oct 2017 13:03:11 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.19.110] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id B9E29F6B for ; Thu, 19 Oct 2017 16:03:09 +0300 (MSK) To: freebsd-net@freebsd.org Reply-To: lev@FreeBSD.org From: Lev Serebryakov Subject: igb0 sometimes consume 100% of 4 cores for not-too-heavy traffic Organization: FreeBSD Message-ID: <82cf7080-b473-3e6c-5e8f-9f004c8a288f@FreeBSD.org> Date: Thu, 19 Oct 2017 16:03:02 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3A2Pw5sjFaI1BjgAJCIfpv7NXHxXINCUX" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2017 13:03:12 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3A2Pw5sjFaI1BjgAJCIfpv7NXHxXINCUX Content-Type: multipart/mixed; boundary="xfhOwXpHAIp8VjXjcLjfvNDaw8o3MOIa5"; protected-headers="v1" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: freebsd-net@freebsd.org Message-ID: <82cf7080-b473-3e6c-5e8f-9f004c8a288f@FreeBSD.org> Subject: igb0 sometimes consume 100% of 4 cores for not-too-heavy traffic --xfhOwXpHAIp8VjXjcLjfvNDaw8o3MOIa5 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable I have system on SuperMicro MoBo with built-in I210 adapters. CPU is E3-1220v3, 4 cores, and igb0 driver creates 4 queues. FreeBSD version is 11.1-STABLE r324205. Sometimes system becomes very unresponsive and igb0 queues consume 100% of CPU for tens of minutes. System doesn't have any firewall, NAT or other additional network processing. I don't believe, that it is normal behavior, because only possible load on this server at these moments is torrents, which could not be more than 100MBit/s (my connection to Internet). 100% of 4 cores of E3-1220v3 for 50-60Mbit/s? Really? Looks like a bug= =2E --=20 // Lev Serebryakov --xfhOwXpHAIp8VjXjcLjfvNDaw8o3MOIa5-- --3A2Pw5sjFaI1BjgAJCIfpv7NXHxXINCUX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAlnoooxfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5 NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c R48gkA/+I/xcl/wg6NT34AWD90lAnp1Y2wlyFBJ90VE/Qn10hzBbvrVNbGGJ14xp ppusCisX4cKh0sL9kKkW/voaVkP1gNtzaMcm36Uoc+pkobW9T8WMBZ+pS3wsq7Kn u/KjmF44Yau8s940kp4iOUZgCdGmG7P7zalzJZe8z3G9guDckCvGlNGff4xaT8P2 /Rpl1SHEgjfFIMFwp6sqVgm0/1rj0oFzzxIVHJ06X31+k/bhz5nmIJCvGbOPzuE8 Wj2DlWXOUW6RuPRfuvok27aef0IKlDpRIFXAGfmYrroBVl8h4uxQoxzGy1k3gP2R cNz6dMugCkkedt8LicU/9O9GX/4i8fOQ7gMBKeqtR7cPDA+w1T3QnG4/wO3WIQjl VWTP26UBcbZbnoSF6WApM1sKaNZMnJWaN726EyZtsfD8AE7kaH/loMyHQ8GkOTiA Sy6AxnN7FdZgEpMr56r0zfiAmFwoFQsffQz1lgjy2kuW/NtyFfoWQJWNUK8wsL9W VSUTAogn4kXBXWnoQgCxy9elYIbCoj5mi/8O0SAkX+HCWaWPrVNrae5TPNKvULOm cLIMN6Pw2cz5OPyk78u/bRvs3577fq3fT82oqkg4H0VGePvTCKPZOaln0dBQXOyQ aYtwZqxNCq3/ZcbyPy95uJlMpDMWyC+f22L98LkkV+mvpdgi6YA= =I35/ -----END PGP SIGNATURE----- --3A2Pw5sjFaI1BjgAJCIfpv7NXHxXINCUX-- From owner-freebsd-net@freebsd.org Fri Oct 20 04:04:40 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9453E4EF09 for ; Fri, 20 Oct 2017 04:04:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 C562566BC5 for ; Fri, 20 Oct 2017 04:04:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9K44eSV035979 for ; Fri, 20 Oct 2017 04:04:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221317] Netmap issue after ixgbe driver update in r320897 Date: Fri, 20 Oct 2017 04:04:40 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: IntelNetworking, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rstone@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: erj@freebsd.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2017 04:04:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221317 Ryan Stone changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rstone@FreeBSD.org --- Comment #12 from Ryan Stone --- (In reply to Vincenzo Maffione from comment #10) I have some old, uncommited ixgbe code that can stop the receive path of an interface without resetting the entire device. The patch is available here: https://github.com/rysto32/freebsd/commit/db13ef817927b0c84b73906a4326a79a1= 1823266 https://github.com/rysto32/freebsd/commit/5ae7ec4bd3d2fab61aaf7c755fe666457= 327f401 Similar work for the tx side can be found here: https://github.com/rysto32/freebsd/commit/bf7186b90a26ca2df7d873961b19af5b8= 54eb3d0 Feel free to contact me via email if you have questions. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 20 13:52:13 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 268C5E34E80 for ; Fri, 20 Oct 2017 13:52:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 1465C76C7C for ; Fri, 20 Oct 2017 13:52:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9KDqCv3060401 for ; Fri, 20 Oct 2017 13:52:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217606] Bridge stops working after some days Date: Fri, 20 Oct 2017 13:52:13 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mops@punkt.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2017 13:52:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217606 --- Comment #25 from punkt.de Hosting Team --- Hey guys, I am trying to reproduce the problem on a not yet productive server. Un(?)fortunately this system is rock-stable for almost two weeks now. I just noticed that this test system runs 11.1p1 while the problematic serv= er runs 11.0p10 - duh! So ... I'll attach a diff of if_bridge.c of the two releases. Looks like the areas changed cover locking, handling of fragments and handling of mbufs for fragments. Any qualified comment on what might have caused the problem in 11.0 that changed in 11.1? Thanks! Patrick --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 20 13:53:05 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8C60E36004 for ; Fri, 20 Oct 2017 13:53:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 D6B8376ECD for ; Fri, 20 Oct 2017 13:53:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9KDr5ZZ063306 for ; Fri, 20 Oct 2017 13:53:05 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217606] Bridge stops working after some days Date: Fri, 20 Oct 2017 13:53:05 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mops@punkt.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2017 13:53:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217606 --- Comment #26 from punkt.de Hosting Team --- Created attachment 187326 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D187326&action= =3Dedit Diff of if_bridge.c for 11.0 and 11.1 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 20 14:11:07 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 753A2E36843 for ; Fri, 20 Oct 2017 14:11:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 616B677BBA for ; Fri, 20 Oct 2017 14:11:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9KEB7Uh014957 for ; Fri, 20 Oct 2017 14:11:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223129] Addition of an IP address to an interface (SIOCAIFADDR) fails when there is conflicting dynamic route Date: Fri, 20 Oct 2017 14:11:07 +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: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2017 14:11:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223129 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 20 16:44:03 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C75BDE3A6EB for ; Fri, 20 Oct 2017 16:44:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 A8BF082402 for ; Fri, 20 Oct 2017 16:44:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9KGi3GA097399 for ; Fri, 20 Oct 2017 16:44:03 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219390] [ixgbe] [patch] ixgbe stripping vlan_tag by default Date: Fri, 20 Oct 2017 16:44:03 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: krzysztof.galazka@intel.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2017 16:44:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219390 Krzysztof Galazka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |krzysztof.galazka@intel.com --- Comment #7 from Krzysztof Galazka --- (In reply to Charles Goncalves from comment #5) Hi Charles! Thank you for the patch. Could you provide me the reproduction steps and wh= at NIC do you use? The ixgbe_setup_vlan_hw_support() is used also in ixgbe_(un)register_vlan() event handlers so I'd like to check if it covers = all use cases. Thanks! --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 20 17:37:10 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7EB65E3BD00 for ; Fri, 20 Oct 2017 17:37:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 6C7D81B0 for ; Fri, 20 Oct 2017 17:37:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9KHb9fi047891 for ; Fri, 20 Oct 2017 17:37:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 219390] [ixgbe] [patch] ixgbe stripping vlan_tag by default Date: Fri, 20 Oct 2017 17:37:10 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: halfling@halfling.com.br X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2017 17:37:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219390 --- Comment #8 from Charles Goncalves --- (In reply to Krzysztof Galazka from comment #7) Hello Krzysztof! I'm using: Intel 82599ES 10-Gigabit SFI/SFP+ (chip=3D0x10fb8086) I have two machines with crossover connection. test01 <-> test02 On test01 I have ixgbe driver patched and on test02 I don't have. On both machines there is a vlan10 over an ix NIC. Step 1: on machine test02 do a ping to test01 like: ping 10.0.0.1 Step 2: on machine test01 do a tcpdump like: tcpdump -eni netmap:ix0 On Step 2 I'm seeing tcpdump output like: ethertype 802.1Q (0x8100). This i= s an expected behavior. Step 3: on machine test01 do a ping to test02 like: ping 10.0.0.2 Step 4: on machine test02 do a tcpdump like: tcpdump -eni netmap:ix0 On Step 4 I'm seeing tcpdump output like: ethertype IPv4 (0x0800). This is a strange behavior. My inspiration is from em1000 driver: https://github.com/freebsd/freebsd/blob/bb993c697ac4f18efa742ac69db425a5e03= 51117/sys/dev/e1000/if_em.c#L1246+L1249 I hope these steps are clear. If you have any further doubts feel free to contact me. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 20 20:12:32 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FC3DE3ECAC for ; Fri, 20 Oct 2017 20:12:32 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DD0B2640B4 for ; Fri, 20 Oct 2017 20:12:30 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v9KKCL04077002 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Fri, 20 Oct 2017 22:12:22 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id v9KKCH4J005964 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Sat, 21 Oct 2017 03:12:17 +0700 (+07) (envelope-from eugen@grosbein.net) To: "freebsd-net@freebsd.org" From: Eugene Grosbein Subject: loopback routes miss RTF_PINNED flag Message-ID: <59EA589D.7020403@grosbein.net> Date: Sat, 21 Oct 2017 03:12:13 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2017 20:12:32 -0000 Hi! When IP address is being added to an interface, a kernel installs loopback route. For P2P interfaces, we have local IP address and remote one. A route to remote address is added with RTF_PINNED flag, so that it overrides any possibly existing route to that address added by a routing daemon and that's fine. A route to local address created with ifa_maintain_loopback_route() function in https://svnweb.freebsd.org/base/head/sys/net/if.c?annotate=323170#l1711 misess RTF_PINNED flag, so that it cannot override similar possibly existing route and that's not fine as rtrequest1_fib() returns EEXIST in such case. This error is then propagated back to userland ioctl SIOCAIFADD breaking interface configuration sequence. See also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223129 for real world example. Is there a reason for such loopback routes to not have RTF_PINNED flag? From owner-freebsd-net@freebsd.org Fri Oct 20 20:42:23 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4A01E3F821 for ; Fri, 20 Oct 2017 20:42:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 D248B64F13 for ; Fri, 20 Oct 2017 20:42:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9KKgNJo020803 for ; Fri, 20 Oct 2017 20:42:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223129] Addition of an IP address to an interface (SIOCAIFADDR) fails when there is conflicting dynamic route Date: Fri, 20 Oct 2017 20:42:23 +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: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2017 20:42:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223129 --- Comment #1 from Eugene Grosbein --- Created attachment 187334 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D187334&action= =3Dedit proposed fix --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 20 20:43:15 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14E1AE3F8DB for ; Fri, 20 Oct 2017 20:43:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 02E0164FF1 for ; Fri, 20 Oct 2017 20:43:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9KKhE8n022461 for ; Fri, 20 Oct 2017 20:43:14 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 223129] Addition of an IP address to an interface (SIOCAIFADDR) fails when there is conflicting dynamic route Date: Fri, 20 Oct 2017 20:43:15 +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: 11.0-STABLE X-Bugzilla-Keywords: easy, patch-ready X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: eugen@freebsd.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords bug_status assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2017 20:43:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223129 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |easy, patch-ready Status|New |In Progress Assignee|freebsd-net@FreeBSD.org |eugen@freebsd.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 20 22:24:17 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0DC38E41B18 for ; Fri, 20 Oct 2017 22:24:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 F01B7684EA for ; Fri, 20 Oct 2017 22:24:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9KMOGTe049345 for ; Fri, 20 Oct 2017 22:24:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217606] Bridge stops working after some days Date: Fri, 20 Oct 2017 22:24:16 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kp@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2017 22:24:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217606 --- Comment #27 from Kristof Provost --- (In reply to punkt.de Hosting Team from comment #25) I'd try reverting this: https://svnweb.freebsd.org/base?view=3Drevision&revision=3D313050 and seein= g if you can reproduce it then. I do not understand how it'd trigger this, but the other major commit (https://svnweb.freebsd.org/base?view=3Drevision&revision=3Dr306289) should= only happen if you've got a filtering bridge and that's a fix for an mbuf leak. = This doesn't look like an mbuf leak. That said, considering that 11.0 is going out of support in five days I'd recommend just upgrading the box to 11.1. It'll have to be done soon anyway. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sat Oct 21 17:38:49 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 021BBE3476A for ; Sat, 21 Oct 2017 17:38:49 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BE27164AA4 for ; Sat, 21 Oct 2017 17:38:48 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id v9LHcdim035222; Sat, 21 Oct 2017 10:38:39 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id v9LHcboD035221; Sat, 21 Oct 2017 10:38:37 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201710211738.v9LHcboD035221@pdx.rh.CN85.dnsmgr.net> Subject: Re: loopback routes miss RTF_PINNED flag In-Reply-To: <59EA589D.7020403@grosbein.net> To: Eugene Grosbein Date: Sat, 21 Oct 2017 10:38:37 -0700 (PDT) CC: "freebsd-net@freebsd.org" X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2017 17:38:49 -0000 > Hi! > > When IP address is being added to an interface, a kernel installs loopback route. > For P2P interfaces, we have local IP address and remote one. > > A route to remote address is added with RTF_PINNED flag, > so that it overrides any possibly existing route to that address added > by a routing daemon and that's fine. > > A route to local address created with ifa_maintain_loopback_route() function in > https://svnweb.freebsd.org/base/head/sys/net/if.c?annotate=323170#l1711 > misess RTF_PINNED flag, so that it cannot override similar possibly existing route > and that's not fine as rtrequest1_fib() returns EEXIST in such case. > This error is then propagated back to userland ioctl SIOCAIFADD breaking > interface configuration sequence. See also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223129 > for real world example. > > Is there a reason for such loopback routes to not have RTF_PINNED flag? Is there a reason that the kernel is setting a policy at all? These _loopback_route routines are of dubious value and mostly interfere with anyone running a real routing protocol. My local tree removes this code. The reasons claimed to it being added was if you downed/upped an interface you lost these routes, which have traditionally been installed at boot time by /etc/netstart. IMHO this should be handled by code outside the kernel. The only value in these routes is that you pickup the MTU of lo0 for local sockets. Rather than my reversion method of fixing this, they could by wrapped in a #ifdef LO_ROUTES, with a sysctl inside that giving 3 ways to deal with them for everyone, GENERIC gets options LO_ROUTES, the sysctl defaults to on, leaving things as they are now, someone who wants these off but doesnt want to recompile can use the sysctl, and people like me who find this code of no value can remove the option from there kernel. Your propossed RTF_PINNED I think actually just aggrivates the problem with most routing daemons fighting the kernel on adding/removing these routes. bird is very noisy if you do not disable this code. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-net@freebsd.org Sat Oct 21 18:10:45 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB774E361BD for ; Sat, 21 Oct 2017 18:10:45 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7246A6578E for ; Sat, 21 Oct 2017 18:10:44 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v9LIATTn084958 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 21 Oct 2017 20:10:30 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: freebsd-rwg@pdx.rh.CN85.dnsmgr.net Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id v9LIAKV5056358 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 22 Oct 2017 01:10:20 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: loopback routes miss RTF_PINNED flag To: "Rodney W. Grimes" References: <201710211738.v9LHcboD035221@pdx.rh.CN85.dnsmgr.net> Cc: "freebsd-net@freebsd.org" From: Eugene Grosbein Message-ID: <59EB8D87.9080700@grosbein.net> Date: Sun, 22 Oct 2017 01:10:15 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <201710211738.v9LHcboD035221@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2017 18:10:46 -0000 22.10.2017 0:38, Rodney W. Grimes wrote: >> When IP address is being added to an interface, a kernel installs loopback route. >> For P2P interfaces, we have local IP address and remote one. >> >> A route to remote address is added with RTF_PINNED flag, >> so that it overrides any possibly existing route to that address added >> by a routing daemon and that's fine. >> >> A route to local address created with ifa_maintain_loopback_route() function in >> https://svnweb.freebsd.org/base/head/sys/net/if.c?annotate=323170#l1711 >> misess RTF_PINNED flag, so that it cannot override similar possibly existing route >> and that's not fine as rtrequest1_fib() returns EEXIST in such case. >> This error is then propagated back to userland ioctl SIOCAIFADD breaking >> interface configuration sequence. See also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223129 >> for real world example. >> >> Is there a reason for such loopback routes to not have RTF_PINNED flag? > > Is there a reason that the kernel is setting a policy at all? These > _loopback_route routines are of dubious value and mostly interfere > with anyone running a real routing protocol. In case of PPP interfaces, a pinned route to remote side of the interface it absolutely needed. And not only in such case. It was long period during which FreeBSD administrators and PPP daemons suffered from not being able to assign an address to an interface with ifconfig command or corresponding ioctl when there was conflicting dynamic route that had de-facto priority it should not have. With introduction of current RTF_PINNED semantics, this long-stanging problem finally gone. > My local tree removes this code. > > The reasons claimed to it being added was if you downed/upped an > interface you lost these routes, which have traditionally been > installed at boot time by /etc/netstart. Not only for this reason, see above. > IMHO this should be handled by code outside the kernel. Handled by what? Administrator should be able to override dynamic routes with basic system facilities. > Your propossed RTF_PINNED I think actually just aggrivates > the problem with most routing daemons fighting the kernel > on adding/removing these routes. > > bird is very noisy if you do not disable this code. quagga plays this just fine without noise. Routing daemons should learn to respect kernel-created pinned routes, not vice-versa. From owner-freebsd-net@freebsd.org Sat Oct 21 18:30:17 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9E2DE36AD6 for ; Sat, 21 Oct 2017 18:30:17 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C9E8666261 for ; Sat, 21 Oct 2017 18:30:17 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id v9LIUGx2035433; Sat, 21 Oct 2017 11:30:16 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id v9LIUG8U035432; Sat, 21 Oct 2017 11:30:16 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201710211830.v9LIUG8U035432@pdx.rh.CN85.dnsmgr.net> Subject: Re: loopback routes miss RTF_PINNED flag In-Reply-To: <59EB8D87.9080700@grosbein.net> To: Eugene Grosbein Date: Sat, 21 Oct 2017 11:30:16 -0700 (PDT) CC: "freebsd-net@freebsd.org" X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2017 18:30:18 -0000 [ Charset windows-1252 unsupported, converting... ] > 22.10.2017 0:38, Rodney W. Grimes wrote: > > >> When IP address is being added to an interface, a kernel installs loopback route. > >> For P2P interfaces, we have local IP address and remote one. > >> > >> A route to remote address is added with RTF_PINNED flag, > >> so that it overrides any possibly existing route to that address added > >> by a routing daemon and that's fine. > >> > >> A route to local address created with ifa_maintain_loopback_route() function in > >> https://svnweb.freebsd.org/base/head/sys/net/if.c?annotate=323170#l1711 > >> misess RTF_PINNED flag, so that it cannot override similar possibly existing route > >> and that's not fine as rtrequest1_fib() returns EEXIST in such case. > >> This error is then propagated back to userland ioctl SIOCAIFADD breaking > >> interface configuration sequence. See also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223129 > >> for real world example. > >> > >> Is there a reason for such loopback routes to not have RTF_PINNED flag? > > > > Is there a reason that the kernel is setting a policy at all? These > > _loopback_route routines are of dubious value and mostly interfere > > with anyone running a real routing protocol. > > In case of PPP interfaces, a pinned route to remote side of the interface > it absolutely needed. And not only in such case. It was long period > during which FreeBSD administrators and PPP daemons suffered from not being > able to assign an address to an interface with ifconfig command or corresponding ioctl > when there was conflicting dynamic route that had de-facto priority it should not have. > With introduction of current RTF_PINNED semantics, this long-stanging problem finally gone. I do not believe that is correct, ppp well work just fine without a loopback route to the remote ppp address, infact I would not want a loopback route to the remote ppp address as that prevents me from doing a ping test of the ppp link itself. _loopback_route installs a route the the LOCAL ip address via the lo0 interface and had better not be trying to do any remote addresses at all, or that is lot a loopback route but a very debuous short circuit route. # ifconfig tun0 tun0: flags=8051 metric 0 mtu 1426 options=80000 inet 192.168.128.10 --> 192.168.128.9 netmask 0xffffffff nd6 options=21 groups: tun Opened by PID 884 # route -n get 192.168.128.9 route to: 192.168.128.9 destination: 192.168.128.9 fib: 0 interface: tun0 flags: recvpipe sendpipe ssthresh rtt,msec mtu weight expire 0 0 0 0 1426 1 this is NOT a loopback route, this is a tun0 route. # ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=4219b ether 00:22:68:0b:54:01 inet 192.168.32.44 netmask 0xffffff00 broadcast 192.168.32.255 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active # route -n get 192.168.32.44 route to: 192.168.32.44 destination: 192.168.32.44 fib: 0 interface: lo0 flags: recvpipe sendpipe ssthresh rtt,msec mtu weight expire 0 0 0 0 16384 1 0 this IS a loopback route, not created by _loopback_route, but by bird, it would be the same if I was running with the _loopback_route code and not bird. > > > My local tree removes this code. > > > > The reasons claimed to it being added was if you downed/upped an > > interface you lost these routes, which have traditionally been > > installed at boot time by /etc/netstart. > > Not only for this reason, see above. "Claimed" as in I have found the original commit and read why it was done. That it has other effects are not part of that claim. > > > IMHO this should be handled by code outside the kernel. > > Handled by what? Administrator should be able to override dynamic routes > with basic system facilities. The problem is that this _loopback_route code places routing policy in the kernel that is not possible to override by any administrator or daemon, that is simply and fundamentally wrong no matter how correct the routes may be. > > > Your propossed RTF_PINNED I think actually just aggrivates > > the problem with most routing daemons fighting the kernel > > on adding/removing these routes. > > > > bird is very noisy if you do not disable this code. > > quagga plays this just fine without noise. I believe Quagga does not attempt to install the loopback routes unless you specifically configure it to do so. > > Routing daemons should learn to respect kernel-created pinned routes, not vice-versa. Um, kernels should NOT implement routing policy, in any way. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-net@freebsd.org Sat Oct 21 18:46:18 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D7FEEE36FA1 for ; Sat, 21 Oct 2017 18:46:18 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 838E86690B for ; Sat, 21 Oct 2017 18:46:16 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v9LIk7nZ085173 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 21 Oct 2017 20:46:08 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: freebsd-rwg@pdx.rh.CN85.dnsmgr.net Received: from [10.58.0.4] (dadv@[10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id v9LIk0aH066633 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 22 Oct 2017 01:46:00 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: loopback routes miss RTF_PINNED flag To: "Rodney W. Grimes" References: <201710211830.v9LIUG8U035432@pdx.rh.CN85.dnsmgr.net> Cc: "freebsd-net@freebsd.org" From: Eugene Grosbein Message-ID: <59EB95E8.1040807@grosbein.net> Date: Sun, 22 Oct 2017 01:46:00 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <201710211830.v9LIUG8U035432@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Spam-Status: Yes, score=5.5 required=5.0 tests=BAYES_00, DATE_IN_FUTURE_96_Q, LOCAL_FROM,RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 3.3 DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Flag: YES X-Spam-Level: ***** X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2017 18:46:19 -0000 22.10.2017 1:30, Rodney W. Grimes wrote: >>> Is there a reason that the kernel is setting a policy at all? These >>> _loopback_route routines are of dubious value and mostly interfere >>> with anyone running a real routing protocol. >> >> In case of PPP interfaces, a pinned route to remote side of the interface >> it absolutely needed. And not only in such case. It was long period >> during which FreeBSD administrators and PPP daemons suffered from not being >> able to assign an address to an interface with ifconfig command or corresponding ioctl >> when there was conflicting dynamic route that had de-facto priority it should not have. >> With introduction of current RTF_PINNED semantics, this long-stanging problem finally gone. > > I do not believe that is correct, ppp well work just fine without a > loopback route to the remote ppp address, infact I would not want > a loopback route to the remote ppp address as that prevents me > from doing a ping test of the ppp link itself. > _loopback_route installs a route the the LOCAL ip address via > the lo0 interface and had better not be trying to do any remote > addresses at all, or that is lot a loopback route but a very > debuous short circuit route. [skip] I have not said that pinnd route to remote side of the interface is loopback one, that would be plain wrong, as you have noted. I said that in face of PPP interface kernel creates two routes, one loopback and another one to the tunnel interface itself. Both of them should be allowed to override possibly already existing dynamic routes and RTF_PINNED solves this problem. And before RTF_PINNED introduction there were no solution, not to mention complex and not always possible dynamic route filtering. >>> IMHO this should be handled by code outside the kernel. >> >> Handled by what? Administrator should be able to override dynamic routes >> with basic system facilities. > > The problem is that this _loopback_route code places routing > policy in the kernel that is not possible to override by > any administrator or daemon, that is simply and fundamentally > wrong no matter how correct the routes may be. Hmm, why do you thing this is not possible? Of course, kernel supplies API (RTF_PINNED route option flag itself) to override pinned routes. How else PPP daemon or ifconfig/route commands would be allowed to manipulate such routes as they can now? This includes route removal. But route daemon should not override pinned routes that are pinned for the reason. If pinned route is not needed, it should not have been created in first place, I agree. But if it WAS created, it should have absolute priority over dynamic routes or we get into same old trouble solved with RTF_PINNED that I described earlier. >> Routing daemons should learn to respect kernel-created pinned routes, not vice-versa. > Um, kernels should NOT implement routing policy, in any way. I'm not sure I understand what is 'routing policy implemented with kernel' you talk about. From owner-freebsd-net@freebsd.org Sat Oct 21 20:16:29 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E94B6E38E2A for ; Sat, 21 Oct 2017 20:16:29 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CC06769CEC for ; Sat, 21 Oct 2017 20:16:29 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id v9LKGRbc035753; Sat, 21 Oct 2017 13:16:27 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id v9LKGPnh035752; Sat, 21 Oct 2017 13:16:25 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201710212016.v9LKGPnh035752@pdx.rh.CN85.dnsmgr.net> Subject: Re: loopback routes miss RTF_PINNED flag In-Reply-To: <59EB95E8.1040807@grosbein.net> To: Eugene Grosbein Date: Sat, 21 Oct 2017 13:16:25 -0700 (PDT) CC: "freebsd-net@freebsd.org" X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2017 20:16:30 -0000 I think we are talking either about 2 different issues, or we are having a very major breakdown in communications. I am going to try again to clarify what I have said and try to get a better picture of what you might be experiencing. > 22.10.2017 1:30, Rodney W. Grimes wrote: > > >>> Is there a reason that the kernel is setting a policy at all? These > >>> _loopback_route routines are of dubious value and mostly interfere > >>> with anyone running a real routing protocol. > >> > >> In case of PPP interfaces, a pinned route to remote side of the interface ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >> it absolutely needed. And not only in such case. It was long period > >> during which FreeBSD administrators and PPP daemons suffered from not being > >> able to assign an address to an interface with ifconfig command or corresponding ioctl > >> when there was conflicting dynamic route that had de-facto priority it should not have. > >> With introduction of current RTF_PINNED semantics, this long-stanging problem finally gone. > > > > I do not believe that is correct, ppp well work just fine without a > > loopback route to the remote ppp address, infact I would not want > > a loopback route to the remote ppp address as that prevents me > > from doing a ping test of the ppp link itself. > > _loopback_route installs a route the the LOCAL ip address via > > the lo0 interface and had better not be trying to do any remote > > addresses at all, or that is lot a loopback route but a very > > debuous short circuit route. > > [skip] > > I have not said that pinnd route to remote side of the interface is loopback one, > that would be plain wrong, as you have noted. Ok, but your proposed patch is changing a route to pinned, this is a local loopback route that well be via the lo0 interface. You mentioned "pinned rolute to remote side" which lead me down that path and to the above comment about it not beeing needed. > > I said that in face of PPP interface kernel creates two routes, one loopback > and another one to the tunnel interface itself. Both of them should be allowed > to override possibly already existing dynamic routes and RTF_PINNED solves this problem. I think I see what your getting to, your bringing up an interface that routes into a network that we have already learned about over some routing protocol. When the if comes up the maintain_loopback_route clashes with that route and you get a complaint, adding RTF_PINNED clears that issue up some how? > And before RTF_PINNED introduction there were no solution, not to mention complex > and not always possible dynamic route filtering. Um, I have been and still am routing with ppp and ethernet using the FreeBSD kernel since pre 1.0 without using RTF_PINNED, so I do not agree here. THere are solutions, infact it just works. > > >>> IMHO this should be handled by code outside the kernel. > >> > >> Handled by what? Administrator should be able to override dynamic routes > >> with basic system facilities. > > > > The problem is that this _loopback_route code places routing > > policy in the kernel that is not possible to override by > > any administrator or daemon, that is simply and fundamentally > > wrong no matter how correct the routes may be. > > Hmm, why do you thing this is not possible? I did not say it was not possible, I said that routing policy does not belong in the kernel. And I actually think part of what is causing you problems is the fact that it does. > Of course, kernel supplies API (RTF_PINNED route option flag itself) > to override pinned routes. How else PPP daemon or ifconfig/route commands > would be allowed to manipulate such routes as they can now? > This includes route removal. > > But route daemon should not override pinned routes that are pinned for the reason. > If pinned route is not needed, it should not have been created in first place, I agree. Ok, so why is it that these maintain_loopback_route routes are needed, the world works and lives fine without them, other than a minor in effecency in traffic to the local ip address of the interface. > > But if it WAS created, it should have absolute priority over dynamic routes > or we get into same old trouble solved with RTF_PINNED that I described earlier. That is a policy decision, your policy is that you want these kernel routes to take precedence over the dynamicly created ones, I want the ones that my bird configuration says that I want and unless I go ripe this code out of the kernel I can not get them cause the kernel keeps changing them back. > > >> Routing daemons should learn to respect kernel-created pinned routes, not vice-versa. > > Um, kernels should NOT implement routing policy, in any way. > > I'm not sure I understand what is 'routing policy implemented with kernel' you talk about. maintain_loopback_route adds routes to the kernel routing table, technically that is a routing policy. Let me try to get my proposal into a patch form and see if it doesnt solve your problem too. I have no issue with you adding RTF_PINNED to the route that is created now, as my solution just totally disables that code anyway.. that is if you want it disabled. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-net@freebsd.org Sat Oct 21 21:04:08 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BAEF2E3A33A for ; Sat, 21 Oct 2017 21:04:08 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4E7536BCB6 for ; Sat, 21 Oct 2017 21:04:07 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v9LL41J8086053 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 21 Oct 2017 23:04:02 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: freebsd-rwg@pdx.rh.CN85.dnsmgr.net Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id v9LL3qC0007116 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 22 Oct 2017 04:03:52 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: loopback routes miss RTF_PINNED flag To: "Rodney W. Grimes" References: <201710212016.v9LKGPnh035752@pdx.rh.CN85.dnsmgr.net> Cc: "freebsd-net@freebsd.org" From: Eugene Grosbein Message-ID: <59EBB633.2050201@grosbein.net> Date: Sun, 22 Oct 2017 04:03:47 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <201710212016.v9LKGPnh035752@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2017 21:04:08 -0000 22.10.2017 3:16, Rodney W. Grimes wrote: > I think we are talking either about 2 different issues, Yes, we are. I'm trying to solve a problem described in detail here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223129 >> I said that in face of PPP interface kernel creates two routes, one loopback >> and another one to the tunnel interface itself. Both of them should be allowed >> to override possibly already existing dynamic routes and RTF_PINNED solves this problem. > > I think I see what your getting to, your bringing up an interface that > routes into a network that we have already learned about over some > routing protocol. Exactly. Plus, local address of the PPP interface also conflicts with dynamic route. > When the if comes up the maintain_loopback_route > clashes with that route and you get a complaint, adding RTF_PINNED > clears that issue up some how? Exactly. RTF_PINNED signals kernel to override dynamic route: kernel atomically deletes dynamic route and installs its own pinned route. Without RTF_PINNED flag, dynamic route persists, IP address configuration fails with EEXIST, so PPP daemon fails to setup the tunnel. >> And before RTF_PINNED introduction there were no solution, not to mention complex >> and not always possible dynamic route filtering. > > Um, I have been and still am routing with ppp and ethernet using > the FreeBSD kernel since pre 1.0 without using RTF_PINNED, so I > do not agree here. THere are solutions, infact it just works. It works in some configurations only. It does not work in others. For example, it is not possible to filter OSPF routes inside single OSPF area. One cannot filter out dynamic route and needs a way to override it. This is consistent with other router implementations like Cisco: one always can configure and have "connected" route with administrative distance 0 despite of presence of any other routes (except of another "connected" interface). >> But route daemon should not override pinned routes that are pinned for the reason. >> If pinned route is not needed, it should not have been created in first place, I agree. > > Ok, so why is it that these maintain_loopback_route routes are needed, > the world works and lives fine without them, other than a minor > in effecency in traffic to the local ip address of the interface. I would be totally fine with any other solution instead of loopback route that gives me standard features: 1. Routing daemon has "something" instead of loopback route to redistribute prefix created with another part of a system like PPP daemon or just "ifconfig" command. 2. Traffic to local IP address goes through loopback interface, that is: - it is seen with "tcpdump -i lo0" (bpf "sees" it within lo0) - it is matched with packet filter rule like "ipfw allow ip from any to any via lo0" And I'm not saying this should be same for everyone. I'm just saying new code should make it possible to use these features as they are very useful. If new code allows administrator to optionally break this, that's fine until it is an option and defaults do not break POLA. >> But if it WAS created, it should have absolute priority over dynamic routes >> or we get into same old trouble solved with RTF_PINNED that I described earlier. > > That is a policy decision, your policy is that you want these kernel > routes to take precedence over the dynamicly created ones, I want > the ones that my bird configuration says that I want and unless I > go ripe this code out of the kernel I can not get them cause the > kernel keeps changing them back. I see. You are just happy without loopback routes, you need not traffic to local addresses go through loopback interface, and you was never hit by a problem that gave birth to pinned routes. I struggled with that problem for years hoping that one day "ifconfig vlan100 X.X.X.X/24" would just work no matter if local routing daemon installed this prefix to the routing table already, or not. So, I'm just happy with pinned routes and want them more :-)