[GH-ISSUE #5685] Policy Restricting Ping Does Not Take Effect Immediately #11640

Open
opened 2026-08-05 01:30:15 -04:00 by saavagebueno · 1 comment
Owner

Originally created by @cheetah747 on GitHub (Mar 24, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5685

Describe the problem

When I add and enable a policy that allows Peer A to ping Peer B, the change takes effect immediately. However, when I disable this policy, Peer A can still ping Peer B unless I manually disconnect and then reconnect Peer A's client, or wait for some time before testing again. The change does not take effect instantly.

To Reproduce

Steps to reproduce the behavior:

  1. Ping Peer B from Peer A → the ping fails.
  2. In the console, add a policy to allow Peer A → ICMP → Peer B.
  3. Ping Peer B from Peer A → the ping succeeds.
  4. In the console, disable the previously added policy to block Peer A → ICMP → Peer B.
  5. Ping Peer B from Peer A → the ping still succeeds.

6.1. Manually disconnect Peer A's client, then manually reconnect Peer A.
7.1. Ping Peer B from Peer A → the ping fails.
or
6.2. Wait for some time without performing any operations.
7.2. Ping Peer B from Peer A → the ping fails.

Expected behavior

After disabling the policy, Peer A should no longer be able to ping Peer B.

Are you using NetBird Cloud?

No, I'm using self-host

NetBird version

latest

Is any other VPN software installed?

No

If yes, which one?

Debug output

To help us resolve the problem, please attach the following anonymized status output

netbird status -dA

Create and upload a debug bundle, and share the returned file key:

netbird debug for 1m -AS -U

Uploaded files are automatically deleted after 30 days.

Alternatively, create the file only and attach it here manually:

netbird debug for 1m -AS

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

Have you tried these troubleshooting steps?

  • Reviewed client troubleshooting (if applicable)
  • Checked for newer NetBird versions
  • Searched for similar issues on GitHub (including closed ones)
  • Restarted the NetBird client
  • Disabled other VPN software
  • Checked firewall settings
Originally created by @cheetah747 on GitHub (Mar 24, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5685 **Describe the problem** When I add and enable a policy that allows Peer A to ping Peer B, the change takes effect immediately. However, when I disable this policy, Peer A can still ping Peer B unless I manually disconnect and then reconnect Peer A's client, or wait for some time before testing again. The change does not take effect instantly. **To Reproduce** Steps to reproduce the behavior: 1. Ping Peer B from Peer A → the ping fails. 2. In the console, add a policy to allow Peer A → ICMP → Peer B. 3. Ping Peer B from Peer A → the ping succeeds. 4. In the console, disable the previously added policy to block Peer A → ICMP → Peer B. 5. Ping Peer B from Peer A → the ping still succeeds. 6.1. Manually disconnect Peer A's client, then manually reconnect Peer A. 7.1. Ping Peer B from Peer A → the ping fails. or 6.2. Wait for some time without performing any operations. 7.2. Ping Peer B from Peer A → the ping fails. **Expected behavior** After disabling the policy, Peer A should no longer be able to ping Peer B. **Are you using NetBird Cloud?** No, I'm using self-host **NetBird version** latest **Is any other VPN software installed?** No If yes, which one? **Debug output** To help us resolve the problem, please attach the following anonymized status output netbird status -dA Create and upload a debug bundle, and share the returned file key: netbird debug for 1m -AS -U *Uploaded files are automatically deleted after 30 days.* Alternatively, create the file only and attach it here manually: netbird debug for 1m -AS **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** Add any other context about the problem here. **Have you tried these troubleshooting steps?** - [x] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (if applicable) - [x] Checked for newer NetBird versions - [x] Searched for similar issues on GitHub (including closed ones) - [x] Restarted the NetBird client - [x] Disabled other VPN software - [x] Checked firewall settings
saavagebueno added the triage-needed label 2026-08-05 01:30:15 -04:00
Author
Owner

@SamFusco commented on GitHub (Mar 25, 2026):

I'm guessing because the session is still alive in the table. Try it again but this time while peer B is pinging peer A use peer C to ping peer A after you disable the firewall and see what happens.

<!-- gh-comment-id:4123946012 --> @SamFusco commented on GitHub (Mar 25, 2026): I'm guessing because the session is still alive in the table. Try it again but this time while peer B is pinging peer A use peer C to ping peer A after you disable the firewall and see what happens.
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#11640