FW: Windows 7 support? Should I be able to PING over the VPN?
Guus Sliepen
guus at tinc-vpn.org
Mon Jul 19 11:38:02 CEST 2010
You got it working now, but to answer a few open questions:
On Sun, Jul 18, 2010 at 07:05:08PM -0400, Alan S. Lawee wrote:
> It looks like the two nodes are communicating - they seem to be able to
> exchange RSA keys & MetaKeys, but for some reason, they start trying to
> exchange data on random ports (1361, 1362, 1436, etc.) before the connection
> has been completely established and I'm guessing that they might be getting
> blocked by Windows Firewall (I did add tinc.exe to the program exception
> list, along with port 655 on TCP and on UDP in the Firewall). There are no
> clues in the manual as to why it changes port numbers, but I guess that it's
> a security issue.
This is completely normal behaviour for TCP connections. The program that
initiates a connection gets assigned a random, unused port number, and it will
connect to a well-known port number on the other side.
> I am also getting error messages "Cannot route packet from _xxx_ (MYSELF):
> unknown IPv4 destination address 192.168.3.255" The manual mentions that I
> should ignore broadcast messages (ending in .255), so I'm not sure if this
> message is relevant.
Those messages about broadcast packets are indeed not relevant.
--
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: 198 bytes
Desc: Digital signature
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20100719/f4b25378/attachment.pgp>
More information about the tinc
mailing list