Hi.

While trying out the BIND capability of the SOCKS server I came across 
the following behavior.
There seems to be timeout which closes the socket opened with the BIND 
command. I also tested this with the danted socks server which does not 
close the connection right away. Here is the log which I'm getting.

09/07 15:45:57.52 [12013] 37+1: # SSL record head[ 5  1  0  0  0] SSL2 
3?/1284
09/07 15:45:57.52 [12013] 37+1: isinSSL ? [5] from client
09/07 15:45:57.52 [12013] 37+1: [SocksV5-serv] VER[5] NMETHODS[1] [0][0]
09/07 15:45:57.52 [12013] 37+1: [SocksV5-serv] VER[5] CMD[2] ATYP[1] 
137.226.208.12:1081
09/07 15:45:57.53 [12013] 37+1: UDP_client_open[11] 
time://137.226.208.12:37 ...
09/07 15:45:57.53 [12013] 37+1: checkIF-UDP connected [11] 
{137.226.208.12:37 <- 137.226.143.233:37187} [0.000s]
09/07 15:45:57.53 [12013] 37+1: 
server_open(VSocket,reno.tvk.rwth-aachen.de:0,listen=1)
09/07 15:45:57.53 [12013] 37+1: server_open: reno.tvk.rwth-aachen.de:0
09/07 15:45:57.53 [12013] 37+1: 
server_open(VSocket,reno.tvk.rwth-aachen.de:0) BOUND
09/07 15:45:57.53 [12013] 37+1: VSocket BIND/SocksV5 
137.226.143.233:33886 137.226.208.12:1081 listen=1 = 11
09/07 15:45:57.53 [12013] 37+1: [SocksV5-serv] resp 0 
[137.226.143.233:33886]
09/07 15:46:07.53 [12013] 37+1: ## accept([11]:33886) failed polling, 
errno=0
09/07 15:46:07.53 [12013] 37+1: VSocket ACPT/SocksV5 
137.226.143.233:33886 137.226.208.12:1081  = -3
09/07 15:46:07.53 [12013] 37+1: [SocksV5-serv] resp 1 
[137.226.143.233:33886]
09/07 15:46:07.53 [12013] 37+1: disconnected [50] 
-@[137.226.143.175]eeknay.tvk.rwth-aachen.de:1711 (1220795167.526s)(0)

As a configuration file I use this:

-P1081
SERVER=socks
STLS="-fcl"
TLSCONF="-vd,cache:no"
RES_CONF=/etc/resolv.conf
RES_WAIT=0
RELIABLE="*"
REMITTABLE="*"
ADMIN=user@reno



Another question is whether the SOCKS server opens a socket via BIND for 
just one connection or does it work like a regular server socket
which can serve multiple requests?

Regards,
Andre