nmcli loosing connectivity

[panina]

Hello

I've been using Qubes as my everyday OS for a month or so.
During the whole time I've had a lot of wifi issues. I'm guessing it
might be some problem with the passthrough, but am not sure.

What usually happends is that the system looses connectivity from time
to time. Sys-net reports the wifi as connected, but cannot ping my
gateway. The solution is to use nmcli to bring the connection down, and
up again. This will most of the time bring up the connectivity again.
Restarting the NetworkManager service does not help.

Does anyone recognize this issue, and does anyone have ideas on how to
find the bug?

My system is an AMD Lenovo Thinkpad A485, and my WiFi card is an Realtek
RTL8822BE.
The WiFi works fine under basic Fedora.

Grateful for any ideas, and just ask for more info (eg logs) if needed

<3
/panina

[awokd]

panina:

> What usually happends is that the system looses connectivity from time
> to time. Sys-net reports the wifi as connected, but cannot ping my
> gateway. The solution is to use nmcli to bring the connection down, and
> up again. This will most of the time bring up the connectivity again.
> Restarting the NetworkManager service does not help.

Try swapping your sys-net template from Fedora to Debian or vice-versa.
Sometimes one distro will handle a wifi card better than another.

[panina]

Brilliant idea!
But sadly turned out to be mainly informative. Debian doesn't see the
wifi card at all, it only works on fedora 29 & 30 (not 28). But I've
tried fedora 29 & 30 baremetal on this machine, and this doesn't happen
there. So it is either Qubes- or Xen-specific.

Any other ideas are welcome.

<3
/panina

[awokd]

panina:

> But sadly turned out to be mainly informative. Debian doesn't see the
> wifi card at all, it only works on fedora 29 & 30 (not 28). But I've
> tried fedora 29 & 30 baremetal on this machine, and this doesn't happen
> there. So it is either Qubes- or Xen-specific.

You might need to install the Realtek firmware package in the Debian
template. I wouldn't be too hasty to rule out Fedora; I've seen a number
of bugs filed against Network Manager + wifi on 29 & 30. Did you run it
baremetal as long as you have in Qubes?

[0brand]

> Brilliant idea!
> But sadly turned out to be mainly informative. Debian doesn't see the
> wifi card at all, it only works on fedora 29 & 30 (not 28). But I've
> tried fedora 29 & 30 baremetal on this machine, and this doesn't happen
> there. So it is either Qubes- or Xen-specific.
>
> Any other ideas are welcome.
>

Your wifi driver might not be availble in Debian 10. You need to find
out the wifi card you are using and check to see if it is supported in
Debian (buster, testing, unstable)

https://packages.debian.org/buster/firmware-iwlwifi
https://packages.debian.org/bullseye/firmware-iwlwifi
https://packages.debian.org/sid/firmware-iwlwifi

Step 1)

If supported in Debian buster.

sudo apt-get install iwlwifi

If supported in bullseye (debian testing)

See:

https://www.whonix.org/wiki/Install_Software#Install_from_Debian_Testing

If supported in sid (debian unstable)

See:

https://www.whonix.org/wiki/Install_Software#Install_from_Debian_Unstable

Step 2)

Find the correct pci (wifi) device to attach to the the sys-net VM.

https://www.qubes-os.org/doc/pci-devices/













--
GPG Public Key: 0xCFDBC23923C0433B
Fingerprint: B67C 6FE6 4BAE 05CD 05ED 775D CFDB C239 23C0 433B