[vnet] windows ip and route configuration #51690
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
flyinghermit
approved these changes
Feb 4, 2025
| "golang.zx2c4.com/wireguard/tun" | ||
| ) | ||
|
|
||
| const ( | ||
| tunInterfaceName = "TeleportVNet" |
There was a problem hiding this comment.
Not sure if we can reuse the service name defined in https://github.com/gravitational/teleport/blob/master/lib/vnet/service_windows.go#L36.
If we want a different name for the tun, maybe spell out TeleportVNetTUN
There was a problem hiding this comment.
i think i'll leave it as-is they are separate concepts that just happen to be the same string, i prefer naming the TUN interface just TeleportVNet
smallinsky
approved these changes
Feb 4, 2025
c3e05c8 to
d646d38
Compare
cfff7f3 to
af60426
Compare
d646d38 to
0dee98d
Compare
af60426 to
4c4d5d3
Compare
This PR adds OS configuration for VNet on Windows. Specifically, the TUN interface is now configured with a V6 and V4 IP address, and IP routes are configured so that IP packets in the VNet IP ranges for each cluster are routed to the TUN interface and handled by VNet. This PR does *not* configure the VNet DNS nameserver on Windows, that will come in a following PR. With these changes, VNet kind of works, without DNS. You can manually query the IP address of VNet's DNS server and get back a v4 and v6 address for the app. TCP connections to either of these addresses then work for connecting to the app.
4c4d5d3 to
9b6d12f
Compare
|
@nklaassen See the table below for backport results.
|
nklaassen
added a commit
that referenced
this pull request
Feb 6, 2025
Backport #51690 to branch/v17
nklaassen
added a commit
that referenced
this pull request
Feb 6, 2025
Backport #51690 to branch/v17
nklaassen
added a commit
that referenced
this pull request
Feb 6, 2025
Backport #51690 to branch/v17
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 7, 2025
Backport #51690 to branch/v17
carloscastrojumo
pushed a commit
to carloscastrojumo/teleport
that referenced
this pull request
Feb 19, 2025
This PR adds OS configuration for VNet on Windows. Specifically, the TUN interface is now configured with a V6 and V4 IP address, and IP routes are configured so that IP packets in the VNet IP ranges for each cluster are routed to the TUN interface and handled by VNet. This PR does *not* configure the VNet DNS nameserver on Windows, that will come in a following PR. With these changes, VNet kind of works, without DNS. You can manually query the IP address of VNet's DNS server and get back a v4 and v6 address for the app. TCP connections to either of these addresses then work for connecting to the app.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of RFD 195.
This PR adds OS configuration for VNet on Windows. Specifically, the TUN interface is now configured with a V6 and V4 IP address, and IP routes are configured so that IP packets in the VNet IP ranges for each cluster are routed to the TUN interface and handled by VNet.
This PR does not configure the VNet DNS nameserver on Windows, that will come in a following PR.
With these changes, VNet kind of works, without DNS. You can manually query the IP address of VNet's DNS server and get back a v4 and v6 address for the app. TCP connections to either of these addresses then work for connecting to the app.