Persistent routes in Secure Platform Persistent routes in Secure Platform Both of these utilities write the routes to a file /etc/sysconfig/cpnetstart ... the o/s also supports the route command and normally in linux these would be added to a static-route file that would be persistent through a reboot. Checkpoint however keeps all the routes in the cpnetstart file if you do not add the routes through the 2 recommended methods you will see the routes in the tables however upon first reboot they will be gone. For bulk route adds consider either 2 methods... you can add the routes directly to the cpnetstart file however you will need to follow the syntax in the file... (Linux and Solaris users see script below) or you can use the normal route command and add it to the route table in memory then run the sysconfig utility and add one last route using it. The sysconfig utility reads all the routes from memory and writes them to the file when doing it in this fashion and will properly format the file for you. Routes in memory can also be written to the cpnetstart file by running route --save in NG AI R55. conv_routes2splat.sh: Convert linux/solaris routes to cpnetstart format FAQForm FAQs.Class: FAQs.OS: OsSecurePlatform FAQs.Version: |