How kernelkit/infix works
Infix is a managed network-appliance OS. Its principal workflow is configuring a device through the CLI or web UI, applying modeled configuration through sysrepo-backed services, and exposing operational state for monitoring. The repository also includes routing backends, host-status collectors, and configuration-file transfer. The README documents shared YANG-driven CLI and API access; source excerpts show selected routing, service, and status behaviors. Several subsystem connections are documented rather than directly traced in the sampled source.
Main entry points: main.c YANG configuration · server.go Web UI · core.h Config handlers · netd.c Routing daemon
Components 18
User Interfaces
- Generated CLI
src/klish-plugin-infix/src/infix.c - Web UI
src/webui/internal/server/server.go - RESTCONF client
src/webui/internal/restconf/client.go - Config transfer
src/bin/copy.c
Configuration Runtime
- YANG configuration
src/confd/src/main.c - Config handlers
src/confd/src/core.h - Service management
src/confd/src/services.c - Sysrepo helpers
src/libsrx/src/srx_val.c
Networking
- Routing configuration
src/confd/src/routing.c - Routing daemon
src/netd/src/netd.c - FRR JSON builder
src/netd/src/json_builder.c - Linux backend
src/netd/src/linux_backend.c
Operations and Status
- Status daemon
src/statd/statd.c - YANG status collectors
src/statd/python/yanger/ietf_routing.py - Host access
src/statd/python/yanger/host.py - Status views
src/webui/internal/handlers/dashboard.go - System logs
src/statd/journal.c
Other components
- Administrator
Connections 16
- Administrator → Generated CLI: configures via
- Administrator → Web UI: configures via
- Generated CLI → YANG configuration: edits YANG
- Web UI → RESTCONF client: uses API
- RESTCONF client → YANG configuration: accesses models
- Config transfer → YANG configuration: imports exports
src/bin/copy.c - YANG configuration → Config handlers: dispatches changes
- Config handlers → Service management: handles services
src/confd/src/services.c - Config handlers → Routing configuration: handles routes
src/confd/src/routing.c - Routing configuration → Routing daemon: signals RIP needs
- Routing daemon → FRR JSON builder: builds FRR JSON
- Routing daemon → Linux backend: applies networking
- Status daemon → YANG status collectors: collects status
- YANG status collectors → Host access: runs host commands
src/statd/python/yanger/ietf_routing.py - Web UI → Status views: renders status
- Status daemon → System logs: records events