Hi, The wayback machine has a copy of the binary-free sakis3g, that may be an option, even if it is very old https://web.archive.org/web/20130330200728/http://www.sakis3g.org/#download https://web.archive.org/web/20130330200728/http://www.sakis3g.org/versions/l... echo "f60763ca65a0a9fdb2608e1734171740 sakis3g.gz" | md5sum -c gunzip sakis3g.gz chmod +x sakis3g ./sakis3g --interactive You can try to load that from a usb drive. -- Andy Am 16.03.21 um 21:58 schrieb Morten Bo Johansen via arch-general:

On 2021-03-16 WorMzy Tykashi via arch-general wrote:

...

Have you seen https://wiki.archlinux.org/index.php/USB_3G_Modem ?

Yes, I have seen it. The problem is that none of the most viable solutions (for me), netctl, libmbm and mmcli are on the installation medium. I am stuck with wvdial and pppd.

But I must carry on and see if I can get it to work. If there are any other suggestions, I would be greatful to hear them.

Morten

Morten Bo Johansen via arch-general wrote:

On 2021-03-16 Andreas Bosch via arch-general wrote:

...

Hi,

The wayback machine has a copy of the binary-free sakis3g, that may be an option, even if it is very old

Thanks, I just tried it, but I could not get a connection with it. It seems I must plug away with wvdial.

Thanks, Morten

Which usb modem you are using? Have you got it working in another machine? In this machine with another OS? If yes, how? -- u34

Am 17.03.21 um 11:32 schrieb Morten Bo Johansen via arch-general:

It seems that usb_modeswitch is not activated during the arch_boot installation, so I am looking at that and then I must see if I can get wvdial to work. It is a bit of a hassle with no guarantee of success, so if you have any other suggestions, I am all ears.

The Huawei E3372 might automatically use the cdc_ether driver (hilink). Does it appear as a network device like "wwp..."? Then make sure the interface is up with DHCP and try to open its configuration page with lynx. The modem ip should be the gateway ip set by dhcp, often 192.168.8.1 There is also an API available to control hilink devices. I found a tool, but it is not available as an arch package: https://github.com/kenshaw/hilink For libmbim you could manually download, copy and install these packages: libgudev libmbim If you want modemmanager, then it would be libgudev libmbim libmm-glib libqmi libqrtr-glib mobile-broadband-provider-info modemmanager -- Andy

Bjoern Franke via arch-general wrote:

Hi,

...

The Huawei E3372 might automatically use the cdc_ether driver (hilink). Does it appear as a network device like "wwp..."? Then make sure the interface is up with DHCP and try to open its configuration page with lynx. The modem ip should be the gateway ip set by dhcp, often 192.168.8.1

I had several issues with Huawei devices which only went into cdc_ether mode after running usb_modeswitch. So it's somehow an chicken-and-egg problem.

Regards Bjoern

I think that a work around is to set up a temporary storage. And have the usb_modeswitch, with all its dependencies, downloaded into it. Some archlinux live systems might already doing that, so you might want to consider installing with them. The wiki derivatives article can help you find one. -- u34

On 2021-03-17 Andreas Bosch via arch-general wrote:

The Huawei E3372 might automatically use the cdc_ether driver (hilink). Does it appear as a network device like "wwp..."? Then make sure the interface is up with DHCP and try to open its configuration page with lynx. The modem ip should be the gateway ip set by dhcp, often 192.168.8.1

I managed to get it to work: # vim wv.conf [Dialer Defaults] Init1 = ATZ Init2 = ATQ0 V1 S0=0 Modem = /dev/ttyUSB1 Modem Type = Analog Modem Stupid mode = 1 Dial Command = ATDT Password = ; Username = ; Phone = *99# Init3 = AT+CGDCONT=1,"IP","bredband.oister.dk" # wvdial -C wv.conf I was wrong about usb_modeswitch not being activated. It is because its documentation states that a device, /dev/gsmmodem, is being created and since it wasn't there, I assumed that it had not been run, but it was /dev/ttyUSB1 Oddly enough, when I tried /dev/ttyUSB0 first with no response and then changed to ttyUSB1, I got the error, "invalid dial command, ATDT*99# i.e. wvdial somehow strips the space between the ATDT command and the number so one must reset the modem and try again. Wvdial is a wily program ;) Thanks, Morten PS: I tried to mail the wv.conf file to myself, but the mail command wasn't there!