Skip to content

Posture-checks: note mobile support for Peer Network Range #724

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pappz wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Posture-checks: note mobile support for Peer Network Range #724

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6da6dac
docs(posture-checks): note mobile support for Peer Network Range in 0…
pappz May 4, 2026
612ef80
Merge remote-tracking branch 'origin/main' into docs/posture-checks-m…
pappz May 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 3 additions & 24 deletions src/pages/manage/access-control/posture-checks/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -117,30 +117,9 @@ If you revisit the `Posture Checks` dashboard, you'll notice a green dot next to

Following these steps, you can effectively implement and manage NetBird's Posture Checks, significantly enhancing your network's security posture.

## Known Limitations

### Peer Network Range Check on Mobile Platforms

iOS and Android do not allow applications to enumerate the device's local network interfaces, so ranges intended to match a peer's **local NIC IPs** (e.g. an office LAN like `192.168.1.0/24`) cannot be evaluated on those platforms.

Ranges that target the **public connection IP** still work on mobile, because the management server observes that source IP itself — it does not depend on anything the client reports. So public CIDRs (e.g. `203.0.113.10/32`, `1.0.0.0/24`) and public-IP-based deny/allow rules behave the same on mobile as on desktop.

**Affected platforms:**
- iOS
- Android

**Impact:**

If a policy's Peer Network Range posture check relies on local NIC ranges, the check cannot match on mobile clients and routes gated by that policy may become unavailable on those devices — even when the device is outside the blocked local range.

**Recommendation:**

If your deployment includes iOS or Android clients and you need to gate on local network membership, consider one of the following:

- Create separate policies for mobile clients that do not include local-NIC-based Peer Network Range posture checks
- Use alternative posture checks (such as Geo Location) that are supported on mobile platforms
- Use Peer Network Range checks based on the **public connection IP**, which work on every platform
- Apply local-NIC-based Peer Network Range posture checks only to policies targeting desktop platforms (Windows, macOS, Linux)
<Note>
The Peer Network Range posture check on iOS and Android requires NetBird client version [0.70.0](https://github.com/netbirdio/netbird/releases) or newer. On earlier mobile client versions, the check cannot be evaluated due to platform restrictions on accessing local network information.
</Note>

## Get started with NetBird
<p float="center" >
Expand Down
Loading