-
Notifications
You must be signed in to change notification settings - Fork 199
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
System.Net.Sockets.SocketException (55): No buffer space available #425
Comments
That's a new one. Have to look into that. I wonder if it is trying to set the socket options, when it really shouldn't do it on any other OS than Windows. |
@NiclasOlofsson it sets ReceiveBufferSize to int.Max before platformId check so that's the problem. Probably should be moved into that if statement. |
Should probably check to see if it can give me a proper max size for the platfom in question. |
Hello, EDIT; I moved the lines pointed out by undrfined, seems to work |
OS X max seems to be 7280*1024 for me. |
OSX does not support DontFragment either (on Catalina atleast) |
Then i would say OSX is a security risk. It's a pretty common attack vector to framgent messages on UDP. And it's really difficult to spot since the IO won't communicate it outside of the "kernel" sort of. |
Is this still an issue? Do we need to look into this or do we mark this as won't fix? @NiclasOlofsson |
When starting MiNET, it throws the following error:
OS: macOS Mojave
.NET core: 2.1.403
I'm not able to connect to the server.
The text was updated successfully, but these errors were encountered: