How to connect to internet by using a mobile broadband USB modem ?

[M]

How to connect to internet by using a mobile broadband USB modem ?

I have tried to set up a new network connection by clicking on Network Connection -> Add. and following the guide. At the end I can’t click on save as it says: “No polkit authorization to perform the action”. And I have tried it both when I was logged in as user and as root - with the same result.

The modem is: Huawei E3372 - the version with onboard drivers for both Linux, Windows and Mac.

[M]

In the meantime I have tried to add intel USB controller to the list of devices in sys-net VM under Devices.

And when I clicked on the settings of the Whonix VM, Qubes OS somehow cleared the settings of the USB controller so that I now can’t use my mouse or keyboard.

I have also tried to restart the pc. But there doesn’t seem to be any connection to the USB mouse and keyboard as they doesn’t light.

How can I get them to work again... ?

[unman]

On Tue, Jan 28, 2020 at 08:29:06PM -0800, M wrote:
> How to connect to internet by using a mobile broadband USB modem ?
>

> I have tried to set up a new network connection by clicking on Network Connection -> Add. and following the guide. At the end I can???t click on save as it says: ???No polkit authorization to perform the action???. And I have tried it both when I was logged in as user and as root - with the same result.

>
> The modem is: Huawei E3372 - the version with onboard drivers for both Linux, Windows and Mac.
>

You will probably get better results by opening just one thread per
issue, and being clear about what the issue is.
In this case, where did you perform the action (clicking on Network
Connection -> Add)?

[M]

Okay, I’ll try. But sometimes I first find it appropriate afterwards.

I clicked on the Qubes-icon on the far left in the menu line in top of the screen -> System Tools -> Network Connection -> Add. Followed the guide.

But after searching the net, it seems that this guide only works in other Linux OS’s and not in Qubes OS.

Instead I have to go into the sys-net settings... I have tried to follow the following guide, bit it seems that this method can’t bee used in 4.0.3 as sys-net settings looks very differently and without the same guide to manage internet connections.

Link to viewed guide: https://bytefreaks.net/gnulinux/qubes-os-connect-to-wi-fi-or-ethernet-or-another-network

Image of sys-net settings: https://bytefreaks.net/gnulinux/qubes-os-connect-to-wi-fi-or-ethernet-or-another-network/attachment/06-qubes-dom0-settings-application-for-sys-net

Image of the window to manage internet connections: https://bytefreaks.net/gnulinux/qubes-os-connect-to-wi-fi-or-ethernet-or-another-network/attachment/07-qubes-dom0-wi-fi-and-ethernet-settings-for-sys-net

[M]

After reinstalling Qubes OS 4.0.3 I tried to insert the USB modem after the first restart and let it be in the pc while doing the last configurations.

When I afterwards logged into Qubes OS as user, a red network icon was visible in the menu in the upper right corner of the screen with the text: “No network connection”.

By right clicking on it and choosing “Edit connection”, it is possible to add the new mobile broadband connection. Just follow the guide, it’s quite intuitive.

But now I’m stuck again...

Hope someone will help me further...

[M]

After restarting the pc and login a new window appear about connection to the Tor network. I have tried both a direct connection and by using one of the bridges. They all stops after loading 2 or 5 %.

Isn’t it possible to use Qubes OS to connect to the internet without a VPN, and if so how ?

I’m totally stuck.

And I have wasted several hours searching the web trying to find some guidance on how to connect to the internet with a USB modem in Qubes OS without any luck.

I suggest some more guidance on this in Qubes OS or at least on Qubes OS’s documentation page.

[M]

On github.com 0spinboson wrote to me: “assuming you have a USB qube (sys-usb) configured, you'll first need to click on the qubes devices systray icon, then connect the USB modem to your sys-net qube, before it'll be able to talk to it.”

As I use a USB keybord and mouse, I think the installer told me that the sys-usb and the sys-net was combined in one qube. But I’m not certain.

I have tried to connect the USB modem to the sys-net qube by clicking on devices, then on the USB modems storage device and click on the sum sign to the left of sys-net. But the result seemed to be the same. And I have also tried to add the mobile broadband connection afterwards. But there’s still no network.

I have also tried open the sys-net Qube Settings. Here it says:
Under Basic -> Networking: None
Under Devices -> Selected: None is shown
Under Services: Only clocksync is shown with a tick

Shall I connect the USB modem to the sys-net qube in another way, and if so how ?

Or does anyone have any other ideas on how I can get Qubes OS connected to the internet by using the USB modem (Huawei E3372 with also Linux drivers on it) ?

[M]

I should properly also mention that under devices only one other device besides the microphone is listed when the USB modem is plugged in. And that is: “dom0: sda - TF_CARD_Storage () (sys-net)”.

When the USB modem isn’t plugged in, only the microphone is listed here.

[awokd]

M:

Try a dom0 terminal instead. Qvm-ls will list your VMs. Use it to
determine if you have a separate sys-usb. Next, use qvm-usb with your
modem plugged in to see if Qubes recognizes it. If you don't have a
separate sys-usb, it should be connected to sys-net automatically. Use a
terminal in sys-net to troubleshoot further.

Please also include the portion of this email you are replying to, if a
reply is needed. If you are using the Google web interface, I think you
have to specify "reply inline". In your posts to the list, I can only
see what you typed and not what you're responding to, which makes
putting it into context challenging and harder to assist you.

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

[M]

Yes, I use the Google interface as I find it easier to work with.

Could you elaborate on >>specify "reply inline"<<. Sorry I don’t understand what you would like me to do. Although I understand that I somehow should get Google to send the other post in the thread with every message that is being sent. But I don’t know how to do that. Shall I instead just reply to the received mail, or... ?

I have used qvm-ls in a dom0 terminal to list all VM’s. No sys-usb found.

I have used qvm-usb in a dom0 terminal: No USB devices is shown. Neither USB modem, USB keyboard or USB mouse. Just mentioned in case they also should be shown here.

“If you don't have a separate sys-usb, it [the USB modem] should be connected to sys-net automatically. Use a terminal in sys-net to troubleshoot further.”
How shall I use the sys-net terminal to troubleshoot further ?

[awokd]

M:

> Yes, I use the Google interface as I find it easier to work with.
>
> Could you elaborate on >>specify "reply inline"<<. Sorry I don’t understand what you would like me to do. Although I understand that I somehow should get Google to send the other post in the thread with every message that is being sent. But I don’t know how to do that. Shall I instead just reply to the received mail, or... ?

I'm subscribed to the list through email, so don't know exactly how
their web interface works. Replying might work better.

> I have used qvm-ls in a dom0 terminal to list all VM’s. No sys-usb found.
>
> I have used qvm-usb in a dom0 terminal: No USB devices is shown. Neither USB modem, USB keyboard or USB mouse. Just mentioned in case they also should be shown here.
>
> “If you don't have a separate sys-usb, it [the USB modem] should be connected to sys-net automatically. Use a terminal in sys-net to troubleshoot further.”
> How shall I use the sys-net terminal to troubleshoot further ?
>

The same way you would troubleshoot USB modem problems in any Linux
distribution (Fedora if you're using the default template). If USB
controller passthrough is working, and it's to sys-net, it's most likely
not a Qubes issue. Another way to confirm your USB controller is in the
VM you need is with qvm-pci. This should show your USB controller(s)
assigned to sys-net.

To start troubleshooting sys-net, unplug and plug in your USB modem. Go
to a terminal window in it and enter "sudo journalctl -b". Hold down
space until you get to the end. See if you have any related error
messages, then put them in a search engine along with "Fedora" and look
for suggestions. Is there some package you need to install to support
your modem?

[Foppe de Haan]

I searched a little because the whole TF_Card_reader seemed a really strange identifier to me for a wifi dongle, and I found https://gist.github.com/jfstenuit/13becfe728046074f5aaa0cb7f899ab9 . is for a different model, but the same principle may well apply. If so, you'll need to tell the dongle to switch to wifi connection mode before it'll work. To make triaging easier, it may be handy to use a fedora live boot USB.

[M E]

I’m new to both Linux and Qubes OS. I have only experience with windows and mac. So the way to troubleshoot here in Linux is totally new for me.

qvm-pci in sys-net terminal returns “command not found” some text and “Curl error (6)”.

The modem works both with PartedMagic Linux, Trails 4.2.2 and Windows 10. And I have read that it also works with Fedora .

The USB modem has both drivers for Win 10, OSX and Linux on it.

I have tried to write “lsusb” in the dom0 user terminal. Here it recognizes the USB modem: 

ID 12d1:14dc Huawei Technologies Co., Ltd.

But when i run the same command in sys-net, there is only two devices listed - even after I have mounted the storage drive to sys-net: “Adomax Technology QEMU USB”  and  “Linux foundation 2.0 root hub”.

How shall I proceed... ?

--
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/2Z1rD5fn6io/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qubes-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/264dc768-7b1e-1fdc-2978-5fe25feca599%40danwin1210.me.

[M E]

Yes, I have also found something here:

Here it says that it should work well with kernel higher than 4.7:

https://unix.stackexchange.com/questions/309370/4g-modem-works-only-on-livecd-in-fedora

Maybe this is more helpful, but I probably need som help if I’m going to do this:

https://ask.fedoraproject.org/t/huawei-e3372h-153-stick-mode-fedora-30-usb-modeswitch/3724

I will take a closer look on the last one as it seems to fit better with what I’m experiencing although Qubes OS behave a little bit different...

I hope you will help me configure it correctly...

tor. 30. jan. 2020 kl. 17.52 skrev Foppe de Haan <0spin...@gmail.com>:

I searched a little because the whole TF_Card_reader seemed a really strange identifier to me for a wifi dongle, and I found https://gist.github.com/jfstenuit/13becfe728046074f5aaa0cb7f899ab9 . is for a different model, but the same principle may well apply. If so, you'll need to tell the dongle to switch to wifi connection mode before it'll work. To make triaging easier, it may be handy to use a fedora live boot USB.

--

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/2Z1rD5fn6io/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qubes-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a57f24a6-82ef-4c62-b5ea-cae851b39a3f%40googlegroups.com.

[M E]

In the last link I send, it says:

Bus 001 Device 007: ID 12d1:14dc Huawei Technologies Co., Ltd.

There are two ID numbers separated by colons 12d1 & 14dc
These are your two original ID numbers and you are going to need them later on in the same order, so write them down.
Next you need to be able to manually put your device into the correct mode i.e get it working as a modem. The command for this will be:

$ sudo usb_modeswitch -J -v 0x12d1 -p 0x14dc

In which terminal shall I write this ?

tor. 30. jan. 2020 kl. 18.09 skrev M E <annee...@gmail.com>:

Yes, I have also found something here:

Here it says that it should work well with kernel higher than 4.7:

https://unix.stackexchange.com/questions/309370/4g-modem-works-only-on-livecd-in-fedora

Maybe this is more helpful, but I probably need som help if I’m going to do this:

https://ask.fedoraproject.org/t/huawei-e3372h-153-stick-mode-fedora-30-usb-modeswitch/3724

I will take a closer look on the last one as it seems to fit better with what I’m experiencing although Qubes OS behave a little bit different...

I hope you will help me configure it correctly...

tor. 30. jan. 2020 kl. 17.52 skrev Foppe de Haan <0spin...@gmail.com>:

I searched a little because the whole TF_Card_reader seemed a really strange identifier to me for a wifi dongle, and I found https://gist.github.com/jfstenuit/13becfe728046074f5aaa0cb7f899ab9 . is for a different model, but the same principle may well apply. If so, you'll need to tell the dongle to switch to wifi connection mode before it'll work. To make triaging easier, it may be handy to use a fedora live boot USB.

--

[M E]

In the sys-net terminal, the result is “No devices in default mode.”

In the dom0 terminal the result is:

So it seems that didn’t work...

I’ll try to read the link further...

tor. 30. jan. 2020 kl. 18.19 skrev Foppe de Haan <0spin...@gmail.com>:

in the terminal of the qube that the modem is connected to, so presumably sys-net.

On 1/30/20 6:18 PM, M E wrote:

In the last link I send, it says:

Bus 001 Device 007: ID 12d1:14dc Huawei Technologies Co., Ltd.

There are two ID numbers separated by colons 12d1 & 14dc
These are your two original ID numbers and you are going to need them later on in the same order, so write them down.
Next you need to be able to manually put your device into the correct mode i.e get it working as a modem. The command for this will be:

$ sudo usb_modeswitch -J -v 0x12d1 -p 0x14dc

In which terminal shall I write this ?

tor. 30. jan. 2020 kl. 18.09 skrev M E <annee...@gmail.com>:

Yes, I have also found something here:

Here it says that it should work well with kernel higher than 4.7:

https://unix.stackexchange.com/questions/309370/4g-modem-works-only-on-livecd-in-fedora

Maybe this is more helpful, but I probably need som help if I’m going to do this:

https://ask.fedoraproject.org/t/huawei-e3372h-153-stick-mode-fedora-30-usb-modeswitch/3724

I will take a closer look on the last one as it seems to fit better with what I’m experiencing although Qubes OS behave a little bit different...

I hope you will help me configure it correctly...

tor. 30. jan. 2020 kl. 17.52 skrev Foppe de Haan <0spin...@gmail.com>:

I searched a little because the whole TF_Card_reader seemed a really strange identifier to me for a wifi dongle, and I found https://gist.github.com/jfstenuit/13becfe728046074f5aaa0cb7f899ab9 . is for a different model, but the same principle may well apply. If so, you'll need to tell the dongle to switch to wifi connection mode before it'll work. To make triaging easier, it may be handy to use a fedora live boot USB.

--
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/2Z1rD5fn6io/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qubes-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a57f24a6-82ef-4c62-b5ea-cae851b39a3f%40googlegroups.com.

-- 
-----BEGIN PGP PUBLIC KEY BLOCK-----

mQINBFjqNnYBEADR/lrTia4IbwINTGj/Q53m+baKiNnWnLBOPJVYn2hhldUQY9m7
nNOgvL0sY9tzcNOW9FNQ4MKkEbmAl645z2O1jfm4ae+SE5yqi3gbtcbsbvO5mHkl
PYSLb4B6FRd9drJULfvg0Igb7qMe0ojjaWv/OiEA3Ms1rHfx8RHI3kcPuJhjQxqw
7bWusOYMHQ5ZIBWUZVkk7zJNSTpoEiRVPEIoneQJLO63xkBmTyoYdxu9sTeS7tw5
zVN6cp0yBmktmyksSb6eTdkRVhpmF44adH+XIIxbn7xnr6xhHpFM2d+lXbO4HxWm
egxisr+4eUH5NViQd33P68c8l1AekF9LyI262AkdQCQDXj/BhOCushkIvTssow+O
jP9zpyHfcWkkgxS0Ak+Y6DlC/PzxsMcppbYEDi+xdE/Wt41J5m8AScrTN6fiZgQY
qfZiNABvt729J98pBeyxQOhvXwUFwy4R7KCASgF3FhFVkCntTGt3OyREaGprJj9m
pb5tRu5E6urOUxynuXrVvnYF7OZ1PBTUX5MIo61Ds9Ni4Huh7BupiNS4GvxG53/M
6j4VSPYYzrIaeEq87knL/EclCYytBA1ISkXKGyfkD9RvZp678OdlnrUkc6iOo+6S
Mhc4inFx+nwWUq+4tZ1nDL6HeNzde+T1dX0VrrnS9Ia9rNHagcme9wCRgwARAQAB
tCRGb3BwZSBkZSBIYWFuIDwwc3BpbmJvc29uQGdtYWlsLmNvbT6JAlQEEwEIAD4C
GyMFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AWIQRC980f1hI5U+LBZ//86SnHMPuM
FgUCWOo4XAUJEOrRZgAKCRD86SnHMPuMFmyWEACRe+PNpus/mRze5+7/5ld0lW2d
00Q18EZ+f/E8mlfsdatE0MCmGEHr7aC+EnarTZRBe8pMEsje5q0eweJk7HtEYl7t
v0UHRw3YEc+5m5b9kjVp83h075jtp8OgJ0zD+FmyUO2pe5S6hvWo7jtS4Lw53SK2
kZkmoAazIDn7WpqGszQoe5hc9xA46Z5qaUcabSEufLW7DwzJ3L+I0NNag1e9dWe+
BuPigJb8r/VFrpP5S/AfBRY8nnyqJuxcTWJyN5HLhqtNwJ1HYIICLubYG3soOJ1c
g2C6LQbV0AlBeGwyOZLnj8G83rLLbzkfrs3KPx58UAacUzohtxEATbae6IcFhd+Q
ZuHv2VX6kf8Svvz2W9j1dLQvHUPOjmYl70JDENjsIZ806lG82E0CktVg0X9T4gWN
W8nDAUuZ4TTINOKnAKyJEanVvakqcO2KyDJ3sKMbl69UQRW5jBUVqhwCLB5TT+qx
E0yqRsDkLUfN5B01z2ZN0JuWwKHFFlBUhZvy1nm0n4rvomjaZBNzOWCJVBMsEE8I
0Y0krk2LpcGorrQF8Ssl4gd8WyCxnMglrq7kuMVaUvUFaVE8yhsNRiaQ2itXf7aV
1sEFApp3k9dY3bpClFG4ZUX/7S/YcRMRylBGb7cMB6rWenZz1rv6gftgodGs2Gkg
7BrNHkQ25U469Rzvm7kCDQRY6jZ2ARAAybn1ZrLi1hLKo+/mxj9Z7M8CBcyqtzd6
KBfZUVAaJa3z+xmFwUnpuSRq8ZJIaqes8DWfzYD358+/dVZVjwRmA7+l4Mw8gSF1
MR7ZhKt8l3E3x6HhmF0BfIJWfniDnAmd3UfcVfTZgYRM9/uF10KTTAnZ5TpM55Fx
VPEENjQ7/XByZbiB5j3+TuR9jdnvoNSJPtdLVG+oWaiwUfrEhxxPoyU9/8mSL1hT
lgDMKFZl6zROjLVRrbOL1R4KpVHjIDH72S8G5CF34gr14QVCZhC3d8tsylV9uWvH
SOoM+r9kRxYvZHnlnjtvEUr47PCpzi3QV28t/W5K6VKA353vfilgT39uH8bxS9dY
pluEHixCobWElmfnrxU0dTAGnmV6brvmdFiR+9OucwxLmUUK5Y4WGgJo0k9jI8XF
nyjppR5Ix+HQqLF8kah8JNXLp3Rvay49CIspdtiYPVK9N3iPq8bTzs+80l9BqTsa
io4vst9GXn3fpkKN0TFUq7zAbXWbnT3zrd+x9nd5oF/Lhv7FJ2geMx7H3zyiFZvN
CCC6FExhLRvd127m/qH6/gral/quvWOYb7/z/PWS6x4sgArSILCCtIaVPStL6mqG
itCQMpPIXcmCR/0BRkYC2/OzhOgaph1/WLQyYtlr5fx1lmbZsrBN0fkTInkB+Bap
L+8B5Sr5AP0AEQEAAYkCPAQYAQgAJgIbDBYhBEL3zR/WEjlT4sFn//zpKccw+4wW
BQJY6jhcBQkQ6tFmAAoJEPzpKccw+4wWOyIQAL5KQVQ6XdJVbtFEaOQT/33qvbDJ
JEvDMdEH652N8ZsLODWE4+V3a24TySieAuy3UWVT1qS+FnTCpnkpxN9vYb0tMox6
SpczGBgbB3+XSZ4y3xvBBazDwK0hx1lDQtf2Zg0YbJPcl6Srx8DDS4XOavm6Yrzp
gt4xknX9Y3gimPdpm+4B0alY/a4Q+bl28bCs2t9HdEcxYpmS5dkkrI9u21cAeaKQ
T3YTks44up7dgsLHwqZzYkOC6m7lh+MA6jp5/nXEn7GJFXyZvWZCr3yRCniGFAxd
Kk2AZwyCulI4zeiptGrqLBWR0kJQbCe1GSPHE0jGqQKRENHuYIOKsmDhNZRAdmBS
UcO388pRSlUF6OWoHyOYOKbVEAsQRADdeEuSaSA5Yzf3lHoLN4Zh5ZXHekCeIqKL
iuX5YWhWPcLfAkOT0dH3pajG8Z5nMAFfIn22bYF7+I5IWMJZ3M6A5P15YMLnjta8
5xfQuLLDVWYgdQPdufTU+zcLKFeYGon+7qSOE/8IzmNvWHf97FSWefdeH18eLY9A
aGjKfJ7SD3fRnnx7CJJumR/j860QZrPkXIK+yhQG49nXJSFv8eR3ipCdOhEPD/tG
ZQ6p7oUZKH2YayzZcF2dzqiC/CZFJDz3fcfuh4xGzIaiHW3O/V5qktXWKQB3R1Bf
CJm1UauVgwt41zd5
=WSya
-----END PGP PUBLIC KEY BLOCK-----

[M E]

I’ll try to do the following which is my short and edited version of the last link:

Create a file with a text editor of any kind and insert the following:

#!/bin/bash

sudo usb_modeswitch -J -v 0x12d1 -p 0x14dc

Be sure to include YOUR numbers.

Then save the file with a relevant name and save it in a place (remember the path to the directory) that you will not delete it by accident for as long as you will need to use your Huawei modem.

The next step is to get Fedora to know how you want this script to be dealt with, to run it as a script and not open it to view the file.

To execute the following command you should be in the target directory where you saved the file to, so for example Desktop if that is where you did save it:

$ sudo chmod +x {your file name}

This will let the system know to run this as a script.

The next step is to create a rule file in the same place as all the other rules. So go to /lib/udev/rules.d/
give yourself Super User rights by typing command:

$ su

You will be prompted for password and then you should see the # key appear.

Name this rule anything you want, perhaps 99-myhuaweimodem.rules.
I do recommend however to use the number 99 so we can find the rules easily and also to give it a .rules ending so that it fits in with the rest.

When I was in the path /lib/udev/rules.d/ I opened a terminal there and then used the command

$ nano

This should open up a text editor in the terminal where you will paste the following being sure to use your device numbers where you see them in this line:

ACTION==“add”, ATTRS{idVendor}==“12d1”, ATTRS{idProduct}==“14dc”, RUN+="/home/{your-user-name}/Desktop/{your-file-name}"

Please ensure that you use your numbers and that the path
/home/{your-user-name}/Desktop/{your-file-name} corresponds to where you saved the file(script) you created earlier and the user name etc is yours obviously and do not include the { } signs! Then save this file.

I’m uncertain about if I shall replace {idVendor} and {idProduct} with something different (don’t know what) or they shall be left as such.

The last and final step:

The user (yourself) needs the authorization to run a command such as sudo without a password. So that is done by adding an exception to the sudoers file which can be found in /etc/sudoers

However, this monkey won’t let us make any changes to this file unless we are are sudo and admin ourselves, so you need to edit this text file as root (sudo or su) and do it using nano, the terminal text editor like we did earlier using the command:

$ sudo nano sudoers

At the very end of this file once we have opened it we need to add the line at the bottom:

{your-user-name} ALL=NOPASSWD: /usr/sbin/usb_modeswitch

Be sure to insert your system user name where I wrote {your-user-name} without the { } signs.

Now save the changes you made and restart your machine.

The changes should take effect and now when you insert your modem, it will work as a modem automatically.

I searched a little because the whole TF_Card_reader seemed a really strange identifier to me for a wifi dongle, and I found https://gist.github.com/jfstenuit/13becfe728046074f5aaa0cb7f899ab9 . is for a different model, but the same principle may well apply. If so, you'll need to tell the dongle to switch to wifi connection mode before it'll work. To make triaging easier, it may be handy to use a fedora live boot USB.

[M]

For a guide to use the text editor “Nano”, see here: https://linuxize.com/post/how-to-use-nano-text-editor/

[M E]

This method didn’t change the result. The USB modem is still recognized by Qubes OS as a USB storage device instead of a modem. All though it is recognized as a modem by Tails 4.2.2 and by PartedMagic - both Linux live OS’s.

And I have checked if I have written anything wrongly.

So I still can’t get any network connection.

So it would be nice to hear how others who use the same USB modem has managed to get Qubes connected to the internet.

tor. 30. jan. 2020 kl. 22.35 skrev M <annee...@gmail.com>:

For a guide to use the text editor “Nano”, see here: https://linuxize.com/post/how-to-use-nano-text-editor/

--
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/2Z1rD5fn6io/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qubes-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bc67e834-e967-4875-a6bd-85c2e9a7d88a%40googlegroups.com.

[M E]

New method tried that didn’t work

I have tried another method which seems to work in Ubuntu and which I’ve found here, but it didn’t work either:

https://askubuntu.com/questions/757638/can-not-connect-huawei-e3372-modem-on-ubuntu-15-10-please-help

The method

“Add a new network connection using Network Manager panel. The connection type is 'Ethernet'. In Device Mac Address, select the mac address of your modem and click 'Save'. This new connection should come up in your Network Manager now. I hope this answer helps others.”

I’ve found the USB modem’s MAC address by running a Linux Live OS (PartedMagic), and looked under System profiles -> Network -> Devices, and wrote it down.

I then logged into Qubes OS, right clicked on the red network icon in the menu -> Edit connections -> Add -> Ethernet.

Writing the MAC address in the input field beside “Device”, pressed Enter and pressed Save.

And I have tried it both before and after I have connected the USB device to sys-net VM.

The problem

Of course the problem is that the USB modem’s MAC address doesn’t exist in the OS as long as the device isn’t recognized as a modem. So by entering the MAC address in the Network Manager, there is just being entered an address to a device which doesn’t match the MAC address of any device according to the OS.

So somehow Qubes OS needs to recognize the device as a USB modem.

Questions

So the question remains: How can I get Qubes OS to recognize the USB device as a modem... ?

And as some other Linux distros (Fedora ( see link: https://unix.stackexchange.com/questions/309370/4g-modem-works-only-on-livecd-in-fedora ), Ubunto, Arch, Tails 4.2.2 and PartedMagic) is able to recognize the USB device as a modem, it seems that Qubes OS miss something that makes it possible for the OS to recognize the device as a modem.

For example in this forum the users said from dec. 2017 and onwards that the modem Huawei E3372 is recognized and work with other Linux distros. 

http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2756

An obvious question is then: What does these distros have which Qubes OS doesn’t have, that makes them being able to recognize the device as a modem ?

And is it something that can be downloaded an added to Qubes OS to make it recognize the device as a modem ?

If so, I would appreciate a download-link.

[M E]

Maybe I should have investigated Foppe’s suggestion further before I looked into the other methods I found...

https://gist.github.com/jfstenuit/13becfe728046074f5aaa0cb7f899ab9

On this page there is a link to this page:

https://www.draisberghof.de/usb_modeswitch/

where some packages are offered for download.

I’ll try the method described above and get back afterwards...

Some days will probably pass before I’ll return with an update...

[M]

I have made a thread here: https://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3&t=2922

[awokd]

M E:

> I’m new to both Linux and Qubes OS. I have only experience with windows and
> mac. So the way to troubleshoot here in Linux is totally new for me.
>
> qvm-pci in sys-net terminal returns “command not found” some text and “Curl
> error (6)”.
>
> The modem works both with PartedMagic Linux, Trails 4.2.2 and Windows 10.
> And I have read that it also works with Fedora .
>
> The USB modem has both drivers for Win 10, OSX and Linux on it.
>
> I have tried to write “lsusb” in the dom0 user terminal. Here it recognizes
> the USB modem:
> ID 12d1:14dc Huawei Technologies Co., Ltd.
>
> But when i run the same command in sys-net, there is only two devices
> listed - even after I have mounted the storage drive to sys-net: “Adomax
> Technology QEMU USB” and “Linux foundation 2.0 root hub”.
>
> How shall I proceed... ?

Qvm-pci only works in a dom0 terminal.

[M]

To stay using a USB modem directly plugged into the pc, this seems to be the best option: https://wiki.loopback.org/plugins/servlet/mobile?contentId=19234871#content/view/19234871

Else it is possible to connect the USB modem to the pc’s LAN-port by using TP-LINK TL-MR3420 - link: https://www.tp-link.com/dk/home-networking/3g-4g-router/tl-mr3420/