SSL-VPN feature (NetExtender): packets dropped with "Enforced firewall rule" or "Policy drop"

Packets dropped with "Enforced firewall rule" or "Policy drop".

Packet capture shows the following:

Resolution for SonicOS 6.5

This release includes significant user interface changes and many new features that are different from the SonicOS 6.2 and earlier firmware. The below resolution is for customers using SonicOS 6.5 firmware.

Be sure to configure NetExtender as shown in the following guide:

• How Do I Configure The SSL-VPN Feature For Use With NetExtender Or Mobile Connect?

How to Test:

Setup packet capture for a specific service, setting the Destination IP to the WAN IP and internal system IP - all packets should show up as forwarded or consumed.

• If the issue persist please check if the interface where the SSL-VPN traffic is routed is in bridge with another interface.

Below an example:

If the interface is in bridge mode check if is configured an access rule that allow the traffic also from the SSL-VPN Zone to the Zone/Interface that is bridged; SSL-VPN to WLAN in this example.

Here how to configure:

• Go to Manage | Rules | Access Rule
• Select the combination of zones that are involved

Following the previous example  should be allowed the traffic between the SSL-VPN Zone and the WLAN zone, or in general between the SSL-VPN zone and the Zone/Interface Bridged:

The same access rule should be create to allow the traffic from the WLAN Zone to SSL-VPN Zone.

Resolution for SonicOS 6.2 and Below

The below resolution is for customers using SonicOS 6.2 and earlier firmware. For firewalls that are generation 6 and newer we suggest to upgrade to the latest general release of SonicOS 6.5 firmware.

Be sure to configure NetExtender as shown in the following guide:

• How Do I Configure The SSL-VPN Feature For Use With NetExtender Or Mobile Connect?

• Verify Firewall Rules:

• The above drops might occur if there is an existing firewall rule clearing the traffic but no internal system NAT exists to translate the traffic to internal zone subnets. After creating the NAT the traffic will be forwarded properly.

How to Test:

Setup packet capture for a specific service, setting the Destination IP to the WAN IP and internal system IP - all packets should show up as forwarded or consumed.

• If the issue persist please check if the interface where the SSL-VPN traffic is routed is in bridge with another interface.

Below an example:

If the interface is in bridge mode check if is configured an access rule that allow the traffic also from the SSL-VPN Zone to the Zone/Interface that is bridged; SSL-VPN to WLAN in this example.

Here how to configure:

• Go to Firewall | Access Rule
• Click on Matrix
• Select the combination of zones that are involved

Following the previous example  should be allowed the traffic between the SSL-VPN Zone and the WLAN zone, or in general between the SSL-VPN zone and the Zone/Interface Bridged:

The same access rule should be create to allow the traffic from the WLAN Zone to SSL-VPN Zone.