mirror of
https://github.com/kernelkit/infix.git
synced 2026-07-30 04:33:00 +02:00
Joachim Wiberg
f78f161dbe
The initial modem import used a standalone infix-modem YANG module with
an integer-indexed list under /infix-modem:modems carrying a bearer
config mixed in with hardware config. Infix has adopted the ietf-hardware
model to allow for a clearer separation of concerns, this commit aims to
improve on that situation by refactoring the modem model to use the same
architectural pattern already used for WiFi radios, GPS receivers, and
USB ports:
Hardware:
/ietf-hardware:hardware/component[class=infix-hardware:modem]
/ietf-hardware:hardware/component[class=infix-hardware:sim]
Interface:
/ietf-interfaces:interfaces/interface[type=infix-if-type:modem]
Configuration split:
modem component — admin-state (enable/disable), radio access mode,
frequency bands, location services, probe-timeout
sim component — PIN, PUK, carrier profile
wwan interface — APN, IP type, roaming, route-preference, auth
This also enables the modem to appear in 'show hardware' alongside
other hardware components, and to be managed over NETCONF/RESTCONF
using the same ietf-hardware RPCs used for USB and WiFi.
YANG changes:
- infix-modem.yang removed (1089 lines, standalone module)
- infix-hardware.yang: new modem and sim containers, modem-state and
sim-state operational state, typedefs for bands/modes/location,
notification status-update; actions restart/reset/send-sms are
augmented directly on the component list entry (not inside container
modem) to work around sysrepo NP-container parent validation — when
checking a nested action's parent, sysrepo restricts its operational
data fetch to the container path, excluding the sibling 'class' leaf
needed to evaluate the container's 'when' condition, so the container
is never instantiated and the parent check fails
- infix-if-modem.yang: new submodule (same pattern as wifi/wireguard)
adds the wwan bearer container to ietf-interfaces
- infix-if-type.yang: new modem identity for wwan interface type
- confd version bumped to 1.9
confd:
- if-modem.c: new file replaces the stub modem_gen() in modem.c;
generates dagger init scripts with probe-timeout wait loop and
unconditional dummy wwan creation so downstream IP config succeeds
when a USB modem is slow to enumerate at boot
- hardware.c: start/stop/enable/disable modemd (and modem-manager)
in response to admin-state changes on the modem hardware component;
use finit_enable/disable consistently
- hardware_cand_infer_class(): auto-set class for modemN/simN names
- modem.c: stripped to RPC/notification forwarding only; the old
genconf() / enable() / disable() logic is gone — hardware.c owns
the lifecycle now
- interfaces.c: remove wwan from wait-interface timeout (the modem
interface appearance is managed by modemd, not confd's init scripts)
- migrate/1.9: script fully migrates /infix-modem:modems to the new
split model; each modem[N] becomes a modemN hardware component and
simN sim component; each bearer becomes a wwanN interface (bearers
numbered globally across modems); APN, IP type, roaming, preferred-
mode, bands, location, PIN/PUK/carrier are all carried over; plain-
text bearer credentials are moved to a named keystore symmetric-key
(base64-encoded) referenced from bearer/authentication/password;
apn-type, firewall-enabled, dns-enabled and default-route are
dropped (no equivalent in the new model)
modemd:
- load_config() replaces the infix-modem sysrepocfg call; reads from
ietf-hardware (modem/sim config), ietf-interfaces (bearer config),
and ietf-keystore (credentials) — three standard modules instead of
one proprietary one; modems absent from sysrepo config but present
in system.json are still started (physical detection wins)
- Default route written to /etc/net.d/<iface>.conf (picked up by
netd/staticd/zebra) instead of a direct 'ip route add'; routes are
now visible to FRR for redistribution and metric-based failover
- Addresses tagged with proto wwan (rt_addrprotos entry 7) for
precise flush on disconnect without touching other address sources
- _derive_gateway() handles point-to-point bearers where modem
reports gateway as "--"; derives peer from link-scope subnet route
- SimThread exits cleanly on platforms without /dev/simctrl
- sim-setup, modem-info, modem-udev, modem-rpc, modem-sms all ported
to the ietf-hardware/ietf-interfaces namespace
statd:
- infix_modem.py now emits modem-state and sim-state into ietf-hardware
component entries (modem0, sim0, ...) instead of a separate tree;
sim-state reports physical slot, lock state, and SIM operator name
- ietf_hardware.py: hardware component names deduplicated by rename
(cpu → cpu, cpu1, ...) to prevent LY_EVALID when hwmon and thermal
sysfs both normalise to the same sensor name
- show hardware: Cellular Modems and SIM Cards tables added; sensor
table width now adapts to the widest section in the output
- 00-probe: USB modem detection writes to system.json["modem"], same
source as wifi-radios, feeding gen-hardware which emits the
ietf-hardware component entries at factory config generation time
CLI:
- 'show modem [ref]': without ref shows Cellular Modems and SIM Cards
tables (same data subset as 'show hardware'); with ref shows a full
per-modem dump (hardware info, status, cellular, SIM, bearers, GPS)
- 'modem restart <ref>': disconnect and reconnect all bearers without
a full hardware reset
- 'modem reset <ref>': factory-reset the modem firmware
- 'modem sms <ref> <number> <message>': send an SMS via the modem
(uses the signalling plane; no active data bearer required)
- MODEMS PTYPE provides tab-completion reading modem names from
/run/system.json
doc:
- Add initial User Guide for modems
- Update ChangeLog with modem news
- Use absolute URLs in ChangeLog. Relative links only work for in-tree
references, not in release notes
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
439 lines
18 KiB
Markdown
439 lines
18 KiB
Markdown
# Cellular Modem (WWAN)
|
|
|
|
Infix supports cellular modem connectivity via modems that expose a
|
|
QMI or MBIM control interface over USB. Form factor does not matter:
|
|
USB dongles, mPCIe cards, and M.2 Key-B modules all work as long as
|
|
the modem chipset uses USB on the connector (the typical case for
|
|
4G/LTE modems). See *Supported Modems* below for the exceptions.
|
|
|
|
Setup involves three configuration items:
|
|
|
|
- A `modem0` hardware component for the physical modem
|
|
- A `sim0` hardware component for the SIM card slot
|
|
- A `wwan0` network interface that references both and carries the
|
|
bearer (APN) configuration
|
|
|
|
## Architecture
|
|
|
|
Infix uses a three-layer architecture for cellular modem support:
|
|
|
|
1. **Modem hardware component (modem0)**: the physical modem
|
|
- Configured via `ietf-hardware` with class `infix-hardware:modem`
|
|
- `admin-state` controls whether ModemManager and modemd are active
|
|
- Holds physical-layer config: allowed bands, preferred mode, location
|
|
- Auto-discovered into factory-default config when the modem is
|
|
present at first boot
|
|
|
|
2. **SIM hardware component (sim0)**: the SIM card slot
|
|
- Configured via `ietf-hardware` with class `infix-hardware:sim`
|
|
- Holds PIN/PUK credentials and carrier profile
|
|
- Auto-discovered into factory-default config alongside the modem
|
|
|
|
3. **Network interface (wwan0)**: data bearer to the cellular network
|
|
- Configured via `ietf-interfaces` with type `infix-if-type:modem`
|
|
- References a modem component and a SIM component
|
|
- Holds bearer config: APN, IP type, roaming, route preference,
|
|
authentication
|
|
- Always added by the user, never auto-created
|
|
|
|
## Naming Conventions
|
|
|
|
| **Name Pattern** | **Type** | **Description** |
|
|
|------------------|----------------------|-------------------------------------------------|
|
|
| `modemN` | Modem hardware | Hardware component for the physical modem |
|
|
| `simN` | SIM hardware | Hardware component for the SIM card slot |
|
|
| `wwanN` | Modem interface | Network interface for cellular data |
|
|
|
|
Where `N` is a number (0, 1, 2, ...).
|
|
|
|
> [!TIP]
|
|
> Using these naming conventions simplifies configuration since type and
|
|
> class are automatically inferred. Creating a hardware component named
|
|
> `modem0` automatically sets its class to `infix-hardware:modem`, and
|
|
> creating an interface named `wwan0` automatically sets its type to
|
|
> `infix-if-type:modem`.
|
|
>
|
|
> **Note:** This inference only works via the CLI. When configuring
|
|
> over NETCONF or RESTCONF the class and type must be set explicitly.
|
|
|
|
## Multi-Bearer (Multiple APNs)
|
|
|
|
Multiple wwan interfaces can reference the same modem component, each
|
|
with a different APN. Same idea as multi-SSID on a WiFi radio: one
|
|
hardware modem, several independent data connections.
|
|
|
|
Configure `wwan0` and `wwan1` both pointing to `modem0`:
|
|
|
|
```
|
|
edit interface wwan0 wwan
|
|
set modem modem0
|
|
set bearer apn internet
|
|
|
|
edit interface wwan1 wwan
|
|
set modem modem0
|
|
set bearer apn corporate.vpn.apn
|
|
```
|
|
|
|
## Current Limitations
|
|
|
|
- The modem must be present at boot. Hot-plug is not supported.
|
|
- If the modem is absent at boot, and no `probe-timeout` is set, a
|
|
dummy `wwan0` placeholder is created immediately so IP configuration
|
|
can proceed. A reboot is required once the hardware is inserted.
|
|
|
|
## Supported Modems
|
|
|
|
Modems exposing a CDC-WDM control interface over USB are supported,
|
|
regardless of physical form factor. Two protocols are handled by
|
|
ModemManager:
|
|
|
|
- **MBIM**: Mobile Broadband Interface Model (e.g. Sierra Wireless,
|
|
Quectel EM06/EM12)
|
|
- **QMI**: Qualcomm MSM Interface (e.g. Sierra Wireless EM7xxx,
|
|
Quectel EM/RMxxx)
|
|
|
|
Most 4G/LTE modules (USB dongles, mPCIe cards, M.2 Key-B) use USB on
|
|
the connector even when the slot also carries PCIe lanes. From Infix's
|
|
view they are all USB modems. PCIe-only modems (some 5G NR modules)
|
|
are not supported, since the modemd / ModemManager pipeline assumes a
|
|
USB-attached control interface.
|
|
|
|
## Step-by-step Setup
|
|
|
|
### 1. Hardware Detection
|
|
|
|
At first boot, USB modems detected by the kernel are written to
|
|
`/run/system.json` and added as hardware components in the
|
|
factory-default configuration. Verify the modem appears:
|
|
|
|
<pre class="cli"><code>admin@example:/> <b>show modem</b>
|
|
──────────────────────────────────────────────────────────────
|
|
<span class="title">Cellular Modems</span>
|
|
NAME MANUFACTURER MODEL STATE NETWORK SIGNAL
|
|
modem0 Quectel EM06-E registered lte good
|
|
──────────────────────────────────────────────────────────────
|
|
<span class="title">SIM Cards</span>
|
|
NAME SLOT STATE OPERATOR
|
|
sim0 1 unlocked Tele2
|
|
</code></pre>
|
|
|
|
The `STATE`, `SIM STATE`, and `SIGNAL` columns are color-coded so the
|
|
healthy / attention / problem cases are visible at a glance: green for
|
|
`registered`, `connected`, `unlocked`, `excellent`, `good`; yellow for
|
|
transient or attention states like `enabling`, `pin-required`, `poor`;
|
|
red for `failed`, `not-inserted`, `bad`.
|
|
|
|
If `modem0` does not appear:
|
|
|
|
- Verify the kernel sees the modem (`dmesg | grep -i mbim` or
|
|
`dmesg | grep -i qmi`). Without a kernel driver no further setup
|
|
is possible.
|
|
- On boards with a custom factory configuration, or after replacing
|
|
hardware on a running system, the components may need to be added
|
|
manually. See Step 2.
|
|
|
|
### 2. Hardware Components
|
|
|
|
If `show modem` already lists `modem0` and `sim0`, the components were
|
|
auto-discovered into the factory-default configuration and you can skip
|
|
ahead to Step 3.
|
|
|
|
Otherwise, add them manually. The class is inferred from the component
|
|
name (`modemN` → `infix-hardware:modem`, `simN` → `infix-hardware:sim`).
|
|
The `admin-state` must be set explicitly. There is no implicit default,
|
|
and without `unlocked` confd will not start ModemManager or modemd:
|
|
|
|
<pre class="cli"><code>admin@example:/> <b>configure</b>
|
|
admin@example:/config/> <b>edit hardware component modem0</b>
|
|
admin@example:/config/hardware/component/modem0/> <b>set state admin-state unlocked</b>
|
|
admin@example:/config/hardware/component/modem0/> <b>end</b>
|
|
admin@example:/config/hardware/> <b>edit component sim0</b>
|
|
admin@example:/config/hardware/component/sim0/> <b>set state admin-state unlocked</b>
|
|
admin@example:/config/hardware/component/sim0/> <b>leave</b>
|
|
admin@example:/>
|
|
</code></pre>
|
|
|
|
To take the modem offline cleanly without removing the configuration,
|
|
set `admin-state locked`. All related services are stopped and the
|
|
bearer is torn down before the modem goes offline:
|
|
|
|
<pre class="cli"><code>admin@example:/config/> <b>edit hardware component modem0</b>
|
|
admin@example:/config/hardware/component/modem0/> <b>set state admin-state locked</b>
|
|
admin@example:/config/hardware/component/modem0/> <b>leave</b>
|
|
</code></pre>
|
|
|
|
#### Slow USB Modems
|
|
|
|
USB modems can be slow to enumerate at boot. The kernel wwan interface
|
|
may not appear until several seconds after confd starts applying
|
|
configuration. The `probe-timeout` leaf inside the `modem` hardware
|
|
configuration container controls how long confd waits. It defaults to
|
|
30 seconds when the container is present.
|
|
|
|
To enable the timeout, create the modem configuration container (this
|
|
also lets you configure bands, preferred mode, etc.):
|
|
|
|
<pre class="cli"><code>admin@example:/config/> <b>edit hardware component modem0 modem</b>
|
|
admin@example:/config/hardware/component/modem0/modem/> <b>leave</b>
|
|
</code></pre>
|
|
|
|
With `probe-timeout` at its default of 30, confd waits up to 30 seconds
|
|
for the wwan interface to appear before proceeding. For most modems it
|
|
is ready in 2-5 seconds. If the modem has not appeared within the
|
|
timeout, a dummy placeholder interface is created and a reboot is
|
|
required for the real interface to take over. Set `probe-timeout 0`
|
|
to disable waiting entirely.
|
|
|
|
> [!NOTE]
|
|
> Some Quectel modules (e.g. EM05) re-enumerate the USB device several
|
|
> times during a cold-boot firmware-init sequence that takes around 50
|
|
> to 60 seconds. Bump `probe-timeout` to 90 for those, otherwise the
|
|
> dummy placeholder fires before the modem settles and the real
|
|
> interface ends up with a different name (`wwan1` instead of `wwan0`).
|
|
|
|
### 3. Configure the Bearer (APN)
|
|
|
|
Bearer configuration lives on the `wwan0` interface. Reference the
|
|
modem hardware component and set the APN:
|
|
|
|
<pre class="cli"><code>admin@example:/> <b>configure</b>
|
|
admin@example:/config/> <b>edit interface wwan0</b>
|
|
admin@example:/config/interface/wwan0/> <b>set wwan modem modem0</b>
|
|
admin@example:/config/interface/wwan0/> <b>set wwan sim sim0</b>
|
|
admin@example:/config/interface/wwan0/> <b>set wwan bearer apn internet</b>
|
|
admin@example:/config/interface/wwan0/> <b>leave</b>
|
|
</code></pre>
|
|
|
|
The modem will connect automatically once the bearer is configured and
|
|
the hardware is unlocked.
|
|
|
|
**Key bearer parameters:**
|
|
|
|
- `apn`: Access Point Name, required, provided by your operator
|
|
(e.g. `internet`, `data.vodafone.com`, `web.tele2.se`)
|
|
- `route-preference`: Administrative distance for the default route
|
|
(default: `200`). Higher value = lower priority. The default of 200
|
|
places cellular behind wired Ethernet (distance 5) and WiFi, so
|
|
cellular acts as a failover when the wired link is up
|
|
- `roaming`: Allow data when roaming on a foreign network
|
|
(default: `false`)
|
|
- `ip-type`: `ipv4`, `ipv6`, or `ipv4v6` dual-stack
|
|
(default: `ipv4v6`)
|
|
|
|
### 4. Configure Authentication
|
|
|
|
Most consumer APNs connect without credentials. If your operator
|
|
requires authentication, first store the password in the keystore, then
|
|
reference it from the bearer.
|
|
|
|
Create the keystore entry for the APN password:
|
|
|
|
<pre class="cli"><code>admin@example:/> <b>configure</b>
|
|
admin@example:/config/> <b>edit keystore symmetric-key apn-pass</b>
|
|
admin@example:/config/keystore/…/apn-pass/> <b>set key-format passphrase-key-format</b>
|
|
admin@example:/config/keystore/…/apn-pass/> <b>change cleartext-symmetric-key</b>
|
|
Passphrase: ************
|
|
Retype passphrase: ************
|
|
admin@example:/config/keystore/…/apn-pass/> <b>leave</b>
|
|
</code></pre>
|
|
|
|
Then point the bearer's authentication at it:
|
|
|
|
<pre class="cli"><code>admin@example:/> <b>configure</b>
|
|
admin@example:/config/> <b>edit interface wwan0 wwan bearer</b>
|
|
admin@example:/config/interface/wwan0/wwan/bearer/> <b>set authentication username myuser</b>
|
|
admin@example:/config/interface/wwan0/wwan/bearer/> <b>set authentication password apn-pass</b>
|
|
admin@example:/config/interface/wwan0/wwan/bearer/> <b>leave</b>
|
|
</code></pre>
|
|
|
|
Setting any leaf inside `authentication` creates the container, which
|
|
enables authentication. The `password` leaf is a reference to a
|
|
symmetric key in the keystore, not the plaintext password itself.
|
|
|
|
The authentication protocol defaults to `chap`. To use PAP instead:
|
|
|
|
<pre class="cli"><code>admin@example:/config/interface/wwan0/wwan/bearer/> <b>set authentication type pap</b>
|
|
</code></pre>
|
|
|
|
### 5. Configure SIM PIN
|
|
|
|
If the SIM requires a PIN to unlock, configure it on the SIM hardware
|
|
component:
|
|
|
|
<pre class="cli"><code>admin@example:/config/> <b>edit hardware component sim0</b>
|
|
admin@example:/config/hardware/component/sim0/> <b>set sim pin 1234</b>
|
|
admin@example:/config/hardware/component/sim0/> <b>leave</b>
|
|
</code></pre>
|
|
|
|
### 6. Verify Connectivity
|
|
|
|
Once connected, the `wwan0` interface receives an IP address from the
|
|
carrier and modemd installs the default route:
|
|
|
|
<pre class="cli"><code>admin@example:/> <b>show interface wwan0</b>
|
|
name : wwan0
|
|
type : modem
|
|
index : 5
|
|
mtu : 1500
|
|
operational status : up
|
|
ip forwarding : enabled
|
|
physical address : 12:34:56:78:9a:bc
|
|
ipv4 addresses : 10.142.87.33/30 (wwan)
|
|
ipv6 addresses : 2001:db8:1:2::1/64 (wwan)
|
|
in-octets : 84213
|
|
out-octets : 31456
|
|
</code></pre>
|
|
|
|
Check the full modem state including signal quality and registration:
|
|
|
|
<pre class="cli"><code>admin@example:/> <b>show modem modem0</b>
|
|
<span class="header">MODEM: modem0 </span>
|
|
──────────────────────────────────────────────────────────────
|
|
<span class="title">Hardware Information</span>
|
|
Manufacturer : Quectel
|
|
Model : EM06-E
|
|
Firmware Version : EM06ELAR04A07M4G
|
|
Serial Number : 352753090141905
|
|
IMSI : 240021234567890
|
|
ICCID : 8946020000001234567
|
|
──────────────────────────────────────────────────────────────
|
|
<span class="title">Status</span>
|
|
State : connected
|
|
Power State : on
|
|
Signal : Quality: 72% good RSSI: -59 dBm RSRP: -95 dBm RSRQ: -11.0 dB
|
|
──────────────────────────────────────────────────────────────
|
|
<span class="title">Cellular</span>
|
|
Registration : home
|
|
Service State : attached
|
|
Operator : Tele2
|
|
Operator ID : 23002
|
|
Network Type : lte
|
|
──────────────────────────────────────────────────────────────
|
|
<span class="title">SIM Card</span>
|
|
Name : sim0
|
|
Slot : 1
|
|
Lock State : unlocked
|
|
Operator : Tele2
|
|
</code></pre>
|
|
|
|
When the modem is in trouble, the same view shows why. A
|
|
`State: failed` line is followed by `Failed Reason` (e.g.
|
|
`sim-missing`), and the `SIM Card` section's `Lock State` reads
|
|
`not-inserted` or `pin-required` to match.
|
|
|
|
## Cellular Failover
|
|
|
|
The default `route-preference` (200) is deliberately higher than the
|
|
distances used by wired Ethernet (udhcpc default: 5) and WiFi. When a
|
|
wired link is up it takes precedence automatically; cellular becomes
|
|
the active path only if higher-priority routes are withdrawn.
|
|
|
|
A default route via the bearer is always installed when the bearer
|
|
connects. To adjust the failover priority between two cellular modems,
|
|
or to prefer cellular over WiFi, set `route-preference` explicitly:
|
|
|
|
<pre class="cli"><code>admin@example:/config/> <b>edit interface wwan0 wwan bearer</b>
|
|
admin@example:/config/interface/wwan0/wwan/bearer/> <b>set route-preference 100</b>
|
|
admin@example:/config/interface/wwan0/wwan/bearer/> <b>leave</b>
|
|
</code></pre>
|
|
|
|
Lower `route-preference` = higher priority.
|
|
|
|
## Roaming
|
|
|
|
Data roaming is disabled by default. To allow the modem to connect
|
|
when on a foreign (roaming) network:
|
|
|
|
<pre class="cli"><code>admin@example:/config/> <b>edit interface wwan0 wwan bearer</b>
|
|
admin@example:/config/interface/wwan0/wwan/bearer/> <b>set roaming true</b>
|
|
admin@example:/config/interface/wwan0/wwan/bearer/> <b>leave</b>
|
|
</code></pre>
|
|
|
|
> [!IMPORTANT]
|
|
> Enabling roaming may incur significant charges depending on your
|
|
> mobile subscription. Check with your operator before enabling.
|
|
|
|
## Management Commands
|
|
|
|
### Restart Bearer
|
|
|
|
Disconnect and reconnect all bearers without resetting the modem
|
|
hardware. Use this after changing APN or authentication settings:
|
|
|
|
<pre class="cli"><code>admin@example:/> <b>modem restart modem0</b>
|
|
</code></pre>
|
|
|
|
### Reset Modem
|
|
|
|
Factory-reset the modem firmware. This clears all modem-internal
|
|
settings and takes longer than a restart. Only use it if the modem is
|
|
in a bad state that a bearer restart cannot fix:
|
|
|
|
<pre class="cli"><code>admin@example:/> <b>modem reset modem0</b>
|
|
</code></pre>
|
|
|
|
> [!NOTE]
|
|
> Not all modules accept `--reset` from ModemManager. Quectel EM05,
|
|
> for example, rejects both `--reset` and `--factory-reset`. The only
|
|
> way to recover from a hung firmware on these is a physical power
|
|
> cycle. When the modem reports the rejection, modemd logs it once and
|
|
> stops retrying.
|
|
|
|
### Send SMS
|
|
|
|
Send an SMS message via the signalling plane. No active data bearer
|
|
is required; the modem only needs to be registered on the network:
|
|
|
|
<pre class="cli"><code>admin@example:/> <b>modem sms modem0 +46701234567 "Hello from Infix"</b>
|
|
</code></pre>
|
|
|
|
> [!NOTE]
|
|
> Some SIM cards have Fixed Dialing Number (FDN) enabled, which
|
|
> restricts outgoing SMS and calls to a pre-configured whitelist. If
|
|
> `modem sms` fails, check whether FDN is active with `mmcli -m 0` and
|
|
> look for `enabled locks: fixed-dialing` in the output.
|
|
|
|
## Troubleshooting
|
|
|
|
**Modem not detected (`show modem` shows no modem entry)**
|
|
|
|
- Verify the modem is connected and recognized by the kernel: check
|
|
`dmesg` for `cdc_mbim` or `qmi_wwan` driver messages
|
|
- Confirm `/sys/class/usbmisc/` contains a `cdc-wdm*` entry
|
|
- The modem must be present at boot; hotplug after boot is not
|
|
supported
|
|
|
|
**`wwan0` shows as `down` or has no IP address**
|
|
|
|
- Check `show modem modem0`. The State should show `registered` or
|
|
`connected`, not `failed`
|
|
- If the State is `failed`, look at the `Failed Reason` line that
|
|
immediately follows:
|
|
- `sim-missing`: the SIM Card section will also show
|
|
`Lock State: not-inserted`. Power off the device, insert the
|
|
SIM, power back on. A warm reboot is not enough; on most M.2
|
|
slots the SIM tray stays powered through reboot, so the modem
|
|
keeps the original not-inserted reading
|
|
- `unlock-required`: the SIM Card section will show
|
|
`Lock State: pin-required`. Configure the PIN with
|
|
`set hardware component sim0 sim pin <code>`
|
|
- `sim-wrong` / `sim-error`: the SIM is not compatible or is
|
|
damaged. Try a different SIM
|
|
- Verify the APN is correct for your operator
|
|
- Check system logs with `show log` for modemd or ModemManager
|
|
messages
|
|
|
|
**`wwan0` interface is a dummy (no data flows, no carrier address)**
|
|
|
|
- The modem was not enumerated by the kernel before confd applied
|
|
config
|
|
- Create the modem hardware configuration container (see Step 2),
|
|
which enables the default 30-second probe-timeout so confd waits for
|
|
the wwan interface before falling back to a dummy placeholder
|
|
|
|
**High latency or poor signal**
|
|
|
|
- Use `show modem modem0` to check signal quality and RSRP
|
|
- Signal below -110 dBm RSRP typically indicates poor coverage
|
|
- Consider repositioning the antenna or the device
|