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: >=20 > =EF=BB=BF >>=20 >> As far as I remember it works just fine other than the standard caveats a= bout bridging over wireless interfaces which involve some odd inconsistencie= s that could crop up from time to time especially with like DHCP, but a lot o= f that depends on your network config as a whole.=20 >> The approach I would consider taking for a wireless host is if the guest d= oesn't need direct access to the network just do a NAT network or a routed n= etwork and route through the wlan interface instead of trying to do bridging= with it directly. >=20 > 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 wi= th one and only one MAC address. >=20 Like Jason wrote, it=E2=80=98s best to use NAT on wireless (especially if yo= u=E2=80=99re moving between networks frequently). Using something like vm-bh= yve, it=E2=80=99s 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>