<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Documentation on NetworkManager</title>
    <link>https://networkmanager.dev/docs/</link>
    <description>Recent content in Documentation on NetworkManager</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://networkmanager.dev/docs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>NetworkManager for administrators</title>
      <link>https://networkmanager.dev/docs/admins/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://networkmanager.dev/docs/admins/</guid>
      <description>Information for administrators</description>
    </item>
    <item>
      <title>Resources for developers</title>
      <link>https://networkmanager.dev/docs/developers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://networkmanager.dev/docs/developers/</guid>
      <description>D-Bus API NetworkManager provides a D-Bus interface on the system bus. You can use this interface to query network state and the details of network interfaces like current IP addresses or DHCP options, and to activate, deactivate, created, edit, and delete saved network connections.&#xA;Check the D-Bus API reference: STABLE DEVEL libnm API libnm wraps the D-Bus API in easy-to-use GObjects and is often much simpler for glib-based applications to use.</description>
    </item>
    <item>
      <title>man pages</title>
      <link>https://networkmanager.dev/docs/man-pages/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://networkmanager.dev/docs/man-pages/</guid>
      <description>This page contains a collection of man pages for NetworkManager. For each page there are two links: stable is the version in the latest stable release of NetworkManager, while devel is the version from the latest development snapshot.&#xA;Services NetworkManager (8) STABLE DEVEL NetworkManager.conf (5) STABLE DEVEL NetworkManager-dispatcher (8) STABLE DEVEL NetworkManager-wait-online.service (8) STABLE DEVEL Clients and Utilities nmcli (1) STABLE DEVEL nmcli-examples (5) STABLE DEVEL nmtui (1) STABLE DEVEL nm-online (1) STABLE DEVEL nm-cloud-setup (8) STABLE DEVEL nm-initrd-generator (8) STABLE DEVEL nm-openvswitch (7) STABLE DEVEL Settings Each connection profile contains multiple settings (connection, ipv4, ipv6, ethernet, etc.</description>
    </item>
    <item>
      <title>Video tutorials</title>
      <link>https://networkmanager.dev/docs/video/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://networkmanager.dev/docs/video/</guid>
      <description>WireGuard configuration </description>
    </item>
    <item>
      <title>VPN support</title>
      <link>https://networkmanager.dev/docs/vpn/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://networkmanager.dev/docs/vpn/</guid>
      <description>NetworkManager supports VPN connections for all popular VPN connections via plugins.&#xA;A VPN plugin consists of the editor dialog and a D-Bus service that manages the actual VPN connection.&#xA;Natively Supported by NetworkManager WireGuard NetworkManager 1.16.0+ supports WireGuard natively and requires no plugin Plugin maintenance status Some VPN plugins are no longer maintained at all and are used at your own risk. For an unmaintained plugin, nobody is reviewing contributions, fixing bugs or making releases; issues and merge requests go unanswered and known defects, including security issues, stay unfixed.</description>
    </item>
    <item>
      <title>RFKill</title>
      <link>https://networkmanager.dev/docs/rfkill/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://networkmanager.dev/docs/rfkill/</guid>
      <description>The rfkill subsystem in Linux provides a mechanism to disable radio transmitters, as Wi-Fi, Bluetooth cards or WWAN modems installed in the system.&#xA;From the kernel point of view, such devices typically have a associated rfkill device (also called killswitch) that is visible in the output of the rfkill utility.&#xA;$ rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth tpacpi_bluetooth_sw blocked unblocked 2 wlan phy0 blocked unblocked Each rfkill device has a type (bluetooth, wlan, wwan) and two flags to indicate whether the killswitch is hard-blocked (when radio transmission is blocked via a hardware switch) or soft-blocked (when radio is disabled but can be re-enabled in software).</description>
    </item>
  </channel>
</rss>
