{"id":25238,"date":"2026-11-17T10:46:18","date_gmt":"2026-11-17T10:46:18","guid":{"rendered":"https:\/\/atalnetworks.com\/?p=25238"},"modified":"2026-11-17T10:54:31","modified_gmt":"2026-11-17T10:54:31","slug":"10gbps-vpn-server-requirements","status":"publish","type":"post","link":"https:\/\/atalnetworks.com\/el\/10gbps-vpn-server-requirements\/","title":{"rendered":"Sizing a 10Gbps VPN Server: WireGuard, OpenVPN, CPU, and Concurrent Users"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">A VPN server can have a 10Gbps port and still deliver much less than 10Gbps of useful traffic. Encryption, packet processing, CPU allocation, and the network path all affect the result. So does the way people use the service.<\/span><\/p>\n<p><b>The main 10Gbps VPN server requirements are a network path with enough sustained capacity, a CPU that can process the chosen VPN workload, enough memory for connection state, and spare capacity for traffic peaks and failures. There is no fixed core count or users-per-server number that applies to every deployment.<\/b><\/p>\n<p><span style=\"font-weight: 400;\">We size a VPN gateway from its expected workload, then test that workload on the proposed hardware. This guide explains how to do that for WireGuard and OpenVPN, including OpenVPN Data Channel Offload, or DCO.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The numerical scenarios below are planning examples. They are not Atal Networks benchmark results.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">What Does \u201c10Gbps VPN Performance\u201d Mean?<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Before comparing servers, define which rate you need to reach.<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Measurement<\/b><\/th>\n<th><b>What it tells us<\/b><\/th>\n<th><b>What it does not prove<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Port speed<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The nominal link capacity<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Available Internet bandwidth or VPN speed<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Plain network throughput<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Performance without VPN encryption<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Encrypted gateway capacity<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Encrypted tunnel traffic<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Traffic carried by the outer VPN connection<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Useful application data delivered<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Application goodput<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Useful data received by the application<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Performance for every packet size and user pattern<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Sustained service capacity<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Traffic supported while meeting latency and loss targets<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Capacity after a node fails unless tested separately<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">Goodput is the most useful starting point for user capacity. It excludes bytes that carry the data rather than form part of the application&#8217;s useful payload.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A link also carries headers and VPN overhead. As a result, a nominal 10Gbps Ethernet link cannot deliver a full 10Gbps of application payload through a VPN.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Decide whether your target means one fast tunnel, the total across many tunnels, or a busy Internet exit gateway. Those are different tests.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Test the Whole Gateway Path<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">An iperf3 test that ends on the VPN server measures an endpoint workload. It does not test the full forwarding path of an Internet exit service.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For a gateway test, traffic should travel from the client, through the encrypted tunnel, through the VPN server&#8217;s routing and firewall rules, and onward to a separate destination. Return traffic must follow the intended path too.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Include network address translation, or NAT, if production traffic uses it. Include the firewall rules and monitoring you plan to keep enabled.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Calculate Demand From Active Users<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">An account is not a traffic measurement. Neither is a configured WireGuard peer or an idle OpenVPN session.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We need to distinguish four quantities:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Accounts:<\/b><span style=\"font-weight: 400;\"> People or organizations allowed to use the service.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Connected devices:<\/b><span style=\"font-weight: 400;\"> Devices with a session or recent tunnel activity.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Active devices:<\/b><span style=\"font-weight: 400;\"> Devices moving traffic during the measurement period.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Flows:<\/b><span style=\"font-weight: 400;\"> Individual connections carried by those devices.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">One active device can open hundreds of flows. A connected device can also remain almost idle.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Build a Busy-Hour Traffic Model<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Start with this estimate for each user group:<\/span><\/p>\n<p><b>Expected demand = connected devices \u00d7 active share \u00d7 average rate per active device<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Calculate download and upload demand separately. Use rates measured during the same busy period, where possible.<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Example group<\/b><\/th>\n<th><b>Connected devices<\/b><\/th>\n<th><b>Active share<\/b><\/th>\n<th><b>Download rate per active device<\/b><\/th>\n<th><b>Estimated download demand<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Group A<\/span><\/td>\n<td><span style=\"font-weight: 400;\">1,000<\/span><\/td>\n<td><span style=\"font-weight: 400;\">25%<\/span><\/td>\n<td><span style=\"font-weight: 400;\">12 Mbps<\/span><\/td>\n<td><span style=\"font-weight: 400;\">3,000 Mbps<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Group B<\/span><\/td>\n<td><span style=\"font-weight: 400;\">200<\/span><\/td>\n<td><span style=\"font-weight: 400;\">50%<\/span><\/td>\n<td><span style=\"font-weight: 400;\">20 Mbps<\/span><\/td>\n<td><span style=\"font-weight: 400;\">2,000 Mbps<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Total<\/span><\/td>\n<td><span style=\"font-weight: 400;\">1,200<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Varies<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Varies<\/span><\/td>\n<td><span style=\"font-weight: 400;\">5,000 Mbps<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">These rates are assumptions for the example, not standard requirements for browsing, video, or business applications.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The model is a first estimate. Compare it with total busy-hour traffic and short traffic peaks. A software release or company-wide meeting can make user activity rise at the same time.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Do not add separate groups&#8217; percentile values and describe the result as the measured percentile for the whole service. Use an aligned traffic record to see how their peaks overlap.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Leave Spare Capacity<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Suppose a candidate server delivers 8Gbps of application goodput under a representative test. That is a measured ceiling for that workload, not a recommended normal load.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If we choose a 70% operating target for this example:<\/span><\/p>\n<p><b>8Gbps \u00d7 0.70 = 5.6Gbps operating budget<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The 5Gbps example workload fits within that budget, with 0.6Gbps left before reaching the operating target. Whether that margin is enough depends on traffic variation, growth, and the recovery plan.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The 70% figure is a planning choice. It is not a universal rule.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Since the 8Gbps measurement already represents application goodput, do not subtract an estimated VPN overhead percentage from it again. Check the outer link counters separately to confirm that the physical network also has room.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Estimate Users Only After Defining the Workload<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">A 5.6Gbps budget could support 560 active devices averaging 10Mbps each <\/span><b>from a bandwidth-only calculation<\/b><span style=\"font-weight: 400;\">:<\/span><\/p>\n<p><b>5,600 Mbps \u00f7 10 Mbps = 560 active devices<\/b><\/p>\n<p><span style=\"font-weight: 400;\">That does not prove the server supports 560 devices with acceptable service. Packet rate, connection state, client speed, CPU load, and traffic peaks can reduce the usable count.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It also does not tell us how many accounts we can sell. That requires measured activity patterns and a clear service policy.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">WireGuard vs OpenVPN: Compare the Implementation<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">A protocol name alone does not describe how a server processes traffic. Record the implementation, version, operating system, and configuration used for each result.<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Test option<\/b><\/th>\n<th><b>What to record<\/b><\/th>\n<th><b>Main sizing question<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Linux kernel WireGuard<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Kernel version, peer count, MTU, CPU, and NIC settings<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Does the intended traffic spread across available processing resources?<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Userspace WireGuard<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Exact application, version, and packet-processing settings<\/span><\/td>\n<td><span style=\"font-weight: 400;\">How does this implementation behave on the chosen host?<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">OpenVPN without DCO<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Version, transport, cipher, process layout, and client count<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Does a busy process or CPU core limit throughput?<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">OpenVPN with DCO<\/span><\/td>\n<td><span style=\"font-weight: 400;\">OpenVPN version, driver, cipher, supported settings, and runtime status<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Is the data channel actually using offload during the test?<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3><span style=\"font-weight: 400;\">WireGuard and CPU Encryption Features<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">WireGuard uses ChaCha20 for encryption and Poly1305 for authentication. It carries tunnel packets over UDP.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This means an AES acceleration feature is not a direct measure of WireGuard performance. CPU architecture, software implementation, packet handling, and the network path still need testing.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Do not treat all userspace WireGuard programs as equivalent. Tailscale&#8217;s published engineering work shows how changes to batching and network offloads affected its own implementation. Those results are useful technical evidence, but they are not a capacity promise for another application or server.\u00a0<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">OpenVPN With and Without DCO<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">OpenVPN DCO moves data-channel processing into the kernel on supported systems. The userspace process still handles control functions.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For a fair comparison, run the intended OpenVPN deployment with DCO disabled and then with DCO active, where the configuration supports both. Keep the hardware, client workload, cipher, and network path consistent.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Installing a package with DCO support does not prove that offload is active. Check the startup logs and runtime state. Unsupported settings or a missing driver can change the result.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">DCO support depends on the OpenVPN release, operating system, driver, and configuration. Consult the documentation for the release you deploy. The current project documentation lists supported authenticated-encryption ciphers and configuration limits.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Do not apply an old non-DCO benchmark to a current DCO deployment.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Match the Protocol to the Service<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Throughput is one requirement. Client support, access control, authentication, network restrictions, and operational tools also affect the choice.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Test OpenVPN over TCP separately if you need that transport. Do not present a UDP result as proof of TCP performance.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For installation basics, see our <\/span><a href=\"https:\/\/atalnetworks.com\/el\/how-to-set-up-a-virtual-private-network-vpn\/\"><span style=\"font-weight: 400;\">VPN setup guide<\/span><\/a><span style=\"font-weight: 400;\">. Here, we focus on capacity after the required configuration is in place.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">CPU, RAM, and Network Requirements<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">A fixed shopping list cannot prove 10Gbps VPN capacity. We use the following checks to select hardware and identify the resource that needs more capacity.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">CPU: Inspect Each Core<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">A server can show moderate total CPU use while one core is fully occupied. That core may handle a busy process, a network queue, or another part of the packet path.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Record:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CPU model and generation.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Physical cores and logical threads.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Sustained clock speed under load.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Per-core use, including network processing.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Thermal or power-related clock limits.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CPU allocation and steal time on virtual machines.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Steal time is time when a virtual CPU waits while the host runs other work. A VPS with a large vCPU count can still have inconsistent processing time.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">More cores help only when the workload can use them. A higher core count does not guarantee that one tunnel or one busy processing path will run faster.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Linux receive-side scaling, or RSS, can distribute incoming flows among NIC queues. Related mechanisms can move packet processing across CPUs. The distribution depends on the device, driver, and configuration.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Inspect the actual queue and CPU distribution before changing settings. Encrypted outer flows may distribute differently from the application flows inside them.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">RAM: Size for State and Services<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">There is no fixed amount of RAM required per gigabit of VPN traffic.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Memory use depends on the operating system, peer or session state, packet buffers, firewall connection tracking, monitoring, and any other services on the gateway.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For an Internet exit server, record the number of tracked connections during the busy period. Many small application connections can create a different memory load from a few large transfers.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Watch memory pressure, swap activity, connection-tracking limits, and allocation failures. Raising a connection limit without checking memory use can move the failure elsewhere.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">NIC, PCIe, and NUMA: Check the Path to the CPU<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">A 10Gbps label does not describe every part of the network path. Check the negotiated link speed, driver, queue count, interface errors, and PCIe connection.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">On a multi-socket server, note which CPU socket connects to the NIC and where the workload runs. Memory and device access across sockets can affect performance.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Record offload settings before each benchmark. Features such as packet segmentation and receive aggregation can change CPU cost and the packet sizes visible to software. Keep these settings documented so another engineer can repeat the test.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Storage: Check Logging and Recovery Needs<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Forwarding VPN traffic usually does not require writing each packet to disk. Storage can still become busy if the server records detailed flow logs or runs other services.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Test the logging level you intend to use. Measure disk latency, write rate, retention needs, and recovery procedures. A benchmark with logging disabled may not describe the production service.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Packet Size, MTU, and Traffic Direction<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">A server&#8217;s bandwidth result needs packet-size context. Small packets require more packet-processing work for the same payload rate.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Packet Rate Can Become the Limit<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">At a payload rate of 1Gbps, the approximate packet rate is:<\/span><\/p>\n<p><b>Packets per second = payload bits per second \u00f7 (payload bytes per packet \u00d7 8)<\/b><\/p>\n<table>\n<thead>\n<tr>\n<th><b>UDP payload size<\/b><\/th>\n<th><b>Payload rate<\/b><\/th>\n<th><b>Approximate packets per second<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">1,200 bytes<\/span><\/td>\n<td><span style=\"font-weight: 400;\">1Gbps<\/span><\/td>\n<td><span style=\"font-weight: 400;\">104,167<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">120 bytes<\/span><\/td>\n<td><span style=\"font-weight: 400;\">1Gbps<\/span><\/td>\n<td><span style=\"font-weight: 400;\">1,041,667<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">This calculation excludes UDP, IP, VPN, Ethernet, and physical-layer overhead. It is not an Ethernet wire-rate calculation.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The smaller payload requires ten times as many packets in this example. That does not mean CPU use will rise by exactly ten times. Batching, offloads, and fixed processing costs affect the result.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Test both large transfers and small-packet traffic. A large-packet benchmark alone can hide a packet-rate limit.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">MTU Must Fit the Actual Path<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">The maximum transmission unit, or MTU, limits packet size at a given layer. A VPN adds outer headers, so the tunnel must fit within the available path MTU.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A poorly matched MTU can cause fragmentation, loss, or connections that stall on larger transfers. IPv4 and IPv6 paths also need separate checks.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Do not copy one MTU value into every deployment. Test the intended client networks and tunnel path. For TCP, MSS adjustment may address some packet-size problems, but it does not fix all UDP traffic or every path issue.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">A Full-Duplex Port Does Not Mean 20Gbps of VPN Payload<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">A 10Gbps full-duplex port can receive and transmit at the same time. Adding those two rates does not automatically create 20Gbps of useful VPN capacity.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Consider a single-interface Internet exit gateway:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A user download enters from the Internet, then leaves toward the VPN client.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A user upload enters from the VPN client, then leaves toward the Internet.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Both traffic directions consume receive and transmit capacity on that interface. Roughly, the combined download and upload payload contributes to each direction, with different overhead on the encrypted and unencrypted legs.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A single one-way transfer is not automatically limited to half the port rate either. The answer depends on which links it crosses and where traffic enters and leaves.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Measure each physical interface separately. Label forward, reverse, and bidirectional results, and state whether a reported total adds both directions.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Can a VPS Handle a 10Gbps VPN Workload?<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">A VPS can be suitable when its CPU and network allocation meet the workload. The product&#8217;s advertised host port speed is not enough information.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Ask the provider:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Is 10Gbps available to this guest or only to the physical host?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Is guest bandwidth capped, shared, or subject to a sustained-use policy?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Are CPU resources shared or dedicated?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Are there packet-rate limits?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Does the guest support the required kernel, tunnel device, and DCO driver?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What transfer allowance and overage rules apply?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Can we run a permitted capacity test before committing?<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">A dedicated server gives us direct control over its physical CPU and NIC configuration. That can make troubleshooting easier. It still does not prove that the upstream network or VPN configuration will meet the target.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u039c\u03b1\u03c2 <\/span><a href=\"https:\/\/atalnetworks.com\/el\/10gbps-vps-vs-10gbps-dedicated-server\/\"><span style=\"font-weight: 400;\">10Gbps VPS vs. dedicated server comparison<\/span><\/a><span style=\"font-weight: 400;\"> explains the resource-allocation differences in more detail.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">A Practical 10Gbps VPN Test Matrix<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">We need separate tests for network capacity, encryption, packet processing, and user behavior. One peak speed result cannot answer all four questions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Use traffic generators and receivers with enough capacity for the target. A slow client or receiver can make a capable gateway appear slow.<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Test<\/b><\/th>\n<th><b>Workload<\/b><\/th>\n<th><b>What it helps identify<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Plain network baseline<\/span><\/td>\n<td><span style=\"font-weight: 400;\">One TCP flow, then multiple flows without a VPN<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Network or test-host limits<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Routing baseline<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Forward traffic through the intended firewall and NAT rules without encryption<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Forwarding and policy cost<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Single-tunnel test<\/span><\/td>\n<td><span style=\"font-weight: 400;\">One peer with one flow, then several flows<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Single-flow and single-peer limits<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Many-peer test<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Independent clients or peer instances carrying traffic<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Aggregate capacity across peers<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Protocol comparison<\/span><\/td>\n<td><span style=\"font-weight: 400;\">WireGuard, OpenVPN without DCO, and confirmed OpenVPN DCO<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Implementation-specific limits<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Packet-size test<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Controlled UDP payloads such as 120, 512, and 1,200 bytes<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Packet-rate limits and loss<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Direction test<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Upload, download, then both directions<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Directional and shared-resource limits<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Application test<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Busy-hour traffic mix with production rules and logging<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Service quality under expected demand<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Connection-change test<\/span><\/td>\n<td><span style=\"font-weight: 400;\">New sessions, rekeys, and a reconnect wave<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Control-plane pressure<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Failure test<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Remove one gateway and restore service<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Remaining capacity and recovery behavior<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">Use larger packet sizes only after checking the path MTU. Keep client count, traffic direction, and application mix explicit in each result.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Record Enough Detail to Repeat the Test<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Record hardware, operating system, kernel, VPN software, cipher, DCO state, NIC driver, MTU, and offload settings. Include the topology and the number of independent peers.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">During each run, collect:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Receiver-side goodput and offered traffic rate.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Per-core CPU use on the gateway and test hosts.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Interface rates, errors, and drops.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TCP retransmissions or UDP loss and jitter.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Latency before and during load, including p95 and p99.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Memory use, connection state, and logging activity.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">The p95 latency is the value at or below which 95% of recorded samples fall. It helps show delays that an average can hide.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Use iperf3 Without Treating Streams as Users<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">iperf3 supports reverse-direction tests with <\/span><span style=\"font-weight: 400;\">-R<\/span><span style=\"font-weight: 400;\">, parallel streams with <\/span><span style=\"font-weight: 400;\">-P<\/span><span style=\"font-weight: 400;\">, and bidirectional tests with <\/span><span style=\"font-weight: 400;\">&#8211;bidir<\/span><span style=\"font-weight: 400;\">. UDP tests can set an offered rate with <\/span><span style=\"font-weight: 400;\">-b<\/span><span style=\"font-weight: 400;\"> and a payload size with <\/span><span style=\"font-weight: 400;\">-l<\/span><span style=\"font-weight: 400;\">. With parallel streams, the bandwidth setting applies per stream. Check the installed version&#8217;s manual before running tests.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Eight parallel streams through one VPN peer still represent one peer. They do not prove performance for eight independent users or tunnels.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Record the iperf3 version as well. Its threading behavior changed in version 3.16, so older and newer releases can place different limits on the test host.\u00a0<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Increase Load in Steps<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Start below the expected operating rate. Raise the offered traffic in stages while watching goodput, loss, latency, and CPU load.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A workable test plan might use a warm-up period, three 60-second runs at each candidate rate, and a 30-minute sustained run near the proposed operating limit. These durations are a starting procedure, not a formal standard. Extend the runs for longer traffic cycles or intermittent problems.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Define acceptable loss, latency, and recovery time before testing. The usable capacity is the highest workload that stays within those targets with the required spare capacity. It is not necessarily the highest number seen for a few seconds.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">How to Read the Results<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">A useful benchmark tells us what to change next.<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Observation<\/b><\/th>\n<th><b>Possible cause<\/b><\/th>\n<th><b>Next check<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">One CPU core stays busy while total CPU looks low<\/span><\/td>\n<td><span style=\"font-weight: 400;\">A process, queue, or packet path limits work distribution<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Per-core load, process use, and queue distribution<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Most cores stay busy, and throughput stops rising<\/span><\/td>\n<td><span style=\"font-weight: 400;\">CPU processing capacity may be exhausted<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Lower offered rate and compare loss and latency<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">VPN and plain tests stop at a similar rate<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Network, client, receiver, or provider limit<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Test-host load and interface counters<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Small packets fail before large packets<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Packet-rate processing limit<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Packets per second, drops, and network CPU work<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Larger transfers stall while small requests work<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Possible MTU or path issue<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Packet sizes, path MTU, and retransmissions<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Latency rises sharply near the speed ceiling<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Queue buildup or resource saturation<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Reduce load and inspect queues<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Performance varies between VPS runs<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Possible host contention or path variation<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Steal time, time-of-day patterns, and plain baseline<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Reconnects fail during a busy period<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Control-plane, authentication, or dependency pressure<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Session setup rate and dependency logs<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">These observations are starting points, not final diagnoses. Change one factor at a time and repeat the affected test.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Size for Failures and Growth<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">A fleet that meets normal demand may not have enough capacity when one gateway is unavailable.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Suppose each gateway has a tested operating budget of 5.6Gbps and total demand is 8Gbps:<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Deployment<\/b><\/th>\n<th><b>Normal combined budget<\/b><\/th>\n<th><b>Budget after one gateway fails<\/b><\/th>\n<th><b>Bandwidth-only result<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Two gateways<\/span><\/td>\n<td><span style=\"font-weight: 400;\">11.2Gbps<\/span><\/td>\n<td><span style=\"font-weight: 400;\">5.6Gbps<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Cannot carry the full example demand<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Three gateways<\/span><\/td>\n<td><span style=\"font-weight: 400;\">16.8Gbps<\/span><\/td>\n<td><span style=\"font-weight: 400;\">11.2Gbps<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Has enough remaining bandwidth in this example<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">The second design works only if clients can reach the remaining gateways and the workload distributes as intended. CPU limits, packet rates, authentication services, and network paths still need testing.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A load balancer does not automatically preserve VPN tunnel state or NAT mappings. Clients may need to reconnect, and existing application connections may break. Test the actual recovery process.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Add growth based on measured busy-hour demand and the time needed to deploy more capacity. Set alerts early enough to act before service quality falls.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Choose the Server From a Written Requirement<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Before ordering, prepare a short requirement that includes the protocol, active peers, expected traffic rates, packet mix, and recovery target.<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Requirement<\/b><\/th>\n<th><b>Evidence to request or collect<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">CPU capacity<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Workload-specific results on the proposed CPU<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Sustained network capacity<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Guest or server limit, port policy, and test results<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Memory capacity<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Peak state-table and memory use during a representative run<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Software support<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Required kernel, tunnel access, and offload support<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Transfer costs<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Included traffic, billing method, and excess-use terms<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Service quality<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Latency and loss measurements at the operating target<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Failure capacity<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Recovery test with one gateway unavailable<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">For the wider purchasing checklist, read <\/span><a href=\"https:\/\/atalnetworks.com\/el\/how-to-choose-a-10gbps-dedicated-server\/\"><span style=\"font-weight: 400;\">how to choose a 10Gbps dedicated server<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If you are considering our <\/span><a href=\"https:\/\/atalnetworks.com\/el\/10gbps-server\/\"><span style=\"font-weight: 400;\">10Gbps server options<\/span><\/a><span style=\"font-weight: 400;\">, share your VPN protocol, expected active devices, client regions, and busy-hour upload and download demand. We can use those requirements to discuss a suitable configuration and the tests needed before production use.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">\u03a3\u03c5\u03c7\u03bd\u03ad\u03c2 \u03b5\u03c1\u03c9\u03c4\u03ae\u03c3\u03b5\u03b9\u03c2<\/span><\/h2>\n<h3><span style=\"font-weight: 400;\">How many CPU cores does a 10Gbps VPN server need?<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">There is no universal core count. The requirement depends on the CPU model, VPN implementation, packet sizes, peer count, and network configuration. Test the intended workload and inspect each core. A high total core count does not fix every single-flow or queue limit.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">How many concurrent users can a 10Gbps VPN server support?<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Start with active devices and their busy-hour traffic rates. Divide the tested operating budget by the expected rate per active device for a bandwidth-only estimate. Then test packet rate, connection state, latency, and reconnect behavior. Connected but idle devices are a separate part of the model.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Is WireGuard always faster than OpenVPN?<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">No universal speed ranking applies to every deployment. Compare the exact WireGuard implementation with the intended OpenVPN version and DCO state. Use the same hardware, network path, traffic direction, and workload. Older non-DCO results do not describe every current OpenVPN deployment.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Does AES-NI help WireGuard reach 10Gbps?<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">WireGuard uses ChaCha20-Poly1305 rather than AES for its data encryption. AES-NI support alone is therefore not a WireGuard sizing rule. For an OpenVPN deployment using AES, assess the CPU and software&#8217;s available acceleration through a representative test.\u00a0<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Does OpenVPN DCO guarantee 10Gbps?<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">No. DCO changes where data-channel work runs, but the CPU, NIC, clients, network path, and configuration still set limits. Confirm that DCO is active, then measure the complete gateway workload.\u00a0<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">How much RAM does a 10Gbps VPN server need?<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Port speed does not set a fixed RAM requirement. Measure peer state, firewall connection tracking, packet buffers, monitoring, and any additional services. Leave room for traffic peaks and reconnects, and check for memory pressure during sustained load.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Is a 10Gbps port the same as 10Gbps unmetered bandwidth?<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">No. Port speed describes link capacity. Unmetered describes a billing arrangement, subject to the plan&#8217;s terms. Confirm whether the port is shared or dedicated, what sustained traffic is allowed, and whether the provider applies other limits.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Why is one VPN client slower than the server&#8217;s total benchmark?<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">The client may have a slower CPU, Wi-Fi link, access connection, or network path. A single flow or tunnel may also use processing resources differently from many peers. Test individual-client performance and aggregate server capacity separately.<\/span><\/p>","protected":false},"excerpt":{"rendered":"<p>A VPN server can have a 10Gbps port and still deliver much less than 10Gbps of useful traffic. Encryption, packet [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":25241,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[1],"tags":[],"class_list":["post-25238","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-enterprise-grade-server"],"acf":[],"_links":{"self":[{"href":"https:\/\/atalnetworks.com\/el\/wp-json\/wp\/v2\/posts\/25238","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/atalnetworks.com\/el\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/atalnetworks.com\/el\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/atalnetworks.com\/el\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/atalnetworks.com\/el\/wp-json\/wp\/v2\/comments?post=25238"}],"version-history":[{"count":4,"href":"https:\/\/atalnetworks.com\/el\/wp-json\/wp\/v2\/posts\/25238\/revisions"}],"predecessor-version":[{"id":25244,"href":"https:\/\/atalnetworks.com\/el\/wp-json\/wp\/v2\/posts\/25238\/revisions\/25244"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/atalnetworks.com\/el\/wp-json\/wp\/v2\/media\/25241"}],"wp:attachment":[{"href":"https:\/\/atalnetworks.com\/el\/wp-json\/wp\/v2\/media?parent=25238"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/atalnetworks.com\/el\/wp-json\/wp\/v2\/categories?post=25238"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/atalnetworks.com\/el\/wp-json\/wp\/v2\/tags?post=25238"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}