Roland Mainz wrote: > While working on the IPv6 patch for ksh93 I found two issues with SCTP > support in OS/Net: > 1. |getservbyname()| does not seem to support "sctp" as |proto| value, > e.g. |getservbyname(str, "sctp")| seems to return |NULL| in all cases. > 2. |getaddressinfo()| seems to override the |ai_protocol| from the > |hints| with a default value, e.g. if |IPPROTO_SCTP| is set I get the > value |0| in |res|'s |ai_protocol|.
Yes, this is a known issue :-( > Are these bugs or is there a reason for that (quick look over the code > in OS/Net shows more cases where TCP and UDP are handled explicitly but > not SCTP; per > http://src.opensolaris.org/source/search?q=tcp+udp+-sctp&defs=&refs=&path=%2Fonnv&hist= > this seems to include libraries, commands, IPfilter and kernel code... > ;-( ) ? The only reason is that SCTP is "new" and there are still a lot of uncertainties. For example, how does a NAT (part of ipfilter) work with SCTP when an association is multi-homed. The difficulty is that not all packets of the association will go through the same NAT. Up to now, most of the "core" network technologies work with SCTP in Solaris, such as IPsec, clustering, Trusted extension, inetd... When the need arises and the uncertainties cleared, we will update the other technologies. Please list all the needed features for ksh93 to work with SCTP and we will file bugs to fix those. -- K. Poon. [EMAIL PROTECTED] _______________________________________________ networking-discuss mailing list [email protected]
