[stunnel-users] Connection Refused by libwrap

[Eddie Atherton]

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