[stunnel-users] Connection Refused by libwrap

This is a discussion on [stunnel-users] Connection Refused by libwrap within the Stunnel Users forums, part of the Networking and Network Related category; Hi, With Version 4.14, I've now started seeing the following messages occaisionally when I fire up 4 concurrent ...


Go Back   Usenet Forums > Networking and Network Related > Stunnel Users

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 01-08-2006
Eddie Atherton
 
Posts: n/a
Default [stunnel-users] Connection Refused by libwrap

Hi,

With Version 4.14, I've now started seeing the following messages
occaisionally when I fire up 4 concurrent connections from my Windows box,
via stunnel on Linux, to my NewsServer:

Jan 3 17:55:13 The-Tardis stunnel: LOG3[17760:399]: Unexpected socket close
(read_blocking)
Jan 3 17:55:13 The-Tardis stunnel: LOG4[17760:399]: Connection from
192.168.0.2:2073 REFUSED by libwrap
Jan 3 17:55:13 The-Tardis stunnel: LOG3[17761:399]: Unexpected socket close
(read_blocking)
Jan 3 17:55:13 The-Tardis stunnel: LOG4[17761:399]: Connection from
192.168.0.2:2073 REFUSED by libwrap
Jan 3 17:55:13 The-Tardis stunnel: LOG3[17761:400]: Unexpected socket close
(read_blocking)
Jan 3 17:55:13 The-Tardis stunnel: LOG4[17761:400]: Connection from
192.168.0.2:2074 REFUSED by libwrap
Jan 3 17:55:13 The-Tardis stunnel: LOG3[3824:399]: Unexpected socket close
(read_blocking)
Jan 3 17:55:13 The-Tardis stunnel: LOG4[3824:399]: Connection from
192.168.0.2:2073 REFUSED by libwrap
Jan 3 17:55:13 The-Tardis stunnel: LOG3[3824:400]: Unexpected socket close
(read_blocking)
Jan 3 17:55:13 The-Tardis stunnel: LOG4[3824:400]: Connection from
192.168.0.2:2074 REFUSED by libwrap
Jan 3 17:55:13 The-Tardis stunnel: LOG3[3824:401]: Unexpected socket close
(read_blocking)
Jan 3 17:55:13 The-Tardis stunnel: LOG4[3824:401]: Connection from
192.168.0.2:2075 REFUSED by libwrap

Following this, the connections continues as normal.

Now, ASAIK, I'm not using the wrappers. I'm starting stunnel as a daemon, in
rc.local. There are no entries in inetd.conf for the port that the windows
machine connects from. Here's the relevent parts of the config file:

; Use it for client mode
client = yes

[nntps]
accept = 563
connect = newsgroups.comcast.net:563

Cheers,
Eddie
_______________________________________________
stunnel-users mailing list
stunnel-users@mirt.net
http://stunnel.mirt.net/mailman/listinfo/stunnel-users
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 07:33 AM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0