Hi, Thanks for the quick reply,
> > I would find that a useful thing, but admit that I have only theoretical > knowledge about SCTP (and have no time to work on it). > > I've been reading up on SCTP and making test apps with it, I'm also in contact with Randy Stewart who is the main person behind the spec and Michael Tuexen who's done a lot of research on it, both are very helpful. I won't say I'm an expert but I think I know my way around and I'll be happy to give it a serious try. > The code parts in question inside OpenVPN (socket.c) are somewhat > complicated due to lots of existing options and lots of existing > operating systems being supported, so this will not be a trivial > task. > > Would it be a good idea to limit the scope of this project by concentrating on one OS first? I was thinking FreeBSD first since that contains the reference implementation of SCTP. > What I'd definitely recommend to do is base your work on JJO's IPv6 > transport patches, because he already changed large parts of socket.c > - so if you base your work on "plain 2.2", there will be endless conflicts. > > Yes, I'll have a closer look at the IPv6 work. > functionality to listen on multiple sockets in parallel, This is somethings SCTP has build in. One SCTP association (connection over one or more nodes) can contain multiple independent data streams. Regards, Olivier > > gert > > -- > USENET is *not* the non-clickable part of WWW! > // > www.muc.de/~gert/ > Gert Doering - Munich, Germany > g...@greenie.muc.de > fax: +49-89-35655025 > g...@net.informatik.tu-muenchen.de > -- “If you know what you're doing, three layers is enough; if you don't, even seventeen levels won't help”. ~ Padlipsky
