Using tinc on a blocked network..

[Guus Sliepen]

On Fri, May 11, 2007 at 09:28:15AM +0100, willy at gardiol.org wrote:

[...]
> The problem is that network B is behind a firewall that for
> some reasons cannot be opened whatsoever. This mean that:
> Network B can freely connect to network A (SSH, for example)
> Netowkr A cannot access network B in any way (except, trough
> a connection already open by Network B).
> 
> Up to now i have used a PPP connection over a SSH tunnel
[...]
> I have tried, but seems like i cannot make it work! 
> 
> This is part of the log from Network A:
> Sending PING to client (81.208.74.190 port 22971): 8
> Sending 2 bytes of metadata to client (81.208.74.190 port 22971)
> Flushing 2 bytes to client (81.208.74.190 port 22971)
> Got PONG from client (81.208.74.190 port 22971): 9
> Read packet of 98 bytes from Linux tun/tap device (tun mode)
> Sending packet of 98 bytes to client (81.208.74.190 port 655)
> 
> Note that i cannot open any port (or DMZ in any way) the
> firewall at 81.208.74.190!

By default, tinc will try to send UDP packets to port 655. However, the
firewall of network B will probably block any incoming UDP packets. Try
to add the option "TCPOnly = yes" to hosts/client.

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://brouwer.uvt.nl/pipermail/tinc/attachments/20070514/3b9ed3df/attachment.pgp