Exploring MLPS options and connecting across oceans.
Exploring MLPS options and connecting across oceans.
Hello everyone, thank you for your feedback and suggestions. My office is located in Chiang Mai, Thailand, with our main headquarters in Sydney, Australia. We sometimes need to connect remotely via RDP or transfer files between the two locations. Right now we rely on Cisco Easyconnect VPN and Windows RDP, which functions adequately for server management. However, file transfers are quite slow. Additionally, we aim to develop a straightforward estimating tool through this link to maintain transparency across our offices. This process is also slow. We’re currently experiencing around 200Mbps download and 100Mbps upload speeds via our ISP in Chiang Mai. Upgrading to a higher bandwidth line seems possible, but I’m unsure it will significantly improve remote connection performance through the Easyconnect platform. One of our IT professionals suggested implementing an MLPS service to address these challenges. I’m interested in learning how effective this would be for connecting to the Sydney server and setting up a DFS system to replicate some directories on their side. The main concern is cost. Quotes suggest domestic speeds of 100Mbps and international at 50Mbps, priced around $2,500 per month through one provider, plus a separate MLPS service at $1,250 per month for the other ISP—this appears quite high. I’m seeking alternative options, aiming for roughly 20Mbps or better speeds to our Sydney link. If you have any other ideas, I’d appreciate them. I’m not after unrealistic connections but a more practical solution. Please let me know if I missed anything important. Thank you all for your time.
MPLS won't solve the issue. With MPLS you'll still face the same bandwidth problem; just eliminate the VPN segment (data will be routed directly on Layer 2 between sites). An alternative is to use an SD-WAN Accelerator. These devices compress data from start to finish and improve throughput. Also consider the firewall's CPU performance under VPN conditions—can it handle the full bandwidth through the VPN link? It might be underperforming.
MPLS comes with a high cost. It's unclear how much bandwidth loss occurs via IPSEC, but it probably isn't worth the price tag for MPLS. Consider using IPSEC alongside other MPLS solutions to reduce its attack surface. Acceptable trade-offs include longer RDP delays. Verify your equipment supports the available bandwidth and monitor IPSEC performance. A DFS-R share is a solid option—it creates an offsite copy, allowing remote offices to sync changes in sequence. Also explore BranchCache, though I'm still unfamiliar with it.
Do you have more than one connection in Thailand? If you secure two separate ISP links, you might set up a load balancing tunnel between Thailand and the Australian office to boost overall bandwidth. This works best if each ISP provides its own distinct route. Creating several load balancing tunnels could help increase competition for overseas connections. MPLS seems excessive here. I believe using pfSense or OpenVPN would be more suitable for your VPN requirements.
most folks overlook the amount of CPU power needed for VPNs over high-speed connections, particularly on older systems lacking dedicated encryption handling. lowering your encryption settings can help, and testing it yourself will clarify if it’s a problem. to understand various options better, reach out to a provider—like a major ISP—and ask them to demonstrate their solutions. they’ll share the advantages, disadvantages, and pricing, often giving you valuable guidance without any cost.
The problem lies in Australia with its slow internet connection. I’d consider moving your servers to a datacenter in Sydney for improved performance. Alternatively, setting up a VDI or RDS service in Thailand could keep data local and reduce transfer needs. Physically, there are no direct fiber links from Southeast Asia to Sydney, so you’d need several hops. From the East Coast US to Brisbane I typically experience around 250ms latency.
MPLS operates under your ISP’s authority, meaning it functions reliably within their network. Once the link exits their control, things become less predictable. They might still have deals with other providers, but for places like Thailand and Vietnam, these restrictions seem to matter most.
Recognized. Today another ISP visited and quoted us just over 3000$ per month for their MPLS service. They mentioned alternative options, including using multiple ISPs or a private line supporting up to 16 IP addresses. Since the discussion was in Thai, I found it hard to grasp the specifics. I’ll share their quote once I get it and clarify what they’re proposing. Appreciate your responses.
It could help to confirm the datacenter in Syndey. The VPN shouldn’t severely limit your upload when downloads reach 180. With speeds of 1/1GB/s and current tests showing 180/3 or 200/100, you should achieve roughly 50/50 performance. If you can connect via RDP to Sydney, run some speed checks. While VPNs add overhead, they shouldn’t be outdated unless they’re decades old. Rather than a VPN, consider using HTTPS or RemoteApp (Microsoft Windows RDS) as alternatives. Horizon is costly for VDI but may suit your needs if required. For smaller firms, virtual desktops with Apache Guacamole offer a budget-friendly option to share desktops. Keep in mind your local connection might only reach 200/100 to resources in Thailand or Vietnam—have you tested speeds in India, the UK, or the US?
I verified the speeds using the RPD link and recorded 831Mbps down and 805Mbps up when reaching the best server between Sydney and Sydney. My location isn’t at my office, but I tested my home connection across several US and Australian points. The ISP there provides 100/30 Mbps. I experience 200-250ms ping and roughly 110Mbps to 130Mbps with upload speeds of about 6-8Mbps when connecting to servers in the USA and Australia. I’ll review the office setup and possibly share a video or photos for clearer insight into my performance.