@bdruth @marcoarment Since this issue is based on a bug in XNU’s TCP code, you might not run in to it much if you’re only using Network.framework APIs rather than sockets directly. There’s a separate userspace TCP stack used by Network.framework that might not have the same issue. Read up on “skywalk” / “skywalkctl” if you want more background.