diff --git a/public/docs-static/img/get-started/openwrt/netbird-connected-setup-key.png b/public/docs-static/img/get-started/openwrt/netbird-connected-setup-key.png
new file mode 100644
index 00000000..c876ee0a
Binary files /dev/null and b/public/docs-static/img/get-started/openwrt/netbird-connected-setup-key.png differ
diff --git a/public/docs-static/img/get-started/openwrt/netbird-installed.png b/public/docs-static/img/get-started/openwrt/netbird-installed.png
new file mode 100644
index 00000000..8569bd4c
Binary files /dev/null and b/public/docs-static/img/get-started/openwrt/netbird-installed.png differ
diff --git a/public/docs-static/img/get-started/openwrt/openwrt-package-update.png b/public/docs-static/img/get-started/openwrt/openwrt-package-update.png
new file mode 100644
index 00000000..d04e0fd9
Binary files /dev/null and b/public/docs-static/img/get-started/openwrt/openwrt-package-update.png differ
diff --git a/src/components/NavigationDocs.jsx b/src/components/NavigationDocs.jsx
index 58b519a6..4a48cb12 100644
--- a/src/components/NavigationDocs.jsx
+++ b/src/components/NavigationDocs.jsx
@@ -70,6 +70,7 @@ export const docsNavigation = [
{ title: 'TrueNAS', href: '/get-started/install/truenas' },
{ title: 'pfSense', href: '/get-started/install/pfsense' },
{ title: 'OPNsense', href: '/get-started/install/opnsense' },
+ { title: 'OpenWrt', href: '/get-started/install/openwrt' },
{ title: 'Raspberry Pi', href: '/get-started/install/raspberrypi' },
],
},
diff --git a/src/pages/get-started/install/index.mdx b/src/pages/get-started/install/index.mdx
index fb43a22d..37ff4386 100644
--- a/src/pages/get-started/install/index.mdx
+++ b/src/pages/get-started/install/index.mdx
@@ -20,6 +20,7 @@ The NetBird client (agent) allows a peer to join a pre-existing NetBird deployme
* [Install on TrueNAS](/get-started/install/truenas)
* [Install on pfSense](/get-started/install/pfsense)
* [Install on OPNSense](/get-started/install/opnsense)
+* [Install on OpenWrt](/get-started/install/openwrt)
* [Install on Raspberry Pi](/get-started/install/raspberrypi)
* [Install on Proxmox VE](/get-started/install/proxmox-ve)
diff --git a/src/pages/get-started/install/openwrt.mdx b/src/pages/get-started/install/openwrt.mdx
new file mode 100644
index 00000000..90f20ffe
--- /dev/null
+++ b/src/pages/get-started/install/openwrt.mdx
@@ -0,0 +1,170 @@
+import {Note} from "@/components/mdx";
+
+export const description = 'Install the NetBird client on OpenWrt routers using the official package feed and connect them to your NetBird network.'
+
+# OpenWrt Installation
+
+The NetBird client allows a peer to join a pre-existing NetBird deployment. If a NetBird deployment is not yet available,
+there are both managed and [self-hosted](https://docs.netbird.io/selfhosted/selfhosted-quickstart) options available.
+
+NetBird is available in the official OpenWrt package feed. The packaged version depends on your OpenWrt release (versions listed as of the time of writing; the package feeds receive updates over time):
+
+| OpenWrt release | NetBird version | Package manager |
+|---|---|---|
+| 23.05 | 0.24.x | opkg |
+| 24.10 | 0.59.x | opkg |
+| 25.12 and later | 0.66.x | apk |
+
+## Prerequisites
+
+- SSH access to your OpenWrt router
+- Enough free flash storage for the NetBird package (the binary is relatively large, low-storage routers may not have space)
+- A [setup key](/manage/peers/register-machines-using-setup-keys#types-of-setup-keys) to authenticate and register the router
+
+
+ The NetBird one-line installation script (`pkgs.netbird.io/install.sh`) does not support OpenWrt. Use the OpenWrt package feed as described below.
+
+
+## Installation
+
+1. **Log in to your router via SSH**
+
+ ```bash
+ ssh root@192.168.1.1
+ ```
+
+2. **Install the NetBird package**
+
+ On OpenWrt `24.10` and earlier:
+
+ ```bash
+ opkg update
+ opkg install netbird
+ ```
+
+ On OpenWrt `25.12` and later:
+
+ ```bash
+ apk update
+ apk add netbird
+ ```
+
+
+
+3. **Enable and start the NetBird service**
+
+ The package installs a procd init script at `/etc/init.d/netbird`:
+
+ ```bash
+ /etc/init.d/netbird enable
+ /etc/init.d/netbird start
+ ```
+
+
+
+## Connect the router to your NetBird network
+
+Authenticate with a setup key:
+
+```bash
+netbird up --setup-key
+```
+
+If you are self-hosting NetBird, point the client to your management server:
+
+```bash
+netbird up --setup-key --management-url https://netbird.example.com:443
+```
+
+Verify the connection:
+
+```bash
+netbird status -d
+```
+
+
+
+Once connected, the router appears on the **Peers** page in the NetBird dashboard. NetBird creates a WireGuard interface named `wt0` and manages it directly. Do not configure `wt0` through the OpenWrt WireGuard UI or LuCI, NetBird fully manages the interface and keys.
+
+## DNS configuration
+
+OpenWrt runs dnsmasq on port 53, which conflicts with NetBird's managed DNS. To use NetBird DNS features such as [domain resources](/manage/networks#domain-resources) and peer name resolution, run NetBird's resolver on an alternative port and forward NetBird domains to it through dnsmasq.
+
+1. **Set a custom DNS resolver address**
+
+ When port 53 is taken, NetBird automatically falls back to an alternative port, but pinning the address keeps the dnsmasq forwarding rule below valid:
+
+ ```bash
+ netbird up --dns-resolver-address 127.0.0.1:5053
+ ```
+
+2. **Forward NetBird domains in dnsmasq**
+
+ Add a server entry to `/etc/config/dhcp` under the `dnsmasq` section, replacing `netbird.cloud` with `netbird.selfhosted` or your custom DNS domain if you are self-hosting:
+
+ ```bash
+ uci add_list dhcp.@dnsmasq[0].server='/netbird.cloud/127.0.0.1#5053'
+ uci commit dhcp
+ /etc/init.d/dnsmasq restart
+ ```
+
+## Routing LAN traffic through NetBird
+
+As a simple client peer, no additional network or firewall configuration is required. To use the router as a [routing peer](/manage/networks/how-routing-peers-work) so devices on your LAN can reach NetBird resources, or so peers can reach your LAN, you need to configure the OpenWrt firewall for the `wt0` interface.
+
+1. **Add the NetBird interface to the network configuration**
+
+ ```bash
+ uci set network.netbird=interface
+ uci set network.netbird.proto='none'
+ uci set network.netbird.device='wt0'
+ uci commit network
+ ```
+
+2. **Create a firewall zone and allow forwarding**
+
+ ```bash
+ uci add firewall zone
+ uci set firewall.@zone[-1].name='netbird'
+ uci set firewall.@zone[-1].input='ACCEPT'
+ uci set firewall.@zone[-1].output='ACCEPT'
+ uci set firewall.@zone[-1].forward='ACCEPT'
+ uci set firewall.@zone[-1].masq='1'
+ uci add_list firewall.@zone[-1].network='netbird'
+
+ uci add firewall forwarding
+ uci set firewall.@forwarding[-1].src='lan'
+ uci set firewall.@forwarding[-1].dest='netbird'
+
+ uci add firewall forwarding
+ uci set firewall.@forwarding[-1].src='netbird'
+ uci set firewall.@forwarding[-1].dest='lan'
+
+ uci commit firewall
+ /etc/init.d/firewall restart
+ ```
+
+ This permits all traffic on the NetBird interface so that NetBird's own [access control policies](/manage/access-control) govern access restrictions.
+
+3. **Advertise your LAN in NetBird**
+
+ Add the router's LAN subnet as a [network resource](/manage/networks) in the NetBird dashboard with the router as the routing peer.
+
+## Persistence across reboots and upgrades
+
+The OpenWrt package preserves NetBird's configuration across sysupgrade, so the router stays registered after firmware upgrades. No extra steps are needed. The storage location depends on the package version:
+
+- On OpenWrt 25.12 and later, the service stores state in `/root/.config/netbird`.
+- On OpenWrt 24.10 and earlier, the configuration lives at `/etc/netbird/config.json`.
+
+Both paths are registered as package configuration files and are included in the sysupgrade backup.
+
+## Get started
+
+
+
+
+- Make sure to [star us on GitHub](https://github.com/netbirdio/netbird)
+- Follow us [on X](https://x.com/netbird)
+- Join our [Slack Channel](/slack-url)
+- NetBird [latest release](https://github.com/netbirdio/netbird/releases) on GitHub
+
+3. **Enable and start the NetBird service**
+
+ The package installs a procd init script at `/etc/init.d/netbird`:
+
+ ```bash
+ /etc/init.d/netbird enable
+ /etc/init.d/netbird start
+ ```
+
+ 
+
+## Connect the router to your NetBird network
+
+Authenticate with a setup key:
+
+```bash
+netbird up --setup-key 
+
+Once connected, the router appears on the **Peers** page in the NetBird dashboard. NetBird creates a WireGuard interface named `wt0` and manages it directly. Do not configure `wt0` through the OpenWrt WireGuard UI or LuCI, NetBird fully manages the interface and keys.
+
+## DNS configuration
+
+OpenWrt runs dnsmasq on port 53, which conflicts with NetBird's managed DNS. To use NetBird DNS features such as [domain resources](/manage/networks#domain-resources) and peer name resolution, run NetBird's resolver on an alternative port and forward NetBird domains to it through dnsmasq.
+
+1. **Set a custom DNS resolver address**
+
+ When port 53 is taken, NetBird automatically falls back to an alternative port, but pinning the address keeps the dnsmasq forwarding rule below valid:
+
+ ```bash
+ netbird up --dns-resolver-address 127.0.0.1:5053
+ ```
+
+2. **Forward NetBird domains in dnsmasq**
+
+ Add a server entry to `/etc/config/dhcp` under the `dnsmasq` section, replacing `netbird.cloud` with `netbird.selfhosted` or your custom DNS domain if you are self-hosting:
+
+ ```bash
+ uci add_list dhcp.@dnsmasq[0].server='/netbird.cloud/127.0.0.1#5053'
+ uci commit dhcp
+ /etc/init.d/dnsmasq restart
+ ```
+
+## Routing LAN traffic through NetBird
+
+As a simple client peer, no additional network or firewall configuration is required. To use the router as a [routing peer](/manage/networks/how-routing-peers-work) so devices on your LAN can reach NetBird resources, or so peers can reach your LAN, you need to configure the OpenWrt firewall for the `wt0` interface.
+
+1. **Add the NetBird interface to the network configuration**
+
+ ```bash
+ uci set network.netbird=interface
+ uci set network.netbird.proto='none'
+ uci set network.netbird.device='wt0'
+ uci commit network
+ ```
+
+2. **Create a firewall zone and allow forwarding**
+
+ ```bash
+ uci add firewall zone
+ uci set firewall.@zone[-1].name='netbird'
+ uci set firewall.@zone[-1].input='ACCEPT'
+ uci set firewall.@zone[-1].output='ACCEPT'
+ uci set firewall.@zone[-1].forward='ACCEPT'
+ uci set firewall.@zone[-1].masq='1'
+ uci add_list firewall.@zone[-1].network='netbird'
+
+ uci add firewall forwarding
+ uci set firewall.@forwarding[-1].src='lan'
+ uci set firewall.@forwarding[-1].dest='netbird'
+
+ uci add firewall forwarding
+ uci set firewall.@forwarding[-1].src='netbird'
+ uci set firewall.@forwarding[-1].dest='lan'
+
+ uci commit firewall
+ /etc/init.d/firewall restart
+ ```
+
+ This permits all traffic on the NetBird interface so that NetBird's own [access control policies](/manage/access-control) govern access restrictions.
+
+3. **Advertise your LAN in NetBird**
+
+ Add the router's LAN subnet as a [network resource](/manage/networks) in the NetBird dashboard with the router as the routing peer.
+
+## Persistence across reboots and upgrades
+
+The OpenWrt package preserves NetBird's configuration across sysupgrade, so the router stays registered after firmware upgrades. No extra steps are needed. The storage location depends on the package version:
+
+- On OpenWrt 25.12 and later, the service stores state in `/root/.config/netbird`.
+- On OpenWrt 24.10 and earlier, the configuration lives at `/etc/netbird/config.json`.
+
+Both paths are registered as package configuration files and are included in the sysupgrade backup.
+
+## Get started
+