[prev in list] [next in list] [prev in thread] [next in thread] 

List:       stunnel-users
Subject:    Re: [stunnel-users] issue with running stunnel
From:       Thomas Eifert <kxkvi () wi ! rr ! com>
Date:       2012-03-18 0:13:40
Message-ID: 4F6528B4.2060503 () wi ! rr ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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 
> <mailto: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  <mailto: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  <mailto: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 <mailto: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.


[Attachment #5 (text/html)]

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi again Dewen;<br>
    <br>
    It sounds to me like Stunnel isn't being accessed at all.&nbsp; You
    should be seeing something in the <br>
    Stunnel log window.&nbsp; I run Stunnel under Windows, so what I
    generally do is get Stunnel to listen<br>
    to the loopback interface at address 127.0.0.1, or some other
    address within the loopback interface<br>
    range.&nbsp; As such, if I was attempting to access it with a utility
    like Netcat, my basic stunnel.conf would<br>
    look something like this for the client side:<br>
    <br>
    <br>
    debug =7<br>
    <br>
    [service.name]<br>
    client = yes<br>
    accept = 127.0.0.1:12035<br>
    connect = destination.address:1230<br>
    <br>
    <br>
    Then, I would point Netcat to the listening address and port.&nbsp; In
    your case, that might be netcat 127.0.0.1:12035.<br>
    <br>
    Then see if Stunnel logs your connection attempt.<br>
    <br>
    Again, this is under Windows, so your mileage may vary.<br>
    <br>
    Let us know how it works out for you.<br>
    <br>
    Regards;<br>
    <br>
    Thomas<br>
    <br>
    On 3/17/2012 12:32 PM, Dewen Kong wrote:
    <blockquote
cite="mid:CAG3qBkgjHuYwr6ahW=M4dHYzjL+F8SnvT+cB=nHK2MdS=5hsvQ@mail.gmail.com"
      type="cite">Hi Thomas,
      <div><br>
      </div>
      <div>Thank you for your help.</div>
      <div><br>
      </div>
      <div>here is the config file in one computer</div>
      <div>
        <blockquote type="cite">
          <blockquote type="cite">
            <div>client = yes</div>
            <div>[ncat]</div>
            <div>
              accept = 12035</div>
            <div>connect = ***.***.***.***:1230</div>
          </blockquote>
        </blockquote>
      </div>
      <div>
        <blockquote type="cite">
          <div>and on this computer, I run the command: cat test.file |
            netcat&nbsp;&nbsp;***.***.***.***: 12035. to connect \
                the&nbsp;remote&nbsp;server
            with IP(&nbsp;***.***.***.***) on port 12035. I figure on stunnel
            will accept the port 12035 and connect to the remote server
            on port 1230 or &nbsp;I thought.</div>
        </blockquote>
      </div>
      <div>
        <div><br>
        </div>
      </div>
      <div>and no another&nbsp;remote&nbsp;server, I run the command netcat -l -p
        1230 which means listen to the port 1230.&nbsp;</div>
      <div><br>
      </div>
      <div>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&nbsp;communication.&nbsp;&nbsp;the last line
        of the log file is still "configuration successfully"</div>
      <div><br>
      </div>
      <div>&nbsp;and the version of stunnel I use is 4.42</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>any suggests that may be wrong?</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>Dewen Kong</div>
      <div><br>
      </div>
      <div>
        <blockquote type="cite">
          <div><br>
          </div>
        </blockquote>
      </div>
      <div>
        <blockquote type="cite">
          <div><br>
          </div>
        </blockquote>
      </div>
      <div><br>
        <div class="gmail_quote">On Fri, Mar 16, 2012 at 10:14 PM,
          Thomas Eifert <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:kxkvi@wi.rr.com">kxkvi@wi.rr.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000"> Dewen;<br>
              <br>
              I think I misread your post.&nbsp; Please forgive me, as I'm
              unfamiliar with the Netcat application.<br>
              <br>
              If you could provide some additional detail, that might be
              helpful.<br>
              <br>
              Regards;<br>
              <br>
              Thomas
              <div>
                <div class="h5"><br>
                  <br>
                  <br>
                  On 3/16/2012 9:38 PM, Thomas Eifert wrote:
                  <blockquote type="cite"> Dewen;<br>
                    <br>
                    I don't know anything about Netcat, so I'm taking a
                    stab in the dark here, but it looks as if<br>
                    you're pointing Netcat at port 1230, while your
                    config file indicates that Stunnel would be <br>
                    listening on port 12035.&nbsp; Try redirecting Netcat to
                    the listening port.<br>
                    <br>
                    If you need to post again, please indicate the
                    version of Stunnel you are using, and what<br>
                    platform your are running it on.<br>
                    <br>
                    Regards;<br>
                    <br>
                    Thomas<br>
                    <br>
                    <br>
                    On 3/16/2012 5:35 PM, Dewen Kong wrote:
                    <blockquote type="cite">
                      <div>Hi all,</div>
                      <div>&nbsp;</div>
                      <div>I am a new guy to stunnel.</div>
                      <div>&nbsp;</div>
                      <div>here is the issue I meet, i install my
                        stunnel in the lab. and trying to run the test
                        with netcat. </div>
                      <div>&nbsp;</div>
                      <div>Here is the config file i test:</div>
                      <div>&nbsp;</div>
                      <div>&nbsp;</div>
                      <div>client side:</div>
                      <div>...</div>
                      <div>...</div>
                      <div>output = stunnel.log</div>
                      <div>client = yes</div>
                      <div>[ncat]</div>
                      <div>accept = 12035</div>
                      <div>connect = ***.***.***.***:1230</div>
                      <div>then I run "stunnel test.conf "and the the
                        log file shows configuration successfully</div>
                      <div>&nbsp;</div>
                      <div>then I run the command&nbsp; "cat test.file |
                        netcat ***.***.***.*** 12035 on the client side</div>
                      <div>and run netcat -l -p 1230 &gt; output</div>
                      <div>nothing happens. </div>
                      <div>And&nbsp;I check the log file. there is no record
                        about the netcat.&nbsp; I don't know what happened. </div>
                      <div>&nbsp;</div>
                      <div>&nbsp;</div>
                      <div><br clear="all">
                        <br>
                        -- <br>
                        <b><i><span><span style="FONT-SIZE:large"><font
                                  face="georgia, serif">Dewen \
Kong</font></span></span></i></b><br>  </div>
                      <br>
                      <fieldset></fieldset>
                      <br>
                      <pre>_______________________________________________
stunnel-users mailing list
<a moz-do-not-send="true" href="mailto:stunnel-users@stunnel.org" \
target="_blank">stunnel-users@stunnel.org</a> <a moz-do-not-send="true" \
href="http://stunnel.mirt.net/mailman/listinfo/stunnel-users" \
target="_blank">http://stunnel.mirt.net/mailman/listinfo/stunnel-users</a> </pre>
                    </blockquote>
                    <br>
                    <pre cols="72">-- 
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. </pre>  <br>
                    <fieldset></fieldset>
                    <br>
                    <pre>_______________________________________________
stunnel-users mailing list
<a moz-do-not-send="true" href="mailto:stunnel-users@stunnel.org" \
target="_blank">stunnel-users@stunnel.org</a> <a moz-do-not-send="true" \
href="http://stunnel.mirt.net/mailman/listinfo/stunnel-users" \
target="_blank">http://stunnel.mirt.net/mailman/listinfo/stunnel-users</a> </pre>
                  </blockquote>
                  <br>
                  <pre cols="72">-- 
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. </pre>  </div>
              </div>
            </div>
            <br>
            _______________________________________________<br>
            stunnel-users mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:stunnel-users@stunnel.org">stunnel-users@stunnel.org</a><br>
  <a moz-do-not-send="true"
              href="http://stunnel.mirt.net/mailman/listinfo/stunnel-users"
              target="_blank">http://stunnel.mirt.net/mailman/listinfo/stunnel-users</a><br>
  <br>
          </blockquote>
        </div>
        <br>
        <br clear="all">
        <div><br>
        </div>
        -- <br>
        <b><i><span style="background-color:rgb(255,255,255)"><span
                style="font-size:large"><font face="georgia, serif">Dewen
                  Kong</font></span></span></i></b><br>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
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. </pre>  </body>
</html>



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


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic