Skip to main content

Remote Access VPN (IPsec) - IOS - radius (ISE)

Today I change the configuration from my previous post, and instead of ACS I will add ISE (version 1.1).

First modification:
 
!
radius-server host 192.168.202.152 key cisco123
!

Next I add a new network device on ISE:

ra-ipsec4-1.jpg 

ra-ipsec4-2.jpg

In next step I add a new user group and next a new user: “ezvpn”

ra-ipsec4-3.jpg 

ra-ipsec4-4.jpg

And now the new user:

ra-ipsec4-5.jpg

Now it’s time to add a new authorization profile with radius attributes:
ra-ipsec4-6.jpg
ra-ipsec4-7.jpg

And then a new Authorization Profile:
 
ra-ipsec4-8.jpg

When I try to connect I see following log messages:
 
*Nov 24 20:17:04.534: RADIUS/ENCODE(00000086):Orig. component type = VPN IPSEC
*Nov 24 20:17:04.538: RADIUS:  AAA Unsupported Attr: interface         [221] 8   1767295532
*Nov 24 20:17:04.538: RADIUS(00000086): Config NAS IP: 0.0.0.0
*Nov 24 20:17:04.542: RADIUS(00000086): Config NAS IPv6: ::
*Nov 24 20:17:04.542: RADIUS/ENCODE(00000086): acct_session_id: 123
*Nov 24 20:17:04.546: RADIUS(00000086): sending
*Nov 24 20:17:04.550: RADIUS/ENCODE: Best Local IP-Address 10.0.0.2 for Radius-Server 192.168.202.152
*Nov 24 20:17:04.554: RADIUS(00000086): Sending a IPv4 Radius Packet
*Nov 24 20:17:04.558: RADIUS(00000086): Send Access-Request to 192.168.202.152:1645 id 1645/81,len 96
*Nov 24 20:17:04.558: RADIUS:  authenticator AA 57 75 1D DD AC 36 7C - 7B 50 8C E1 55 59 D3 D3
*Nov 24 20:17:04.562: RADIUS:  User-Name           [1]   7   "ezvpn"
*Nov 24 20:17:04.562: RADIUS:  User-Password       [2]   18  *
*Nov 24 20:17:04.566: RADIUS:  Calling-Station-Id  [31]  17  "192.168.202.1
R14#78"
*Nov 24 20:17:04.566: RADIUS:  NAS-Port-Type       [61]  6   Virtual                   [5]
*Nov 24 20:17:04.570: RADIUS:  NAS-Port            [5]   6   1
*Nov 24 20:17:04.574: RADIUS:  NAS-Port-Id         [87]  10  "10.0.0.2"
*Nov 24 20:17:04.574: RADIUS:  Service-Type        [6]   6   Outbound                  [5]
*Nov 24 20:17:04.578: RADIUS:  NAS-IP-Address      [4]   6   10.0.0.2
*Nov 24 20:17:04.578: RADIUS(00000086): Started 5 sec timeout
*Nov 24 20:17:04.614: RADIUS: Received from id 1645/81 192.168.202.152:1645, Access-Reject, len 20
*Nov 24 20:17:04.614: RADIUS:  authenticator 94 87 98 D6 18 1D 00 1B - 49 9C C3 7C 2C 92 52 76
*Nov 24 20:17:04.618: RADIUS(00000086): Received from id 1645/81
*Nov 24 20:17:04.762: %CRYPTO-6-IKMP_NOT_ENCRYPTED: IKE packet from 192.168.202.178 was not encrypted and it should've been.
*Nov 24 20:17:04.774: %CRYPTO-6-IKMP_NOT_ENCRYPTED: IKE packet from 192.168.202.178 was not encrypted and it
R14# should've been.
R14#

On ISE I see:

ra-ipsec4-9.jpg

The problem is related with one IOS limitation which allows on one fixed password “cisco” for user = isakmp client group. You can change a password policy but minimum number of characters is 6:

ra-ipsec4-10.jpg

I can’t find any solution but if you know how to omit the limitation, let me know and I will update my post.
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

Data Leak Prevention (DLP) on Fortigate

Today I would like to present one interesting feature you may find on your Fortigate - Data Leak Prevention. I know there are much better, dedicated solutions on the market but in certain situations the DLP feature available on FortiOS is good enough. Why you should use it? This is very important to say: the DLP in such deployment (on Fortigate) can't protect your data against every data leak. Users in your network with his/her mobile can easily take a photo of any document. Why we should still consider it? It is a good (and easy to deploy) method to prevent users' mistakes. It happened hundreds of time when a user attached a wrong file. Sound familiar? Using the DLP you can create policies which stop such leak. Let me show you how you can configure it. Step #1 First, you have to check if DLP is enabled in a "Feature Visibility" and "Security Features" section: When you do not see the feature, make sure your Fortigate works in a proxy-ba...
Post a Comment
Read more