Thanks to visit codestin.com
Credit goes to github.com

Skip to content

UDP QUIC forwarding doesn't work properly #15492

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.

Sign up for GitHub

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

Jump to bottom
Open
deansheather opened this issue Nov 13, 2024 · 3 comments
Open

UDP QUIC forwarding doesn't work properly #15492

deansheather opened this issue Nov 13, 2024 · 3 comments
Labels
bug risk Prone to bugs networking Area: networking s2 Broken use cases or features (with a workaround). Only humans may set this.

Comments

@deansheather
Copy link
Member

Trying to forward webtransport QUIC traffic from a QUIC server in a workspace to local doesn't seem to work. It may have something to do with MTUs and packet sizes.

It seems to be related to coder port-forward and not an issue with the QUIC server/client since using a different UDP forwarding method such as a vscode extension seems to work just fine (UDP encapsulated in TCP).

Private Slack thread with customer: https://codercom.slack.com/archives/C06JMTAKSNS/p1725293840165049
@coder-labeler coder-labeler bot added bug risk Prone to bugs networking Area: networking labels Nov 13, 2024
@bpmct bpmct added the s2 Broken use cases or features (with a workaround). Only humans may set this. label Dec 12, 2024
@bpmct
Copy link
Member

bpmct commented Dec 12, 2024

@coadler - are you able to take this for the sprint?

@matifali
Copy link
Member

I also rediscovered this while testing Amazon-DCV module.

@coadler coadler self-assigned this Dec 17, 2024
@ghost
Copy link

ghost commented Jan 8, 2025

Mosh via coder port-forward --udp exhibits similar behaviour that looks like MTU issues. Mosh sessions connect fine but after a short interval block completely with the dreaded mosh: Last contact 12 seconds ago. [To quit: Ctrl-^ .] message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug risk Prone to bugs networking Area: networking s2 Broken use cases or features (with a workaround). Only humans may set this.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@coadler @matifali @deansheather @bpmct