We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda NextGen Firewall X

VPN tunnel is established but traffic is not forwarded

  • Type: Knowledgebase
  • Date changed: 6 months ago

Solution #00005073

 

Scope:
This solution replies to:
- NG Firewall firmware versions 4.2.x, 5.0.x, 5.2.x
- netfence firmware versions 4.2.x

 
Symptoms:

Any type of VPN tunnel can successfully be established but no traffic is forwarded into or out of the tunnel.


 

Solution:

There are three common reasons for this problem:

 

1. No firewall service is defined on the NG Firewall gateway that hosts the "VPN service". VPN tunnels are terminated before the firewall service. If no firewall service is running on the system, traffic arriving on the netfence gateway cannot be forwarded into the network.

 

2. A firewall service is running but no rule allowing traffic out of or into the VPN tunnel is configured in the firewall rule set.

 

3. The rule allowing traffic into the VPN traffic uses the connection type ProxyDyn. This prevents the traffic from being routed into the VPN tunnel correctly.

Introduce a firewall service on the netfence gateway that is hosting the "VPN service". Make sure to define a firewall rule that allows VPN traffic. Do not use "ProxyDyn" as connection type - use "Client" instead.

 

 

Link to This Page:
https://campus.barracuda.com/solution/50160000000IKXqAAO