https://community.checkpoint.com/t5/Scripts/Sync-interface-suggested-IP-range-script/m-p/269896#M1434 <P>Hey guys,</P> <P>Wondering if someone would be willing to try this script in their lab to see what they get? I tested it in mine and gave me below. It would simply suggest ranges for sync IPs based on whats already configured.</P> <P>Lab:</P> <P>[Expert@CP-FW-01:0]# dos2unix *<BR />dos2unix: converting file check_critical_files.sh to Unix format ...<BR />dos2unix: converting file cp_cluster_ha_report.sh to Unix format ...<BR />dos2unix: converting file cp_cluster_sanity.sh to Unix format ...<BR />dos2unix: converting file cp_suggest_sync_range.sh to Unix format ...<BR />[Expert@CP-FW-01:0]# chmod 777 *<BR />[Expert@CP-FW-01:0]# ./cp_suggest_sync_range.sh<BR />ClusterXL Sync Range Suggestions (non-overlapping with local interfaces/routes)<BR />======================================================================<BR />Detected used networks (interfaces + routes): 5</P> <P>Top 10 suggestions (/ 30):</P> <P>1. 10.255.255.0/30 MemberA: 10.255.255.1 MemberB: 10.255.255.2<BR />2. 10.255.255.4/30 MemberA: 10.255.255.5 MemberB: 10.255.255.6<BR />3. 10.255.255.8/30 MemberA: 10.255.255.9 MemberB: 10.255.255.10<BR />4. 10.255.255.12/30 MemberA: 10.255.255.13 MemberB: 10.255.255.14<BR />5. 10.255.255.16/30 MemberA: 10.255.255.17 MemberB: 10.255.255.18<BR />6. 10.255.255.20/30 MemberA: 10.255.255.21 MemberB: 10.255.255.22<BR />7. 10.255.255.24/30 MemberA: 10.255.255.25 MemberB: 10.255.255.26<BR />8. 10.255.255.28/30 MemberA: 10.255.255.29 MemberB: 10.255.255.30<BR />9. 10.255.255.32/30 MemberA: 10.255.255.33 MemberB: 10.255.255.34<BR />10. 10.255.255.36/30 MemberA: 10.255.255.37 MemberB: 10.255.255.38</P> <P>Notes:<BR />- Use a DEDICATED, non-routed VLAN/segment for Sync if possible.<BR />- Ensure this subnet does NOT overlap anywhere else in your enterprise (not just on this gateway).<BR />- Prefer /30 for 2-member clusters. Use /29 only if you truly need extra hosts.<BR />[Expert@CP-FW-01:0]#</P> Fri, 06 Feb 2026 14:00:28 GMT the_rock 2026-02-06T14:00:28Z https://community.checkpoint.com/t5/Scripts/Sync-interface-suggested-IP-range-script/m-p/269896#M1434 3 Fri, 06 Feb 2026 14:00:28 GMT https://community.checkpoint.com/t5/Scripts/Sync-interface-suggested-IP-range-script/m-p/269896#M1434 the_rock 2026-02-06T14:00:28Z https://community.checkpoint.com/t5/Scripts/Sync-interface-suggested-IP-range-script/m-p/269903#M1435 <P>That script is probably useful for small networks. However, in large and enterprise environments, it's better to rely on IP address management solutions and potentially their APIs to identify available non-routed networks and free /30 subnets.</P> Fri, 06 Feb 2026 14:02:44 GMT https://community.checkpoint.com/t5/Scripts/Sync-interface-suggested-IP-range-script/m-p/269903#M1435 Vincent_Bacher 2026-02-06T14:02:44Z https://community.checkpoint.com/t5/Scripts/Sync-interface-suggested-IP-range-script/m-p/269904#M1436 <P>100%. I always use 169.254.x.x, so Im trying to see how to modify the script to suggest broader non routable subnets, rather than just what it gave me.</P> Fri, 06 Feb 2026 14:10:07 GMT https://community.checkpoint.com/t5/Scripts/Sync-interface-suggested-IP-range-script/m-p/269904#M1436 the_rock 2026-02-06T14:10:07Z https://community.checkpoint.com/t5/Scripts/Sync-interface-suggested-IP-range-script/m-p/270001#M1454 <P>I've never had an issue with the Scalable Platforms default range of 192.0.2.0/24, so I usually suggest that.</P> Sun, 08 Feb 2026 21:54:08 GMT https://community.checkpoint.com/t5/Scripts/Sync-interface-suggested-IP-range-script/m-p/270001#M1454 emmap 2026-02-08T21:54:08Z https://community.checkpoint.com/t5/Scripts/Sync-interface-suggested-IP-range-script/m-p/270002#M1455 <P>I always suggest non-routable IP range, seems to work best.</P> Sun, 08 Feb 2026 21:56:27 GMT https://community.checkpoint.com/t5/Scripts/Sync-interface-suggested-IP-range-script/m-p/270002#M1455 the_rock 2026-02-08T21:56:27Z