dlnax.blogg.se

Last proposal: 0x0, reserved: 0x0, length: 44

SA Next payload: KE, reserved: 0x0, length: 48 Jul 24 18:20:20 CEST: IKEv2:Next payload: SA, version: 2.0 Exchange type: IKE_SA_INIT, flags: INITIATOR Message id: 0, length: 560 Jul 24 18:20:20 CEST: IKEv2:Received Packet Jul 24 18:20:20 CEST: IKEv2:Incrementing incoming negotiating sa count by one Jul 24 18:20:20 CEST: IKEv2:New ikev2 sa request admitted Jul 24 18:20:20 CEST: IKEv2:Processing an item off the pak queue Jul 24 18:20:20 CEST: IKEv2:Got a packet from dispatcher Jul 24 18:20:19 CEST: IKEv2:Processing an item off the pak queue Jul 24 18:20:19 CEST: IKEv2:Got a packet from dispatcher Jul 24 18:20:15 CEST: IKEv2:Processing an item off the pak queue There's no NAT configured on the device (so ignore the NAT statement from the interface config), and the connection itself isn't traversing any NAT devices.ĭebug crypto ikev2 packet/internal/error/default - this is what I see in the logs (I've removed everything related to the other VPN): Jul 24 18:20:15 CEST: IKEv2:Got a packet from dispatcher Match identity remote address 255.255.255.255Ĭrypto ipsec transform-set vpn-transform esp-aes 256 esp-sha256-hmac Relevant config (where I've changed the information to hide possibly sensitive information, I've added around the value): This VPN already has an IKEv2 VPN configured to an Azure VPN gateway, which is working without issue, but I'm having issues with the VPN from the Check Point and I'm struggling to understand why that is. I'm in the process of setting up a new IKEv2 VPN from a Check Point device, terminating on a 1921 router running 15.4(3)M3.