FW Acceleration on Smart1-Cloud SMS

[Nikolaos_Liakop]

Hello there,

I would like to disable FW acceleration on a Cluster of Checkpoint Devices (R80.30) that are managed by Smart1-Cloud.

I have read that disabling the FW acceleration is not an option from >R80.20.

Then I moved on how we can whitelist traffic between our VOICE VLANS so that acceleration is does not take place. The file that needs to be edited is table.def which resides on Smart1-Cloud.

How can we edit the table.def on Smart1-Cloud SMS ?

Regards

[Timothy_Hall]

The instructions to edit table.def and add the f2f_addresses directive: sk104468: How to disable SecureXL for specific IP addresses

Normally you disable SecureXL for all connections to/from a set of IP addresses, but it is possible to disable it for specific connections as well.

[Nikolaos_Liakop]

Hello Timothy.

I am very well aware of the SK that you sent us. Also I am aware of the following Location of 'table.def' files on Security Management Server.

However my SMS is cloud based. That's the issue...

Thank you.

[PhoneBoy]

Open a TAC case, they can make the necessary changes for you.

[Fadi_Moussa]

hi @Nikolaos_Liakop ,

can you please ellaborate on why would you like to disable SXL? can you please mention the reasons for doing so? 

Thanks,

Fadi 

[Nikolaos_Liakop]

The reason that I would like to either disable the Acceleration or either whitelist the below mentioned traffic is the following.

We have panasonic VoIP devices that reside on a VOICE VLAN and they communicate periodically, with the PBX which resides on another VLAN. With FW acceleration enabled which is the default setting, the phones every now and then restart. With FW acceleration disabled, the phones behave normally ie no restart occurs.

So , ideally I would like to whitelist the traffic, but i am not able to do so due to the fact that my SMS is cloud based. Therefore, I reside on completely disabling the FW acceleration.

[G_W_Albrecht]

Did you have a TAC case open for the VoIP issue yet ? I would rather get that resolved so it works with SecureXL as it does for other customers!

[PhoneBoy]

If disabling SecureXL solves a problem, then open a TAC case.
Which you need to do anyway to implement the .def changes 🙂