|
|
On Friday 02 July 2004 08:12, Torge Szczepanek wrote:
> On Friday 02 July 2004 10:59, Daniel Berger wrote:
> > > - for (i = 0; i < 100; i++) {
> > > + for (i = 0; i < 1000; i++) {
> > > snprintf(buf,sizeof(buf),name,i);
> > > if (__dev_get_by_name(buf) == NULL) {
> > > strcpy(dev->name, buf);
>
> Performance is going to be bad. A hashed device lookup is a better idea. I
> ran some test with many devices and network load. Without a hashed device
> lookup you will get performance problems when going to more than about 250
> devices and network traffic.
I'm checking into this thread late, so I'm not sure if this has already been
discussed, but what about using the OpenVPN 2.0 features to multiplex a large
number of clients though a single tun interface?
OpenVPN 2.0 already has an efficient hash-based lookup to allow the
multiplexing algorithm to scale up to hundreds or thousands of clients,
provided the CPU and/or acceleration hardware can keep up with the crypto
load.
James
____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users
|