[Samba] Samba & STunnel

[Stephen Lee]

On Wed, 2002-02-27 at 08:58, VIA Internet Tech Support wrote:

> On my office firewall I have the following stunnel command:
> 
> /usr/sbin/stunnel -d 140 -r 192.168.0.15:139
> 
> On my firewall I have this command:
> 
> /usr/sbin/stunnel -c -d 139 -r 202.44.170.5:140
> 
> Now, the way I read this is that my firewall says - take anything on tcp 
> port 139, and send it via stunnel to 202.44.170.5 using port 140 - and then 
> the office firewall says - take anything on tcp port 140, and send it 
> unencrypted to 192.168.0.15 using port 139.
> 
> I then try a map from my PC using the following "\\firewall\public", which 
> is in my windows hosts file as - 192.168.0.1  firewall.  As far as I can 
> see, this should give me a tcp tunnel from my firewall to the office 
> firewall using port 140, with my PC sending tcp port 139 packets into the 
> tunnel, and the tunnel spitting them out the other end to the Samba 
> fileserver.  As far as the Samba server is concerned the packets should be 
> coming from the firewall, and it is set to accept connections from 192.168.0.
> 
> So, what have I missed?  Why doesn't it work?  Have I screwed something up, 
> or will this never work because Samba uses UDP or OOBC (out of band 
> communications?), or something?
>

I think what you want is vpn. Stunnel only does TCP via SSL and I think
browsing uses UDP.

Stephen