-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
ecn bug #4178
Comments
I can confirm this. My project has seen a lot of users getting "sendmsg: invalid argument" caused by ECN. I guess we should have ECN detection, something similar to |
@heixiaoma You shouldn't need the QUIC_GO_DISABLE_GSO code path. quic-go does that automatically now. Also note that these environment variables shouldn't be set dynamically, as they won't apply to old connections.
I'm not opposed to that. However, ideally I'd like this to be more specific than just matching an |
"You're right. Currently, it seems like this is the only solution. If there are specific error messages or ways to check if Ecn is supported in order to configure it, that would be even better." |
adding some extra data point to this. I was able to reproduce this problem as well while running on a docker within a synology NAS. Disabling it manually via the ENV variable fixed the problem. |
Currently, I am using the gomobile library to compile into an AAR package for use in Android. Specifically, version 0.39 works fine on my Android phone. However, when I upgraded to version 0.4, I encountered the "sendmsg: invalid argument" issue. Fortunately, I was able to resolve this problem by using the code os.Setenv("QUIC_GO_DISABLE_ECN", "true"). I suspect there might be compatibility issues with ECN in version 0.4, but I am unsure how to express it precisely.
The text was updated successfully, but these errors were encountered: