Iam facing an overlaping nw issue while establishing a S2S VPN tunnel .Remote end is Cisco PIX Firewall ; however that is an internal PIX Firewall (with public IP) . The remote perimeter fw is Checkpoint (next hop of PIX)
My end vpn gateway is VPN Concentrator but perimeter fw is Checkpoint fw.One of the interface of my end CP Firewall is VPN Concentrator . My end VPN Conc and CP FW are connected to L2 Switch which connects to Internet router .
There is an issue when i am trying to establish VPN TUNNEL between PIX (remote gateway) and VPN Concentrator (my end).The issue is that the remote end is having the subnet 10.34.226.0/24 and trying to access the subnet 192.168.1.0 at my end ;however 192.168.1.0 is present at their end also. Please let me know as to how can i configure the NATTING at my VPN Concentrator end to translate the addresses , if i want those ppl should come with different destn IP Address to access devices at my end .
The crypto acl in the VPN Conc (my end ) includes 192.168.70.12 (which is a free IP) I want that remote users with IP Range 10.34.226.0/24 should connect to this IP (192.168.70.12) when packet will hit the VPN Conc and should get translated to 192.168.1.31
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...