What steps will reproduce the problem?
1.Add an alias IPv6 to an interface in some windows machine
2.Create socket for IPv6 and bind using the alias ip
3.Try to establish connection in client mode with some other SCTP server
What is the expected output? What do you see instead?
== The initial INIT packet should originate from the alias IPv6 used during
bind, but the source IPv6 found to be the primary IPv6 of that interface and
eventually it aborts the connection after receiving INIT_ACK from the peer node.
What version of the product are you using? On what operating system?
== I am using the revision 9168 (latest as of now) of the product in Windows 7
ultimate 64-bit machine.
Please provide any additional information below.
== The library works fine for alias IPs when used for IPv4
Original issue reported on code.google.com by dghosh....@gmail.com on 18 Feb 2015 at 3:53
Original issue reported on code.google.com by
dghosh....@gmail.comon 18 Feb 2015 at 3:53