The Problem is, that i have the AT-Command Version of this Stick and this HowTo is for the Web-Interface Version.
When i try to configure the Stick as lte-modem
diagnose sys lte-modem info
says, that the Modem is not connected.
So i tried to configure the Stick as "normal" Modem. The Modem itself seems to work properly:
diagnose sys modem query USB status: Connected manufacturer: huawei model: E3372 IMEI number: 868230032061123 SIM state: Valid service status: Valid Service signal level: 3/4 network name: E-Plus network type: E-UTRAN location area code: active profile(AT&V): COMMAND NOT SUPPORT
But in the Debug Messages a Timout occures (At the end after CONNECTED):
recv 0: recv 19: COMMAND NOT SUPPORT recv 0: recv 8: ^RSSI:19 recv 0: recv 24: ^HCSQ:"LTE",46,46,126,22 chat: abort on (BUSY) chat: abort on (NO DIAL TONE) chat: abort on (NO DIALTONE) chat: abort on (NO ANSWER) chat: abort on (ERROR) chat: send (atz^M) chat: expect (OK) chat: ^M chat: ^HCSQ:"LTE",46,46,131,24^M chat: ^M chat: OK chat: -- got it
chat: send (ath0^M) chat: abort on (NO CARRIER) chat: expect (OK) chat: ^M chat: ^M chat: OK chat: -- got it
chat: send (ats7=90^M) chat: timeout set to 90 seconds chat: expect (OK) chat: ^M chat: ^M chat: OK chat: -- got it
chat: send (AT+CGDCONT=1,"IP","internet.partner1"^M) chat: expect (OK) chat: ^M chat: ^M chat: OK chat: -- got it
"The configuration for the modem is usually performed under config sys lte-modem, not under config sys modem was for 3G...not LTE if I really correctly......there can be an issue if you have both modem/ltemodem enabled on the device as it can create a USB conflict."
He will check but needs some time to go through old engineer reports.
We will then come back to you once he will have the result of these tests.
hm usb modem sticks are always problematic. This after all is due to a big fail by design in usb protocoll. Due to this every manufacturer creates its own pair of device and vendor id and the kernel drivers would have to know every single one because additionally there is no generic standard like there is for usb storage devices. That means one Stick might work and annother will not even though it contains the same hardware.
I tried with several such sticks on Fortigates and I only found one that worked. I finally ended up using FortiExtenders or LTE capable routers because that doesn't need any kernel driver support.
They just hand you ethernet on an interface.
"It is a mistake to think you can solve any major problems just with potatoes." - Douglas Adams
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.