peter/infix
1
0
Fork 0
mirror of https://github.com/kernelkit/infix.git synced 2026-08-06 15:43:02 +02:00
Code Issues Packages Projects Releases Wiki Activity

Deployed 497990a2 to dev with MkDocs 1.6.1 and mike 2.1.3

Browse Source
This commit is contained in:
github-actions[bot]
2025-09-05 16:55:51 +00:00
parent 604e6cc370
commit 47b2d1e8e9
8 changed files with 89 additions and 89 deletions
Download Patch File Download Diff File Expand all files Collapse all files
dev/boot/index.html
+17 -17
View File
@@ -2055,7 +2055,7 @@ password in VPD, are detailed later in this section.</p>
where the base MAC address and per-device password hash is stored.
(Generic builds use the same MAC address and password)</li>
<li>On every boot the system's <code>factory-config</code> and <code>failure-config</code> are
generated from the YANG<sup id="fnref:2"><a class="footnote-ref" href="#fn:2">2</a></sup> models of the current firmware version.
generated from the YANG<sup id="fnref:2"><a class="footnote-ref" href="#fn:2">3</a></sup> models of the current firmware version.
This ensures that a factory reset device can always boot, and that
there is a working fail safe, or rather <em>fail secure</em>, mode</li>
<li>On first power-on, and after a factory reset, the system does not
@@ -2073,7 +2073,7 @@ password in VPD, are detailed later in this section.</p>
<ol>
<li>First boot, or after factory reset: <code>startup-config</code> cannot be
created or loaded, and <code>failure-config</code> cannot be loaded. The
system ends up in an unrecoverable state, i.e., <strong>RMA<sup id="fnref:3"><a class="footnote-ref" href="#fn:3">3</a></sup> Mode</strong></li>
system ends up in an unrecoverable state, i.e., <strong>RMA<sup id="fnref:3"><a class="footnote-ref" href="#fn:3">4</a></sup> Mode</strong></li>
<li>The system has booted (at least) once with correct VPD and password
and already has a <code>startup-config</code>. Provided the <code>startup-config</code>
is OK (see below), it is loaded and system boots successfully</li>
@@ -2097,7 +2097,7 @@ provide per-product <code>failure-config</code>, or <code>factory-config</code>
product's preferences.</p>
</div>
<p><em>Fail Secure Mode</em> is a fail-safe mode provided for debugging the
system. The default<sup id="fnref:4"><a class="footnote-ref" href="#fn:4">4</a></sup> creates a setup of isolated interfaces with
system. The default<sup id="fnref:4"><a class="footnote-ref" href="#fn:4">1</a></sup> creates a setup of isolated interfaces with
communication only to the management CPU, SSH and console login using
the device's factory reset password, IP connectivity only using IPv6
link-local, and device discovery protocols: LLDP, mDNS-SD. The login
@@ -2117,7 +2117,7 @@ which offers lots of benefits out-of-the-box:</p>
media like USB sticks or SD-cards) and from remote servers using FTP
or HTTP(S).</li>
</ul>
<p>To initiate a system upgrade from the shell<sup id="fnref:1"><a class="footnote-ref" href="#fn:1">1</a></sup>, run:</p>
<p>To initiate a system upgrade from the shell<sup id="fnref:1"><a class="footnote-ref" href="#fn:1">2</a></sup>, run:</p>
<div class="highlight"><pre><span></span><code><a id="__codelineno-4-1" name="__codelineno-4-1" href="#__codelineno-4-1"></a>root@example:~# rauc install &lt;file|url&gt;
<a id="__codelineno-4-2" name="__codelineno-4-2" href="#__codelineno-4-2"></a>...
</code></pre></div>
@@ -2357,25 +2357,25 @@ can funtion reasonably well without a persistent <code>/var</code>, loosing
<div class="footnote">
<hr />
<ol>
<li id="fn:1">
<p>See <a href="../upgrade/">Upgrade &amp; Boot Order</a> for more information.&#160;<a class="footnote-backref" href="#fnref:1" title="Jump back to footnote 1 in the text">&#8617;</a></p>
</li>
<li id="fn:2">
<p>YANG is a modeling language from IETF, replacing that used for
SNMP (MIB), used to describe the subsystems and properties of
the system.&#160;<a class="footnote-backref" href="#fnref:2" title="Jump back to footnote 2 in the text">&#8617;</a></p>
</li>
<li id="fn:3">
<p>Return Merchandise Authorization (RMA), i.e., broken beyond repair
by end-user and eligible for return to manufacturer.&#160;<a class="footnote-backref" href="#fnref:3" title="Jump back to footnote 3 in the text">&#8617;</a></p>
</li>
<li id="fn:4">
<p>Customer specific builds can define their own <code>failure-config</code>.
It may be the same as <code>factory-config</code>, with the hostname set to
<code>failure</code>, or a dedicated configuration that isolates interfaces, or
even disables ports, to ensure that the device does not cause any
security problems on the network. E.g., start forwarding traffic
between previously isolated VLANs.&#160;<a class="footnote-backref" href="#fnref:4" title="Jump back to footnote 4 in the text">&#8617;</a></p>
between previously isolated VLANs.&#160;<a class="footnote-backref" href="#fnref:4" title="Jump back to footnote 1 in the text">&#8617;</a></p>
</li>
<li id="fn:1">
<p>See <a href="../upgrade/">Upgrade &amp; Boot Order</a> for more information.&#160;<a class="footnote-backref" href="#fnref:1" title="Jump back to footnote 2 in the text">&#8617;</a></p>
</li>
<li id="fn:2">
<p>YANG is a modeling language from IETF, replacing that used for
SNMP (MIB), used to describe the subsystems and properties of
the system.&#160;<a class="footnote-backref" href="#fnref:2" title="Jump back to footnote 3 in the text">&#8617;</a></p>
</li>
<li id="fn:3">
<p>Return Merchandise Authorization (RMA), i.e., broken beyond repair
by end-user and eligible for return to manufacturer.&#160;<a class="footnote-backref" href="#fnref:3" title="Jump back to footnote 4 in the text">&#8617;</a></p>
</li>
</ol>
</div>
dev/container/index.html
+7 -7
View File
@@ -2315,7 +2315,7 @@ containers. Please note, that this is an advanced topic that require
time and analysis of your container application to figure out which
capabilities you need.</p>
<h2 id="networking-and-containers">Networking and Containers<a class="headerlink" href="#networking-and-containers" title="Permanent link">&para;</a></h2>
<p>By default, unlike other systems, persistent<sup id="fnref:1"><a class="footnote-ref" href="#fn:1">2</a></sup> containers have no
<p>By default, unlike other systems, persistent<sup id="fnref:1"><a class="footnote-ref" href="#fn:1">1</a></sup> containers have no
networking enabled. All network access has to be set up explicitly.
Currently two types of of container networks are supported:</p>
<ul>
@@ -2417,7 +2417,7 @@ admin@example:/config/container/ntpd/network/interface/docker0/&gt; leave
</code></pre></div>
<h3 id="container-host-interface">Container Host Interface<a class="headerlink" href="#container-host-interface" title="Permanent link">&para;</a></h3>
<p>Another common use-case is to move network interfaces into the network
namespace of a container<sup id="fnref:3"><a class="footnote-ref" href="#fn:3">1</a></sup>. This of course works with plain Ethernet
namespace of a container<sup id="fnref:3"><a class="footnote-ref" href="#fn:3">2</a></sup>. This of course works with plain Ethernet
interfaces as well, but here we will use one end of a VETH pair as an
example.</p>
<p>The network <code>option</code> setting is available also for this case, but only
@@ -2749,15 +2749,15 @@ Container Image</a> (above).</p>
<div class="footnote">
<hr />
<ol>
<li id="fn:3">
<p>Something which the container bridge network type does behind the
scenes with one end of an automatically created VETH pair.&#160;<a class="footnote-backref" href="#fnref:3" title="Jump back to footnote 1 in the text">&#8617;</a></p>
</li>
<li id="fn:1">
<p>this does not apply to the admin-exec command <code>container run</code>.
This command is intended to be used for testing and evaluating
container images. Such containers are given a private network
behind an IP masquerading bridge.&#160;<a class="footnote-backref" href="#fnref:1" title="Jump back to footnote 2 in the text">&#8617;</a></p>
behind an IP masquerading bridge.&#160;<a class="footnote-backref" href="#fnref:1" title="Jump back to footnote 1 in the text">&#8617;</a></p>
</li>
<li id="fn:3">
<p>Something which the container bridge network type does behind the
scenes with one end of an automatically created VETH pair.&#160;<a class="footnote-backref" href="#fnref:3" title="Jump back to footnote 2 in the text">&#8617;</a></p>
</li>
<li id="fn:2">
<p>The <code>nsenter</code> program is available from either the util-linux
dev/networking/index.html
+23 -23
View File
@@ -2700,7 +2700,7 @@ nodes <code>admin-state</code> and <code>oper-state</code> show the status, . P
are listed in the YANG model.</p>
<p>The <code>custom-phys-address</code> can be used to set an interface's MAC address.
This is an extension to the ietf-interfaces YANG model, which defines
<code>phys-address</code> as read-only<sup id="fnref:4"><a class="footnote-ref" href="#fn:4">4</a></sup>. The following shows the different
<code>phys-address</code> as read-only<sup id="fnref:4"><a class="footnote-ref" href="#fn:4">1</a></sup>. The following shows the different
configuration options.</p>
<p>The <code>description</code> is saved as Linux <code>ifalias</code> on an interface. It is a
free-form string, useful for describing purpose or just adding comments
@@ -2765,7 +2765,7 @@ over NETCONF or RESTCONF requires setting the type explicitly.</p>
</div>
<p><img alt="A MAC bridge with two ports" src="../img/mac-bridge.svg" /></p>
<p>It is possible to create multiple MAC bridges, however, it is
currently<sup id="fnref:5"><a class="footnote-ref" href="#fn:5">5</a></sup> <em>not recommended</em> to use more than one MAC bridge on
currently<sup id="fnref:5"><a class="footnote-ref" href="#fn:5">2</a></sup> <em>not recommended</em> to use more than one MAC bridge on
products with Marvell LinkStreet switching ASICs. A VLAN filtering
bridge should be used instead.</p>
<h4 id="vlan-filtering-bridge">VLAN Filtering Bridge<a class="headerlink" href="#vlan-filtering-bridge" title="Permanent link">&para;</a></h4>
@@ -2913,7 +2913,7 @@ an IGMP/MLD fast-leave port.</p>
consist of multiple "join" and "leave" operations on groups. They
can also, per group, list which senders to allow or block. Switches
usually only support the group subscription, and even more common
also only support filtering on the MAC level<sup id="fnref:3"><a class="footnote-ref" href="#fn:3">3</a></sup></li>
also only support filtering on the MAC level<sup id="fnref:3"><a class="footnote-ref" href="#fn:3">5</a></sup></li>
<li><strong>Querier election</strong>: the process of determining who is the elected
IGMP/MLD querier on a LAN. Lowest numerical IP address wins, the
special address 0.0.0.0 (proxy querier) never wins</li>
@@ -2986,7 +2986,7 @@ member ports are available:</p>
lag member, while in static mode only carrier is used. This additional
exchange in LACP ensures traffic can be forwarded in both directions.</p>
<p>Traffic distribution, for both modes, across the active lag member ports
is determined by the hash policy<sup id="fnref:1"><a class="footnote-ref" href="#fn:1">1</a></sup>. It uses an XOR of the source,
is determined by the hash policy<sup id="fnref:1"><a class="footnote-ref" href="#fn:1">3</a></sup>. It uses an XOR of the source,
destination MAC addresses and the EtherType field. This, IEEE
802.3ad-compliant, algorithm will place all traffic to a particular
network peer on the same link. Meaning there is no increased bandwidth
@@ -3288,7 +3288,7 @@ order for fixed speed/duplex to apply. Only speeds <code>0.1</code>(100 Mbit/s)
and <code>0.01</code> (10 Mbit/s) can be specified. 1 Gbit/s and higher speeds
require auto-negotiation to be enabled.</p>
<h4 id="ethernet-statistics">Ethernet statistics<a class="headerlink" href="#ethernet-statistics" title="Permanent link">&para;</a></h4>
<p>Ethernet packet statistics<sup id="fnref:6"><a class="footnote-ref" href="#fn:6">6</a></sup> can be listed as shown below.</p>
<p>Ethernet packet statistics<sup id="fnref:6"><a class="footnote-ref" href="#fn:6">4</a></sup> can be listed as shown below.</p>
<div class="highlight"><pre><span></span><code><a id="__codelineno-29-1" name="__codelineno-29-1" href="#__codelineno-29-1"></a>admin@example:/&gt; show interfaces name eth1
<a id="__codelineno-29-2" name="__codelineno-29-2" href="#__codelineno-29-2"></a>name : eth1
<a id="__codelineno-29-3" name="__codelineno-29-3" href="#__codelineno-29-3"></a>index : 2
@@ -3519,7 +3519,7 @@ ignore the latter.</p>
</tr>
<tr>
<td style="text-align: left;">link-local</td>
<td style="text-align: left;">ietf-ip<sup id="fnref:2"><a class="footnote-ref" href="#fn:2">2</a></sup></td>
<td style="text-align: left;">ietf-ip<sup id="fnref:2"><a class="footnote-ref" href="#fn:2">6</a></sup></td>
<td style="text-align: left;">(RFC4862) Auto-configured link-local IPv6 address (<em>fe80::0</em> prefix + interface identifier, e.g., <em>fe80::ccd2:82ff:fe52:728b/64</em>)</td>
</tr>
<tr>
@@ -4050,35 +4050,35 @@ currently supported, namely <code>ipv4</code> and <code>ipv6</code>.</p>
<div class="footnote">
<hr />
<ol>
<li id="fn:1">
<p><code>(source MAC XOR destination MAC XOR EtherType) MODULO num_links</code>&#160;<a class="footnote-backref" href="#fnref:1" title="Jump back to footnote 1 in the text">&#8617;</a></p>
</li>
<li id="fn:2">
<p>Link-local IPv6 addresses are implicitly enabled when enabling
IPv6. IPv6 can be enabled/disabled per interface in the
<a href="https://www.rfc-editor.org/rfc/rfc8344">ietf-ip</a> YANG model.&#160;<a class="footnote-backref" href="#fnref:2" title="Jump back to footnote 2 in the text">&#8617;</a></p>
</li>
<li id="fn:3">
<p>For example, IPv4 groups are mapped to MAC multicast addresses by
mapping the low-order 23-bits of the IP address in the low-order 23
bits of the Ethernet address 01:00:5E:00:00:00. Meaning, more than
one IP multicast group maps to the same MAC multicast group.&#160;<a class="footnote-backref" href="#fnref:3" title="Jump back to footnote 3 in the text">&#8617;</a></p>
</li>
<li id="fn:4">
<p>A YANG deviation was previously used to make it possible to set
<code>phys-address</code>, but this has been replaced with the more flexible
<code>custom-phys-address</code>.&#160;<a class="footnote-backref" href="#fnref:4" title="Jump back to footnote 4 in the text">&#8617;</a></p>
<code>custom-phys-address</code>.&#160;<a class="footnote-backref" href="#fnref:4" title="Jump back to footnote 1 in the text">&#8617;</a></p>
</li>
<li id="fn:5">
<p>MAC bridges on Marvell Linkstreet devices are currently limited to
a single MAC database, this may be a problem if the same MAC address
appears in different MAC bridges.&#160;<a class="footnote-backref" href="#fnref:5" title="Jump back to footnote 5 in the text">&#8617;</a></p>
appears in different MAC bridges.&#160;<a class="footnote-backref" href="#fnref:5" title="Jump back to footnote 2 in the text">&#8617;</a></p>
</li>
<li id="fn:1">
<p><code>(source MAC XOR destination MAC XOR EtherType) MODULO num_links</code>&#160;<a class="footnote-backref" href="#fnref:1" title="Jump back to footnote 3 in the text">&#8617;</a></p>
</li>
<li id="fn:6">
<p>Ethernet counters are described in <em>ieee802-ethernet-interface.yang</em>
and <em>infix-ethernet-interface.yang</em>. There is a dedicated document on
<a href="../eth-counters/">Ethernet Counters</a> that provide additional details
on the statistics support.&#160;<a class="footnote-backref" href="#fnref:6" title="Jump back to footnote 6 in the text">&#8617;</a></p>
on the statistics support.&#160;<a class="footnote-backref" href="#fnref:6" title="Jump back to footnote 4 in the text">&#8617;</a></p>
</li>
<li id="fn:3">
<p>For example, IPv4 groups are mapped to MAC multicast addresses by
mapping the low-order 23-bits of the IP address in the low-order 23
bits of the Ethernet address 01:00:5E:00:00:00. Meaning, more than
one IP multicast group maps to the same MAC multicast group.&#160;<a class="footnote-backref" href="#fnref:3" title="Jump back to footnote 5 in the text">&#8617;</a></p>
</li>
<li id="fn:2">
<p>Link-local IPv6 addresses are implicitly enabled when enabling
IPv6. IPv6 can be enabled/disabled per interface in the
<a href="https://www.rfc-editor.org/rfc/rfc8344">ietf-ip</a> YANG model.&#160;<a class="footnote-backref" href="#fnref:2" title="Jump back to footnote 6 in the text">&#8617;</a></p>
</li>
</ol>
</div>
dev/search/search_index.json
+1 -1
View File
File diff suppressed because one or more lines are too long
dev/sitemap.xml
+36 -36
View File
@@ -2,146 +2,146 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://kernelkit.github.io/infix/dev/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/boot/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/branding/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/container/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/developers-guide/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/dhcp/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/discovery/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/eth-counters/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/hardware/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/license/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/management/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/netboot/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/networking/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/override-package/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/qos/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/scripting-prod/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/scripting-restconf/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/scripting-sysrepocfg/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/scripting/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/syslog/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/system/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/test-arch/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/testing/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/tunnels/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/upgrade/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/virtual/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/vpd/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/wifi/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/cli/configure/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/cli/introduction/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/cli/keybindings/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/cli/netcalc/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/cli/quick/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/cli/tcpdump/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/cli/text-editor/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
<url>
<loc>https://kernelkit.github.io/infix/dev/cli/upgrade/</loc>
<lastmod>2025-09-02</lastmod>
<lastmod>2025-09-05</lastmod>
</url>
</urlset>
dev/sitemap.xml.gz
BIN
View File
Binary file not shown.
latest
+1 -1
View File
@@ -1 +1 @@
25.08
dev
versions.json
+4 -4
View File
@@ -2,13 +2,13 @@
{
"version": "dev",
"title": "dev",
"aliases": []
"aliases": [
"latest"
]
},
{
"version": "25.08",
"title": "25.08",
"aliases": [
"latest"
]
"aliases": []
}
]