Just another site

Category Archives: Checkpoint

ISP Redundancy on Checkpoint R75.45 Gaia – does not work

I installed R75.45 Gaia on a UTM-1 270 appliance recently, installation from USB went fine and performance was adequate with a low load, VPN, default IPS and a short QOS rule set.

In order to support a degree of resilience we’re using ISP Redundancy at all sites with multiple internet connections, despite configuring this site identically I was not able to get the failover to work. Usually, the script cp_isp_update runs and updates the gateways default route to match that of the secondary ISP, however when i tested this on R75.45 the route was not updated when primary was disconnected.

I contacted Checkpoint support and was informed that ISP Redundancy does not work in either version of Gaia, R75.45 or R75.40 – however there is a patch available for R75.40 if you contact them and reference this sk. I applied this patch on 75.40 but still didn’t see the solution work as expected so instead deployed R75.30 as I have at other ISP redundant sites.

I should also mention that my in no way scientific, cursory observations indicated that load on the CPU was much lower (15-20pc lower) on SPLAT (with 75.30) than on either version of GAIA. Something to bear in mind for older appliances like the UTM-1 270.


Migrating Security Gateways from Checkpoint R65 to R71.10 on HP/Intel Hardware

Having completed this process several times I thought other people might find the experience useful.

Having built a new smartcenter on R71.10, this is the process i used to migrate R65 gateways to R71.10 with a minimum of hassle. All the gateways run SPLAT on late-model HPDL360 G5’s with intel/hp nics, all hardware IS on the HCL but this doesnt seem to make a blind bit of difference and we’ve had issues with duplex retention and negotiation since moving to R65 on kernel 2.6, R71.10 on 2.6 hasnt fixed this either and I’ve yet to look at R75.

This process reuses the same R65 firewall object in the policy and upgrades it to R71.10, i’ve not had any issues with doing this as new certificates are issued and it reduces the amount of configuration needed. I’m sure it’s still better practice to totally recreate it mind. 

  1. Log onto smartcenter
  2. Reset sic for your device
  3. Change platform to proper security blade license – i use a separate management server so no need for the management products. Don’t be tempted to tick any new feature boxes as they’ll mess with the license if you’ve upgraded it.
  4. Push policy
  5. Install R71.10 on hardware,+ any other products you’ve paid for.
  6. Determine interfaces and label so on paper, there is no rhyme or reason to the names or order it assigns them, totally different from R65 and actually, if you install it twice on the same hardware it’ll still randomise them and they won’t match up. All I do is unplug all of them, plug one in scan in initial install when it’s looking for a management interface, note down it’s interface, label cable, plug another, scan, note down interface ad infinitum. You can also do this from the shell once it’s installed, unplug all the nics and get it to flash lights from each port but seems like more aggro than it’s worth, besides you need to id them before you can even get into the shell.
  7. Step through the install, giving the device it its own internal mgt/lan address as default gateway (remove this from webgui later)
  8. Reboot
  9. Log on through web browser, define interfaces according to step 6.
  10. Define routes, deleting default internal route and creating external default route
  11. Use google or provider dns (google is, EXTERNAL NTP for setting time, here i use as my primary and set to sync every 60 seconds, Leave the rest on default pretty much,
  12. Allow it to build
  13. Reboot again
  14. Log back onto SmartCentre
  15. Establish SIC
  16. Go to topology,  Get interfaces (Don’t get interfaces with topology it’ll create a bunch of new objects which will break your existing fw object in the policy).
  17. Check interfaces look right and match up with step 6 and 9 and make sure internal/external/networks behind is set correctly
  18. Push policy – you should be online. Now comes all the stupid hoop jumping getting the duplex to work both initially and after a reboot on HP/intel nics and others i suspect. oh, btw, thanks for fixing this Checkpoint, it’s only been a much reported issue for three years with half the hardware on the HCL. Essentially, if you set the duplex from expert mode, it will be forgotten on restart, and dont even think about setting it in the gui – the gui duplex switches are about as much use as a chocolate fireguard.
  19. Log onto fw through ssh or console
  20. Enter expert mode
  21. Run mii-tool and review interface list, if duplex look good, try to change them to manually set and see if you get reconnected (obviously give them 60 seconds to re-establish), if not leave them on auto. It seems that still with this new version of the splat if you manually define it sometimes the other side will not accept despite defaulting to 100/full or 10/full when on auto….. nice. Either way this is the most important thing to get right in the process as it will much up performance for everything if you have any interfaces flapping around on half on one side.
  22. To manually set a duplex from expert shell: Ethtool –s eth1 (or whatever) speed 100 duplex full autoneg off
  23. To reset an interface back to auto: ethtool –s eth1 (or whatever) autoneg on
  24. To review interfaces status: mii-tool
  25. To review an interface for collisions after changing: Ethtool –S eth1 (or whatever)
  26. To make the duplex persistent across reboots you need to enter the correct commands in /etc/rc.d/rc.local, see below for my rc.local. to get here from expert shell type: cd /etc/rc.c, then vi rc.local, if you haven’t used vi before look at:

Test the manual duplex setting with a reboot and then go back in and look at mii-tool, i don’t use the web interface for this purpose as the web interface tells LIES it has no idea what the duplex/speed settings actually are and when you change the settings it’s like the buttons on one of those kiddies helicopter rides at the supermarket, you can press them all day and it won’t make a damn bit of difference, nothing happens.

License the fw from the user centre: 

  1. Use software blades (R70 and above)
  2. Download and install from smart update
  3. As soon as you install the license you’ll probably lose connectivity, this is because a big red light just came on on someones desk in Tel Aviv notifying Checkpoint that you were using more cores/features than you have paid for, the only way to restore connectivity is a reboot so the Kernel can slam the door on all that processing power we don’t get for only 35000usd per year (excluding hardware).

Et Voila! Brand new shiny R71.10 firewall, inspection throughput  is massively improved in my situation, we will only notice this on the UTM 270 in a branch office, as despite being only 12 months old it’s beating heart is a 600mhz Celeron from ten years ago, still cost 4500usd though. As the other sites are on xeons and openservers we’re not even getting close to the performance ceiling if a single core (200mbps real world with sensible scanning and sd according to

Freesco router for VMware

If you aren’t already using FREESCO in your sandbox it’s a tremendous application and allows you to stage  multisite application implementations and upgrades easily in fairly conservative virtual environments.

This link details setting the application up to work properly in vmware. Alternately just go here and download a working OVF:

It’s really useful for firewall labs and topology changes etc. The VM itself uses practically no resources (its perfectly happy with 12-16mb), is hugely robust and has a mind-boggling array of features. Combined with the VMWare Workstations bandwidth limitation for the virtual networks possible to look at how applications perform over varying quality connections to other sites.

Other FREESCO links:

Home Pages:

Download page: