tinc - Nov 2008 - Problems after upgrading from 1.0.7 to 1.0.8

A gentoo based server running running tinc for years serving some dozens clients
has problems after upgradng from 1.0.7 to 1.0.8 using official gentoo ebuilds. 
The clienst are running linux and windows with different version of tinc. The 
clients still get a connect but sending data results in just no answer from the 
(updated) server side. The server log shows this for an example (IP changed):

1227111771 tinc.jan[10406]: Got PACKET from Philipp (5.216.18.5 port 53591): 17
84
1227111771 tinc.jan[10406]: Received packet of 84 bytes from Philipp (5.216.18.5
port 655)
1227111771 tinc.jan[10406]: Writing packet of 84 bytes to Linux tun/tap device 
(tun mode)
1227111771 tinc.jan[10406]: Read packet of 256 bytes from Linux tun/tap device 
(tun mode)
1227111771 tinc.jan[10406]: Sending packet of 256 bytes to Philipp (5.216.18.5 
port 655)
1227111771 tinc.jan[10406]: Node Philipp (5.216.18.5 port 655) is not reachable

Is there any change to configuration files I've to consider? I've not
changed
anything on any side and did not find any hint what to change so far.

The client IP logged by tinc is the offcial one, not the one inside the VPN, I 
guess this is correct? Also routing and firewall rules (iptables) seems to be OK
to me. tinc and the box has been restarted several times before and was running 
stable for years until now.

I guess this is a common issue and easy to fix. Any help?

TiA,
Jan

On Wed, Nov 19, 2008 at 06:17:39PM +0100, Jan Schubert wrote:
> The clients still get a connect but sending data results in just no answer
from the
> (updated) server side. The server log shows this for an example (IP
changed):
[...]
> 1227111771 tinc.jan[10406]: Read packet of 256 bytes from Linux tun/tap
device (tun mode)
> 1227111771 tinc.jan[10406]: Sending packet of 256 bytes to Philipp
(5.216.18.5 port 655)
> 1227111771 tinc.jan[10406]: Node Philipp (5.216.18.5 port 655) is not
reachable
> 
> Is there any change to configuration files I've to consider? I've
not changed
> anything on any side and did not find any hint what to change so far.
There have been no big changes between 1.0.7 and 1.0.8. You shouldn't have
to
change any configuration files.

Can you tell me which version of tinc you are running on the Windows machines,
and can you give the command "tincd -n jan -kUSR2" on the server while
the VPN
is up and send me the resulting output which gets written to the syslog?
> The client IP logged by tinc is the offcial one, not the one inside the
VPN, I
> guess this is correct?
That is correct.
> I guess this is a common issue and easy to fix. Any help?
This is the first time I've heard of this particular problem.

-- 
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: 197 bytes
Desc: Digital signature
Url :
http://www.tinc-vpn.org/pipermail/tinc/attachments/20081119/470c6ad0/attachment.pgp