aboutsummaryrefslogtreecommitdiffstats
path: root/lib/diameter/test/diameter_traffic_SUITE.erl
diff options
context:
space:
mode:
authorAnders Svensson <[email protected]>2017-04-10 15:28:43 +0200
committerAnders Svensson <[email protected]>2017-06-11 16:30:37 +0200
commit618acfe5dcb0aa3d8ec0101704cd8fc774ac6c90 (patch)
treed85e23ff6cb82501d25d926198d0fa3490cfbe21 /lib/diameter/test/diameter_traffic_SUITE.erl
parentc02abb8185bc9c33b93d13cd720539e5bf5e2fad (diff)
downloadotp-618acfe5dcb0aa3d8ec0101704cd8fc774ac6c90.tar.gz
otp-618acfe5dcb0aa3d8ec0101704cd8fc774ac6c90.tar.bz2
otp-618acfe5dcb0aa3d8ec0101704cd8fc774ac6c90.zip
Deal with SCTP association id quirk on Solaris
In particular, that the association id received in messages on a one-to-one socket after peeloff may be different from the id received on the listen socket at comm_up. This seems odd, since it's then not possible to send until the id is discovered by reception of an SCTP message containing it, but it's unclear if this is a bug or a feature, or if it's specific to certain platforms. Treat it as a feature in this commit, and get the association id as mentioned, an incoming CER being expected before anything is sent. Commit da3e5d67 has more history.
Diffstat (limited to 'lib/diameter/test/diameter_traffic_SUITE.erl')
0 files changed, 0 insertions, 0 deletions