Network hardware not recognized in Debian-based NetVM

[Joshua Bashir Gabriel]

Hello,

Although the default NetVM in Qubes is based on Fedora, I wanted to be able to use NetworkManager 1.4.2 to automatically spoof my MAC address when connecting to networks. In order to do this, I followed the instructions here:

https://www.qubes-os.org/doc/anonymizing-your-mac-address/

I created a new template for Debian 9 as instructed, then created a new NetVM from that template and added the Network Connections app to it, as well as my WiFi adapter (under the Devices tab).

However, the Debian-based NetVM will not see the hardware. The Fedora-based NetVM can see it fine, but when I power that down and power up the Debian-based VM, no such luck.

I am running Qubes 3.2 with all the latest updates applied. This email was sent from a Firefox session inside a disposable VM, so I know using the Fedora-based NetVM works. I also created additonal NetVMs based on Fedora, Debian 8, and Debian 9. The Debian-based NetVMs do not see my WiFi card. The Fedora-based NetVM does.

Any advice would be very appreciated.

Thanks,

Bash

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Perhaps you have the required drivers in your Fedora template but not
your Debian template. You may want to investigate whether they're
available in a Debian package.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYdrEHAAoJENtN07w5UDAweZMP/jdYXuWNLHJ4oxdan5YOWimx
OltWijWNGkUjmA0D//hpSso8UAro8eBK2sWj0CcH0qlRi25gD7Dvpf4ufscd2X9S
O1kZ6ztq2rQKy8A87HWO/vTd5MR8Wu4meYOZtOJ7PHwkzZb/6x0v9QSoqwMDE5Xu
yAKpCV1LY5WdsFTlAi75vcPmiUKpmPcuCmhuD+2Y89Y83jEKJpAR0OxqVnEt/XQp
vorA5IIFvp7DN+mPnVloFS430JgEWCziM6WW1rMUvnXjU1sveVjtFFs+aU02BOPa
vRPOGDw7IzULN+NiZp3i1L/93dKkxEihoqm3ebwYSl0hGc9mxhyyRkDc6TP0NvxL
/oUe47FY3ieqgt95drE9icX2kNlF+46xkh42dSZuMU4/9FTaSqTDiE1OvEEhvzxq
qBPTwG+pRwRTmVqTZTE7PrYnQJX09hMj9BgleMwdt9NkJfh4A3NhNd8ZPYaImwDR
vlBPGqNLlsThvE12GJTpmE+Ct+93x5EmF7AcRNkpeJK51jN1GzqZ/pR0rGjjISBT
JNdtX9nfYbJCTLdL3T2RqF8F9fOY+OuMGY3DS5y0VR51kG88oQa0uKM+aA5ynAFJ
aa4TxYNHKA1tKzU7FFa6hD1EgR6/gGVMeqI32xDS3dFLcEhMH/oXoaTVcE5jtLX1
27Q0w19AY1LSWluGcrmF
=/OP4
-----END PGP SIGNATURE-----

[Joshua Bashir Gabriel]

Update: Got it working. It needed the wifi drivers for Debian 8/9, as well as a couple of other utilities, found here: https://wiki.debian.org/WiFi.

Also, I added the client for PrivateInternetAccess.com to the Net VM so I have a single netvm with always-on VPN. 

Cheers,

Bash

[Chris Laprise]

On 01/17/2017 06:49 PM, 'Joshua Bashir Gabriel' via qubes-users wrote:
> Update: Got it working. It needed the wifi drivers for Debian 8/9, as
> well as a couple of other utilities, found here:
> https://wiki.debian.org/WiFi.
>
> Also, I added the client for PrivateInternetAccess.com to the Net VM
> so I have a single netvm with always-on VPN.
>
>
> Cheers,
> Bash

> --

Just FYI, configuring VPN in sys-net is not recommended because NetVMs
are generally untrusted. Its better to configure a proxyVM to manage VPN
connections.

Also, those vendor-supplied packages are not usually equipped to block
leaks in a Qubes network environment (i.e. where the VPN client
essentially runs in an isolated 'router'); They are designed to block
leaks originating with locally-running apps, so their assurances of
stopping leaks probably won't hold in Qubes.

For a secure Qubes configuration, see
https://www.qubes-os.org/doc/vpn/#set-up-a-proxyvm-as-a-vpn-gateway-using-iptables-and-cli-scripts

Chris