[PR #6368] [MERGED] [management] Emit IPv6 default permit rule for exit node routes #25531

Closed
opened 2026-08-05 07:06:07 -04:00 by saavagebueno · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/netbirdio/netbird/pull/6368
Author: @lixmal
Created: 6/8/2026
Status: Merged
Merged: 6/9/2026
Merged by: @lixmal

Base: mainHead: ipv6-exit-node-default-permit


📝 Commits (1)

  • 8eb50c7 Emit IPv6 default permit firewall rule for exit node routes

📊 Changes

2 files changed (+49 additions, -2 deletions)

View changed files

📝 management/server/types/networkmap_components.go (+6 -2)
📝 management/server/types/networkmap_components_correctness_test.go (+43 -0)

📄 Description

Describe your changes

Exit node routes (0.0.0.0/0) without access control groups only emitted an IPv4 default permit firewall rule. For peers with IPv6 support the client installs a ::/0 route but never received a matching forward-accept rule, so IPv6 traffic was routed to the exit node and then dropped at the forward chain.

  • Emit an IPv6 default permit rule (::/0 source and destination) for default exit node routes in the default-permit path, matching the behavior already present for ACL-protected routes

https://github.com/netbirdio/netbird/discussions/6172

Stack

Checklist

  • Is it a bug fix
  • Is a typo/documentation fix
  • Is a feature enhancement
  • It is a refactor
  • Created tests that fail without the change (if possible)
  • This change does not modify the public API, gRPC protocols, functionality behavior, CLI / service flags, or introduce a new feature — OR I have discussed it with the NetBird team beforehand (link the issue / Slack thread in the description). See CONTRIBUTING.md.

By submitting this pull request, you confirm that you have read and agree to the terms of the Contributor License Agreement.

Documentation

Select exactly one:

  • I added/updated documentation for this change
  • Documentation is not needed for this change (explain why)

Docs PR URL (required if "docs added" is checked)

Paste the PR link from https://github.com/netbirdio/docs here:

https://github.com/netbirdio/docs/pull/__

Summary by CodeRabbit

  • Bug Fixes

    • Fixed IPv6 firewall rule generation to properly create default-permit rules when using default exit routes, ensuring IPv6 connectivity is correctly configured alongside IPv4 default routes.
  • Tests

    • Added test coverage for IPv6 default permit rules in exit node routing configurations.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netbirdio/netbird/pull/6368 **Author:** [@lixmal](https://github.com/lixmal) **Created:** 6/8/2026 **Status:** ✅ Merged **Merged:** 6/9/2026 **Merged by:** [@lixmal](https://github.com/lixmal) **Base:** `main` ← **Head:** `ipv6-exit-node-default-permit` --- ### 📝 Commits (1) - [`8eb50c7`](https://github.com/netbirdio/netbird/commit/8eb50c77040b353d0c471a53281c4ee3772de2ef) Emit IPv6 default permit firewall rule for exit node routes ### 📊 Changes **2 files changed** (+49 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `management/server/types/networkmap_components.go` (+6 -2) 📝 `management/server/types/networkmap_components_correctness_test.go` (+43 -0) </details> ### 📄 Description ## Describe your changes Exit node routes (`0.0.0.0/0`) without access control groups only emitted an IPv4 default permit firewall rule. For peers with IPv6 support the client installs a `::/0` route but never received a matching forward-accept rule, so IPv6 traffic was routed to the exit node and then dropped at the forward chain. - Emit an IPv6 default permit rule (`::/0` source and destination) for default exit node routes in the default-permit path, matching the behavior already present for ACL-protected routes ## Issue ticket number and link https://github.com/netbirdio/netbird/discussions/6172 ## Stack <!-- branch-stack --> ### Checklist - [x] Is it a bug fix - [ ] Is a typo/documentation fix - [ ] Is a feature enhancement - [ ] It is a refactor - [x] Created tests that fail without the change (if possible) - [x] This change does **not** modify the public API, gRPC protocols, functionality behavior, CLI / service flags, or introduce a new feature — **OR** I have discussed it with the NetBird team beforehand (link the issue / Slack thread in the description). See [CONTRIBUTING.md](https://github.com/netbirdio/netbird/blob/main/CONTRIBUTING.md#discuss-changes-with-the-netbird-team-first). > By submitting this pull request, you confirm that you have read and agree to the terms of the [Contributor License Agreement](https://github.com/netbirdio/netbird/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT.md). ## Documentation Select exactly one: - [ ] I added/updated documentation for this change - [x] Documentation is **not needed** for this change (explain why) ### Docs PR URL (required if "docs added" is checked) Paste the PR link from https://github.com/netbirdio/docs here: https://github.com/netbirdio/docs/pull/__ <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Fixed IPv6 firewall rule generation to properly create default-permit rules when using default exit routes, ensuring IPv6 connectivity is correctly configured alongside IPv4 default routes. * **Tests** * Added test coverage for IPv6 default permit rules in exit node routing configurations. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
saavagebueno added the pull-request label 2026-08-05 07:06:07 -04:00
Sign in to join this conversation.
No Label pull-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#25531