tinc - Jun 2011 - Weird behaviour between Windows Vista & Windows 7 VPN - can anyone help?. Still no success

I am at a loss to explain why it still doesn't work.  I regenerated the keys
and have eliminated the 'Bogus data received message'.  In fact, the
debug
log looks totally normal now.  However, when I try to 'ping' from the
Home
PC to the Office PC, I get a 'request timed out' message & Windows
Networking is still not able to see the PC at the other end.  I do see a
burst of activity in the debug log window when I issue the 'ping'
request,
so I'm pretty certain that the message is getting across to the other side.

 

I was reluctant to use the 'switch' mode because I didn't really
understand
if the traffic going across the VPN would be limited to what was generated
by the PC running the tinc daemon, or if all traffic on the LAN would be
forwarded.  Now that you have recommended it and I am using it, I'm
beginning to wonder if the problem isn't to do with the firewall (Norton
Internet Security).  I will try to verify this by disabling the firewall the
next time I visit the client.  I did open port 655 on both the physical
adapter and the TAP adapter, but I'm now wondering if there is something
more that I have to do.  

 

This is all very perplexing.  Thanks for the help,

Alan

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20110620/e11c8422/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Liben.zip
Type: application/octet-stream
Size: 5592 bytes
Desc: not available
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20110620/e11c8422/attachment.obj>

On Mon, Jun 20, 2011 at 12:48:26PM -0400, Alan S. Lawee wrote:
> I am at a loss to explain why it still doesn't work.  I regenerated the
keys
> and have eliminated the 'Bogus data received message'.  In fact,
the debug
> log looks totally normal now.  However, when I try to 'ping' from
the Home
> PC to the Office PC, I get a 'request timed out' message &
Windows
> Networking is still not able to see the PC at the other end.  I do see a
> burst of activity in the debug log window when I issue the 'ping'
request,
> so I'm pretty certain that the message is getting across to the other
side.
The logs indeed look normal. However, if you cannot ping, then either the
LibenVPN interface is not configured correctly, or your firewall is blocking
packets from the VPN.
> I was reluctant to use the 'switch' mode because I didn't
really understand
> if the traffic going across the VPN would be limited to what was generated
> by the PC running the tinc daemon, or if all traffic on the LAN would be
> forwarded.
Tinc will not see traffic from the LAN interface regardless of the Mode
setting, unless you explicitly set up routing or bridging to forward traffic
between the LAN and LibenVPN interface.
> Now that you have recommended it and I am using it, I'm
> beginning to wonder if the problem isn't to do with the firewall
(Norton
> Internet Security).  I will try to verify this by disabling the firewall
the
> next time I visit the client.  I did open port 655 on both the physical
> adapter and the TAP adapter, but I'm now wondering if there is
something
> more that I have to do.  
You should allow everything on the TAP adapter. Port 655 is only used on the
physical adapter.

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20110621/7f9b28e9/attachment.pgp>