Flex VPN With Spoke TO Spoke-1
Flex VPN With Spoke TO Spoke-1
FlexVPN hub and spoke tunnel ,there is no direct communication between the spoke routers. All traffic goes through the
hub router. It is possible to configure FlexVPN so that spoke routers can communicate with each other directly just like
DMVPN Phase 2 & 3. we use the Next Hop Resolution Protocol (NHRP) to accomplish this.
There is a difference between how DMVPN and FlexVPN use NHRP:
FlexVPN doesn’t use NHRP to register spoke routers with the hub router. Instead, we can use IKEv2 routing to advertise a
/32 route for the IP address of the tunnel interface to the remote router. This allows communication between the hub and
spoke router.
To “convert” a regular FlexVPN hub and spoke network into a network where direct spoke to spoke traffic is possible, we
need to make these changes:
• On the hub router, we have to add an NHRP network ID and enable NHRP redirection.
• The spoke routers require a dynamic VTI for spoke-to-spoke VPN tunnels.
• The spoke routers require the NHRP network ID and we need to enable NHRP shortcut switching.
• The spoke routers require some IKEv2 changes so they can authenticate each other.
IN this lab we exchange route using of IKEV2 instead of Dynamic routing protocol
R1(HUB)
1.IKEv2 Proposal
The proposal is a collection of items we use in the negotiation of the IKEv2 security
association (SA).
2.IKEv2 Policy
This policy contains proposals we want to use in the negotiation
3. IKEv2 Keyring
a keyring that contains the pre-shared key(s) we want to use.
AAA new-model
AAA authorization network FLEX-LOCAL local
ip access-list standard FLEX-ROUTE
permit 192.168.1.0 0.0.0.255
crypto ikev2 authorization policy IKEV2-AUTHORIZ
route set interface
route set access-list FLEX-ROUTE
5.IKEv2 Profile
The IKEv2 profile, we configure the local and remote identity and the authentication we want
to use.
7. IPSec Profile
This is where we combine the IKEv2 profile and our IPSec transform-set:
8. Dynamic VTI
The hub connects to multiple spoke routers, we need a dynamic VTI. Same IP address and subnet as the tunnel
interfaces on the spoke routers. However, you can’t configure the IP address directly on the dynamic VTI interface.
We need to add an NHRP ID and enable NHRP redirection on the virtual-template interface:
Int looopback0
Ip address 172.16.0.1 255.255.255.255
No shut
!
Int virtual-template 1 type tunnel
Ip unnumbered Loopback 0
Tunnel protection ipsec profile IPSECPROFILE
Ip nhrp network-id 1
Ip nhrp redirect
R2 (Spoke 1) R3(Spoke2)
1.IKEv2 Proposal 1.IKEv2 Proposal
The proposal is a collection of items we use in the The proposal is a collection of items we use in the
negotiation of the IKEv2 security negotiation of the IKEv2 security
association (SA). association (SA).
crypto ipsec transform-set TRANSFORM-SET esp-aes crypto ipsec transform-set TRANSFORM-SET esp-aes
256 esp-sha256-hmac 256 esp-sha256-hmac
mode tunnel mode tunnel
we need a dynamic VTI for spoke-to-spoke traffic.We we need a dynamic VTI for spoke-to-spoke traffic.We
need to identify and authenticate spoke routers we want need to identify and authenticate spoke routers we want
to communicate with. to communicate with.