Windows client not honorring the Port directive?

[Guus Sliepen]

On Wed, Jan 30, 2008 at 06:09:46PM +0100, sich wrote:

> > I have trouble making a tinc daemon on a Windows XP machine behave properly.
> > In order to let the connection go through the (NAT) firewall I need to
> > be able to pinpoint the exact portnumber used, so I can make the
> > proper rewriting rules.
> > 
> > However when I don't specify any Port number the firewall receives
> > connection attempt for the other tinc machine on the internet from a
> > "random" high port number (1025 and up, increasing with each attempt).
> > 
> > If I *do* specify a Port directive in the Host configuration then the
> > daemon is still using the "random" high portnumbers.
[...]
> The tinc port is the destination port. The source port is randomly generate.

The source port of tinc's TCP connections is random, but each tinc
daemon will use a fixed source port for UDP packets. If you see UDP
packets from random port numbers, there is a NAT somewhere in your
network. You can add "TCPOnly = yes" to tinc.conf to tunnel everything
via TCP.

-- 
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://www.tinc-vpn.org/pipermail/tinc/attachments/20080131/142fad3c/attachment.pgp