Support Center > Search Results > SecureKnowledge Details
When disabling SecureXL with "fwaccel off" in R80.20 and above, traffic is still being accelerated Technical Level
Symptoms
  • When disabling SecureXL with "fwaccel off" in R80.20 and above, traffic is still being accelerated.

  • Output of the "fwaccel stat" command shows that SecureXL is disabled:

    Example:

    [Expert@FW]# fwaccel stat
    +----------------------------------------------------------------------------------+
    |Id|Name     |Status       |Interfaces              |Features                      |
    +----------------------------------------------------------------------------------+
    |0 |SND      |disabled     |eth4,eth5,eth6,eth7     |Acceleration,Cryptography     |
    |  |         |             |                        |Crypto: Tunnel,UDPEncap,MD5,  |
    |  |         |             |                        |SHA1,NULL,3DES,DES,AES-128,   |
    |  |         |             |                        |AES-256,ESP,LinkSelection,    |
    |  |         |             |                        |DynamicVPN,NatTraversal,      |
    |  |         |             |                        |AES-XCBC,SHA256               |
    +----------------------------------------------------------------------------------+
    
    Accept Templates : disabled by Firewall
                       Layer Network disables template offloads from rule #22
                       Throughput acceleration still enabled.
    Drop Templates   : enabled
    NAT Templates    : disabled by Firewall
                       Layer Network disables template offloads from rule #22
                       Throughput acceleration still enabled.
    
Cause

Starting from R80.20, communication between SecureXL and Firewall-1 is asynchronous.
All connections that were accelerated continue to be handled by SecureXL.


Solution
Note: To view this solution you need to Sign In .