Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages wha2tsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
WAN links tend to have much lower single-session throughput compared to a LAN, even if technically they are at the same speed, due to latency.
Yes and no. For TCP traffic, you can obtain the same "speed" as on LANs, but you need to insure receiving host's RWIN is sized for path's BDP.
However, what cannot be avoided, because of latency, is slow start is even slower to "ramp up" and congestion recovery is also slower to "ramp up".
Oh, things like Windows, file transfers tend to slow as latency increases, as they tend to be "chatty", especially Windows later file systems with their embedded alternative streams and file attributes.
WAAS/WAFS can often help much with WAN transfer rates, or you need an application that can slice and dice a single session transfer into multiple/concurrent session transfers.
