Skip to content

Commit 780c395

Browse files
Merge pull request #11069 from mendix/nc-private-conn-4via6
Private Connectivity subnet access changes
2 parents 47b34df + 8438dd6 commit 780c395

2 files changed

Lines changed: 15 additions & 1 deletion

File tree

content/en/docs/control-center/security/private-connectivity/configure-private-connectivity.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -478,7 +478,12 @@ The Mendix internal systems operate on the following subnets:
478478
* 172.20.0.0/16
479479

480480
As such, when you expose a subnet or a single IP address, it must not conflict with our private IP ranges.
481-
If you absolutely must use the subnets on which Mendix operates, please configure [Network address translation (NAT)](https://en.wikipedia.org/wiki/Network_address_translation) on your infrastructure.
481+
If you absolutely must use the subnets on which Mendix operates, configure [4via6 subnet routers](https://tailscale.com/docs/features/subnet-routers/4via6-subnets) on your infrastructure. Follow these steps to do that:
482+
483+
1. Generate the IPv6 subnet route – Run `tailscale debug via 100 <Your IPv4 range>` in your terminal.
484+
2. Advertise the IPv6 subnet route – Run `tailscale set --advertise-routes=<Newly generated IPv6 range>` in your terminal.
485+
486+
You can then continue with the steps in the [Enabling and Disabling Resources](/control-center/configure-private-connectivity/#private-connectivity-resources-enable-disable) section. Once you expose resources, make sure to use the generated IPv6 route to connect from your app to the resource, not the original IPv4 route.
482487

483488
### Restricted IP Ranges
484489

content/en/docs/releasenotes/control-center/2026.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,15 @@ weight: 1
77
numberless_headings: true
88
---
99

10+
## April 2026
11+
12+
### April 21, 2026
13+
14+
#### Improvements
15+
16+
* We have moved away from [Network address translation (NAT)](https://en.wikipedia.org/wiki/Network_address_translation) for Private Connectivity subnet access, and are now requiring [4via6 subnet routers](https://tailscale.com/docs/features/subnet-routers/4via6-subnets) instead.
17+
For details, refer to [Configuring and Using Private Connectivity](/control-center/configure-private-connectivity/).
18+
1019
## February 2026
1120

1221
### February 1, 2026

0 commit comments

Comments
 (0)