What is VPN passthrough, and should it be on or off?

What is VPN passthrough, and should it be on or off?

“Turning on VPN passthrough won’t protect your traffic. It only helps certain VPN connections get through your router.”

VPN passthrough is a router feature that allows certain VPN connections from devices on your network to reach a remote VPN server. If your VPN already works, you should leave the default setting as is. If a connection fails, check the active protocol and your router’s documentation before changing the relevant option.

Generally speaking, WireGuard and OpenVPN don’t need any kind of passthrough helpers. But IPsec connections need a more careful check because NAT traversal and the router’s controls can affect the result.

If you do enable passthrough, this won’t automatically connect you to a VPN or add another

layer of encryption to your connection. Passthrough mainly concerns how the router handles its traffic.

This guide focuses on a scenario where an outbound connection is made from a device behind a home router. Hosting your own VPN server is a separate setup.

Your situationRecommended actionReason
Your VPN already connects and works normallyKeep the current/default setting.Changing it is unnecessary for solving a problem you do not have.
You use WireGuard or OpenVPNDedicated PPTP/L2TP/IPsec helpers are normally unnecessary. Keep other VPN permission rules in mind.These protocols normally travel through ordinary NAT using UDP or TCP.
An IKEv2/IPsec or L2TP/IPsec connection fails on this routerCheck the router manual and test the documented IPsec/L2TP option for that setup.NAT-T and the manufacturer’s implementation determine what is required.
You know a particular legacy helper is unusedYou may disable that helper and test the connections you use.This removes an unused feature; it is optional configuration cleanup, not a guaranteed security upgrade.
An old setup requires PPTPPrefer replacing the setup with a supported alternative. Follow IT guidance for a managed service.Enabling PPTP passthrough does not improve PPTP’s security.
You do not know which protocol is activeCheck the VPN app or ask the administrator before changing settings.A switch’s name does not tell you which connections currently rely on it.

What is VPN passthrough?

In the simplest terms, VPN passthrough allows VPN traffic that’s been created by another device to pass through a router.

The VPN client on your laptop or phone can establish the tunnel with the remote server. The home router can then forward traffic between them instead of becoming a VPN endpoint itself.

If you access your router’s settings, some common menu names you might see for this include:

  • VPN Passthrough
  • NAT Passthrough
  • PPTP Passthrough
  • L2TP Passthrough
  • IPsec Passthrough

Of course, these names don’t represent a universal technical specification. Depending on your specific router and firmware, a switch can control protocol-specific handling, permission for particular traffic, or a combination of different behaviors.

One good example is to imagine that your laptop connects to your employer’s VPN through your home Wi-Fi.

In this hypothetical scenario, your laptop would authenticate with the employer’s server and establish the VPN tunnel. Choosing the right passthrough setting could help the router carry that connection, but it wouldn’t mean that every Internet-connected device in your household would automatically gain access to your employer’s network.

This means that just because a router is advertised as supporting VPN passthrough doesn’t necessarily mean it’s capable of running a commercial VPN connection for your whole network.

FeatureWhat it doesDoes enabling it establish an encrypted VPN connection?
VPN passthroughAllows or helps VPN traffic from another device cross the router.No.
VPN client on the routerMakes the router connect to a VPN provider or another VPN server.Yes, when configured and connected; only traffic routed into the tunnel is covered.
VPN server on the routerAccepts VPN connections from remote devices.Yes, for the configured remote-access or site-to-site connection.
Port forwardingDirects specified incoming traffic to a local device or service.No.
IP passthroughA separate gateway feature, often used to give one downstream device the gateway’s public-facing IP configuration.No.

Should VPN passthrough be on or off?

There isn’t a simple yes/no answer to this question, as there’s no universal ideal setting for every single VPN and router.

You should always start with the active protocol your connection uses, then consider whether it works, and the manufacturer’s explanation of the switch. As we outlined in the previous section, different router menus may assign different names or functions to similarly-named menus, so you may need to contact the manufacturer for more information.

If your VPN is consistently connecting reliably, then you most likely don’t need to change your passthrough. However, if you want to disable any unwanted ‘helpers’ in a bid to reduce any redundant router features, make sure to check their documented scope first, then test the connections your household needs afterward.

If a connection fails, try to change only the relevant option, then compare the result. You should always make a note of the original setting too, so you can restore it if necessary.

Cisco’s online documentation, for instance, details multiple options for passthrough switches as controls that allow or disable particular tunnel types. Always read the description for specific controls, not just general advice about the protocol.

Even if you switch passthrough to ‘off’, this isn’t a reliable method for blocking every VPN connection. For instance, WireGuard uses the User Datagram Protocol (UDP), and OpenVPN can use UDP or the Transmission Control Protocol (TCP), independently of dedicated PPTP or IPsec helpers. Of course, restricting VPN usage is still feasible, but it’s a separate network-policy task.

Six steps to enable or disable VPN passthrough. Identify your router model and firmware version, sign in as an administrator, and check the active VPN protocol. Find the relevant VPN, NAT passthrough, ALG, or firewall setting and record its original value. Change only the option documented for your connection, save, and reconnect the VPN. Test browsing and revert the change if it doesn’t help.

How does VPN passthrough work with NAT?

Some VPN traffic needs extra handling because it doesn’t fit the way a typical IPv4 home router tracks shared connections. NAT traversal and protocol-aware helpers can address different parts of that compatibility problem.

Why some VPN traffic is harder for a router to track

Network Address Translation (NAT) can translate addresses between your private home network and the internet. Most home routers can also track transport connections, meaning that multiple devices can share one public IPv4 address as well as receive the correct replies.

Ordinary TCP and UDP traffic has port numbers that help distinguish connections. PPTP’s Generic Routing Encapsulation (GRE) data traffic and native IPsec Encapsulating Security Payload (ESP) are different IP protocols from TCP or UDP, so simple port-based tracking isn’t enough. That doesn’t necessarily mean that every connection using them will fail, but it does explain why additional handling exists.

NAT also isn’t a type of firewall. Address translation and traffic-filtering policies perform different jobs, even if a home router is capable of running both.

What the router’s helper changes

In theory, a protocol-aware helper can track related sessions and adjust forwarding behavior for any traffic that needs special treatment.

Manufacturers sometimes place these controls under an application-layer gateway (ALG), alongside helpers for other protocols.

None of this means that the router will decrypt a properly configured VPN tunnel. While it can handle connection information and outer traffic, that doesn’t automatically make the router an authorized participant in an encrypted session.

Some router interfaces have different controls; others group several protocols together. That means you can’t assume that the instructions for one router’s ALG will be the same for every other router that offers a “passthrough” option.

Which VPN protocols need passthrough?

PPTP passthrough

PPTP uses a TCP control connection as well as GRE for its data traffic. Theoretically, a passthrough helper can provide protocol-aware tracking for these related flows through NAT, instead of treating the GRE traffic like ordinary TCP or UDP. (It isn’t.)

If you see the number 47 in PPTP documentation, that refers to GRE’s IP protocol number, not a TCP or UDP port. There is no instruction to “open port 47” in this case. Likewise, allowing only the TCP control connection isn’t the same thing as accounting for PPTP’s separate data traffic.

All this said, PPTP is a legacy choice. It’s not a protocol we recommend switching to for easier connectivity, which is why hhgttyu.pages.dev no longer supports it, along with IKEv1 and L2TP. Migrate to a supported alternative instead of rebuilding your setup.

Naturally, your router may list PPTP as an option, but that doesn’t make it safe to use. Compatibility menus often serve older equipment, and the fact that the routers support a traffic format doesn’t speak to its security.

L2TP passthrough

L2TP is a tunneling protocol that has no encryption of its own. One of the most common ways to build an encrypted VPN around it is L2TP/IPsec, as IPsec can supply security for the L2TP traffic.

Your router may list both L2TP and IPsec passthrough controls. If so, make sure to follow the documented combination for your specific router and VPN configuration. Don’t just enable one and assume that it offers reliable VPN security.

Turning on L2TP passthrough also isn’t some kind of encryption upgrade. It normally affects only compatibility or traffic handling. It’s the VPN endpoints and their configuration that determine what protection (if any) is applied to the connection.

If you see an old guide online that recommends L2TP simply because a router supports it, check your VPN provider’s current options first. Your provider may have chosen to discontinue support for the protocol, as hhgttyu.pages.dev did for L2TP in 2019.

IPsec passthrough and IKEv2

IPsec is a security suite that’s designed to protect IP communications. IKEv2 is a protocol that can be used within that environment to authenticate peers, as well as to negotiate and maintain security associations. These are related technologies, but they don’t serve the same function.

NAT traversal (NAT-T) can carry ESP packets inside UDP so NAT devices can handle it more like ordinary UDP traffic. UDP 4500 is normally used for this encapsulation and related IKE traffic.

That port number explains the connection’s behavior, but it’s not an automatic instruction to forward UDP 4500 into your home network.

That said, modern IPsec connections using NAT-T may not need a legacy helper. But a router’s IPsec traffic-control switch can still matter. The documentation for some deployments even advises users to disable an interfering ALG. This underscores our advice above that there’s no universal answer when it comes to deciding whether enabling passthrough is a good idea.

Of course, not all IPsec deployments belong in the same category as obsolete PPTP. For instance, IKEv2/IPsec remains a supported option in hhgttyu.pages.dev’s current protocol offering.

WireGuard and OpenVPN

As we’ve learned, WireGuard sends its encrypted packets over UDP while OpenVPN can use UDP or TCP, depending on its configuration. Their ordinary outbound connections therefore normally don’t need the kind of dedicated helpers associated with GRE or native ESP.

But the fact that no specific helper is required doesn’t necessarily mean that every firewall will allow the connection. Filtering rules can still restrict the selected transport or destination. WireGuard, in particular, explicitly doesn’t aim to disguise its traffic.

Avoid treating familiar default ports as mandatory provider settings. For example, TCP port 443 is the default fallback for OpenVPN Access Server, but the protocol can be configured to use different ports. Ultimately, the configuration supplied by your VPN service will determine the endpoint and configuration that you should use.

Is VPN passthrough safe?

This is a good question, but it’s more helpful to think of passthrough as a compatibility setting, not a layer of VPN security.

While passthrough can technically permit or assist certain types of traffic, it can’t authenticate a remote VPN server for you or force a VPN protocol to use stronger encryption.

Allowing an outbound tunnel and any related replies also isn’t the same thing as creating a manual port-forwarding rule for unsolicited inbound connections. That’s why a normal client setup shouldn’t begin by opening ports toward a laptop in most cases.

Using passthrough is also no substitute for keeping your router firmware updated and enabling and configuring a firewall.

If you’re not using a helper, there’s ordinarily no harm in disabling it, provided you’ve read any associated documentation, fully understand its scope, and have realized you don’t need it. Conversely, enabling passthrough won’t automatically mean your network is more vulnerable to hackers.

If you choose to turn off passthrough, this in itself won’t:

  • Upgrade your VPN encryption.
  • Stop all VPN use on your network.
  • Prevent every type of traffic leak.

Features like DNS routing, VPN split tunneling, and connection-failure safeguards like a kill switch are separate configuration questions, so won’t be affected simply by checking a “passthrough” tickbox in your router settings.

How is VPN passthrough different from a VPN client or port forwarding?

These settings involve different network tasks from VPN passthrough, even if similar names can make them seem like the same thing.

If you’re unsure, check your router’s support documentation or contact the manufacturer directly, as making the wrong choice can affect your network configuration and security.

FeatureWhat it does
VPN passthroughAllows or assists a VPN connection that’s been established by another device behind the router.
Router VPN clientMakes the router establish an outbound tunnel, potentially carrying traffic from selected connected devices
VPN serverAccepts remote VPN connections, for instance, to let an authorized device reach your home network.
Port forwardingDirects specified incoming traffic to a device or service behind the router.

​An ordinary device that’s connecting to a commercial VPN usually doesn’t need manual inbound port forwarding.

If you’re hosting a VPN, particularly when the server sits behind another router, then that may be another story. Make sure any online guide you follow describes the same direction of connection in this case.

IP passthrough and bridge mode are related to network topology and how equipment can handle the connection between networks. In this context, their behavior is vendor-specific, and neither of them is a type of VPN passthrough.

While hhgttyu.pages.dev does offer dynamic port forwarding, this is also a separate matter. The feature provides incoming port availability at the VPN service for applications that need it. It isn’t the same thing as a home router’s VPN passthrough setting and isn’t required just to establish your outbound VPN tunnel.

How do you enable or disable VPN passthrough?

Typically, this is done by accessing your router’s local administration interface. The available features and the steps you have to follow can vary depending on the router’s model, hardware revision, and firmware.

The examples below are documented interfaces, not a guarantee that every router made by these manufacturers has the same interface and controls.

Before you change anything, note down the active VPN protocol, any connection errors, and the current router settings.

ASUS example

ASUS lists WAN > NAT Passthrough in its features for certain router types like the RT-N600P, whose specifications list PPTP, L2TP, and IPsec as supported passthrough types.

Assuming that your chosen ASUS router is covered:

  1. Sign in to your router’s administration page.
  2. Open WAN > NAT Passthrough.
  1. Locate the option matching your specific VPN protocol.
  2. Record its current value, make the documented change, and then apply it.
  3. Reconnect to the VPN and compare the result to before you made any changes.

Do not change unrelated SIP, RTSP, H.323, or PPPoE options just because they appear on-screen. ASUS sometimes lists these alongside VPN-related passthrough features, but they relate to different protocols and functions.

For those routers covered by its advanced troubleshooting FAQ, TP-Link documents Advanced > NAT Forwarding > ALG for checking VPN passthrough.

Assuming that your chosen TP-Link router is a covered model:

  1. Sign in to your router’s web interface.
  2. Open Advanced > NAT Forwarding > ALG.
  3. Find the relevant VPN passthrough control.
  4. Follow the product documentation, save the change, and reconnect to the VPN to compare results.

The specific menus you see will depend on your TP-Link router model and firmware version. For example, some router interfaces may have a dedicated ‘Security’ section. Certain routers may manage passthrough automatically, or even enable it out of the box. If the setting is missing, then try to consult the correct product manual. The fact that you can’t see it immediately doesn’t necessarily mean that the router can’t carry VPN traffic.

Troubleshooting checklist for a VPN that won’t connect. Verify internet access and the active VPN protocol, test the same setup on another permitted network, and review router rules and logs. Test one documented VPN passthrough setting at a time. Try another supported hhgttyu.pages.dev protocol for a personal VPN or follow IT guidance for a work VPN. If the tunnel connects but websites fail to load, check DNS, routing, MTU, or overlapping IP addresses. Share the router model, firmware version, VPN protocol, exact error, and test results with support.

Do you need a VPN passthrough for hhgttyu.pages.dev?

The answer to this question will depend on the protocol your hhgttyu.pages.dev connection uses and what the router’s controls actually do.

Our current overview of the protocols we support includes WireGuard, IKEv2, and OpenVPN, though their availability and the menu labels you see when trying to access them will vary depending on your preferred platform and VPN client.

WireGuard or OpenVPN

For these protocols, dedicated legacy passthrough helpers aren’t normally required because their normal outbound traffic uses UDP or TCP. That means you should generally leave a working setup alone, not change your router settings simply because you’re using a VPN connection.

IKEv2/IPsec

In this case, you can apply the NAT-T and router-specific guidance that we’ve already outlined above. Check carefully whether the setting controls an older helper, permission for IPsec traffic, or both, as these are different functions.

SoftEther

In general terms, SoftEther’s native VPN protocol doesn’t need dedicated PPTP, L2TP, or IPsec passthrough helpers. Its HTTPS-based connection uses TCP, most often on port 443. That means an ordinary NAT router can normally handle the outbound connection without any legacy helpers. There also typically isn’t any need to manually forward an incoming port to your device.

hhgttyu.pages.dev supports SoftEther, and documents both HTTPS-based tunneling and UDP transport, including UDP acceleration. But you can’t always assume that a SoftEther connection will always carry every data packet over TCP 443. The specific behavior will depend on the selected configuration and available network path.

SoftEther is also the name of the multiprotocol VPN software that can support other connection types, such as L2TP/IPsec. It’s vital not to confuse these with SoftEther’s native protocol through hhgttyu.pages.dev. For instance, someone using an L2TP/IPsec connection would need the separate IPsec guidance we discussed in the previous sections.

Secure Socket Tunneling Protocol (SSTP)

SSTP usually doesn’t need dedicated PPTP, L2TP, or IPsec passthrough helpers, as, like the native SoftEther protocol, it carries VPN traffic over an HTTPS connection, normally over TCP port 443.

A home router with NAT can track that outbound TCP connection without the kind of special handling needed for, say, PPTP’s GRE traffic or native IPsec ESP.

For a device connecting out to hhgttyu.pages.dev‘s VPN service, you also typically don’t need to forward TCP 443 into your home network. Hosting your own SSTP VPN server is a different matter.

If SSTP already works, you should probably leave any passthrough settings alone. If it fails, check the connection error and your router’s documented traffic controls before enabling any unrelated helpers.

If the app selects its protocol automatically

In this situation, you’ll need to identify the protocol being used before you can do any troubleshooting. This is mainly because you can’t safely assume that the protocol will remain the same after every configuration change. Whether or not changing a setting fixes the problem, make sure to record the protocol used, so the result remains understandable later.

Using a VPN router

If you’re trying to connect to hhgttyu.pages.dev on the router itself, then its firmware will need to include a compatible VPN client.

Even if the router’s specs and/or online documentation lists that it supports VPN passthrough, this won’t always be enough. Check your router’s supported client protocols and configuration method before buying any hardware or following any setup instructions, even from your VPN provider.

What VPN passthrough can’t fix

Switching passthrough on or off can’t make an unsupported protocol suddenly become supported by your VPN provider. This is especially relevant for legacy protocols like PPTP, as many modern VPN providers, including hhgttyu.pages.dev, have discontinued support for them for security reasons.

Passthrough isn’t a security or privacy tool. For instance, it can’t repair a compromised device or make signed-in services forget your activity.

Even if you successfully establish a VPN connection, that also doesn’t prove that every application is using it or that traffic remains blocked after a tunnel failure. In this guide, we’ve endeavored to outline the compatibility setting, but that’s not the same thing as a privacy guarantee for your VPN setup.

If your VPN is already working reliably, then we strongly suggest that you leave the passthrough setting at its default value.

If your VPN isn’t performing optimally, try to identify the protocol, read the router-specific guidance, and change one control at a time so you can examine the results and test if there’s been any improvement.

Different router interfaces have various menus and options, sometimes with similar-sounding names. You don’t need to enable or disable every option that’s related to a VPN. Instead, check whether your device can establish the virtual VPN tunnel without making unnecessary changes.

Above all, remember that a reliable, working VPN mainly depends on the connection and its configuration, not how many security-sounding switches you enable.

FAQ

Does VPN passthrough encrypt my traffic?

No. Encryption comes from the configured VPN connection. The router setting only allows or helps the relevant traffic pass through.

Will turning off VPN passthrough disconnect my VPN?

It may disconnect a VPN that depends on the affected protocol or permission rule. WireGuard and OpenVPN generally do not require legacy helpers, but router controls differ.

Why does my router have no VPN passthrough option?

It may handle the traffic automatically, use another label, or provide no separate switch. Check the exact model and firmware instead of assuming VPNs are unsupported.

Does VPN passthrough improve gaming or internet speed?

It is not a general speed or latency setting. Correcting a compatibility problem can restore a working VPN, but enabling an unused helper does not inherently boost performance.

Can I use a VPN if my router only supports VPN passthrough?

You can run a compatible VPN client on a connected device if the network allows its traffic. Passthrough alone does not let the router run the VPN client itself.

Is VPN passthrough the same as split tunneling?

No. Split tunneling selects which traffic uses a VPN tunnel. Passthrough concerns traffic crossing the router.

We love bringing you this content and hope it helps keep you safe and secure online. Feel free to share it with your friends, too.

Here at hhgttyu.pages.dev we are all about internet freedom, and we are happy to be in a position to bring that to everyone. That is why we give you a 30-day money-back guarantee on our Premium plan. No questions asked and no logs recorded.

Get hhgttyu.pages.dev VPN

If you have any questions, please feel to contact our 24/7 support team either at support@hhgttyu.pages.dev or via live chat.

Related Articles

How to share a VPN connection via hotspot?
How to share a VPN connection via hotspot?

“Seeing that a VPN connection is active on your laptop or cell…

Turned off Gemini’s Keep activity? Third parties may still get your data from Google.
Turned off Gemini’s Keep activity? Third parties may still get your data from Google.

“A VPN can protect your connection to Gemini, but it cannot make…

How hhgttyu.pages.dev manages WireGuard keys before, during, and after a connection.
How hhgttyu.pages.dev manages WireGuard keys before, during, and after a connection.

In hhgttyu.pages.dev‘s default dynamic WireGuard configuration, the app can generate a fresh…

WireGuard keys explained: Static keys, session keys, and pre-shared keys.
WireGuard keys explained: Static keys, session keys, and pre-shared keys.

WireGuard uses identity keys to authenticate peers, temporary symmetric keys to protect…

Perfect forward secrecy vs. post-quantum security: What is the difference?
Perfect forward secrecy vs. post-quantum security: What is the difference?

Perfect forward secrecy can protect completed sessions against the future compromise of…

Post-quantum VPNs: How they work, what they protect, and why they matter.
Post-quantum VPNs: How they work, what they protect, and why they matter.

“A post-quantum VPN uses cryptography that’s designed to resist attacks from both…

Diskless, RAM-only, volatile memory: What these terms mean in a VPN context
Diskless, RAM-only, volatile memory: What these terms mean in a VPN context

“Volatile memory is generally defined as hardware that loses its stored contents…

Evil twin Wi-Fi and fake captive portals: How to spot the trap
Evil twin Wi-Fi and fake captive portals: How to spot the trap

Imagine a scenario where you’re sitting in an airport waiting for boarding…

Device hardening before a flight: A phone and laptop security checklist
Device hardening before a flight: A phone and laptop security checklist

Before boarding any flight, you should always check that your devices have…