after updating to version higher than 2.0.1, the device changed it's USB ID and is no longer exposing the same interface and starts supporting RNDIS.
Downgrading the device to older firmware fails (the script does not see the device).
On windows, this device shows as empty SD-card reader. After ejecting, this device shows as different device. (This actually allows the downgrade to see the device, but it fails anywas later)
the device after ejecting is D-Link USB Composite Device 2001.
before eject:
idVendor: 0x2001
idProduct: 0xAB00
after eject:
idVendor: 0x2001
idProduct: 0x7E35
Any ideas on how to:
Connect the device in current mode.
Try "ejecting" the device on Hex? (it does not appear in /disk)
I purchased a brand new original packaged but still old D-Link DWM-222. Hardware rev A1 and firmware 2.1.2EU. This device with this firmware uses a proprietary software on Windows that will configure it as I believe to be an PPP device. Theoretically a setup as PPP client should therefore be possible. I did not go that route further, as RouterOS reported “could not aquire serial port”.
D-Link provides a newer firmware 2.1.4EU and 2.1.5EU via their FTP:
These newer firmwares will change the DWM-222 to an RNDIS device compatible with RouterOS “config-less LTE” providing the lte1 interface without any further configuration. The configuration interface of the dongle resides at http://192.168.0.1/ and can be routed and reached via the MikroTik device.
Edit, another finding:
After the firmware update to 2.1.4EU or 2.1.5EU, RouterOS did not pick up the config-less LTE interface right away. In fact it was required to connect with the dongle one time using Windows. On 2.1.4EU I had to start the “StartModem.exe” in the storage area of the dongle.
Edit, another finding regarding the stability:
I noticed that the following things work/dont work:
disconnecting the USB and replugging it while powered on - SOMETIMES crashes the connection until the MIkroTik is rebooted (no more DHCP answers from the stick, only discovers visible in logs)
disabling lte1 and reenabling it - works fine
doing dhcp renewals - works fine
booting with the stick attached - works mostly fine
storage part of the DWM-222 with an sd card inserted - works fine (in parallel with the modem function)
Edit, conclusion:
I conclude that OPs solution may be to actually push the firmware to the latest available option. The RNDIS interface is actually most likely what you want with current RouterOS versions and hardware. Correct me if wrong.
About a year ago i was testing DWM-222 on a different brand of router. Started as a cd rom, but the router managed to perform the switch on its own to lte modem.
Afterwards i was able to use it as a secondary WAN and more importantly to send SMS notifications from Home Assistant via console commands.
Newer fimware changed it to RNDIS as mentioed in post above, but I was unable to access the modem via AT commands. I managed to downgrade it back to original fimware. It took several attempts, and trying multiple fw versions.
Original fw allows more options for tinkering. Its not the most reliable lte dongle - when router is rebooted, i have to manually replug the modem.