@@ -3,35 +3,49 @@ icon: fas fa-info-circle
3
3
order : 1
4
4
---
5
5
6
- Infix is a free, Linux based, immutable[ ^ 1 ] operating system for
7
- networked equipment. Although primarily focused on switches and
8
- routers, its core values may be appealing for other use-cases as
9
- well:
6
+ Infix is a free, Linux-based, immutable[ ^ 1 ] operating system based on
7
+ [ Buildroot] [ 2 ] and completely modeled in YANG using [ sysrepo] [ 3 ] . This
8
+ allows for full remote control and monitoring using NETCONF or RESTCONF.
9
+ Initially focused on switches and routers, Infix has grown to be useful
10
+ for many other use-cases as well.
11
+
12
+ An immutable operating system greatly enhances security. Configuration
13
+ and data, e.g, containers, is stored on separate partitions to ensure
14
+ complete separation from system files and allow for seamless backup,
15
+ restore, and provisioning.
16
+
17
+ ### Core Values
10
18
11
19
- Runs from a squashfs image on a read-only partition
12
20
- Single configuration file on a separate partition
13
- - Linux switchdev provides open switch APIs
14
- - Atomic upgrades to secondary partition
15
- - Highly security focused
21
+ - Linux switchdev (DSA) provides open switch APIs
22
+ - Atomic upgrades using common A/B partitioning
23
+ - Highly security focused — LTS kernel + Buildroot
24
+
25
+ ### YANG vs NETCONF vs RESTCONF
16
26
17
27
The entire system is modeled using [ YANG] [ 1 ] with standard IETF models
18
28
and dedicated models when needed to fully leverage Linux capabilities.
19
29
Meaning, not only is the system configuration derived from YANG, but
20
30
also system state and any operations (RPC/actions), like upgrade.
21
31
22
- An immutable operating system greatly enhances security. Configuration
23
- and data, e.g, containers, is stored on separate partitions to ensure
24
- complete separation from system files and allow for seamless backup,
25
- restore, and provisioning.
32
+ The * wire protocol* to interact with Infix devices is NETCONF (xml over
33
+ ssh) and RESTCONF (json over https). The latter is particularly useful
34
+ for scripting (and demo) purposes, while the former has more tooling
35
+ available, e.g., [ Clixon Controller] [ 4 ] , which is a NETCONF controller.
36
+
37
+ ### Adaptability with Containers
26
38
27
- In itself Infix is perfectly suited for dedicated networking tasks and
39
+ In itself, Infix is perfectly suited for dedicated networking tasks and
28
40
native support for Docker containers provides a versatile platform that
29
41
can easily be adapted to any customer need. Be it legacy applications,
30
42
network protocols, process monitoring, or edge data analysis, it can run
31
43
close to end equipment. Either directly connected on dedicated Ethernet
32
44
ports or indirectly using virtual network cables to exist on the same
33
45
LAN as other connected equipment.
34
46
47
+ ### Summary
48
+
35
49
The simple design of Infix provides complete control over both system
36
50
and data, minimal cognitive burden, and makes it incredibly easy to get
37
51
started.
@@ -45,3 +59,6 @@ started.
45
59
and < https://www.zdnet.com/article/what-is-immutable-linux-heres-why-youd-run-an-immutable-linux-distro/ > .
46
60
47
61
[ 1 ] : https://datatracker.ietf.org/doc/html/rfc7950
62
+ [ 2 ] : https://buildroot.org/
63
+ [ 3 ] : https://www.sysrepo.org/
64
+ [ 4 ] : https://github.com/clicon/clixon-controller
0 commit comments