Date: Wed, 21 Oct 2020 13:57:45 +0200 From: "Kristof Provost" <kp@FreeBSD.org> To: "Patrick M. Hausen" <hausen@punkt.de> Cc: "Andrea Venturoli" <ml@netfence.it>, freebsd-net@freebsd.org Subject: Re: Help with VNET Message-ID: <704712D8-5013-491B-B720-F7E76A7ABFD6@FreeBSD.org> In-Reply-To: <136B0049-8F69-4CED-91DD-C3F6D9EAC9A5@punkt.de> References: <dcbec45d-90e4-fe45-e413-e94799bcffdc@netfence.it> <40361B2B-50AD-474B-A5A7-654F5A958FE2@FreeBSD.org> <799e33d6-c286-3a06-19e1-af87b541645a@netfence.it> <AE406529-7111-4B40-A940-15B060512504@FreeBSD.org> <136B0049-8F69-4CED-91DD-C3F6D9EAC9A5@punkt.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 Oct 2020, at 13:50, Patrick M. Hausen wrote: > Hi all, > >> Am 21.10.2020 um 13:37 schrieb Kristof Provost <kp@FreeBSD.org>: >> >> On 21 Oct 2020, at 13:36, Andrea Venturoli wrote: >>> On 10/21/20 12:20 PM, Kristof Provost wrote: >>> >>>> This is your problem. You can’t bridge over wifi interfaces. >>>> That’s a limitation of station mode wifi. >>> >>> I had the suspect... >>> Is this documented somewhere? Is this a bug or feature? >>> >> That’s inherent to how wifi is designed. It’s arguably a bug, but >> if so it’s one in the 802.11 spec, not in the implementation. > > Well, VMware Workstation and Fusion can do it. > But they rewrite MAC addresses or some such - it's ugly. > Yeah, L2 NAT is the hack to work around that limitation. But … No. Just … No. I also don’t think we have a layer-2 NAT solution in FreeBSD. I have a vague recollection of OpenBSD doing something with L2 and pf (or something that looks like pf on L2), but I can’t immediately find that again. Kristof
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?704712D8-5013-491B-B720-F7E76A7ABFD6>