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 am trying to build Calico on s390x architecture which uses this package for SCTP related logic. I noticed that client would not connect to server spitting out following message:
Upon debugging I found that SCTP_SOCKOPT_CONNECTX3 flag used here caused the issue. When I replaced the flag with SCTP_SOCKOPT_CONNECTX then it works fine.
I am using go version go1.15.2 linux/s390x to compile/run the example included in the repository.
Just wondering what would cause this issue and whether SCTP_SOCKOPT_CONNECTX can be used exclusively during SCTPConnect function?
Thanks!
The text was updated successfully, but these errors were encountered:
Some more update: I noticed that by only changing optlen to uintptr(unsafe.Pointer(&optlen)) makes it work across most of s390x distros. It certainly looks like getsockopt function is having trouble passing the optlen arguments. Wonder if there are other ways of achieving similar results?
Hi there,
I am trying to build Calico on s390x architecture which uses this package for SCTP related logic. I noticed that client would not connect to server spitting out following message:
Upon debugging I found that
SCTP_SOCKOPT_CONNECTX3
flag used here caused the issue. When I replaced the flag withSCTP_SOCKOPT_CONNECTX
then it works fine.I am using
go version go1.15.2 linux/s390x
to compile/run the example included in the repository.Just wondering what would cause this issue and whether
SCTP_SOCKOPT_CONNECTX
can be used exclusively duringSCTPConnect
function?Thanks!
The text was updated successfully, but these errors were encountered: