Date: Sun, 29 Nov 2020 11:10:50 +0100 From: Michael Gmelin <freebsd@grem.de> To: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> Cc: Jason Barbier <jason@corrupted.io>, freebsd-virtualization@freebsd.org Subject: Re: bhyve with wlan0 Message-ID: <87D4E1D7-7CC2-4935-9457-CC16FF2DDD43@grem.de> In-Reply-To: <202011281830.0ASIUMAg037287@gndrsh.dnsmgr.net> References: <202011281830.0ASIUMAg037287@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 28. Nov 2020, at 19:30, Rodney W. Grimes <freebsd-rwg@gndrsh.dnsmgr.net> wrote: > > >> >> As far as I remember it works just fine other than the standard caveats about bridging over wireless interfaces which involve some odd inconsistencies that could crop up from time to time especially with like DHCP, but a lot of that depends on your network config as a whole. >> The approach I would consider taking for a wireless host is if the guest doesn't need direct access to the network just do a NAT network or a routed network and route through the wlan interface instead of trying to do bridging with it directly. > > One very problematic area for wireless and bhyve is that each guests have a different MAC, wireless does NOT like that, as the AP usually associates with one and only one MAC address. > Like Jason wrote, it‘s best to use NAT on wireless (especially if you’re moving between networks frequently). Using something like vm-bhyve, it’s very easy to set up. -m
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87D4E1D7-7CC2-4935-9457-CC16FF2DDD43>