Qubes 3.2: No Internet Connection, neither with Wi-Fi, neither with Ethernet. HELP PLEASE!

[helpp...@vfemail.net]

THIS CONCERNS QUBES 3.2 (latest update, downloaded from the website 3
days ago).
________________________________________________________________________________

PROBLEM: Internet connection does not work, neither with Wi-Fi once
connected to my home router, neither with Ethernet (which Qubes can't
even detect if the cable is plugged in or not, it permanently displays
"Disconnected").


EXPECTED BEHAVIOR:
1-Once the ethernet cable is plugged in the proper ethernet port of
the computer, it should display "Connection Established" with a
notification in top right corner;
2-Once the Wi-fi is "Connected", I should be able to ping google.com
with the command "ping google.com -c 5" inside the sys-net terminal.

ACTUAL BEHAVIOR:
1-Once the ethernet cable is plugged in, absolutely nothing happens.
And on system boot, once the desktop is loading (and if Wi-Fi is
disconnected), the notification "Disconnected - the network connection
has been disconnected" appears in the top right corner.
2-Once the wi-fi connection is established (without any problems at
all), it simply doesn't work, like if it was disconnected. In fact
when I go to sys-net terminal and execute the command "ping google.com
-c 5" it waits a few seconds before displaying "ping: unknown host
google.com".

WHAT YOU SHOULD KNOW, AND WHAT I HAVE TRIED:
1-The ethernet cable, Wi-Fi card, Ethernet card, of the computer are
all perfectly working;
2-Both Ethernet and Wi-fi cards are attached to sys-net VM, under
'devices' as it should be;
3-Both the Wi-Fi card and the Ethernet card are recognized by Qubes,
in fact, here's the output of 2 known commands:

"ifconfig" output below. NOTE: I MODIFIED the inet6 address, and the
ethernet addresses from "Vif2.0" and "wlp0s1" respectively, I would
prefer to keep them private. :

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask
255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1
(Local Loopback) RX packets 36 bytes 4008 (3.9 KiB) RX errors 0
dropped 0 overruns 0 frame 0 TX packets 36 bytes 4008 (3.9 KiB) TX
errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vif2.0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet
10.137.1.1 netmask 255.255.255.255 broadcast 0.0.0.0 inet6
fd72::dasd:sdas:gfgd:gffw prefixlen 64 scopeid 0x20<link> ether
dt:fd:nb:qw:as:fd txqueuelen 32 (Ethernet) RX packets 130 bytes 6464
(6.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 44 bytes
2472 (2.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlp0s1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet
192.168.178.76 netmask 255.255.255.0 broadcast 192.168.178.255 inet6
og45::9n32:j7qq:ofk4:pd92 prefixlen 64 scopeid 0x20<link> ether
x3:p8:l0:b7:po:33 txqueuelen 1000 (Ethernet) RX packets 238 bytes
56207 (54.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets
278 bytes 27217 (26.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0
collisions 0

"lspci" output below. NOTE: I MODIFIED the Ltd. RTL identification
strings, I would prefer to keep them private. :

00:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL0000/0000/0000 PCI Express Gigabit Ethernet Controller (rev 0c)
00:01.0 Network controller: Realtek Semiconductor Co., Ltd. RTL000000
802.11ac PCIe Wireless Network Adapter

4-This problem has been present since the first installation, occured
3 days ago, in the meanwhile I tried to fix it asking on
reddit/r/qubes/ and on whonix forum;
5-From the same usb containing Qubes installation, I have installed
qubes in another computer of mine(laptop), and on it I did not have
such problems (and I used the same ethernet cable);
6-I'm not sure this is as it should be or not: during installation
(which I have repeated in the last 3 days literally 8-9 times across
different pcs.), at any point, I came across a Network setup
configuration like in every other operating system I have ever used
(linuxes and windows), and a guy on reddit told me he went through
something like that;
7-NOT a very important point, you can skeep this one if you want.
I noticed that during boot on my laptop pc (the one where internet
works perfectly) when it asks for the passphrase, it loads a proper
window, with background and box to type in the passphrase. In my
desktop computer instead (the one with the internet problem), this
does not occur, I have to type the passphrase directly in the boot.
All of this made me think that Qubes installation is everytime
overfitted for the current hardware.


TELL ME WHAT YOU NEED TO SEE AND I'LL POST.

PLEASE HELP ME FIX THIS, QUBES WITHOUT INTERNET IS POINTLESS, and
you'll help me get rid of this powerful headache I have right now.


-------------------------------------------------

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!

[Unman]

Well your wifi seems to be fine, in that it has obtained an IP address.
I see you are using whonix, so that may be causing specific issues - I
cant help you there.
You can test if this is the case by attaching a test qube to
sys-firewall, attached to sys-net.
Is it possible to connect from that qube to http://www.qubes-os.org
Is it possible to connect from that qube to http://104.25.151.101

Open a terminal in sys-net, and run 'iptables -L -nv'- see if the
counters are increasing on the FORWARD rules.
Do the same in sys-firewall and watch the traffic when you try to
connect from the downstream qube.
(When you do these tests have just the test qube using the network -
that will make it clearer what is happening.)


You haven't shown anything relating to the other NIC - perhaps ifconfig
-a might show something? (When you click on the Network Manager icon can
you see the Ethernet network relating to your card?)
I assume that you have looked through the output of journalctl and dmesg
and don't see any errors relating to the NICs. If you haven't done this,
please do.

I would focus on the (working) wifi first and then look at the NIC. That
said, try changing the template used by sys-net to Debian and see if
that makes any difference.

unman

[cooloutac]

add only one of the controllers to the vm and see if that works, wifi like unman said remove the ethernet one.

[helpp...@vfemail.net]

BOTH (wi-fi and ethernet) problems FIXED!!!!!!!!!
THANK YOU GUYS!!! YOU ROCK!!!!
___________________________________________________________________________
THE WI-FI PROBLEM FIX:
___________________________________________________________________________
I have been lucky enough to type in the wrong wi-fi password to find a
fix for the bug. After that I did many other tests to find out the
smallest amount of steps to fix the bug.

The bug was fixed by removing the wi-fi connection in the sys-net
Network Connections, and re-adding the wi-fi by inserting first a
wrong wi-fi password, and then the right wi-fi password.
In case a user has the same problem I wrote some more detailed steps below:

The bug was fixed in this way: when you connect to the wi-fi and it
doesn't work, meaning, you go to sys-net terminal and for example use
"ping google.com -c 5" and it returns "ping: unknown host google.com"
e.g. it doesn't have internet connection, you simply go to your
'Network Connections' of sys-net and delete your wi-fi connection
(going in the top right corner in your Qubes panel>right click on the
internet connections icon>edit connections>click on your wi-fi
connection>select delete>press the confirmation delete button (note:
you don't necessarily have to remove the ethernet wired connection if
you have one)), at this point re-connect to the available wi-fi, and
insert A WRONG PASSWORD. Once the password wi-fi reappers because the
psw you typed is wrong, you insert the correct one. Done, your
internet connection should work now, try in the sys-net terminal "ping
google.com -c 5" and you should be able to ping google.
___________________________________________________________________________
ETHERNET PROBLEM FIX:
___________________________________________________________________________
To user 'cooloutac':
Thank you for answering as well. Although I did not need to remove the
ethernet controllers to make the Wi-fi work in the end, I tried to do
so to make the ethernet work by removing the Wi-fi network card from
the devices list as you suggested.
MY MAN!!!!!!!!!!!!!!!!
IT WORKED!!!!!!!!!!!!!!!!!!! IT WORKED!!!!
I changed the devices in the sys-net settings, left only the ethernet
card, rebooted, when desktop loaded the message "CONNECTION
ESTABLISHED" appeared.
Went to sys-terminal, pinged google, it worked.

YOU GUYS ROCK!!!!!!!! THANK BOTH OF YOU A MILLION
TIMES!!!!!!!!!!!!!!!!!!!!!!!!!!
___________________________________________________________________________________
Now that the internet connection problem is gone, I'm going to
reinstall the whole system again, to set up my original qubes project.
Once it's done and internet is gonna work I'll post one more time so
the thread can be closed.
THANKS AGAIN GUYS U ROCK!!! I'M SO HAPPY!!! THANK YOU THANK YOU THANK YOU!!!!!

[helpp...@vfemail.net]

Yea, reinstalled the OS and followed the same steps, internet working
like a charm now!!!
THANK EVERYBODY !! YOU SAVED ME !! REALLY !!!

[secf...@gmail.com]

No luck for me, I even swapped out network cards thinking that was the problem. No internet what so ever. I guess no Qubes for me until this is fixed.

[cooloutac]

whats the model of your ethernet card?

[56lm...@gmail.com]

On Monday, June 26, 2017 at 12:41:36 PM UTC-4, helpp...@vfemail.net wrote:
> THIS CONCERNS QUBES 3.2 (latest update, downloaded from the website 3
> days ago).

No Network Connection: Qubes Os 4.0 - HP z230 desktop
hello everyone, there is really not much help on this os version. I need some assistance please. As i have read this persons post that loves (!!!) i have been able to see a few things that has helped.

With my desktop, sys-net has no connection and does see the nic. When I open the network connection dialog, i'm asked to add connection. when I select add, choose either. the next page is fully grayed out, can't select anything. there are no errors that come up when booted.

I see that I can use a usb wifi stick. but with that said, i need to be able to install a fix to get it to work. is that a true statement?

assistance would be greatly appreciated.

[unman]

Nothing like a bit of necrophilia.

The fact that sys-net does not see the NIC suggests that you are missing
some drivers. Review the boot log in sys-net, and you may see the
problem.

What card do you have in there? I cant see the spec from the HP site.
You could try changing the temaplet for sys-net to Debian instead of
Fedora, and see if the right drivers are loaded.

I',m not sure what you mean bu "install a fix" - if you use a supported
wifi stick, then it should load without further trouble. If you need
further drivers for that, then yes, you will need to install them.
If you do need drivers then you will have to download them on a
different machine or using alive disk.

[lifestyle]

hello and thank you for the response. i apologize, i meant sysnet sees the nic device. the nic is intel(r) i217-LM

What you mention about the usb wifi stick loading with out trouble makes sense. I will check the sys-net log.

most of the support I have seen is mainly for os verion 3.2. I seen someone mention that if you use a usb wifi stick that you had to build a cube for it and set a passthrough for it.

[unman]

Hello

Check the logs in sys-net, as you say. Post back with any problems that
you see there.
Try using a Debian based sys-net, and see if that helps.

As to use of wifi, this will depend on whether you have a USBqube set up
(sys-usb), and what ports/connectors you have available.
If you have multiple connectors, then you can connect 1 directly to
sys-net, and the rest to sys-usb. If you only have 1, then you will have
to try USB pass-through. That isnt difficult but again, check the lists
for reports of problems with particular devices.

best of luck

unman

[LMiller M]

Ok doing some research about this as much as I can learn about. I’m redoing the os 4.0 install. I got the warning that my machine doesn’t have HVM/VT-x/amd-v. Link from Qubes site. Basically no vms will work with anything. Can you help explain how I’m supposed virt-type to PV? Or should I just install the os 3.2?

The main problem I was having was. After running lookup qvm-pci I see my devices fine. The nic card shows up in the listing. In the network connections add connection. Everything is grayed out can’t add anything no vms work

https://github.com/QubesOS/qubes-issues/issues/3208

--
You received this message because you are subscribed to a topic in the Google Groups "qubes-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qubes-users/sEh2LQFiOxI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20181102161712.5hwxd7mngqc4luyr%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

[awokd]

LMiller M:

> Ok doing some research about this as much as I can learn about. I’m redoing
> the os 4.0 install. I got the warning that my machine doesn’t have
> HVM/VT-x/amd-v. Link from Qubes site. Basically no vms will work with
> anything. Can you help explain how I’m supposed virt-type to PV? Or should
> I just install the os 3.2?

Enable the virtualization options in your BIOS setup.

> The main problem I was having was. After running lookup qvm-pci I see my
> devices fine. The nic card shows up in the listing. In the network
> connections add connection. Everything is grayed out can’t add anything no
> vms work

1) Enabling virtualization may fix your sys-net issue.
2) You shouldn't have to add connections manually in most cases. What
does connection info say?
3) Like unman said, switch sys-net to use the Debian template (shut
sys-net down and change in Qube Setting/General tab).
4) If that doesn't fix it, see if your NIC needs additional firmware,
then install that to the template you use for sys-net.

[LMiller M]

I want to thank you both. Sorry for the late reply I wasn’t able to make the necessary adjustments till now.

I feel like a fool, I didn’t think about treating my desktop as a virtual box fresh install. Which completely makes sense because of the Qubes basic idea of the OS! Lol omg...

Anyway, seeing there is nothing explaining this. This is the fix for the issue I had with installing 4.0 os and having that main install error. After setting both virtual options in the PC bios everything loaded as needed on reboot. Network connection connected on boot-up. Everything works fine!

Thank you and I look forward to being apart the Qubes community! Amazing OS!

--
You received this message because you are subscribed to a topic in the Google Groups "qubes-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qubes-users/sEh2LQFiOxI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/629219b4-1dd6-f9dc-2bd3-805825a02116%40danwin1210.me.

[LMiller M]

Ok so one more if I can please, this is on a Asus K56c laptop and it has a kernel failure on boot with Qubes Os 4.0. On the first install it shows the kernel failure and it boots to the OS don0. If I turn off or reboot it shows my kernel failure and won’t load into the os.

I seen something saying I should be able to change the kernel (maybe during the install) don’t remember. I found the kernels on the Qubes site that are excepted, I just don’t see how the change it. Maybe I’m overlooking, I’m not a major Linux person. I know a small bit of ubantu

In this Asus I have the Acronis Loader, I don’t think that has anything to do with it. Just putting it out there.

Qubes OS is the only os install on this laptop drive. All virtual options are enabled. Boots to my login password then stalls.

Any ideas?

[LMiller M]

So, after looking more into the kernel issue. I see on the Qubes site some instructions for trying to change the kernel. I’m going to do a reinstall of the 4.0 os to get back into Dom0 and try it out. I will post back hopefully with success..

[LMiller M]

Update: Kernel failure during boot install OS 4.0

After the install booted into dom0, checking Qubes kernel package to see what three were stored or available. Mine only list one kernel.

4.14.18-1

I checked using the rpm -qa ‘kernel-Qubes-vm*’

Using the install update option I get:

Unable to reset pci device 0000:03:00.2:

Trying to apply the device to the selected box: error: device tab: can’t attach pci device to VM in pvh mode

Does that mode need to be changed?

Stupid question but because honestly I don’t know. How do you check the logs? I’m the terminal?

I downloaded the new kernel to cd, can install from the cd? I don’t see anything on the Qubes kernel page except download from internet throw Qubes. With internet I can’t.

[awokd]

LMiller M:

Glad you got your other computer working at least! So on this one, where
are you getting this kernel failure exactly? If it's booting to dom0,
I'm not following where you're having trouble. There's a message on boot
about failed to load kernel modules that can be safely ignored.

To update dom0, you want to use "sudo qubes-dom0-update". You should
rarely need to update the kernel by itself.

Is that when you are getting the PCI reset error? Is your sys-net
started? Check in Qube Manager. Then, check sys-net's Qube
Settings/Devices to see what's attached there and if 03:00.2 is one of
the devices. If so, see what it is.

[LMiller M]

Ok on first boot after install Qubes will show the kernel failure and bypass and boot into dom0.

Once there, in the Qubes manager dom0 has green state.

Lol ok don’t laugh too hard. So I checked devices like have been, sys-net as you mentioned. Both Ethernet and WiFi devices are there. So I just removed my Ethernet from device selection and bingo sys-net green state!

So I will try now to run system updates for dom0 and fedora.

Thanks again for point things out. Sometimes you look at something so crazy and just need a second thought.

So, can you show me how to check logs if I run into issues? Lol please and thanks

--
You received this message because you are subscribed to a topic in the Google Groups "qubes-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qubes-users/sEh2LQFiOxI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/326f794c-5658-c3bb-a8c7-7ed43b1d63ee%40danwin1210.me.

[LMiller M]

Ok so.... I figured out how to see the logs.

I have been able to figure out why the laptop wasn’t responding to the OS correctly. Now it’s working and updating as needed.

I will explain more as I learn more.

I do appreciate the guidance. I think there is more that can be shown, to help newbies.

I’m going to put something together from my view point to see if you all agree. Maybe it can be useful to all new qube users like me. Lol anyway, I wouldn’t have figured it out as fast for myself with out your help.

Thank you for helping me.

I’m still figuring things out, but this build is awesome and so much to learn with it.

[LMiller M]

Ok back with the laptop. During boot up, dom0 green state, sys-net green state. WiFi connection good, and can reboot! Lol

But with that said nothing else auto loads. I have to start fedora-26 and it will.

When trying to start sys-firewall I get error ( PCI device 02:00.0 is in use by driver xenlight domain sys-net
Log: /var/log/libvirt/libxl/libxl-driver.log

I don’t see this log listed with sys-net, there are no logs with sys-firewall. I don’t see this listed in the Qubes log either.

I have looked up help, but others have usb issues. I don’t have any attached and not trying to do anything with them as stated .

I tried command qvm-pci attach —persistent —option permissive=True —option no-strict-reset

But I’m missing something so it’s not working. I’m in the right direction? I need to reset pci and set no restrictions?

[Stuart Perkins]

On Fri, 9 Nov 2018 10:45:06 -0500

Is your NIC a PCI device? Do you have it assigned to sys-net?

sys-firewall should NOT have the nic assigned to it. It should be a "proxy" VM, with sys-net as its network VM.

Stuart

[awokd]

LMiller M:

> Ok so.... I figured out how to see the logs.
>
> I have been able to figure out why the laptop wasn’t responding to the OS
> correctly. Now it’s working and updating as needed.
>
> I will explain more as I learn more.
>
> I do appreciate the guidance. I think there is more that can be shown, to
> help newbies.
>
> I’m going to put something together from my view point to see if you all
> agree. Maybe it can be useful to all new qube users like me. Lol anyway, I
> wouldn’t have figured it out as fast for myself with out your help.
>
> Thank you for helping me.
>
> I’m still figuring things out, but this build is awesome and so much to
> learn with it.

There is definitely a learning curve to Qubes. On some hardware the
steepest part can unfortunately be right in the beginning with the
install. Glad you're making progress! If you want to help contribute to
the documentation, check out https://www.qubes-os.org/doc/doc-guidelines/.

[LMiller M]

Stuart!

Yes the pci device is my Nic. Thank you.. I didn’t realize sys-Firewall had the Nic assigned to it. I removed t and the firewall started

Thank you..

To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20181109183237.117d8825%40gmail.com.

[LMiller M]

I got sys-firewall to start green state. I cannot get fedora 26 to update. It crashes. Debain 9 starts and updated as required. Both PC and laptop will not let fedora update. Any suggestions?

Yes I would like to contribute to the help documentation. I will look at the link and post what I have come across.

Thank you very much for helping.

[awokd]

LMiller M:

Instead of trying to update the EOL Fedora 26, start from a fresh Fedora
28 template. Install it in dom0 with "sudo qubes-dom0-update
qubes-template-fedora-28", then change the AppVMs you want to have use
it by going into their Qube Settings/General tab.

[LMiller M]

Thank you that worked perfect! Very much appreciated! I think I have enough to help with some documentation for the true beginner.

Both laptop and pc, Qubes is running and I’m learning more of the operating system. Great OS, this platform is awesome.

I do have a question, adding vpn? Or just running a qube with Tor. Recommendations of adding a vpn

Also it seems pointless to adding a Windows Os to. VM I’m Qubes. Just running a template qube seems ideal?

Thanks to everyone who has jumped in with help! I hope I will be able to assist others to pay it forward.

To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5205c71d-5c09-70f9-85bb-b2182d409737%40danwin1210.me.