| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| on secure platform, does ip fprwarding need to be enabled to allow full outbound access for the internal network? Do i need to echo "1" > /proc/sys/net/ipv4/ip_forward to get a InternalNet to Any rule to work? Thanks. |
| |||
| When you enable Check Point it should enable IP forwarding automatically. You shouldn't have to do anything for that. If you are having a problem using the 'InternalNet' object, try creating a network object for your Internal Network. Also make sure that it's Natting to a public IP address. |
| |||
| is natting it to the external interface of the FW required? I did not have to do that on NG SP3 running on NT4.0. All i had to do was enable ip forwarding on the tcp stack within NT. |
| |||
| apparently, my problem was not with IP forwarding...i feel like a tool. It was becasue my internal client (192.168.1.195) was NAT'd to a real external IP address. That should be ok, except my other check point box (the one im upgrading) was still intercepting the ARP's from the new Checkpoint box and was bombing out. Doh. |
![]() |
| Thread Tools | |
| Display Modes | |
| |