I can't run LTE E3372-325 (CL5E3372M) dongle on RouterOS 7.9 (not detected). Dongle E3372-320 (CL4E3372HM) works on the same router.
Please help me solve this problem?
How did you do this ?I found a workaround. I inserted the dongle into a Windows PC, opened http://192.168.8.1, enabled Bridge mode, and voila! The dongle works in the router. I have an lte1 interface without any settings, but it it detects dhcp updates and pings 8.8.8.8.
I've searched everywhere for an update file, but it seems that it doesn't exist. All the records I find say that the modems were updated through the integrated update tool.Could anyone provide the update files or instructions for updating to H057SP9C983? Via WebUI it seems like there is no newer version than the installed available.
Unfortunately I haven't recieved any feedback from the OEM Brovi yet. I just sent them a reminder and will keep you updated if there is any news regarding the mentioned firmware or compatibility.
regards!
Yes, firmware version H057SP9C983 is already reported to work OK. The problem is that some modems do not receive that update and there is no currently known way to manually install it.
Would you please check what is the "Configuration file version" of your modem?
Edit: I think that modems with Configuration file version C778 receive updates and modems with C965 - don't.
Hi, actually I also noticed that the classic Huawei E3372h modems stopped working on v. 7.13. This thread, however, is for another type of modem - Brovi E3372-325.Hi,
my E3372 stopped working since 7.13. actually at bootup it goes up and down twice in same second but after there is no lte device visible.
Can you help me?
I've the issue also, do you've how to fix the issue?Hi, actually I also noticed that the classic Huawei E3372h modems stopped working on v. 7.13. This thread, however, is for another type of modem - Brovi E3372-325.Hi,
my E3372 stopped working since 7.13. actually at bootup it goes up and down twice in same second but after there is no lte device visible.
Can you help me?
Maybe you can open a ticket with the Mikrotik support...
It's already a known issue that would probably be corrected in the next firmware release.I've the issue also, do you've how to fix the issue?