Community modem definitions and drivers for GL.iNet’s stock cellular stack

I have published an open source project for adding unsupported cellular modems to GL.iNet firmware:

gl-modem-community extends the stock modem model table and cellular services instead of replacing them. The GL.iNet admin panel, mobile app backend, JSON-RPC, ubus APIs and existing modem support remain in place.
The first supported setup is:
• Router: GL-MT3000 (Beryl AX)
• Modem: Fibocom FM350-GL
• USB IDs: 0e8d:7126 and 0e8d:7127
• Observed USB composition: RNDIS with ttyUSB serial ports
The two product IDs use different AT port offsets. Product 7126 uses offset 2, while 7127 uses offset 3.
On my reference setup, I have confirmed:
• Detection by GL.iNet’s stock cellular services
• Detection in the GL.iNet admin panel and mobile app
• SIM status
• ICCID and IMSI retrieval
• Runtime addition of the FM350 model definition
• Restoration of the original stock paths when the package is stopped or removed
The project uses runtime overlays, leaving the original SquashFS model table unchanged. Modem-specific RPC handlers can implement only the calls they need. Other calls fall back to GL.iNet’s stock backend.
The current release provides:
• A signed APK package and APK repository index
• An IPK package for aarch64_cortex-a53
• SHA-256 checksums
• CycloneDX SBOMs
• GitHub build provenance
• Automated package and offline test workflows
A few limitations are important:

  1. This package requires GL.iNet’s proprietary cellular backend. It does not work as a standalone modem manager on vanilla OpenWrt.
  2. The GL-MT3000 is currently the only tested reference router.
  3. The IPK package builds against the pinned OpenWrt 24.10 MediaTek Filogic SDK, but I have not validated its runtime behavior on hardware.
  4. Detection and SIM access are confirmed, but the complete PDP, routing, DNS, reconnect, reboot and interface recovery matrix is still being validated.
    I would appreciate hardware reports from users with other GL.iNet routers or unsupported modems. A useful report should include:
    • Router model
    • GL.iNet firmware version
    • Package format, APK or IPK
    • Modem name and firmware version
    • USB vendor and product IDs
    • USB interface layout and AT port
    • Redacted logread output
    • Whether detection, connection, routing, DNS, reconnect and reboot recovery worked
    Please report results or compatibility problems here:
    Issues · rudironsoni/gl-modem-community · GitHub
    Contributions for additional modems are also welcome. The repository documents the extension points, test requirements and hardware evidence expected for a new driver.

3 Likes

Hi, rudironsonijr

Thank you very much for developing and sharing this open-source project with the community!

This provides a valuable approach for extending support for additional cellular modems while retaining GL.iNet’s stock cellular services. The detailed documentation, packaging, testing workflows, and contribution guidelines are especially appreciated.

Thank you again for the time and effort you have put into this project and for your contribution to the community!

1 Like