[GH-ISSUE #2111] Minimum client version posture check issue #4290

Open
opened 2026-08-05 00:56:52 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @JonathanManass on GitHub (Jun 10, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2111

Describe the problem

I noticed that when adding a posture check requiring a certain version of the client, this would only block if both clients were under the required version.

If we have 3 clients, with one not at the minimum version of the posture check, it will still be able to connect to the other ones, if two clients are below the minimum version, they won't be able to communicate with each other.

It seems like it would be more useful to have the option of completely blocking access for a client not having the required version

To Reproduce

  1. Add a posture check requiring the netbird client to be in version 0.27.10
  2. Have three peers, one in version 0.27.9, two in 0.27.10
  3. All of them will be able to communicate

Expected behavior

As said, I would rather have it that if one peer is below the posture check required version and the two others are compliant, those two should communicate to each other, but not with the third non compliant peer

Are you using NetBird Cloud?

No, I'm selfhosting it.

NetBird version

0.27.10

Originally created by @JonathanManass on GitHub (Jun 10, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2111 **Describe the problem** I noticed that when adding a posture check requiring a certain version of the client, this would only block if both clients were under the required version. If we have 3 clients, with one not at the minimum version of the posture check, it will still be able to connect to the other ones, if two clients are below the minimum version, they won't be able to communicate with each other. It seems like it would be more useful to have the option of completely blocking access for a client not having the required version **To Reproduce** 1. Add a posture check requiring the netbird client to be in version 0.27.10 2. Have three peers, one in version 0.27.9, two in 0.27.10 3. All of them will be able to communicate **Expected behavior** As said, I would rather have it that if one peer is below the posture check required version and the two others are compliant, those two should communicate to each other, but not with the third non compliant peer **Are you using NetBird Cloud?** No, I'm selfhosting it. **NetBird version** 0.27.10
saavagebueno added the clientposture-checks labels 2026-08-05 00:56:52 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#4290