

<feed xmlns="http://www.w3.org/2005/Atom">
  <id>/</id>
  <title>KernelKit — Home of Infix OS</title>
  <subtitle>Infix is a free, Linux-based, immutable operating system.  Suitable for switches, routers, and end-devices alike.</subtitle>
  <updated>2026-07-02T09:36:57+02:00</updated>
  <author>
    <name>KernelKit Maintainers</name>
    <uri>/</uri>
  </author>
  <link rel="self" type="application/atom+xml" href="/feed.xml"/>
  <link rel="alternate" type="text/html" hreflang="en"
    href="/"/>
  <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator>
  <rights> © 2026 KernelKit Maintainers </rights>
  <icon>/assets/img/favicons/favicon.ico</icon>
  <logo>/assets/img/favicons/favicon-96x96.png</logo>


  
  <entry>
    <title>Seamless Wi-Fi with Mesh Backhaul and Roaming</title>
    <link href="/posts/wifi-mesh-roaming/" rel="alternate" type="text/html" title="Seamless Wi-Fi with Mesh Backhaul and Roaming" />
    <published>2026-07-02T08:00:00+02:00</published>
  
    <updated>2026-07-02T08:00:00+02:00</updated>
  
    <id>/posts/wifi-mesh-roaming/</id>
    <content type="text/html" src="/posts/wifi-mesh-roaming/" />
    <author>
      <name>mattiaswal</name>
    </author>

  
    
    <category term="howto" />
    
  

  <summary>Covering a building or a yard with Wi-Fi usually means several access points sharing one network name, so a laptop or a phone keeps working as it moves between them.  Two problems show up quickly:     Getting the network to every AP.  Pulling Ethernet to each AP is the reliable way, but it is not always possible.  Where you cannot run a cable, a wireless backhaul has to carry the traffic instea...</summary>

  </entry>

  
  <entry>
    <title>Introducing the Web Interface</title>
    <link href="/posts/introducing-the-web-interface/" rel="alternate" type="text/html" title="Introducing the Web Interface" />
    <published>2026-07-01T09:00:00+02:00</published>
  
    <updated>2026-07-01T09:00:00+02:00</updated>
  
    <id>/posts/introducing-the-web-interface/</id>
    <content type="text/html" src="/posts/introducing-the-web-interface/" />
    <author>
      <name>troglobit</name>
    </author>

  
    
    <category term="showcase" />
    
  

  <summary>Infix has always been a YANG-native system: every setting lives in a model-backed datastore, reachable over the CLI, NETCONF, and RESTCONF. With v26.06 we add a fourth way in: a built-in web interface.  It is not a separate configuration path with its own quirks.  The WebUI speaks RESTCONF to the same datastore as everything else, so what you see and change in the browser is exactly what the CL...</summary>

  </entry>

  
  <entry>
    <title>Building Infix from Source</title>
    <link href="/posts/building-infix-from-source/" rel="alternate" type="text/html" title="Building Infix from Source" />
    <published>2026-05-28T07:00:00+02:00</published>
  
    <updated>2026-05-28T07:00:00+02:00</updated>
  
    <id>/posts/building-infix-from-source/</id>
    <content type="text/html" src="/posts/building-infix-from-source/" />
    <author>
      <name>troglobit</name>
    </author>

  
    
    <category term="howto" />
    
  

  <summary>From git clone to pinging the internet with make run</summary>

  </entry>

  
  <entry>
    <title>PTP Time Synchronization</title>
    <link href="/posts/ptp-time-synchronization/" rel="alternate" type="text/html" title="PTP Time Synchronization" />
    <published>2026-04-07T10:00:00+02:00</published>
  
    <updated>2026-04-07T10:00:00+02:00</updated>
  
    <id>/posts/ptp-time-synchronization/</id>
    <content type="text/html" src="/posts/ptp-time-synchronization/" />
    <author>
      <name>troglobit</name>
    </author>

  
    
    <category term="examples" />
    
  

  <summary>The Precision Time Protocol (PTP, IEEE 1588) synchronizes clocks across a network to sub-microsecond accuracy — far beyond what NTP can achieve.  Infix supports both the standard IEEE 1588 profile and the gPTP profile (IEEE 802.1AS) used in Time-Sensitive Networking.  This post walks through the minimal configurations needed to get two devices talking PTP.  For the full story (protocol concepts...</summary>

  </entry>

  
  <entry>
    <title>Infix in GNS3</title>
    <link href="/posts/infix-in-gns3/" rel="alternate" type="text/html" title="Infix in GNS3" />
    <published>2026-03-12T09:00:00+01:00</published>
  
    <updated>2026-04-09T18:51:35+02:00</updated>
  
    <id>/posts/infix-in-gns3/</id>
    <content type="text/html" src="/posts/infix-in-gns3/" />
    <author>
      <name>troglobit</name>
    </author>

  
    
    <category term="howto" />
    
  

  <summary>Build and test networks virtually, no hardware required</summary>

  </entry>

</feed>


