Hi, There appears to be a limit to the number of services you can define. Services beyond the 64th service appear to get set up without any log warnings or errors, yet don't pass traffic. The code uses select() & FD_SET to accept() an incoming connection & in Windows (using Windows Server 2008) the default is 64 sockets for that so wondering if I can just recompile, setting FD_SETSIZE to something larger. I'll try it either way, just wanted to put it out there to see if anyone else has ever run into this. Thanks, Terren
It is possible to setup stunnel as separate services. I don't know if this would be a suitable workaround for you. On Thu, Apr 4, 2013 at 12:35 PM, Terren Suydam < terren@singleclicksystems.com> wrote:
Hi,
There appears to be a limit to the number of services you can define. Services beyond the 64th service appear to get set up without any log warnings or errors, yet don't pass traffic.
The code uses select() & FD_SET to accept() an incoming connection & in Windows (using Windows Server 2008) the default is 64 sockets for that so wondering if I can just recompile, setting FD_SETSIZE to something larger.
I'll try it either way, just wanted to put it out there to see if anyone else has ever run into this.
Thanks, Terren ______________________________**_________________ stunnel-users mailing list stunnel-users@stunnel.org https://www.stunnel.org/cgi-**bin/mailman/listinfo/stunnel-**users<https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users>
Hi Brian - just to clarify, you mean running multiple instances of stunnel correct? On 4/4/2013 12:52 PM, Brian Wilkins wrote:
It is possible to setup stunnel as separate services. I don't know if this would be a suitable workaround for you.
On Thu, Apr 4, 2013 at 12:35 PM, Terren Suydam <terren@singleclicksystems.com <mailto:terren@singleclicksystems.com>> wrote:
Hi,
There appears to be a limit to the number of services you can define. Services beyond the 64th service appear to get set up without any log warnings or errors, yet don't pass traffic.
The code uses select() & FD_SET to accept() an incoming connection & in Windows (using Windows Server 2008) the default is 64 sockets for that so wondering if I can just recompile, setting FD_SETSIZE to something larger.
I'll try it either way, just wanted to put it out there to see if anyone else has ever run into this.
Thanks, Terren _________________________________________________ stunnel-users mailing list stunnel-users@stunnel.org <mailto:stunnel-users@stunnel.org> https://www.stunnel.org/cgi-__bin/mailman/listinfo/stunnel-__users <https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users>
On Thu, 4 Apr 2013 12:52:09 -0400 Brian Wilkins <bwilkins@gmail.com> wrote:
It is possible to setup stunnel as separate services. I don't know if this would be a suitable workaround for you.
Hi, Since, I can't recall the version (edit: probably since 4.16 as Michal stated in the link below), it is not possible to run more than one instance of stunnel. You can just create service level configurations in the conf file and nothing else. (Previously I, myself, had 2 conf files for client and server too) If there are only allowed 64 services (and therefore ports), I think it might be considered as a new feature to add or as a bug. I never need such ammount of services, but could be interesting to fix and allow more. I wouldn't say 65535 minus 1028 but a few more ;-) Regards. https://www.stunnel.org/pipermail/stunnel-users/2011-August/003178.html
Yes, you can. I currently do it. On Apr 5, 2013 12:19 PM, "Javier" <meresponde2001-stn@yahoo.es> wrote:
On Thu, 4 Apr 2013 12:52:09 -0400 Brian Wilkins <bwilkins@gmail.com> wrote:
It is possible to setup stunnel as separate services. I don't know if this would be a suitable workaround for you.
Hi,
Since, I can't recall the version (edit: probably since 4.16 as Michal stated in the link below), it is not possible to run more than one instance of stunnel. You can just create service level configurations in the conf file and nothing else. (Previously I, myself, had 2 conf files for client and server too)
If there are only allowed 64 services (and therefore ports), I think it might be considered as a new feature to add or as a bug.
I never need such ammount of services, but could be interesting to fix and allow more. I wouldn't say 65535 minus 1028 but a few more ;-)
Regards.
https://www.stunnel.org/pipermail/stunnel-users/2011-August/003178.html _______________________________________________ stunnel-users mailing list stunnel-users@stunnel.org https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
On Fri, 5 Apr 2013 13:09:24 -0400 Brian Wilkins <bwilkins@gmail.com> wrote:
Yes, you can. I currently do it.
Hi, But, don't stop there ;-) How do you do it? I'm talking about the windows binary, not the unix one or a cooked one (recompiled) with such feature. At least in my case, I can't and/or I don't find in the manual any option to have more instances. Any help is really appreciated :-) Regards.
I simply have two entries in services. It requires editing the registry and giving two different names to the service entries, for instance stunnel-client and stunnel-server. You can call different config files too. On Friday, April 5, 2013, Javier wrote:
On Fri, 5 Apr 2013 13:09:24 -0400 Brian Wilkins <bwilkins@gmail.com <javascript:;>> wrote:
Yes, you can. I currently do it.
Hi,
But, don't stop there ;-) How do you do it?
I'm talking about the windows binary, not the unix one or a cooked one (recompiled) with such feature.
At least in my case, I can't and/or I don't find in the manual any option to have more instances.
Any help is really appreciated :-)
Regards. _______________________________________________ stunnel-users mailing list stunnel-users@stunnel.org <javascript:;> https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
On Fri, 5 Apr 2013 18:28:43 -0400 Brian Wilkins <bwilkins@gmail.com> wrote:
I simply have two entries in services. It requires editing the registry and giving two different names to the service entries, for instance stunnel-client and stunnel-server. You can call different config files too.
Hi, Ok, I've played a little with your explanation and SrvAny (link below) and I found that is not exactly as you tell, at least under Windows 2000. I didn't know this, but stunnel can run several instances just renaming the stunnel.exe executable, because what stunnel checks only is the PID name not whatever others applications check to check if it is already running. So just changing the executable name of every stunnel.exe copy is enough to have several intances running. About the services, it is not as you told (with my tests). I created two services, but if they call to the same executable the behavior is as expected: unable to run 2 or more instances. It only works if you link each service with a different named executable. Lets say we create service "stn1" and "stn2"; "stn1" should call to "stunnel1.exe" and "stn2" should call to "stunnel2.exe". Of course, each one can take each own .conf file. Anyway, it was interesting to find out this :-) Regards. Handy application from the NT Resource Kit: http://support.microsoft.com/kb/137890/en Download links, including for Windows 2003 server (microsoft website link): http://www.iopus.com/guides/srvany.htm Remember to pass an antivirus anyway.
Windows 2000.... I have not used that in years. I was referring to XP and I do not need to rename the executable. The executable name should have no bearing on the PID. On Apr 6, 2013 11:34 AM, "Javier" <meresponde2001-stn@yahoo.es> wrote:
On Fri, 5 Apr 2013 18:28:43 -0400 Brian Wilkins <bwilkins@gmail.com> wrote:
I simply have two entries in services. It requires editing the registry and giving two different names to the service entries, for instance stunnel-client and stunnel-server. You can call different config files too.
Hi,
Ok, I've played a little with your explanation and SrvAny (link below) and I found that is not exactly as you tell, at least under Windows 2000.
I didn't know this, but stunnel can run several instances just renaming the stunnel.exe executable, because what stunnel checks only is the PID name not whatever others applications check to check if it is already running. So just changing the executable name of every stunnel.exe copy is enough to have several intances running.
About the services, it is not as you told (with my tests). I created two services, but if they call to the same executable the behavior is as expected: unable to run 2 or more instances. It only works if you link each service with a different named executable. Lets say we create service "stn1" and "stn2"; "stn1" should call to "stunnel1.exe" and "stn2" should call to "stunnel2.exe". Of course, each one can take each own .conf file.
Anyway, it was interesting to find out this :-)
Regards.
Handy application from the NT Resource Kit: http://support.microsoft.com/kb/137890/en
Download links, including for Windows 2003 server (microsoft website link): http://www.iopus.com/guides/srvany.htm
Remember to pass an antivirus anyway. _______________________________________________ stunnel-users mailing list stunnel-users@stunnel.org https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
Below is a link to a tutorial I wrote on how to setup stunnel to run as two services.. it's not really necessary anymore because stunnel can do this natively but some people may still benefit from doing it this way. http://sunshinecoder.blogspot.com/2013/04/setup-stunnel-as-two-services.html On Sat, Apr 6, 2013 at 11:34 AM, Javier <meresponde2001-stn@yahoo.es> wrote:
On Fri, 5 Apr 2013 18:28:43 -0400 Brian Wilkins <bwilkins@gmail.com> wrote:
I simply have two entries in services. It requires editing the registry and giving two different names to the service entries, for instance stunnel-client and stunnel-server. You can call different config files too.
Hi,
Ok, I've played a little with your explanation and SrvAny (link below) and I found that is not exactly as you tell, at least under Windows 2000.
I didn't know this, but stunnel can run several instances just renaming the stunnel.exe executable, because what stunnel checks only is the PID name not whatever others applications check to check if it is already running. So just changing the executable name of every stunnel.exe copy is enough to have several intances running.
About the services, it is not as you told (with my tests). I created two services, but if they call to the same executable the behavior is as expected: unable to run 2 or more instances. It only works if you link each service with a different named executable. Lets say we create service "stn1" and "stn2"; "stn1" should call to "stunnel1.exe" and "stn2" should call to "stunnel2.exe". Of course, each one can take each own .conf file.
Anyway, it was interesting to find out this :-)
Regards.
Handy application from the NT Resource Kit: http://support.microsoft.com/kb/137890/en
Download links, including for Windows 2003 server (microsoft website link): http://www.iopus.com/guides/srvany.htm
Remember to pass an antivirus anyway. _______________________________________________ stunnel-users mailing list stunnel-users@stunnel.org https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
On Tue, 9 Apr 2013 08:17:54 -0400 "bwilkins26 ." <bwilkins@gmail.com> wrote:
Below is a link to a tutorial I wrote on how to setup stunnel to run as two services.. it's not really necessary anymore because stunnel can do this natively but some people may still benefit from doing it this way.
http://sunshinecoder.blogspot.com/2013/04/setup-stunnel-as-two-services.html
Hi, Ok, it works and in a more elegant way than renaming :-) Something is added (someday I'll check what exactly) to the service keys that isn't added with Srvany utility that lets the execution of both instances with the same executable name. Probably is that the main executable (image path) isn't the Stunnel executable. Maybe the magic and the lack of that utility. Anyway, all methods are valid and is great to know about them :-) Thanks for your tutorial. Regards.
participants (4)
-
Brian Wilkins -
bwilkins26 .
-
Javier -
Terren Suydam