tinc - Jan 2007 - strange speed issue

Hello,
I'm trying to connect some windows machines together using tinc 1.0.6.
The basic connectivity (ping) works fine as expected. But I'm getting
really poor speeds over the tinc tunnel. The test machines are on the
same switch and get values ranging from 6-9 MBytes/s speaking directly to
each other. However over the tinc tunnel the speeds are in the range of
20-40 kbytes/s. The machines itself have plenty of horsepower and the
tinc process barely reaches 1% cpu usage with 99% being idle. The result
stays the same when I set "Compression = 0" or "Compression =
10" in all
host files. Same goes with or without "TCPOnly = yes", no relevant
speed
difference.
Tests are done using netio (both tcp and udp), ftp and even windows
filesharing.

These speeds can't be normal for tinc over a lan link, can they?
Are there any known speed problems with the windows client?
I'm pasting some of the relevant config files, it's a really basic
scenario. I'd appreciate any ideas or tips how to release the breaks.

Below are some of the host files:
HostA:
 Address = 10.1.100.152
 Subnet = 192.168.75.10/32
 Compression = 0
 -----BEGIN RSA PUBLIC KEY-----
 (snip)
 -----END RSA PUBLIC KEY-----

HostB:
 Address = 10.1.100.16
 Subnet = 192.168.75.20/32
 Compression = 0
 -----BEGIN RSA PUBLIC KEY-----
 (snip)
 -----END RSA PUBLIC KEY-----

tincd.conf (of HostA):
 Name = HostA
 ConnectTo = HostB
 Interface = mynet

HostA's tap device is configured as 192.168.75.10/24
HostB's tap device is configured as 192.168.75.20/24

netio -s (on HostB)
netio -t 192.168.75.20 (on HostA)
TCP connection established.
Packet size  1k bytes:  21883 Byte/s Tx,  2593 Byte/s Rx.
Packet size  2k bytes:  26800 Byte/s Tx,  4648 Byte/s Rx.
Packet size  4k bytes:  35699 Byte/s Tx,  11597 Byte/s Rx.
Packet size  8k bytes:  37288 Byte/s Tx,  478 KByte/s Rx.
Packet size 16k bytes:  40295 Byte/s Tx,  10347 Byte/s Rx.
Packet size 32k bytes:  41915 Byte/s Tx,  11552 Byte/s Rx.
Done.

netio -b 16k -u 192.168.75.20 (on HostA)
UDP connection established.
Packet size 16k bytes:  40873 Byte/s (99%) Tx,  1898 KByte/s (16%) Rx.
Done.

ftp and cifs transfers are within the same speed ranges roughly.


P.S. On an unrelated note, is the graphviz writer built into the windows
binary? I can't seem to get it to create a file.

P.P.S. I realize someone else just recently made a similar post in this
list, but I decided to make a new one since my problem here is not
limited to TCPonly.


---
Samuel Graenacher
CIT / System Administration
Fr. Sauter AG
http://www.sauter-controls.com

DISCLAIMER:
This communication, and the information it contains is for the sole use of
the intended recipient. It is confidential, may be legally privileged and
protected by law. Unauthorized use, copying or disclosure of any part
thereof may be unlawful. If you have received this communication in error,
please destroy all copies and kindly notify the sender.

On Tue, Jan 02, 2007 at 02:33:33PM +0100, Samuel Graenacher wrote:

[6-9 MB/s LAN, 20-40 kB/s tinc]
> 
> These speeds can't be normal for tinc over a lan link, can they?
> Are there any known speed problems with the windows client?
> I'm pasting some of the relevant config files, it's a really basic
> scenario. I'd appreciate any ideas or tips how to release the breaks.
No, it's not normal. However, more people have reported slow speeds
under Windows. I don't use Windows myself, but I did install it on a few
Windows machines and I have seen better speeds. So I guess it works OK
for some but is bad for others. Things you should try (and report their
success or failure of) are:

1. Increase the priority of the tincd.exe process.
2. Use Mode = switch.
3. Try to install a newer TAP-Win32 driver from OpenVPN, just use the
   Windows installer from http://openvpn.net/download.html.
4. Fiddle with the advanced properties of the TAP-Win32 driver. 
> P.S. On an unrelated note, is the graphviz writer built into the windows
> binary? I can't seem to get it to create a file.
Yes it is, although I didn't test it on Windows.
> P.P.S. I realize someone else just recently made a similar post in this
> list, but I decided to make a new one since my problem here is not
> limited to TCPonly.
That's OK.

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus@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://brouwer.uvt.nl/pipermail/tinc/attachments/20070103/5af31a68/attachment.pgp

On Tue, Jan 02, 2007 at 02:33:33PM +0100, Samuel Graenacher wrote:
> I'm trying to connect some windows machines together using tinc 1.0.6.
> The basic connectivity (ping) works fine as expected. But I'm getting
> really poor speeds over the tinc tunnel.
For the others on the list: I found the bug that caused this. Next
release will feature a huge speed improvement under Windows. It was a
wonder it worked at all.
> P.S. On an unrelated note, is the graphviz writer built into the windows
> binary? I can't seem to get it to create a file.
It works for me. It tries to write a temporary file and then rename it
to the given filename, however that does not work under Windows if that
file already exists. So you should see two files instead of one after a
while. This will be fixed in the next release as well.

Piping it through another command also works under Windows.

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus@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://brouwer.uvt.nl/pipermail/tinc/attachments/20070105/44277455/attachment.pgp