Re: wpa_supplicant error on mac

I could add that you could modify the type of the emulated interface in Virtual Box settings and use the paravirtualized interface virtio, which will be seen in your NetBSD VM as virtio0. This allegedly should work faster, although I haven't gone through any benchmarks, but my VMs with this setup seem to be working fine.

I have only one problem presently with such a setup - when I use a bridged through wireless interface NetBSD VM and I connect it to a physical NetBSD machine attached to the same wireless network, I lose the connectivity between the NetBSD physical machine and the (Windows 10 in my case) Virtual Box host. I just have to ssh through another NetBSD machine connected to the wired interface of the same WiFi spot and from there to the other NetBSD machine and clear the arp cache.

Chavdar

On Sat, 1 Jul 2017 at 10:17 Robert Elz <kre%munnari.oz.au@localhost> wrote:

Date: Wed, 28 Jun 2017 23:37:54 +0700
From: Gua Chung Lim <ptkrisada%gmail.com@localhost>
Message-ID: <20170628163753.GA1396%gmail.com@localhost>

To expand on what maya@ said earlier...

| But I can use wm0 pretty fine both IPv4 and IPv6.
| I'm curious to know what this error means and how to fix it.

Aside from turning off wpa_supplicant, as in:

| wpa_supplicant=YES

wpa_supplicant=NO

instead, there is nothing to fix.

VirtualBox doesn't emulate any wireless networks, your NetBSD has no
wireless interface configured, as maya said, wm0 is a wired interface
(in this case, an emulated wired interface).

The network map, if you like, is that your netbsd system has a wired
ethernet connected to your macos host, which is bridging that wired
network to a wireless network.

You don't have to (in fact, you cannot) on NetBSD configure or control
in any way, any of the wireless parameters. That's all done on the
host (MacOS in your case) where the wireless interface exists.

So there is nothing (real) to fix, nothing to do, it should all just work.

And if for some reason it doesn't, you can always use a virtualbox NAT
configured network instead (though I have no idea how that would work
for IPv6.)

kre