From: Leonardo R. M. <leo...@so...> - 2008-11-17 15:49:46
|
Aleix Dorca escreveu: > Hi again, > > just to update the list on what I've found. > > I've set up another VPN server, but this time using L2TP over IPSEC > (OpenSWAN) using a similar routing like the one with OpenVPN. I've > seen that the problem also happens in that setup. The performance > copying files is horrible and I get the same: > > ICMP (dest unrch) (DF set) from VPNMachine to SambaMachine > > I guess then it has nothing to do with OpenVPN then, maybe Samba. > Searching Google I've seen that if you look for "Samba and VPN" > instead of OpenVPN the performance results are apolling... from time to time we always have someone complaining about M$ File Sharing protocols performance, even with Microsoft or with 3rd party implementations (Samba). I've seen these complains on OpenVPN lists, on IPSec lists, on every kind of network-related lists when there's a low bandwidth/little higher latency connection involved. Not only VPN, but even with WAN links. It seems to me that Microsoft file sharing protocols were simply not designed for those low bandwidth/little higher latency situations. It's interesting to compare these M$ file sharing protocols with other standards protocols, like HTTP/SMTP/FTP/whatever, which are purely TCP ones, and compare that they perform pretty nice on any kind of situation, being limited only by the bandwidth involved. But M$ sharing protocols no ..... they work fine on LAN networks but when it comes to WAN/VPN, it simply sucks. it can be some workarounds to make it a little worst, but it's clear to me that the protocol simply wasnt designed having these connections in mind. It seems clear to me that it was designed to run LAN only. -- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, NÃO mandem email ger...@so... My SPAMTRAP, do not email it |