Wifi but no ethernet in Qubes OS

ItsMyBedtime · 05-16-2017, 12:57 PM

Generally wifi works out-of-the-box for me, but I've yet to connect with this OS. The plug is in, and I've setup the networkmanager gui. There is no applet saying the plug is in and connected. Wifi shows up fine when turned on.

These are the two devices selected in net-sys domain:

02:00.0 Network controller: Intel Corporation Centrino Advancedd-N 6205 [Taylor Peak] (rev 34)

0c:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5761 Gigabit Ethernet PCIe (rev 10)

Some information (let me know if I can post anything else):

Code:

[user@sys-net ~]$ lspci
00:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)
00:01.0 Ethernet controller: Broadcom Limited NetXtreme BCM5761 Gigabit Ethernet PCIe (rev 10)

Code:

[user@sys-net ~]$ lspci -k
00:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
	Subsystem: Intel Corporation Device 0130
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

Code:

[user@sys-net ~]$ ifconfig
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 24  bytes 2076 (2.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 24  bytes 2076 (2.0 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 fe80::fcff:ffff:feff:ffff  prefixlen 64  scopeid 0x20<link>
        ether fe:ff:ff:ff:ff:ff  txqueuelen 32  (Ethernet)
        RX packets 120099  bytes 6557730 (6.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 185645  bytes 267192251 (254.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp0s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.100  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::6e88:14ff:fe42:d1f4  prefixlen 64  scopeid 0x20<link>
        ether 6c:88:14:42:d1:f4  txqueuelen 1000  (Ethernet)
        RX packets 230101  bytes 333308717 (317.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 146626  bytes 12390208 (11.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Seems as if vif2.0 is my ethernet device.

Code:

[user@sys-net ~]$ lsmod
Module                  Size  Used by
fuse                   98304  3
iptable_raw            16384  1
xt_nat                 16384  4
xt_REDIRECT            16384  1
nf_nat_redirect        16384  1 xt_REDIRECT
xen_netback            49152  1
ip6table_filter        16384  1
ip6_tables             28672  1 ip6table_filter
xt_conntrack           16384  2
ipt_MASQUERADE         16384  1
nf_nat_masquerade_ipv4    16384  1 ipt_MASQUERADE
iptable_nat            16384  1
nf_conntrack_ipv4      16384  3
nf_defrag_ipv4         16384  1 nf_conntrack_ipv4
nf_nat_ipv4            16384  1 iptable_nat
nf_nat                 24576  4 nf_nat_redirect,nf_nat_ipv4,xt_nat,nf_nat_masquerade_ipv4
nf_conntrack          106496  5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4
arc4                   16384  2
iwldvm                237568  0
mac80211              708608  1 iwldvm
iwlwifi               155648  1 iwldvm
tg3                   163840  0
cfg80211              557056  3 iwlwifi,mac80211,iwldvm
ptp                    20480  1 tg3
pps_core               20480  1 ptp
rfkill                 24576  2 cfg80211
intel_rapl             20480  0
iosf_mbi               16384  1 intel_rapl
x86_pkg_temp_thermal    16384  0
coretemp               16384  0
crct10dif_pclmul       16384  0
crc32_pclmul           16384  0
pcspkr                 16384  0
crc32c_intel           24576  0
ghash_clmulni_intel    16384  0
xen_pcifront           20480  0
dummy_hcd              36864  0
udc_core               24576  1 dummy_hcd
xen_blkback            45056  0
xenfs                  16384  1
xen_privcmd            16384  9 xenfs
u2mfn                  16384  0
xen_blkfront           40960  6

I tried posting dmesg, but it was too long to post, and I'm not sure which parts would be beneficial to post.

Any suggestions?

mazinoz · 05-16-2017, 06:36 PM

I have had no experience with Qubes. But if you are concerned about security, personally I would not use wifi or bluetooth at all.

What does hwinfo, or lspci show?

ItsMyBedtime · 05-17-2017, 04:04 AM

Quote:

Originally Posted by mazinoz

I have had no experience with Qubes. But if you are concerned about security, personally I would not use wifi or bluetooth at all.

Agreed. That's why I'd like to use ethernet instead, but only wifi is working at present. Bluetooth is turned off at the bios level and cannot be turned on.

Quote:

What does hwinfo, or lspci show?

lspci is shown above in first but, but I received a command not found with hwinfo.

ItsMyBedtime · 05-17-2017, 01:51 PM

Some small progress has been made.

I changed a setting in the file /etc/NetworkManager/NetworkManager.conf:

From:

[ifupdown]
managed=false

to:

plugins=ifupdown

[ifupdown]
managed=true

While I still cannot load the internet I do at least now get a connected signal icon from the manager applet.

Here is ifconfig -a:

Code:

[user@sys-net2 ~]$ ifconfig -a
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 4212 (4.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 36  bytes 4212 (4.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vif4.0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.137.5.1  netmask 255.255.255.255  broadcast 0.0.0.0
        inet6 fe80::fcff:ffff:feff:ffff  prefixlen 64  scopeid 0x20<link>
        ether fe:ff:ff:ff:ff:ff  txqueuelen 32  (Ethernet)
        RX packets 2451  bytes 184852 (180.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2938  bytes 3581637 (3.4 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp0s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.100  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::6e88:14ff:fe42:d1f4  prefixlen 64  scopeid 0x20<link>
        ether 6c:88:14:42:d1:f4  txqueuelen 1000  (Ethernet)
        RX packets 3000  bytes 3594565 (3.4 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2506  bytes 269423 (263.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I noticed that each time the ethernet starts it makes a new profile in NetworkManager, if that means anything.

mazinoz · 05-23-2017, 08:01 PM

Normally in Debian Linux Mint, only one instance of Network Manager runs at a time, if that helps.

Have you tried "rfkill block all" which kills all wireless, bluetooth, radio etc and just try to use ethernet connection? I've had the experience with a hacker changing my wifi networking scripts as I was configuring them! It may be better to just troubleshoot one issue at at a time as well.