Hi, On Sat, Feb 26, 2011 at 11:19:19AM +0000, Olivier Van Acker wrote: > > 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.
Well, you'd certainly start with one OS, but in the long run, you'd want
the mainstream OSes (Linux and Windows) as well...
[..]
> > 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.
This doesn't help me a single bit if I'm sitting behind a firewall that
doesn't even let UDP/1194 pass - listening on SCTP *and* UDP/TCP in parallel
will be necesary, because too many clients won't be able to use SCTP, at
least when starting this.
Or are you implying that by listening on a SCTP socket, the kernel
machinery will also handle incoming "plain UDP" and "plain TCP" connects
via that SCTP socket?
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
pgpEP3POWQCL4.pgp
Description: PGP signature
