From owner-freebsd-net@freebsd.org Tue Mar 2 02:33:45 2021 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F0CA4556B7A for ; Tue, 2 Mar 2021 02:33:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DqLm96Kphz4hfx for ; Tue, 2 Mar 2021 02:33:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id D942D556AE6; Tue, 2 Mar 2021 02:33:45 +0000 (UTC) Delivered-To: net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D90CB556D54 for ; Tue, 2 Mar 2021 02:33:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DqLm95lK9z4hjn for ; Tue, 2 Mar 2021 02:33:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B848A6E2C for ; Tue, 2 Mar 2021 02:33:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 1222Xj1t074048 for ; Tue, 2 Mar 2021 02:33:45 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 1222XjxT074047 for net@FreeBSD.org; Tue, 2 Mar 2021 02:33:45 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 248474] if_ipsec: NAT broken on IPsec/VTI Date: Tue, 02 Mar 2021 02:33:44 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: Unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jeremy.mordkoff@riftio.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.34 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, 02 Mar 2021 02:33:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D248474 jeremy.mordkoff@riftio.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremy.mordkoff@riftio.com --- Comment #35 from jeremy.mordkoff@riftio.com --- (In reply to Andrey V. Elsukov from comment #17) I have a VTI routed tunnel already to another PF Sense. LAN to LAN, no NAT, wide open firewall rules. Bi directional traffic. Works fine.=20 I was trying to create a second VTI tunnel to a different server, but this = one needed SNAT. It is outbound only. The new tunnel was dropping all replies. I could see them arrive on the ipsec* interface but they never exited the rou= ter on the LAN interface.=20 These sysctl changes allowed the new tunnel to work, but they half-break the existing LAN to LAN tunnel. Hosts on the "CORE" side where I made these sys= ctl changes can still reach systems in the remote LAN, but the remote LAN cannot access the core LAN. Again, they arrive on ipsec* but they never exit the L= AN port.=20 (a) Is there a way to have he best of both worlds? I suspect not.=20 (b) Is there a way to configure the old LAN to LAN tunnel such that inbound traffic will flow again? --=20 You are receiving this mail because: You are the assignee for the bug.=