Source based routing on Checkpoint SPLAT

If you have 2 internet connections, or for whatever reason need to route specific traffic down a specific interface, by default you are stuck – checkpoint do not officially support source based routing on the SPLAT platform.

But it is possible using the underlying system.

To create a route that allows all traffic from 10.0.0.0/24 to route through interface 5 try the following:

We add a new routing table by adding to the file:

echo "100 Defaultroute2" >> /etc/iproute2

This will create a new routing table called Defaultroute2.The default routing tables are numbered 253 & above, so as the number assigned to this table is less than 253, ie: 100, it will be used BEFORE the default routes. Next we set up a new rule for this table:

ip rule add from 10.0.0.0/24 table Defaultroute2

This adds a rule that says any traffic FROM 10.0.0.0/24 will have the routing in the Defaultroute2 routing table applied. Next we set up some new routes:

ip route add default via 192.168.0.1 dev Lan5 table Defaultroute2

This sets a default route that pushes traffic to the gateway address 192.168.0.1 via the device Lan5. This route applies to any traffic going via the Defaultroute2l routing table. We can add more routes to this table, so for instance we could route traffic to other IP addresses via a different gateway:

ip route add 212.111.123.0/24 via 212.104.137.254 dev Lan5 table Defaultroute2
and bingo you have not implemented source based routing.
Dont forget however that this config will need to be applied on each boot, or else create a simple startup script.

CheckPoint R65 ndb_open: database ‘magic number’ corrupted(/opt/CPsuite-R65/fw1/database/fwauth.NDB) error

An irritating error which must be a bug, but only comes around every so often.

Anyway the fix is as follows:

login to the box and ensure you are in expert mode.

then do

cd $FWDIR

cd database

mv fwauth.NDB fwauth.corrupt

thats it!

Reinstall your firewall policy and you should now see it sucessfully install and recreate the fwauth.NDB database.

Google urchin analytics session error unable to call default routine.

I am on version 6.602 and have on occasion tried to log in and received the above error – Session error, unable to call default routine.

It took me some digging to find the cause, and it would seem that for some reason – I havent invested the time to find out why yet – that the table uprofiles_tasks gets so big that it causes problems to the login script and prevents logins.

The answer is to login to the mysql database, and truncate the uprofiles_tasks table.

This then fixes logins for a period of time until the table gets large again, but in my experience this is weeks / months rather than days..