Joachim Wiberg
7b7baa0730
Cellular modem location data (GPS coordinates, 3GPP cell info) was
previously CLI-only — 'show modem modem0' shelled out to modem-info
which queried mmcli on demand and rendered straight to terminal.
NETCONF/RESTCONF clients had no view into modem location, and there
was no way to tell how stale any modem-state field was.
This commit moves both into the YANG operational tree so they are
accessible through every northbound interface, not just the CLI. It
is Phase 1 of the modem GPS / location integration plan; Phase 2 will
route the modem's NMEA TTY into the existing gpsd → chronyd pipeline
so cellular modems can also serve as an NTP fallback time source.
YANG (infix-hardware.yang, revision 2026-05-10):
- modem-state/last-change (yang:date-and-time): freshness indicator
for the modem-state subtree, bumped on each modemd poll cycle
- modem-state/location-state container: source (gps|3gpp|...),
latitude/longitude/altitude (decimal64 6/6/1 fraction-digits),
cell-id/lac/tac/mcc/mnc, and its own last-change
Runtime path:
- modemd's check_location() now writes
/run/modemd/modemN/location/data.json with the full location data
plus an RFC3339 last-change. Atomic via tmp+rename. Walks the
mmcli output once instead of twice.
- check() touches /run/modemd/modemN/state.json with a fresh
last-change after each successful state poll.
- yanger/infix_modem.py reads both files via HOST.read_json and
folds them into the modem-state operational subtree.
- cli_pretty show_modem_detail rewritten to consume the operational
tree (same path as 'show modem' overview), with new 'Last Update'
lines for both top-level state and location.
- bin/show/modem() consolidated: both 'show modem' and
'show modem REF' use get_json('/ietf-hardware:hardware') — no
more direct modem-info subprocess call.
Cleanup along the way:
- Removed the legacy /run/modemd/modemN/location/{up,down,disabled,
failed} marker file writes — they had no readers anywhere in the
tree. In-memory self.location['state'] is kept purely as the
edge-trigger for the 'Retrieved GPS location' log line.
- Aligned now_rfc3339() output with yanger.common.YangDate (+00:00
form, not Z) so consumers see one consistent yang:date-and-time
format regardless of producer.
- Fixed multi-modem SIM scoping in show_modem_detail: now derives
sim<N> from modem<N> instead of picking the first SIM globally.
The bearer / hardware-revision / phone-number / supported-carrier
sections of 'show modem REF' are deliberately omitted for now —
those fields are not yet in the YANG tree. Bearer details in
particular likely belong on the wwan interface
(ietf-interfaces:interfaces-state) rather than on the modem hardware
component, and can be addressed in a follow-up.
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Turn any ARM or x86 device into a powerful, manageable network appliance in minutes. From $35 Raspberry Pi boards to enterprise switches — deploy routers, IoT gateways, edge devices, or custom network solutions that just work.
Our Values
🔒 Immutable
Your system never breaks. Read-only filesystem with atomic upgrades
means no configuration drift, no corrupted updates, and instant rollback
if something goes wrong. Deploy once, trust forever.
🤝 Friendly
Actually easy to use. Auto-generated CLI from standard YANG models comes
with built-in help for every command — just hit ? or
TAB for context-aware assistance.
Familiar NETCONF & RESTCONF APIs and comprehensive documentation mean you're never stuck. Whether you're learning networking or managing enterprise infrastructure.
🛡️ Secure
Built with security as a foundation, not an afterthought. Minimal
attack surface, separation between system and data, and container
isolation. Sleep better knowing your infrastructure is protected.
Why Choose Infix
Hardware Flexibility: Start with a $35 Raspberry Pi, scale to enterprise switching hardware. Same OS, same tools, same reliability.
Standards-Based: Built around YANG models and IETF standards. Learn once, use everywhere - no vendor lock-in.
Container Ready: Run your applications alongside networking functions. GPIO access, dedicated Ethernet ports, custom protocols — your device, your rules.
Use Cases
- Home Labs & Hobbyists:
Transform a Raspberry Pi into a full-featured router with WiFi - IoT & Edge Computing:
Bridge devices to the cloud with reliable, updatable gateways - Small Business Networks:
Enterprise-grade features without the complexity or cost - Developers & Makers:
Test networking concepts, prototype IoT solutions, or build custom appliances - Network Professionals:
Consistent tooling from development to production deployment.
How about a digital twin using raw Qemu or GNS3!
Quick Example
Configure an interface in seconds - the CLI guides you with built-in help:
admin@infix-12-34-56:/> configure
admin@infix-12-34-56:/config/> edit interface eth0
admin@infix-12-34-56:/config/interface/eth0/> set ipv4 TAB
address autoconf bind-ni-name dhcp
enabled forwarding mtu neighbor
admin@infix-12-34-56:/config/interface/eth0/> set ipv4 address 192.168.2.200 prefix-length 24
admin@infix-12-34-56:/config/interface/eth0/> show
type ethernet;
ipv4 {
address 192.168.2.200 {
prefix-length 24;
}
}
admin@infix-12-34-56:/config/interface/eth0/> diff
interfaces {
interface eth0 {
+ ipv4 {
+ address 192.168.2.200 {
+ prefix-length 24;
+ }
+ }
}
}
admin@infix-12-34-56:/config/interface/eth0/> leave
admin@infix-12-34-56:/> show interfaces
INTERFACE PROTOCOL STATE DATA
lo ethernet UP 00:00:00:00:00:00
ipv4 127.0.0.1/8 (static)
ipv6 ::1/128 (static)
eth0 ethernet UP 52:54:00:12:34:56
ipv4 192.168.2.200/24 (static)
ipv6 fe80::5054:ff:fe12:3456/64 (link-layer)
admin@infix-12-34-56:/> copy running startup
Notice how TAB completion shows available options, show
displays current config, and diff shows exactly what changed before
you commit your changes with the leave command.
For more information, see CLI documentation.
Get Started
Get pre-built images for your hardware. Use the CLI, web
interface, or standard NETCONF/RESTCONF tools, e.g., curl. Add
containers for any custom functionality you need.
Supported Platforms
- Raspberry Pi 2B/3B/4B/CM4 - Perfect for home labs, learning, and prototyping
- Banana Pi-R3 - Your next home router and gateway
- NanoPi R2S - Compact dual-port router in a tiny package
- x86_64 - Run in VMs or on mini PCs for development and testing
- Marvell CN9130 CRB, EspressoBIN - High-performance ARM64 platforms
- Microchip SparX-5i - Enterprise switching capabilities
- Microchip SAMA7G54-EK - ARM Cortex-A7
- NXP i.MX8MP EVK - Highly capable ARM64 SoC
- StarFive VisionFive2 - RISC-V architecture support
Why start with Raspberry Pi? It's affordable, widely available, has built-in WiFi + Ethernet, and runs the exact same Infix OS you'd deploy in production. Perfect for learning, prototyping, or even small-scale deployments.
Technical Details
Built on proven open-source foundations: Linux, Buildroot, and sysrepo — for reliability you can trust:
- Immutable OS: Read-only filesystem, atomic updates, instant rollback
- YANG Configuration: Industry-standard models with auto-generated tooling
- Hardware Acceleration: Linux switchdev support for wire-speed packet processing
- Container Integration: Docker support with flexible network and hardware access
- Memory Efficient: Runs comfortably on devices with as little as 256 MB RAM
- Code Signing: Releases are cryptographically signed for integrity verification
Perfect for everything from resource-constrained edge devices to high-throughput network appliances.
With the entire system modeled in YANG, scalability is no longer an issue, be it in development, testing, or end users deploying and monitoring their devices. All knobs and dials are accessible from the CLI (console/SSH), or remotely using the native NETCONF or RESTCONF APIs.
Check the Latest Build for bleeding-edge features.
