tinc - Sep 2010 - Windows 7 64-bit clients with high latency

Hi,

Windows 7 64-bit clients have a very high latency (constantly rising) using of
tinc. 32-bit clients are working with normal speed.
Does anyone have a solution for this problem?

Viele Gr??e

Dirk Krause

On Sun, Sep 05, 2010 at 07:08:06PM +0200, Dirk Krause wrote:
> Windows 7 64-bit clients have a very high latency (constantly rising) using
of tinc. 32-bit clients are working with normal speed.
> Does anyone have a solution for this problem?
How high is your latency exactly, and how fast does it rise? Can you also see
if the CPU usage of the tincd.exe process goes up?

-- 
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/20100905/fafbdc15/attachment.pgp>

> -----Urspr?ngliche Nachricht-----
> Von: Guus Sliepen
> Gesendet: Sonntag, 5. September 2010 22:35
> Betreff: Re: Windows 7 64-bit clients with high latency
> 
> On Sun, Sep 05, 2010 at 07:08:06PM +0200, Dirk Krause wrote:
> 
> > Windows 7 64-bit clients have a very high latency (constantly rising)
> using of tinc. 32-bit clients are working with normal speed.
> > Does anyone have a solution for this problem?
> 
> How high is your latency exactly, and how fast does it rise? Can you also
> see if the CPU usage of the tincd.exe process goes up?
> 
First, sorry for the late reply.
The latency varies between 67ms and 1061ms:

C:\>ping 192.168.0.8 -t

Ping wird ausgef?hrt f?r 192.168.0.8 mit 32 Bytes Daten:
Antwort von 192.168.0.8: Bytes=32 Zeit=864ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=1019ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=1058ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=1059ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=98ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=161ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=223ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=286ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=444ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=503ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=568ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=723ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=879ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=943ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=1004ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=1060ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=97ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=222ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=285ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=347ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=417ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=581ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=644ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=708ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=863ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=925ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=987ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=1049ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=1058ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=1051ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=739ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=130ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=703ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=67ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=443ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=482ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=634ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=635ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=856ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=79ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=76ms TTL=127
Antwort von 192.168.0.8: Bytes=32 Zeit=648ms TTL=127

Ping-Statistik f?r 192.168.0.8:
    Pakete: Gesendet = 83, Empfangen = 83, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 67ms, Maximum = 1061ms, Mittelwert = 692ms

The CPU usage of the tincd process is 0% on the Client and the server.

--
Mit freundlichen Gr??en / with kind regards,
Dirk Krause