Jason Maas wrote:
> Hi Aaron,
>
> On Fri, 13 Jun 2008, Aaron Wood wrote:
>
>> Any explanation on the block size reasoning would be great to hear.
>
> VPNs require another layer on the TCP/IP stack, thus leaving less room for
> data in a given packet. It's probably somehow related to that. You often
> need to monkey with MTU (max transmission unit?) sizes. Things like ICMP
> echo packets (ping) will work fine but real data transfer using full size
> packets will weirdly fail. Google for "vpn mtu" for more info...
>
The additional encapsulation required for VPN is probably part of the
problem, then there is the issue of differing MTU size through any
routers along the pathway; all you need is one with a small MTU to cause
packet fragmentation/reassembly problems. Some VPNs are also sensitive
to latency.
You need a local boot server, even if you can get away with a central
application server (which may also be problematic depending on your
bandwidth and latency). You could probably use "thick" clients running
NX connecting to FreeNX on the central server (secure and works well
over WAN connections and has low bandwidth requirements).
--
"History doesn't repeat itself; at best it rhymes."
- Mark Twain
| John Lucas [EMAIL PROTECTED] |
| St. Thomas, VI 00802 http://mrjohnlucas.googlepages.com/ |
| 18.3°N, 65°W AST (UTC-4) |
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
