Skip to main content

FlexVPN - troubleshooting

I would like to share with you very useful commands which can helpful you during your troubleshooting. Instead of checking (sometimes very long) configuration, you can check/compare the same block of configuration between your peers.

1) ikev2 proposal
 
r5#sh crypto ikev2 proposal
 IKEv2 proposal: IKEV2-PROPOSAL
     Encryption : AES-CBC-128
     Integrity  : SHA512
     PRF        : SHA512
     DH Group   : DH_GROUP_1536_MODP/Group 5
 IKEv2 proposal: default
     Encryption : AES-CBC-256 AES-CBC-192 AES-CBC-128
     Integrity  : SHA512 SHA384 SHA256 SHA96 MD596
     PRF        : SHA512 SHA384 SHA256 SHA1 MD5
     DH Group   : DH_GROUP_1536_MODP/Group 5 DH_GROUP_1024_MODP/Group 2
r5#

From above output you can learn about all available ikev2 proposals. As you see there is one proposal default. You can use it in your config but you can also disable it:
 
r5(config)#no crypto ikev2 proposal default

you have to first disable the default policy.
 
r5#sh crypto ikev2 proposal
 IKEv2 proposal: IKEV2-PROPOSAL
     Encryption : AES-CBC-128
     Integrity  : SHA512
     PRF        : SHA512
     DH Group   : DH_GROUP_1536_MODP/Group 5
 IKEv2 proposal: default Disabled
r5#

to enable it again, issue following command:
 
r5(config)#default crypto ikev2 proposal

2) ikev2 policy

 r5#sh crypto ikev2 policy

 IKEv2 policy : IKEV2-POLICY
      Match fvrf  : global
      Match address local : any
      Proposal    : IKEV2-PROPOSAL

 IKEv2 policy : default
      Match fvrf : any
      Match address local : any
      Proposal    : default
r5#

As with the proposal, you can enable/disable it:
 
r5(config)#no crypto ikev2 policy default
r5(config)#default crypto ikev2 policy

3) ikev2 profile
 
r5#sh crypto ikev2 profile

IKEv2 profile: IKEV2-PROFILE
 Ref Count: 3
 Match criteria:
  Fvrf: global
  Local address/interface: none
  Identities:
   address 0.0.0.0
  Certificate maps: none
 Local identity: none
 Remote identity: none
 Local authentication method: pre-share
 Remote authentication method(s): pre-share
 EAP options: none
 Keyring: KEYRING123
 Trustpoint(s): none
 Lifetime: 86400 seconds
 DPD: interval 10, retry-interval 2, periodic
 NAT-keepalive: disabled
 Ivrf: none
 Virtual-template: 1
 AAA EAP authentication mlist: none
 AAA Accounting: none
 AAA group authorization: none
 AAA user authorization: none
r5#

4) transform-set
 
r5#sh crypto ipsec transform-set
Transform set default: { esp-aes esp-sha-hmac  }
   will negotiate = { Transport,  },

Transform set TS: { esp-256-aes esp-sha512-hmac  }
   will negotiate = { Tunnel,  },

r5#

To enable/disable the default transform-set issue the command:
 
r5(config)#no crypto ipsec transform-set default
r5(config)#default crypto ipsec transform-set

5) IPsec profile
 
r5#sh crypto ipsec profile
IPSEC profile IPSEC-PROFILE
        IKEV2 profile IKEV2-PROFILE
        Security association lifetime: 4608000 kilobytes/3600 seconds
        Responder-Only (Y/N): N
        PFS (Y/N): N
        Transform sets={
                TS:  { esp-256-aes esp-sha512-hmac  } ,
        }

IPSEC profile default
        Security association lifetime: 4608000 kilobytes/3600 seconds
        Responder-Only (Y/N): N
        PFS (Y/N): N
        Transform sets={
                default:  { esp-aes esp-sha-hmac  } ,
        }

r5#
r5(config)#default crypto ipsec profile
r5(config)#no crypto ipsec profile default
Labels:

Comments

Post a Comment

Popular posts from this blog

What should you know about HA 'override enabled' setting on Fortigate?

High availability is mandatory in most of today's network designs. Only very small companies or branches can run their business without redundancy. When you have Fortigate firewall in your network you have many options to increase network availability. You can use Fortigate Clustering Protocol ( FGCP ) or Virtual Router Redundancy Protocol ( VRRP ). FGCP has two modes: 'override' disabled (default) and 'override' enabled . I'm not going to explain how to set up HA as you can find many resources on Fortinet websites: https://cookbook.fortinet.com/high-availability-two-fortigates-56/ https://cookbook.fortinet.com/high-availability-with-fgcp-56/ Let's recap what is the main difference between them. The default HA setting is 'override' disabled and this is an order of selection an active unit: 1) number of monitored interfaces - when both units have the same number of working (up) interfaces check next parameter 2) HA uptime - an ...
8 comments
Read more

FortiGate and GRE tunnel

Recently I worked on one project where a client requested to re-route web traffic to the GRE tunnel to perform traffic inspection. I would like to share with you what is required if you configure it on FortiGate. We need a new GRE interface and policy base routing (PBR) to change the route for specific source IPs. Of course you need firewall policies to permit the traffic. Let's start with GRE interface. Unfortunately you can't configure it using the GUI, only CLI is the option: config system gre-tunnel edit "gre1" set interface "port1" set local-gw 55.55.55.55 set remote-gw 44.44.44.44 next end When the end peer is Cisco router, you need to set the IP for the GRE interface: config system interface edit gre1 set ip 192.168.10.10 255.255.255.255 set remote-ip192.168.10.20 end In next step we need to fix routing. We need the alternate path via GRE but to keep the route in the active routing table you need to set the same AD (adminis...
Post a Comment
Read more

Inpection of asymmetric sessions on FortiGate

There is one feature available on FortiGate, and I think you should know it, as it modifies a bit what we know about stateful firewalls. In past every packet was treated individually and you had to create policies in both directions. With stateful firewalls we can track connections, and by checking couple of attributes, we can treat them as part of the same session. For example when you initiate connection from a host1 to host2, the returning connection from host2 to host1 will be treated as part of the same connection (session). They have to have the same source/destination and destination/source IPs, port numbers and interfaces.There is an exception from this rule and FortiGate in some specific cases can accept connections on port which was not used in the initial connection. Let me explain how it works on the below example:      The host1 has a default gateway on R1 (10.0.1.2), but you may notice that it is not the optimal path to host2 subnet. When we analyze ...
1 comment
Read more