Hi again Dewen;

It sounds to me like Stunnel isn't being accessed at all.  You should be seeing something in the
Stunnel log window.  I run Stunnel under Windows, so what I generally do is get Stunnel to listen
to the loopback interface at address 127.0.0.1, or some other address within the loopback interface
range.  As such, if I was attempting to access it with a utility like Netcat, my basic stunnel.conf would
look something like this for the client side:


debug =7

[service.name]
client = yes
accept = 127.0.0.1:12035
connect = destination.address:1230


Then, I would point Netcat to the listening address and port.  In your case, that might be netcat 127.0.0.1:12035.

Then see if Stunnel logs your connection attempt.

Again, this is under Windows, so your mileage may vary.

Let us know how it works out for you.

Regards;

Thomas

On 3/17/2012 12:32 PM, Dewen Kong wrote:
Hi Thomas,

Thank you for your help.

here is the config file in one computer
client = yes
[ncat]
accept = 12035
connect = ***.***.***.***:1230
and on this computer, I run the command: cat test.file | netcat  ***.***.***.***: 12035. to connect the remote server with IP( ***.***.***.***) on port 12035. I figure on stunnel will accept the port 12035 and connect to the remote server on port 1230 or  I thought.

and no another remote server, I run the command netcat -l -p 1230 which means listen to the port 1230. 

after I run the test, it seems on remote server didn't receive anything on the port 1230.the log file of stunnel dooesn't have any record of this communication.  the last line of the log file is still "configuration successfully"

 and the version of stunnel I use is 4.42


any suggests that may be wrong?


Dewen Kong




On Fri, Mar 16, 2012 at 10:14 PM, Thomas Eifert <kxkvi@wi.rr.com> wrote:
Dewen;

I think I misread your post.  Please forgive me, as I'm unfamiliar with the Netcat application.

If you could provide some additional detail, that might be helpful.

Regards;

Thomas



On 3/16/2012 9:38 PM, Thomas Eifert wrote:
Dewen;

I don't know anything about Netcat, so I'm taking a stab in the dark here, but it looks as if
you're pointing Netcat at port 1230, while your config file indicates that Stunnel would be
listening on port 12035.  Try redirecting Netcat to the listening port.

If you need to post again, please indicate the version of Stunnel you are using, and what
platform your are running it on.

Regards;

Thomas


On 3/16/2012 5:35 PM, Dewen Kong wrote:
Hi all,
 
I am a new guy to stunnel.
 
here is the issue I meet, i install my stunnel in the lab. and trying to run the test with netcat.
 
Here is the config file i test:
 
 
client side:
...
...
output = stunnel.log
client = yes
[ncat]
accept = 12035
connect = ***.***.***.***:1230
then I run "stunnel test.conf "and the the log file shows configuration successfully
 
then I run the command  "cat test.file | netcat ***.***.***.*** 12035 on the client side
and run netcat -l -p 1230 > output
nothing happens.
And I check the log file. there is no record about the netcat.  I don't know what happened.
 
 


--
Dewen Kong


_______________________________________________
stunnel-users mailing list
stunnel-users@stunnel.org
http://stunnel.mirt.net/mailman/listinfo/stunnel-users


-- 
Attention: This message and all attachments are private and may contain information that is confidential and privileged. If you received this message in error, please notify the sender by reply email and delete the message immediately. 


_______________________________________________
stunnel-users mailing list
stunnel-users@stunnel.org
http://stunnel.mirt.net/mailman/listinfo/stunnel-users


-- 
Attention: This message and all attachments are private and may contain information that is confidential and privileged. If you received this message in error, please notify the sender by reply email and delete the message immediately.

_______________________________________________
stunnel-users mailing list
stunnel-users@stunnel.org
http://stunnel.mirt.net/mailman/listinfo/stunnel-users




--
Dewen Kong

-- 
Attention: This message and all attachments are private and may contain information that is confidential and privileged. If you received this message in error, please notify the sender by reply email and delete the message immediately.