VPN passthrough Palo Alto

-





R2:

1. Create keyring
crypto ikev2 keyring MYKEYS
 peer R3
  address 203.0.113.1
  pre-shared-key Cisco123

2. Create ikev2 profile 
crypto ikev2 profile IKEV2-PROFILE
 match identity remote address 203.0.113.1 255.255.255.255
 identity local address 203.0.113.3   << without this, peer receives identity 192.168.1.10
 authentication remote pre-share
 authentication local pre-share
 keyring local MYKEYS

3. Create IPSec profile
crypto ipsec profile IPSEC-PROFILE
 set ikev2-profile IKEV2-PROFILE

4. Create tunnel interface
interface Tunnel1
 ip address 172.16.11.1 255.255.255.252
 tunnel source Ethernet0/0
 tunnel mode ipsec ipv4
 tunnel destination 203.0.113.1
 tunnel protection ipsec profile IPSEC-PROFILE


R3:

1. Create keyring
crypto ikev2 keyring MYKEYS
 peer R2
  address 203.0.113.3
  pre-shared-key Cisco123

2. Create ikev2 profile 
crypto ikev2 profile IKEV2-PROFILE
 match identity remote address 203.0.113.3 255.255.255.255
 authentication remote pre-share
 authentication local pre-share
 keyring local MYKEYS

3. Create IPSec profile
crypto ipsec profile IPSEC-PROFILE
 set ikev2-profile IKEV2-PROFILE

4. Create tunnel interface
interface Tunnel1
 ip address 172.16.11.2 255.255.255.252
 tunnel source Ethernet0/0
 tunnel mode ipsec ipv4
 tunnel destination 203.0.113.3
 tunnel protection ipsec profile IPSEC-PROFILE



Palo Alto:




Security Policy
one way is needed to allows tunnel to be established




R2 e0/0 capture





two IKE_SA_INIT packets on UDP/500
two IKE_AUTH packets on UDP 4500


Log




R3 to R2 is denied since no security policy this direction


Add R3 to R2 security policy



Sessions
session on UDP/500 will be timed out after 10 mins, but IKEv2 sa has default lifetime 1 day.
session on UDP/4500 has one hour timeout, if enable DPD on router, it's sent over this port.


note:
at the beginning, VPN didn't come up, IKE_SA_INIT didn't pass through FW for some reason, clear the session resolved the issue.


capture on transmt and receive stages






Comments

Post a Comment

Popular posts from this blog

Firepower FMC and FTD troubleshooting

-
 1. Display real time log on FMC or FTD: pigtail for example: pigtail | grep 192.168.2.20                      pigtail | grep sftunnel 2. Restart communication channel manage_procs.pl run it from  the sensor only, run it from FMC will reset all sensors' channel. This scripts are nice to be used when the FMC and FTD have communication problems like heartbeats are not received, policy deployment is failing or events are not received > expert ************************************************************** NOTICE - Shell access will be deprecated in future releases          and will be replaced with a separate expert mode CLI. ************************************************************** admin@FTD:~$ sudo su Password: root@FTD:/home/admin# manage_procs.pl ****************  Configuration Utility  **************  1   Reconfigure Correlator  2   Reconfigure and flush Correlator  3    Restart Comm. channel  4   Update routes  5   Reset all routes  6   Validate Network  0   Exit *****
Read more

ASA IKEv1 VPN troubleshooting Steps and Tips

-
  1. Phase I proposal mismatch  Run show crypto isakmp sa  Initiator: MM_WAIT_MSG2 Responder: No info  Most likely this is phase1 proposal mismatch, verify IKEv1 policy, other symptoms:   Initiator log: Information Exchange processing failed All configured IKE versions failed to establish the tunnel Initiator debug: Received an un-encrypted NO_PROPOSAL_CHOSEN notify message, dropping Responder log: Error processing payload: Payload ID Responder debug:  All SA proposals found unacceptable 2. IKE version mismatch:  Run  show crypto isakmp sa  no info at both initiator and responder Initiator log: Removing peer from correlator table failed, no match! Reason: User Requested  All configured IKE versions failed to establish the tunnel Initiator debug: Oakley begin quick mode PHASE 1 COMPLETED IKE Initiator sending 1st QM pkt Removing peer from correlator table failed, no match! Session is being torn down. Reason: User Requested Responder log: Tunnel Rejected: Conflicting protocols specified
Read more

Firepower 2100/1100 FTD/ASA initial setup, reimage, upgrade.

-
  Chassis FXOS and FTD share same management IP (default 192.168.45.45) Chassis FXOS (192.168.45.45) and ASA ()use different management IP although on same physical interface. SSH to FXOS/FTD are on FTD CLI prompt, go to FXOS using the  connect fxos  command Console to Chassis is on FXOS CLI prompt, go to FTD using the  connect ftd  command The Firepower 1100 does not support the FXOS Firepower Chassis Manager; only a limited CLI is supported for troubleshooting purposes. The Firepower 2100 runs an underlying operating system called the Firepower eXtensible Operating System (FXOS).  If you run ASA on Firepower 2100, ASA can be in the following modes: Appliance mode (the default after ASA 9.13)—Appliance mode lets you configure all settings in the ASA. Only advanced troubleshooting commands are available from the FXOS CLI. See the  FXOS troubleshooting guide  for more information. Firepower Chassis Manager is not supported . ciscoasa# connect fxos [admin] Connecting to fxos. Connected
Read more