You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm seeing this error on OS X whilst connected to a VPN which is presumably using part of the packet for it's own metadata. It looks like mtu on these interfaces is 1266. I've tried simply calling continue if this check fails but that seems to result in a segfault.
I'm not actually trying to use the VPN interface, or any interface actually, just communicate between two processes on the same node.
The text was updated successfully, but these errors were encountered:
As a simple solution, simply define SOCK_MIN_MSS as 1024. The value is arbitrary and should be lowered.
Scott
On May 4, 2016, at 11:15 AM, Ashley Pittman [email protected] wrote:
I'm seeing this error on OS X whilst connected to a VPN which is presumably using part of the packet for it's own metadata. It looks like mtu on these interfaces is 1266. I've tried simply calling continue if this check fails but that seems to result in a segfault.
I'm not actually trying to use the VPN interface, or any interface actually, just communicate between two processes on the same node.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
I'm seeing this error on OS X whilst connected to a VPN which is presumably using part of the packet for it's own metadata. It looks like mtu on these interfaces is 1266. I've tried simply calling continue if this check fails but that seems to result in a segfault.
I'm not actually trying to use the VPN interface, or any interface actually, just communicate between two processes on the same node.
The text was updated successfully, but these errors were encountered: