What do you mean by 'it doesn't work for all of my stations'? If you're on a device and it can't get to 172.16.1.x, run traceroute and see where the path fails. Then go to that routing device and make sure a correct route exists.
i pasted the routing info from the CP FW.
i tried pinging even from the cp fw itself (by using ssh) to the 172.16 but nada, i can reach 192.168.25.9
i posted the route i added to the cp fw (it`s in the route table)...
any ideas why the cp fw isn`t accepting it..
maybe i need to do something else after i add the route by using the webui ?
Main Topics
Browse All Topics





by: stsonlinePosted on 2009-09-11 at 09:29:04ID: 25311123
>> if i try from a station to ping 172.16.1.1 i can`t until i add route
>> route add 172.16.1.0 mask 255.255.255.192 192.168.25.9
>> then i can ping it
This is correct - nothing on your LAN knows about the 172.16.1.0 network except your 192.168.25.9 machine. You'll need to make sure that all of your network devices use a gateway that knows how to route to 192.168.25.9. You'll also need to make the route on your CP FW permanent so it always sends traffic destined for the 172.16.1.0 net to 192.168.25.9.
>> i tried to configure the route on the checkpoint either by using the webui and by using the ssh - the
>> route appear but it doesn`t work for all my network stations
What do you mean by 'it doesn't work for all of my stations'? If you're on a device and it can't get to 172.16.1.x, run traceroute and see where the path fails. Then go to that routing device and make sure a correct route exists.