In message <_A4052@delegate-en.ML_> on 08/06/08(04:39:24)
you Joe in MPLS <firstname.lastname@example.org> wrote:
|Do the "internal representations of ports" consume resources even if
|they ports aren't used? Unfortunately the server ports aren't assigned
|sequentially in contiguous ranges. If I configured delegate using port
|ranges there would be many ports included in the ranges that wouldn't
|actually get used.
The "internal representation" is merely textually expanded representation
of ports with its socket descriptor. For example -P2000-2003 can be
represented internally as "-P2000/100,2001/101,2002/102,2003/103".
You can see it in the log output of DeleGate.
And of course you can specify a list of non-contiguous ports like
-P2000,2004,2005,2008,... for example. Also it can be specified
separately as -Q2000 -Q2004 -Q2005 -Q2008 ... after DeleGate 9.8.2.
|How high could I go when redefining the "PORTSSIZE" value defined in
|include/dglib.h? The server(s) that I would use would be dedicated to
|running delegate for this application.
The default value of it is 512 and about 70 ports can be represented
in it because about 8 bytes is necessary for each port as "2000/123,".
So the value 3000 will be enough to represents 300 ports.
A possible problem is the limitation of the number of file descriptors
available per process, but typically it's 1024 or so in most OS nowadays.
|Might running delegate as an SSL VPN endpoint be a better way to do this?
I don't know what the role of DeleGate is in the case.
9 9 Yutaka Sato <email@example.com> http://delegate.org/y.sato/
( ~ ) National Institute of Advanced Industrial Science and Technology
_< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller