From nobody Wed Aug 17 20:12:14 2022 X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4M7K1q303zz4Z8t2 for ; Wed, 17 Aug 2022 20:12:31 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gold.funkthat.com [IPv6:2001:470:800b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4M7K1p2t03z4QfX for ; Wed, 17 Aug 2022 20:12:30 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id 27HKCHAW063495 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 17 Aug 2022 13:12:17 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id 27HKCExg063487; Wed, 17 Aug 2022 13:12:14 -0700 (PDT) (envelope-from jmg) Date: Wed, 17 Aug 2022 13:12:14 -0700 From: John-Mark Gurney To: Milan Obuch Cc: freebsd-net@freebsd.org Subject: Re: Tunnel interfaces and vnet boundary crossing Message-ID: <20220817201214.GZ88842@funkthat.com> Mail-Followup-To: Milan Obuch , freebsd-net@freebsd.org References: <20220815085303.2c5cdb02@zeta.dino.sk> List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220815085303.2c5cdb02@zeta.dino.sk> X-Operating-System: FreeBSD 11.3-STABLE amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Wed, 17 Aug 2022 13:12:17 -0700 (PDT) X-Rspamd-Queue-Id: 4M7K1p2t03z4QfX X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of jmg@gold.funkthat.com has no SPF policy when checking 2001:470:800b::2) smtp.mailfrom=jmg@gold.funkthat.com X-Spamd-Result: default: False [-1.80 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[jmg@funkthat.com,jmg@gold.funkthat.com]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-net@freebsd.org]; R_DKIM_NA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FROM_NEQ_ENVFROM(0.00)[jmg@funkthat.com,jmg@gold.funkthat.com]; FREEFALL_USER(0.00)[jmg]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[funkthat.com]; TO_DN_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Milan Obuch wrote this message on Mon, Aug 15, 2022 at 08:53 +0200: > I tried to mimic this in FreeBSD with following commands: > > ifconfig gre1 create tunnel 172.16.1.1 172.16.0.1 vnet ov1 > jexec ov1 ifconfig gre1 10.1.0.2/30 10.1.0.1 > > This does not work. I found some older post which made me believing > this is caused by clearing whole tunnel configuration after moving > interface into different vnet. My (failed) tests indicate this is most > probably the cause. > > So, my question is, does anybody use tunnel interface similar way? Is > it possible to achieve what I am trying with netgraph? I am able to > create some inter-vnet link using epair interface, but this is > something different. Or ideally, is somebody using IPSEC with VNET > jails, processing encapsulating packets in base and raw content in some > child vnet? This doesn't work since the tunnel interface needs to see the interface with the IP to route it to, and since it's in another jail/vnet, it can't get there. The closes thing I can think of is putting an epair in w/ the tunnel interface, and routing the tunnel out of the vnet via the epair interface... Does this make sense? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."