@@ -566,6 +566,38 @@ systemd.services.nginx.serviceConfig.ReadWritePaths = [ "/var/www" ];
566566 was removed, as udev gained native support to handle FIDO security tokens.
567567 </para>
568568 </listitem>
569+ <listitem>
570+ <para>
571+ With this release <literal>systemd-networkd</literal> (when enabled through <xref linkend="opt-networking.useNetworkd"/>)
572+ has it's netlink socket created through a <literal>systemd.socket</literal> unit. This gives us control over
573+ socket buffer sizes and other parameters. For larger setups where networkd has to create a lot of (virtual)
574+ devices the default buffer size (currently 128MB) is not enough.
575+ </para>
576+ <para>
577+ On a machine with >100 virtual interfaces (e.g., wireguard tunnels, VLANs, …), that all have to
578+ be brought up during system startup, the receive buffer size will spike for a brief period.
579+ Eventually some of the message will be dropped since there is not enough (permitted) buffer
580+ space available.
581+ </para>
582+ <para>
583+ By having <literal>systemd-networkd</literal> start with a netlink socket created by
584+ <literal>systemd</literal> we can configure the <literal>ReceiveBufferSize=</literal> parameter
585+ in the socket options (i.e. <literal>systemd.sockets.systemd-networkd.socketOptions.ReceiveBufferSize</literal>)
586+ without recompiling <literal>systemd-networkd</literal>.
587+ </para>
588+ <para>
589+ Since the actual memory requirements depend on hardware, timing, exact
590+ configurations etc. it isn't currently possible to infer a good default
591+ from within the NixOS module system. Administrators are advised to
592+ monitor the logs of <literal>systemd-networkd</literal> for <literal>rtnl: kernel receive buffer
593+ overrun</literal> spam and increase the memory limit as they see fit.
594+ </para>
595+ <para>
596+ Note: Increasing the <literal>ReceiveBufferSize=</literal> doesn't allocate any memory. It just increases
597+ the upper bound on the kernel side. The memory allocation depends on the amount of messages that are
598+ queued on the kernel side of the netlink socket.
599+ </para>
600+ </listitem>
569601 </itemizedlist>
570602 </section>
571603</section>