No network connection

[DVM]

I see the following in the logs:

sys-net kernel: r8169 0000:00:06.0 ens6: No native access to PCI extended config space, falling back to CSI
sys-net kernel: r8169 0000:00:06.0 ens6: Link is Down

Can you open a dom0 terminal and run this command:

qvm-pci ls

Do you have (no-strict-reset=True) on the same line of your network controller?

If not, then turn off sys-net and run these commands:

qvm-pci detach sys-net dom0:<pci slot>
qvm-pci attach --persistent --option no-strict-reset=True sys-net dom0:<pci slot>
# Should be something like dom0:06_00.0
# Check the line of your network controller from the qvm-pci output

Then start sys-net and check if you have a network connection.

[bcz]

I didn’t have (no-strict-reset=True) so i followed all steps but i still don’t have internet connection. I ran qvm-pci ls again and now have the (no-strict-reset=True).

[bcz]

[DVM]

If you run the journalctl -b command again in sys-net, are you able to see the lines of my previous answer?

sudo journalctl -b | grep -Ei "No native access|Link is Down"

[bcz]

Yes, i see.

[DVM]

Turn off sys-net and let’s try with an extra option for the network controller:

# In a dom0 terminal
qvm-pci detach sys-net dom0:<pci slot>
qvm-pci attach --persistent --option permissive=True --option no-strict-reset=True sys-net dom0:<pci slot>

[bcz]

I ran these commands but still no network connection. This problem is strange

[DVM]

Strange. Have you tried connecting manually instead of using DHCP with Network Manager?

[DVM]

Also, can you run this in sys-net and share the output:

ethtool -i ens6

[bcz]

Yes, already tried but didn’t worked too. Im about to give up of use Qubes in that Desktop. I mean, i already spended so much time and didn’t used my PC yet. Thanks for all your effort and attention to help me, really appreciate it. But i think that the best solution for me is just use Qubes in another Desktop.

[bcz]

Yes, i can.

[DVM]

You could also try an external driver. I’m not sure if it supports your current network controller, but it’s worth a try:

GitHub - lwfinger/rtw89: Driver for Realtek 8852AE, an 802.11ax device

If you want to try it out, you need to install everything in the template.
Follow that part of the installation.
Also, make sure to blacklist the other driver, as it was done here.

[bcz]

Will take a look. Thanks!

[bcz]

The internet back to work here. Sys-net now have internet connection, i can connect to whonix and use the internet through whonix. But when i use clearnet (sys-firewall NetVM), i still doesn’t have internet acess. You know what i can do?

[DVM]

The driver worked?
When you say you have no Internet connection, what have you tried?
Are you able to ping an external IP like 1.1.1.1 from sys-firewall?

[bcz]

Yes, the driver worked. I have tried to install softwares with apt and tried to use firefox. None of them has network access. After i set the NetVM to “sys-whonix” i received internet connection.

And yes, im able to ping IPs.

[bcz]

user@personal:~$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=8.16 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=8.38 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=8.35 ms
^C
— 1.1.1.1 ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 8.163/8.297/8.380/0.095 ms
ping status

When i try to install some software with apt, i get stuck on “0% connecting”
user@personal:~$ sudo apt install redshift
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following additional packages will be installed:
geoclue-2.0 iio-sensor-proxy
The following NEW packages will be installed:
geoclue-2.0 iio-sensor-proxy redshift
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 272 kB of archives.
After this operation, 1,274 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Ign:1 Index of /debian bookworm/main amd64 geoclue-2.0 amd64 2.6.0-2
0% [Connecting to deb.debian.org]
Like that

[DVM]

Then it seems to be a DNS problem.
Can you run these commands in sys-net and share the output?

sudo nft list chain ip qubes dnat-dns
sudo cat /etc/resolv.conf

[bcz]

Here:
user@sys-net:~$ sudo nft list chain ip qubes dnat-dns
table ip qubes {
chain dnat-dns {
type nat hook prerouting priority dstnat; policy accept;
}
}
user@sys-net:~$ sudo cat /etc/resolv.conf

Generated by NetworkManager

nameserver 192.168.18.1
nameserver fe80::1%ens6
user@sys-net:~$

[DVM]

That’s probably why it doesn’t work, the chain is empty.

Try this command in sys-net:

sudo /usr/lib/qubes/qubes-setup-dnat-to-ns

Then try to ping a domain from sys-firewall, like qubes-os.org.