On Sat, 20 Mar 2004, Jeroen Massar wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I was wondering if something existed that "NAT"ted/portmap SCTP to TCP. > A Bump In the API or preload would suffice to make this work. > > Hijack the listen() function to listen on both the TCP and SCTP port, > though that would require 2 sockets and thus app support. > It would possibly be easier to do when the kernel handles this > or there was a possiblity to portmap SCTP->TCP thus keeping > the original source address, which is known. > > Let the connect() function first try SCTP and if that fails > let it connect over TCP. This could be done using a BIA trick. I don't see any need to hijack listen() or connect() calls to make an existing TCP application to use SCTP. This can be done by trapping the socket() call and replacing the protocol with IPPROTO_SCTP. The lksctp-tools package does include a utility called 'withsctp' that can used with most of the existing TCP applications to make them use SCTP. You can find it as part of the lksctp-tools-1.0.0-1.i386.rpm at http://sourceforge.net/project/showfiles.php?group_id=26529 -Sridhar > > This would greatly enhance the number of applications that > support SCTP as suddenly everything supports it. > > There is a bit of overhead in that every SCTP connect will > be refused if the remote host doesn't do SCTP at all. > This could be resolved by having a little cache for ip pairs > that don't support SCTP, eg 'SCPT connect fails, don't try > the trick next time when trying this host for the coming <n> days' > > Greets, > Jeroen - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
