Feature proposal: Cellular Router Profile Manager with jurisdiction-aware modem identity management

[LockBox22]

I would like to propose a privacy-aware cellular/network profile system for Flipper One, inspired by portable field-router workflows and devices such as GL.iNet Mudi with cellular modules.

Since Flipper One includes an M.2 Key-B expansion interface with SIM/eSIM lines, it could become a very powerful portable cellular router, VPN gateway, Tor gateway, and network diagnostics device.

Proposal: Cellular Router & Privacy Profile Manager

I propose adding a dedicated “Cellular Router Profile Manager” or “Privacy-Aware Network Profile Mode” for Flipper One.

The goal would be to allow users to create separate, clearly defined network profiles for legitimate use cases such as:

• portable LTE/5G router mode
• VPN gateway mode
• Tor gateway mode
• field network diagnostics
• temporary travel profile
• lab/testing profile
• per-SIM or per-operator configuration
• quick reset of temporary network state

Suggested features

The profile manager could support:

• M.2 LTE/5G modem detection
• APN configuration per profile
• SIM/ICCID-based profile selection
• VPN configuration per profile
• Tor gateway mode per profile
• DNS mode per profile
• firewall / kill switch per profile
• hostname per profile
• DHCP client identity per profile
• MAC address profile/proxying for Ethernet, Wi-Fi, and USB Ethernet
• one-click reset of temporary network settings
• modem diagnostics screen
• signal, band, operator, registration, and roaming status
• modem firmware/version display
• compatibility matrix for tested LTE/5G modules

Suggested modem compatibility targets

I would suggest testing and documenting compatibility with common LTE/5G modules, especially M.2 Key-B modules used in routers, laptops, industrial gateways, and embedded Linux systems.

Suggested native M.2 LTE/5G modules to evaluate:

• Quectel EM06 / EM061K-GL — LTE Cat 6 M.2
• Quectel EM12 / EM120K / EM120R-GL — LTE Cat 12 M.2
• Quectel EM160R-GL — LTE Cat 16 M.2
• Quectel RM500Q-GL — 5G Sub-6 M.2
• Quectel RM500U — 5G Sub-6 M.2
• Quectel RM502Q-AE — 5G M.2
• Quectel RM520N-GL — 5G Release 16 M.2
• Sierra Wireless EM7455 — LTE-A M.2
• Sierra Wireless EM7565 — LTE-A Pro Cat 12 M.2
• Telit Cinterion FN980 — 5G M.2
• Telit Cinterion FN990A28 / FN990A40 — 5G M.2
• Telit Cinterion FN990B40 — 5G M.2
• Fibocom FM350-GL — 5G M.2
• Fibocom FM160-GL — 5G M.2

Legacy / router-reference modules worth documenting separately:

• Quectel EP06 / EG06 class modules, commonly used in some LTE router projects
• Quectel EC25 / EG25 class modules, useful as a reference for older LTE workflows

For Flipper One, the main focus should probably be native M.2 modules, while Mini PCIe modules such as EP06 could be treated as reference devices or adapter-based test cases.

Lawful IMEI management / provisioning

One important feature request is a carefully designed, jurisdiction-aware modem identity management layer.

In some jurisdictions and legitimate service scenarios, modem IMEI repair, restoration, or re-provisioning may be allowed, for example:

• repairing a corrupted modem identity after firmware failure
• restoring the original factory IMEI
• authorized service operations
• lab or certification testing
• lawful use in countries where IMEI reprogramming is permitted
• working with modules that support vendor-authorized provisioning procedures

I am not suggesting a generic IMEI spoofing tool or a feature intended to bypass carrier rules. Instead, I suggest a compliance-aware design with clear boundaries:

• disabled by default
• advanced/developer mode only
• clear legal warning before access
• no random IMEI generation
• no cloning workflow
• no “bypass carrier restriction” workflow
• no default public instructions for unauthorized modification
• documentation should explain that users are responsible for local law compliance
• support should be limited to vendor-documented or vendor-authorized methods
• the compatibility matrix should clearly document whether a module supports only read-only IMEI display, factory restore, authorized repair, or no identity-management operations at all

The UI could separate this into categories:

1. Display modem identity
   Read-only information such as IMEI, firmware version, module model, serial number, and regulatory status.

2. Restore original identity
   For modules where vendor-supported restoration of factory identity is possible.

3. Authorized service / provisioning mode
   Hidden behind a legal warning and intended only for jurisdictions and service cases where this is permitted.

4. Unsupported / blocked
   If a modem vendor does not support lawful IMEI provisioning, Flipper One should clearly display that the feature is unsupported for that module.

Why this would be useful

Flipper One has the potential to become a serious portable Linux-based network tool, not only a general hacking device.

A well-designed cellular profile system would be useful for:

• field engineers
• security researchers
• network administrators
• privacy-conscious users
• travelers
• embedded Linux users
• people testing their own routers, SIMs, VPNs, and network infrastructure

The important part is to make the system transparent, legal, and safe by design.

Instead of encouraging misuse, Flipper One could define a responsible model for cellular modem management:

• clear UI
• strong compliance boundaries
• no hidden behavior
• no unsafe defaults
• complete modem compatibility documentation
• legal warnings where necessary
• focus on legitimate network diagnostics and privacy-preserving configuration

I can help

I would be interested in helping with:

• user stories
• UI flow for the Cellular Router Profile Manager
• modem compatibility matrix draft
• documentation
• testing scenarios
• VPN/Tor gateway workflow
• profile system design
• legal/compliance wording for modem identity management

I think this would fit Flipper One very well because the device already has the hardware direction needed for this: Linux, M.2 expansion, SIM/eSIM lines, Ethernet, Wi-Fi, and portable field use.