No network devices despite sys-net having them attached

After a fresh install of Qubes OS, there are no network devices listed in the little networking icon in the top right of the screen. Looking at sys-net’s settings, it appears that the 2 ethernet adapters are correctly attached to it; one adapter should be connected to my home router and a device does show up from ip a within sys-net but there’s no internet connectivity.

I’m not sure how to start troubleshooting this. From other topics I’ve browsed, it could be an issue of missing drivers. At least, the driver for my ethernet devices should be bnx2 and lsmod | grep bnx2 from within sys-net outputs nothing. I’m not sure how to go about installing those drivers if so since there’s no internet connectivity to be used to download them. For debian it looks like they’re in the package firmware-bnx2. Would I need to manually download the .deb and install it on sys-net?

1 Like

Which template do you use for sys-net?

1 Like

debian-12-xfce

1 Like

Can you elaborate on this:

?

Is it an ip addr show in sys-net that shows an IP/subnet that matches your home router? What do you get with a

ip route show

in sys-net? - does that match your home router? If so, can you ping the IP of your home router from sys-net?

Of interest - and only slightly related to the topic: Did you only install “debian-12-xfce” … or did you also install “fedora-??-xfce” as template? If you also have a Fedora template, could you try starting sys-net based of Fedora?

:slight_smile:

(forgot to say: thanks for the responses)

Actually ip a doesn’t show an IP/subnet for my home network (10.0.0.0/24); it’s unreachable. I’m also now confused by the output of ip r since I don’t know where the one route came from. Please see the attached image.

I did try using the fedora template but there are still no network devices listed on the little red networking icon, and within it ip a only shows the loopback interface.

The vif3.0 you see, is the internal “device”, that eg. sys-firewall will connect to – if you run ip route show in a terminal from sys-firewall, I expect you’ll see something like:

default via 10.137.0.6 dev eth0 onlink

(?)

Could you try to run lspci in sys-net?

What do you get, if you run sudo dmesg -T | grep bnx in sys-net?

:slight_smile:

Thanks for the explanation; the IP in the route in the image is just the IP of the sys-firewall so that makes sense.

lspci is apparently not installed in the debian template but here’s (hopefully) a list of the devices:

And sudo dmesg | grep bnx produces no output.

If you switch the template for sys-net to Fedora (for debugging), do you then have lspci?

:slight_smile:

Yes; here’s the output:


The two ethernet devices show up.

FWIW, also: grepping dmesg output for driver-related stuff doesn’t seem to turn up anything.

Some random searching on the net, suggest to try:

lspci -nnk | grep NetXtreme

… I don’t know if that will give some hint?

:slight_smile:

Unfortunately that yields no new info. After googling around it seems that at some point there could have been issues in fedora/debian with broadcom and tg3 modules being loaded in the wrong order or not at all, but I tried doing so manually and still get the same errors in dmesg output. If anyone runs into this issue, see this about broadcom adapters and hopefully that might lead you down a good track.

I ended up just buying a cheap realtek GbE adapter and whatever drivers in the debian template worked. Thanks for the help anyway.