So I appreciate this is an edge case, but is a feature of Gaia is hampered by standard configuration in R80.20.
I have a SIT tunnel in partnerships with HE tunnel provider, for a routed IPv6 subnet. As with R80.20 you cannot permenantly disable SecureXL, yet SecureXL does not work with a SIT tunnel configured on the device.
I have to manually disable SecureXL for IPv6 each time the system reboots.
I wanted to know if this is something other people have had an issue with and if Check Point are aware of issues with SIT tunnels + SecureXL in R80.20. I've traditionally always had to disable SecureXL to get this to work.
I've tried adding a crontab that disables SecureXL at reboot "@reboot /opt/CPsuite-R80.20/fw1/bin/fwaccel6 off > /dev/null 2>&1" but this doesn't seem to work.
Afaik SecureXL can be permanently disabled through the CPconfig utility. See sk41397 How to enable/disable Check Point SecureXL via CLI.
Can't be permenantly disabled on R80.20 sadly no option in cpconfig.
I shall give that a try, thank you!
So I gave that a try. It seemed to break a lot of things..
It looked like it didn't load the driver at all, and I can only guess that R80.20 relies on it moreso than before - no network traffic passing through the box. Had to revert back for the moment - good shout though.
I'd thought as much, making these sorts of changes - It's not for a critical environment so I'm happy to do things like this, as remembering to flip SXL off each time at boot is more of a pain.
More of a moan towards CP for having conflicting features!
Oh my lord - this is available in a much, much easier way !
Yep that's what I've done!
Seems to work, SXL flipped back on again a while afters but I think it's unrelated.. I swear the cron scheduler never used to provide the option of "At startup" although @reboot has been around since - forever..
Yes, i just did remember in the back of my mind something similar, had a look there and - emacs !
So you could mark mine as the correct answer !
Wow, I somewhat randomly came across this thread when searching to see if there was any way to allow SecureXL to run, but not actually do anything as I would like to have the monitoring visibility of SNMP and Netflow but without the random network communication breakage that seems to resul with it on when using NAT and routed vpnt to vpnt traffic (ie. a WAN tier transport devices and even my client "VPN hub" tier devices). It's an unpleasant surprise to find that the option to turn of secureXL is gone in R80.20 and up versions, but obviously much better than finding out as a surprise after upgrading to R80.20. Did you end up getting a satisfactory solution to this or am I staying on R80.10 for a number of my devices, also bad?
Any details as to how you resolved is appreciated, as well as how stable the solution appears to be.
SecureXL has been significantly revised in R80.20. It now works in user space. This has also led to some changes in "fw monitor", The SecureXL driver takes a certain amount of kernel memory per core and that was adding up to more kernel memory than Intel/Linux was allowing.