Joachim Wiberg
dc2d429093
New Diagnostics page under Maintenance runs ping, traceroute, mtr and nmap with live output, plus a one-shot DNS lookup. A tab per tool shares a target field, source-interface and address-family selectors, and per-tool options; the field is focused on load and Enter runs the active tool from any field. Ping and traceroute stream their output line by line over SSE. mtr runs --raw and its records are translated into a live hop table — Loss%, Snt, Last, Avg, Best, Worst updating in place — running continuously until Stop, or for a set number of cycles. nmap offers a fixed set of scan profiles (quick, standard, service/version, host discovery); a CIDR target sweeps a subnet. Address family is forced with an explicit -4/-6 flag on the base binary, so a dual-stack hostname no longer follows the system's IPv6-first resolver preference on hosts that only have IPv4 routes. The streamer hands the child a real OS pipe and reaps it on exit, so a client disconnect (Stop closing the EventSource) kills the tool without leaking processes. User input is guarded: targets reject a leading dash and whitespace, the source interface is allow-listed against configured interfaces, and arguments are always passed as a slice. The target field keeps a history in localStorage. 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.
