[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

stunnel as transparent proxy.



Hi,

stunnel is installed here with this configuration.
"server" has been substituted for the real name of course.

peter@joule:~$ cat /etc/stunnel/stunnel.conf
# joule:/etc/stunnel/stunnel.conf
[pop3]
client = yes
accept = localhost:110
connect = server:995

[https]
client = yes
accept = localhost:443
transparent = destination

This is the /etc/default/stunnel4.

# /etc/default/stunnel4
# Julien LEMOINE <...>
# September 2003

# Change to one to enable stunnel automatic startup
ENABLED=1
FILES="/etc/stunnel/*.conf"
OPTIONS="debug=debug "

# Change to one to enable ppp restart scripts
PPP_RESTART=0

# Change to enable the setting of limits on the stunnel instances
# For example, to set a large limit on file descriptors (to enable
# more simultaneous client connections), set RLIMITS="-n 4096"
# More than one resource limit may be modified at the same time,
# e.g. RLIMITS="-n 4096 -d unlimited"
RLIMITS=""

Messages can be received from the pop server.  stunnel is working for 
POP3.

An attempt to open a page via HTTPS gives this report in the log.
Jul 16 11:25:16 joule stunnel: LOG5[4]: Service [https] accepted connection from 127.0.0.1:36140
Jul 16 11:25:16 joule stunnel: LOG3[4]: getsockopt SO_ORIGINAL_DST: Protocol not available (92)
Jul 16 11:25:16 joule stunnel: LOG5[4]: Connection reset: 0 byte(s) sent to TLS, 0 byte(s) sent to socket

Appears the client application here has sent the request to port 36140 
and stunnel doesn't have a configuration for that.  

Any ideas before I dig in the client software?

Thanks,            ... Peter E.

-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140            Bcc: peter at easthope. ca


Reply to: