Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UDP port forwarding not working on Windows with network tunnel enabled #6821

Closed
segevfiner opened this issue May 5, 2024 · 6 comments · Fixed by #7617 or #7618
Closed

UDP port forwarding not working on Windows with network tunnel enabled #6821

segevfiner opened this issue May 5, 2024 · 6 comments · Fixed by #7617 or #7618
Assignees
Labels
area/networking kind/enhancement New feature or request platform/windows regression Functionality was working in a previous release and is now broken
Milestone

Comments

@segevfiner
Copy link

Actual Behavior

With the network tunnel enabled host-switch listens for TCP even when exposing a UDP port from a container. Without it enabled wslrelay.exe doesn't listen at all on UDP ports.

Steps to Reproduce

Any container with -p 1234:1234/udp

Result

host-switch listens for TCP on the exposed port instead of UDP.

Expected Behavior

It should listen and forward UDP correctly.

Additional Information

No response

Rancher Desktop Version

1.13.1

Rancher Desktop K8s Version

1.29.4

Which container engine are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

Windows 11 Pro 10.0.22631

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

N/A

@segevfiner segevfiner added the kind/bug Something isn't working label May 5, 2024
@Nino-K Nino-K self-assigned this May 6, 2024
@Nino-K
Copy link
Member

Nino-K commented May 6, 2024

The UDP is not supported currently, however, this is something that I will look into after our current release since I know that the upstream library that we are using may have done some work to support this.

@Nino-K Nino-K added kind/enhancement New feature or request platform/windows area/networking and removed kind/bug Something isn't working labels May 6, 2024
@segevfiner
Copy link
Author

P.S. I also tried WSL mirrored networking mode, but Rancher Desktop won't start in that mode #6665

@AndreKR
Copy link

AndreKR commented Aug 11, 2024

Is this why -p 1234:1234/udp doesn't work when using Rancher Desktop? The port is not reachable. I don't understand what "the network tunnel enabled host-switch" is. Do I have to enable or disable it for UDP ports to work? And where do I enable/disable it?

@stampycode
Copy link

Since switching to v1.15 the legacy networking mode in Rancher Desktop for Windows (which worked for UDP streams) is no longer available, so we are now unable to upgrade to any version beyond v1.14 until UDP forwarding is fixed.

@rcastagno
Copy link

+1
Finding that the only feature making this work has been removed before fixing the problem is frustrating.

@gunamata gunamata added this to the 1.17 milestone Sep 13, 2024
@gunamata gunamata added the regression Functionality was working in a previous release and is now broken label Sep 13, 2024
@VitaliiTrubchaninovUbisoft

This issue makes Rancher Desktop unusable for UDP only applications. Previously we would use internal IP of the WSL instance to communicate with server running in docker container over UDP, but now even that is not available. We had to go back to raw docker installation in WSL. Please consider implementing UDP support sooner than later.

This was referenced Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/networking kind/enhancement New feature or request platform/windows regression Functionality was working in a previous release and is now broken
Projects
None yet
7 participants