* Chavdar Ivanov (ci4...@gmail.com) wrote:
> You have to select "Advanced" and then "Adapter type" - paravirtualized, if
> you want to try vioif0. [image: VirtualBox_2017-07-01_20-33-55.png]
* Robert Elz (k...@munnari.oz.au) wrote:
> That is the wrong place to look - that list is of where your vi
Date:Sun, 2 Jul 2017 01:10:43 +0700
From:Gua Chung Lim
Message-ID: <20170701181043.ga...@gmail.com>
| Yes, I have tried that it has no effects. IPv6 is still OK.
OK.
| I even tried correct ssid but invalid psk, there is no effect.
Once again, ssid is a wireless
You have to select "Advanced" and then "Adapter type" - paravirtualized, if
you want to try vioif0. [image: VirtualBox_2017-07-01_20-33-55.png]
On Sat, 1 Jul 2017 at 19:10 Gua Chung Lim wrote:
> Thank you very much for you responding my questions.
>
> * Robert Elz (k...@munnari.oz.au) wrote:
>
Thank you very much for you responding my questions.
* Robert Elz (k...@munnari.oz.au) wrote:
> 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_supp
vioif0 - by mistake repeated the name in virtualbox form. I haven't had
much problems, except that on occasion the log gets some timeout messages,
but otherwise the connectivity remains OK.
Chavdar
On Sat, 1 Jul 2017 at 13:26 Robert Elz wrote:
> Date:Sat, 01 Jul 2017 09:43:16 +
Date:Sat, 01 Jul 2017 09:43:16 +
From:Chavdar Ivanov
Message-ID:
| 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 virtio
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 s
Date:Wed, 28 Jun 2017 23:37:54 +0700
From:Gua Chung Lim
Message-ID: <20170628163753.ga1...@gmail.com>
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
* m...@netbsd.org (m...@netbsd.org) wrote:
> > % ifconfig wm0
> > wm0: flags=8843 mtu 1500
> wm0 is a wired driver (you can see what it is for by 'man 4 wm' - Intel
> ethernet cards).
Thanks for info.
> I suspect NetBSD doesn't support the network card on your laptop, most
> Broadcom wifi cards do
On Wed, Jun 28, 2017 at 11:37:54PM +0700, Gua Chung Lim wrote:
> % ifconfig wm0
> wm0: flags=8843 mtu 1500
wm0 is a wired driver (you can see what it is for by 'man 4 wm' - Intel
ethernet cards).
I suspect NetBSD doesn't support the network card on your laptop, most
Broadcom wifi cards do not wor
Hi,
I'm running NetBSD 7.1_STABLE as a guest behind VirtualBox.
My machine is MacBook Air 11" mid 2013 running macOS Sierra 10.12.5 as a host.
I set VM network to bridge and login WPA2 (my local wifi network).
I'm not sure if NetBSD 7.1 fully supports Mac's NIC.
wm0 is for connecting outside world
11 matches
Mail list logo
