Configuration d'ipsec entre un routeur Cisco IOS et un client VPN Cisco 4.x pour Windows à l'aide de RADIUS



Documents pareils
ASA/PIX : Exemple de configuration d'adressage IP statique pour client VPN IPSec avec CLI et ASDM

Contenu. Cocher : Network Policy and Access Services > Next > Next. Cocher : Network Policy Server > Next > Install

Les réseaux /24 et x0.0/29 sont considérés comme publics

Au cours de cette étude de cas, l étudiant doit accomplir les étapes suivantes :

HAUTE DISPONIBILITÉ DE MACHINE VIRTUELLE AVEC HYPER-V 2012 R2 PARTIE CONFIGURATION OPENVPN SUR PFSENSE

Configuration de WINS, DNS et DHCP sur les serveurs d'accès

comment paramétrer une connexion ADSL sur un modemrouteur

Intégration de Cisco CallManager IVR et Active Directory

Les logos et marques cités dans ce document sont la propriété de leurs auteurs respectifs

Travaux pratiques : dépannage de la configuration et du placement des listes de contrôle d'accès Topologie

Travaux pratiques Configuration du protocole DHCP avec SDM et l interface de ligne de commande Cisco IOS

Comment utiliser HSRP pour assurer la redondance dans un réseau BGP multihébergé

IMS INTERNET /Paramétrage de l offre / Gateway Cisco IMS INTERNET. Paramétrage de l offre Gateway CISCO. Référence Edition Date de Diffusion Page

Configuration d'un Réseau Privé Virtuel (RPV ) communément appelé VPN

Les réseaux des EPLEFPA. Guide «PfSense»

Guide d'installation et de configuration de Pervasive.SQL 7 dans un environnement réseau Microsoft Windows NT


NAC 4.5 : Exemple de configuration d'import-export de stratégie

Firewall ou Routeur avec IP statique

Instructions Mozilla Thunderbird Page 1

Installation d'un serveur RADIUS

Configuration d'un serveur DHCP Windows 2000 pour Cisco CallManager

Configuration du matériel Cisco. Florian Duraffourg

Administration du WG302 en SSH par Magicsam

NOTICE INSTALLATION. ARCHANGE Simplex Office N&B/Couleur KONICA MINOLTA BUSINESS SOLUTIONS FRANCE

Installation du client Cisco VPN 5 (Windows)

Tunnels et VPN. 22/01/2009 Formation Permanente Paris6 86

VTP. LAN Switching and Wireless Chapitre 4

Exercice : configuration de base de DHCP et NAT

WiFi Security Camera Quick Start Guide. Guide de départ rapide Caméra de surveillance Wi-Fi (P5)

PRODUCTION ASSOCIEE. Le réseau de la M2L est organisé VLANs et comporte des commutateurs de niveau 2 et des routeurs.

SSH, le shell sécurisé

Fonctionnement du protocole DHCP. Protocole DHCP (S4/C7)

Supervision et infrastructure - Accès aux applications JAVA. Document FAQ. Page: 1 / 9 Dernière mise à jour: 15/04/12 16:14

Sécurité des réseaux IPSec

Exercice Packet Tracer : Configuration de base des réseaux locaux virtuels

Skype (v2.5) Protocol Data Structures (French) Author : Ouanilo MEDEGAN

Projet PacketTracer en Labo, et Authentification Wi-Fi Serveur RADUIS (NPS)

Installation du client Cisco VPN 5 (Windows)

Protocoles utilisant des mécanismes d'authentification: TACACS+, RADIUS et Kerberos

Bienvenue sur Lab-Windows Il n'y a de vents favorables que pour ceux qui ont un cap

Installation du client Cisco VPN 5 (Windows)

IPv6. IPv6 et la sécurité: IPsec Objectif: Sécuriser... v.1a IPv6 Théorie et Pratique & Microsoft IPsec 1

Réseaux. Moyens de sécurisation. Plan. Evolutions topologiques des réseaux locaux

Mise en route d'un Routeur/Pare-Feu

Les ACL Cisco. F. Nolot Master 2 Professionnel STIC-Informatique 1

DFL-210, DFL-800, DFL-1600, DFL-2500 Comment configurer une connexion VPN IPSec site à site

Mission 2 : Prise de contrôle à distance sur les éléments d'infrastructures, les serveurs (Contrôleur de domaine et DHCP) et les clients

Pour les caméras IP de modèles : QSTC201 QSTC211. Surveillance à distance via Internet Guide de démarrage

WEB page builder and server for SCADA applications usable from a WEB navigator

Les clés d un réseau privé virtuel (VPN) fonctionnel

(1) Network Camera

PRODUCTION ASSOCIEE. Le réseau de la M2L est organisé VLANs et comporte des commutateurs de niveau 2 et des routeurs.

Travaux pratiques IPv6

2. MAQUETTAGE DES SOLUTIONS CONSTRUCTIVES. 2.2 Architecture fonctionnelle d un système communicant.

TP Configuration de l'authentification OSPF

RX3041. Guide d'installation rapide

Unité de stockage NAS

Travaux pratiques : collecte et analyse de données NetFlow

Devoir Surveillé de Sécurité des Réseaux

Installation du point d'accès Wi-Fi au réseau

calls.paris-neuroscience.fr Tutoriel pour Candidatures en ligne *** Online Applications Tutorial

CAMERA DOME AMELIORÉE DE SURVEILLANCE EN RÉSEAU GUIDE D INSTALLATION

TECHNICAL NOTE. Configuration d un tunnel VPN entre un firewall NETASQ et le client VPN. Authentification par clé pré-partagée. Version 7.

AUTHENTIFICATION x FREERADIUS. Objectifs

Couche application. La couche application est la plus élevée du modèle de référence.

Travaux pratiques Gestion des fichiers de configuration de périphérique via TFTP, Flash et USB

CRI-IUT Serveur d'authentification pour la sécurité des réseaux Wi-Fi

Outils d'analyse de la sécurité des réseaux. HADJALI Anis VESA Vlad

Transport Layer Security (TLS) Guide de mise en œuvre. Version: 1.0

GNS 3 Travaux pratiques

Packet Tracer : configuration des listes de contrôle d'accès étendues, scénario 1

Machine virtuelle Java pour Palm TX

Bravo! Vous venez d acquérir un routeur large bande à 4 ports Conceptronic C100BRS4H.

Network Shutdown Module V3 Extension du Manuel Utilisateur pour architecture Virtualisée VMWare ESX Server 3, 3.5

Pare-feu VPN sans fil N Cisco RV120W

Passerelle de Sécurité Internet Guide d installation

SECURIDAY 2013 Cyber War

Les fichiers de configuration d'openerp

Mise à jour des logiciels de vidéo de Polycom

Administration Switch (HP et autres)

Le protocole RADIUS. Objectifs. Ethernet Switch RADIUS RADIUS

Accès aux ressources informatiques de l ENSEEIHT à distance

Guide d'installation rapide TFM-560X YO.13

TD3 - Radius et IEEE 802.1x

1 Configuration des Fichiers Hosts, Hostname, Resolv.conf

NOTICE INSTALLATION. ARCHANGE WebDAV Office N&B/Couleur KONICA MINOLTA BUSINESS SOLUTIONS FRANCE

Direction des Systèmes d'information

NON URGENTE TEMPORAIRE DEFINITIVE. OBJET : FONCTIONNEMENT OmniVista 4760 SUR UN RÉSEAU VPN / NAT

1. Présentation de WPA et 802.1X

INSTALLATION WINDOWS SERVER 2008 R2

Comment changer le mot de passe NT pour les comptes de service Exchange et Unity

Exemple de configuration d'asa avec WebVPN et authentification unique à l'aide d'asdm et de NTLMv1

TR2 : Technologies de l'internet. Chapitre VI. NAT statique et dynamique Overloading (PAT) Overlapping, port Forwarding Serveur Proxy, DMZ

LP ASUR - Sécurité. Introduction à la Sécurité des Systèmes d'information. Florent Autréau - florent@mataru.com 28 Avril 2013

INSTALLATION DE WINDOWS 2000 SERVER POUR BCDI3. par. G.Haberer, A.Peuch, P.Saadé

NIMBUS TRAINING. Administration de Citrix NetScaler 10. Déscription : Objectifs. Publics. Durée. Pré-requis. Programme de cette formation

Réseaux Locaux Virtuels

Kerberos en environnement ISP UNIX/Win2K/Cisco

Transcription:

Configuration d'ipsec entre un routeur Cisco IOS et un client VPN Cisco 4.x pour Windows à l'aide de RADIUS Contenu Introduction Conditions préalables Conditions requises Composants utilisés Conventions Théorie générale Configurez Diagramme du réseau Configurations Configuration du serveur RADIUS Vérifiez Dépannez Dépannage des commandes Sortie de débogage Informations connexes Introduction Ce document explique comment configurer une connexion entre un routeur Cisco IOS et le client VPN Cisco 4.x utilisant RADIUS pour l autorisation des groupes et l authentification des utilisateurs. Connexions de support de version de logiciel 12.2(8)T et ultérieures de Cisco IOSï ½ du Client VPN Cisco 3.x. Les clients VPN 3.x et 4.x utilisent la stratégie du groupe 2 de Diffie Hellman (DH). La commande «isakmp policy # group 2» active les clients VPN à connecter. Remarque: La comptabilité d'ipsec VPN est maintenant disponible. Référez-vous à IPSec VPN expliquant plus d'informations et de configurations d'échantillon. Conditions préalables Conditions requises Assurez-vous que vous répondez à ces exigences avant d'essayer cette configuration : Un groupe d'adresses à assigner pour IPSec Un groupe a appelé "3000clients" avec une clé pré-partagée de "cisco123" Groupez l'autorisation et l'authentification de l'utilisateur sur un serveur de RAYON Remarque: La comptabilité de RAYON n'est pas prise en charge à ce moment. Composants utilisés Les informations contenues dans ce document sont basées sur les versions de matériel et de logiciel suivantes : Un routeur 2611 qui exécute le Logiciel Cisco IOS version 2.2(8)T. Cisco Secure ACS pour Windows (n'importe quel serveur de RAYON devrait travailler) Client VPN Cisco pour la version 4.8 de Windows (n'importe quel client vpn 4.x devrait travailler) Les informations contenues dans ce document ont été créées à partir des périphériques d'un environnement de laboratoire spécifique. Tous les périphériques utilisés dans ce document ont démarré avec une configuration effacée (par défaut). Si votre réseau est opérationnel, assurez-vous que vous comprenez l'effet potentiel de toute commande. Ceci est sorti de la commande de show version sur le routeur :

vpn2611#show version Cisco Internetwork Operating System Software IOS (tm) C2600 Software (C2600-JK9O3S-M), Version 12.2(8)T, RELEASE SOFTWARE (fc2) TAC Support: http://www.cisco.com/tac Copyright (c) 1986-2002 by cisco Systems, Inc. Compiled Thu 14-Feb-02 16:50 by ccai Image text-base: 0x80008070, data-base: 0x81816184 ROM: System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1) vpn2611 uptime is 1 hour, 15 minutes System returned to ROM by reload System image file is "flash:c2600-jk9o3s-mz.122-8.t" cisco 2611 (MPC860) processor (revision 0x203) with 61440K/4096K bytes of memory. Processor board ID JAD04370EEG (2285146560) M860 processor: part number 0, mask 49 Bridging software. X.25 software, Version 3.0.0. SuperLAT software (copyright 1990 by Meridian Technology Corp). TN3270 Emulation software. 2 Ethernet/IEEE 802.3 interface(s) 1 Serial network interface(s) 32K bytes of non-volatile configuration memory. 16384K bytes of processor board System flash (Read/Write) Configuration register is 0x2102 Conventions Pour plus d'informations sur les conventions utilisées dans ce document, reportez-vous à Conventions relatives aux conseils techniques Cisco. Théorie générale Ce document affiche l'authentification et l'autorisation, telle qu'assigner Windows Internet Naming Service (WINS) et le service de nom de domaine (DN), par le serveur de RAYON. Si vous êtes intéressé à exécuter l'authentification par le serveur et l'autorisation de RAYON localement par le routeur, référez-vous à la configuration d'ipsec entre un routeur Cisco IOS et un Client VPN Cisco 4.x pour Windows utilisant le RAYON pour l'authentification de l'utilisateur. Configurez Cette section vous fournit des informations pour configurer les fonctionnalités décrites dans ce document. Remarque: Utilisez l'outil Command Lookup Tool (clients enregistrés seulement) pour trouver plus d'informations sur les commandes utilisées dans ce document. Diagramme du réseau Ce document utilise la configuration réseau suivante : Remarque: Les adresses IP dans ce réseau d'exemple ne sont pas routable en Internet global parce qu'elles sont des adresses IP privées dans un réseau des travaux pratiques. Configurations Routeur 2611

vpn2611#show run Building configuration... Current configuration : 1884 bytes version 12.2 service timestamps debug uptime service timestamps log uptime no service password-encryption hostname vpn2611 --- Enable AAA for user authentication and group authorization. aaa new-model --- In order to enable extended authentication (Xauth) for user authentication, --- enable the aaa authentication commands. --- "Group radius" specifies RADIUS user authentication. aaa authentication login userauthen group radius --- In order to enable group authorization, --- enable the aaa authorization commands. aaa authorization network groupauthor group radius ip subnet-zero ip audit notify log ip audit po max-events 100 --- Create an Internet Security Association and --- Key Management Protocol (ISAKMP) policy for Phase 1 negotiations. crypto isakmp policy 3 encr 3des authentication pre-share group 2 --- Create the Phase 2 policy for actual data encryption. crypto ipsec transform-set myset esp-3des esp-sha-hmac --- Create a dynamic map and --- apply the transform set that was created. crypto dynamic-map dynmap 10 set transform-set myset --- Create the actual crypto map, --- and apply the AAA lists that were created earlier. crypto map clientmap client authentication list userauthen crypto map clientmap isakmp authorization list groupauthor crypto map clientmap client configuration address respond crypto map clientmap 10 ipsec-isakmp dynamic dynmap fax interface-type fax-mail mta receive maximum-recipients 0 --- Apply the crypto map on the outside interface. interface Ethernet0/0 ip address 10.1.1.1 255.255.255.0

half-duplex crypto map clientmap interface Serial0/0 no ip address shutdown interface Ethernet0/1 ip address 172.18.124.159 255.255.255.0 no keepalive half-duplex --- Create a pool of addresses to be assigned to the VPN Clients. ip local pool ippool 10.16.20.1 10.16.20.200 ip classless ip route 0.0.0.0 0.0.0.0 10.1.1.2 ip http server ip pim bidir-enable --- Create an access control list (ACL) if you want to do split tunneling. --- This ACL is referenced in the RADIUS profile. access-list 108 permit ip 172.18.124.0 0.0.255.255 10.16.20.0 0.0.0.255 --- Specify the IP address of the RADIUS server, --- along with the RADIUS shared secret key. radius-server host 172.18.124.96 auth-port 1645 acct-port 1646 key cisco123 radius-server retransmit 3 call rsvp-sync mgcp profile default dial-peer cor custom line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 end vpn2611# Configuration du serveur RADIUS Configurez le serveur de RAYON pour des clients d'aaa (le routeur) Procédez comme suit : 1. Cliquez sur Add l' entrée pour ajouter le routeur à la base de données du serveur de RAYON.

2. Spécifiez l'adresse IP du routeur "172.18.124.159" avec la clé secrète partagée "cisco123" et choisissez le RAYON dans l'authentifier utilisant la liste déroulante. Configurez le serveur de RAYON pour l'authentification et l'autorisation de groupe Procédez comme suit : 1. Cliquez sur Add/éditez pour ajouter un utilisateur nommé 3000client au serveur de RAYON. 2. Spécifiez le mot de passe cisco pour cet utilisateur. Ce mot de passe est un mot clé spécial pour le Cisco IOS, qui indique qu'un profil de groupe doit être mis en référence. Vous pouvez tracer l'utilisateur à un groupe Cisco Secure si vous préférez. Assurez-vous qu' aucune affectation d'adresse IP n'est choisie.

3. Spécifiez les paramètres d'autorisation de groupe qui seront passés vers le bas par ce compte utilisateur de nouveau au client vpn. Veillez-vous pour avoir des Cisco-poids du commerce-paires activées avec ces attributs : ipsec : key-exchange=ike ipsec : key-exchange=preshared-key ipsec : addr-pool=ippool ipsec:inacl=108 (seulement requis si vous utilisez la Segmentation de tunnel sur le routeur) En outre, assurez-vous que vous faites activer l'ietf RADIUS Attributes de theseg : Attribut 6 : Service-Type=Outbound Attribut 64 : L'ESP de Tunnel-Type=IP Attribut 69 : Tunnel-Password=cisco123 (c'est votre mot de passe de groupe sur le client vpn) Une fois que vous avez terminé, cliquez sur Submit.

Sous des attributs spécifiques de constructeur, vous pouvez également activer ces attributs facultatifs : ipsec : default-domain= ipsec : timeout= ipsec : idletime= ipsec : dns-servers= ipsec : wins-servers= Configurez le serveur de RAYON pour l'authentification de l'utilisateur Procédez comme suit : 1. Cliquez sur Add/éditez pour ajouter l'utilisateur VPN dans la base de données Cisco Secure. Dans cet exemple, le nom d'utilisateur est Cisco. 2. Sur la prochaine fenêtre, spécifiez le mot de passe pour l'utilisateur Cisco. Le mot de passe est également Cisco. Vous pouvez tracer le compte utilisateur à un groupe. Une fois que vous avez terminé, cliquez sur Submit.

Configuration VPN Client 4.8 Terminez-vous ces étapes afin de configurer le client vpn 4.8 : 1. 2. Choisissez le début > les programmes > le client vpn de Cisco Systems > le client vpn. Cliquez sur New pour ouvrir la fenêtre Create New VPN Connection Entry. 3. Entrez le nom de l'entrée de connexion avec une description. Écrivez l'adresse IP extérieure du routeur dans la case d'hôte. Puis, entrez le nom de groupe VPN et le mot de passe et cliquez sur la sauvegarde.

4. Cliquez sur en fonction la connexion que vous voulez au clic d'utiliser-et vous connectez de la fenêtre principale de client vpn. 5. Lorsque vous y êtes invité, saisissez le nom d'utilisateur et le mot de passe pour Xauth et cliquez sur OK pour vous connecter au réseau distant. Le client vpn obtient lié au routeur au lieu d'exploitation principal.

Vérifiez Référez-vous à cette section pour vous assurer du bon fonctionnement de votre configuration. L'Outil Interpréteur de sortie (clients enregistrés uniquement) (OIT) prend en charge certaines commandes show. Utilisez l'oit pour afficher une analyse de la sortie de la commande show. vpn2611#show crypto isakmp sa dst src state conn-id slot 10.1.1.1 10.0.0.1 QM_IDLE 3 0 vpn2611#show crypto ipsec sa interface: Ethernet0/0 Crypto map tag: clientmap, local addr. 10.1.1.1 local ident (addr/mask/prot/port): (10.1.1.1/255.255.255.255/0/0) remote ident (addr/mask/prot/port): (10.16.20.2/255.255.255.255/0/0) current_peer: 10.0.0.1 PERMIT, flags={} #pkts encaps: 5, #pkts encrypt: 5, #pkts digest 5 #pkts decaps: 5, #pkts decrypt: 5, #pkts verify 5 #pkts compressed: 0, #pkts decompressed: 0 #pkts not compressed: 0, #pkts compr. failed: 0, #pkts decompress failed: 0 #send errors 0, #recv errors 0 local crypto endpt.: 10.1.1.1, remote crypto endpt.: 10.0.0.1 path mtu 1500, media mtu 1500 current outbound spi: 77AFCCFA inbound esp sas: spi: 0xC7AC22AB(3349947051) transform: esp-3des esp-sha-hmac, in use settings ={Tunnel, } slot: 0, conn id: 2000, flow_id: 1, crypto map: clientmap sa timing: remaining key lifetime (k/sec): (4608000/3444) IV size: 8 bytes replay detection support: Y inbound ah sas: inbound pcp sas: outbound esp sas: spi: 0x77AFCCFA(2008009978) transform: esp-3des esp-sha-hmac, in use settings ={Tunnel, } slot: 0, conn id: 2001, flow_id: 2, crypto map: clientmap sa timing: remaining key lifetime (k/sec): (4608000/3444) IV size: 8 bytes replay detection support: Y outbound ah sas: outbound pcp sas: local ident (addr/mask/prot/port): (172.18.124.0/255.255.255.0/0/0)

remote ident (addr/mask/prot/port): (10.16.20.2/255.255.255.255/0/0) current_peer: 10.0.0.1 PERMIT, flags={} #pkts encaps: 4, #pkts encrypt: 4, #pkts digest 4 #pkts decaps: 6, #pkts decrypt: 6, #pkts verify 6 #pkts compressed: 0, #pkts decompressed: 0 #pkts not compressed: 0, #pkts compr. failed: 0, #pkts decompress failed: 0 #send errors 0, #recv errors 0 local crypto endpt.: 10.1.1.1, remote crypto endpt.: 10.0.0.1 path mtu 1500, media mtu 1500 current outbound spi: 2EE5BF09 inbound esp sas: spi: 0x3565451F(895829279) transform: esp-3des esp-sha-hmac, in use settings ={Tunnel, } slot: 0, conn id: 2002, flow_id: 3, crypto map: clientmap sa timing: remaining key lifetime (k/sec): (4607999/3469) IV size: 8 bytes replay detection support: Y inbound ah sas: inbound pcp sas: outbound esp sas: spi: 0x2EE5BF09(786808585) transform: esp-3des esp-sha-hmac, in use settings ={Tunnel, } slot: 0, conn id: 2003, flow_id: 4, crypto map: clientmap sa timing: remaining key lifetime (k/sec): (4607999/3469) IV size: 8 bytes replay detection support: Y outbound ah sas: outbound pcp sas: vpn2611#show crypto engine connections active ID Interface IP-Address State Algorithm Encrypt Decrypt 3 Ethernet0/0 10.1.1.1 set HMAC_SHA+3DES_56_C 0 0 2000 Ethernet0/0 10.1.1.1 set HMAC_SHA+3DES_56_C 0 5 2001 Ethernet0/0 10.1.1.1 set HMAC_SHA+3DES_56_C 5 0 2002 Ethernet0/0 10.1.1.1 set HMAC_SHA+3DES_56_C 0 6 2003 Ethernet0/0 10.1.1.1 set HMAC_SHA+3DES_56_C 4 0 Dépannez Utilisez cette section pour dépanner votre configuration. Dépannage des commandes L'Outil Interpréteur de sortie (clients enregistrés uniquement) (OIT) prend en charge certaines commandes show. Utilisez l'oit pour afficher une analyse de la sortie de la commande show. Remarque: Référez-vous aux informations importantes sur les commandes de débogage avant d'utiliser les commandes de débogage. debug crypto ipsec Affiche des informations de débogage sur les connexions IPSec. debug crypto isakmp - Affiche les informations de débogage sur les connexions IPSec et le premier ensemble d'attributs refusés en raison d'incompatibilités sur les deux extrémités. debug crypto engine Affiche des informations du moteur de chiffrement. debug aaa authentication Affiche des informations sur l'authentification AAA/TACACS+. raduis d'autorisation de debug aaa Affiche des informations sur l'autorisation AAA/TACACS+. debug radius Affiche des informations sur la transmission de dépannage entre le serveur de RAYON et le routeur. Sortie de débogage Cette section fournit mettent au point les informations du routeur que vous pouvez utiliser pour dépanner votre configuration. Journaux du routeur vpn2611#show debug General OS: AAA Authorization debugging is on Radius protocol debugging is on

Radius packet protocol debugging is on Cryptographic Subsystem: Crypto ISAKMP debugging is on Crypto IPSEC debugging is on vpn2611# 1w0d: ISAKMP (0:0): received packet from 10.0.0.1 (N) NEW SA 1w0d: ISAKMP: local port 500, remote port 500 1w0d: ISAKMP (0:2): (Re)Setting client xauth list userauthen and state 1w0d: ISAKMP: Locking CONFIG struct 0x830BF118 from crypto_ikmp_config_initialize_sa, count 2 1w0d: ISAKMP (0:2): processing SA payload. message ID = 0 1w0d: ISAKMP (0:2): processing ID payload. message ID = 0 1w0d: ISAKMP (0:2): processing vendor id payload 1w0d: ISAKMP (0:2): vendor ID seems Unity/DPD but bad major 1w0d: ISAKMP (0:2): vendor ID is XAUTH 1w0d: ISAKMP (0:2): processing vendor id payload 1w0d: ISAKMP (0:2): vendor ID is DPD 1w0d: ISAKMP (0:2): processing vendor id payload 1w0d: ISAKMP (0:2): vendor ID is Unity 1w0d: ISAKMP (0:2): Checking ISAKMP transform 1 against priority 3 policy 1w0d: ISAKMP: encryption 3DES-CBC 1w0d: ISAKMP: hash SHA 1w0d: ISAKMP: default group 2 1w0d: ISAKMP: auth XAUTHInitPreShared 1w0d: ISAKMP: life type in seconds 1w0d: ISAKMP: life duration (VPI) of 0x0 0x20 0xC4 0x9B 1w0d: ISAKMP (0:2): atts are acceptable. Next payload is 3 1w0d: ISAKMP (0:2): processing KE payload. message ID = 0 1w0d: ISAKMP (0:2): processing NONCE payload. message ID = 0 1w0d: ISAKMP (0:2): processing vendor id payload 1w0d: ISAKMP (0:2): processing vendor id payload 1w0d: ISAKMP (0:2): processing vendor id payload 1w0d: AAA: parse name=isakmp-id-auth idb type=-1 tty=-1 1w0d: AAA/MEMORY: create_user (0x830CAF28) user='3000client' ruser='null' ds0=0 port='isakmp-id-auth' rem_addr='10.0.0.1' authen_type=none service=login priv=0 initial_task_id='0' 1w0d: ISAKMP (0:2): Input = IKE_MESG_FROM_PEER, IKE_AM_EXCH Old State = IKE_READY New State = IKE_R_AM_AAA_AWAIT 1w0d: ISAKMP-ID-AUTH AAA/AUTHOR/CRYPTO AAA(66832552): Port='ISAKMP-ID-AUTH' list='groupauthor' service=net 1w0d: AAA/AUTHOR/CRYPTO AAA: ISAKMP-ID-AUTH(66832552) user='3000client' 1w0d: ISAKMP-ID-AUTH AAA/AUTHOR/CRYPTO AAA(66832552): send AV service=ike 1w0d: ISAKMP-ID-AUTH AAA/AUTHOR/CRYPTO AAA(66832552): send AV protocol=ipsec 1w0d: ISAKMP-ID-AUTH AAA/AUTHOR/CRYPTO AAA(66832552): found list "groupauthor" 1w0d: ISAKMP-ID-AUTH AAA/AUTHOR/CRYPTO AAA(66832552): Method=radius (radius) 1w0d: RADIUS: authenticating to get author data 1w0d: RADIUS: ustruct sharecount=3 1w0d: Radius: radius_port_info() success=0 radius_nas_port=1 1w0d: RADIUS: Send to ISAKMP-ID-AUTH id 60 172.18.124.96:1645, Access-Request, len 83 1w0d: RADIUS: authenticator AF EC D3 AD D6 39 4F 7D - A0 5E FC 64 F5 DE A7 3B 1w0d: RADIUS: NAS-IP-Address [4] 6 172.18.124.159 1w0d: RADIUS: NAS-Port-Type [61] 6 Async [0] 1w0d: RADIUS: User-Name [1] 12 "3000client" 1w0d: RADIUS: Calling-Station-Id [31] 15 "10.0.0.1" 1w0d: RADIUS: User-Password [2] 18 * 1w0d: RADIUS: Service-Type [6] 6 Outbound [5] 1w0d: RADIUS: Received from id 60 172.18.124.96:1645, Access-Accept, len 176 1w0d: RADIUS: authenticator 52 BA 0A 38 AC C2 2B 6F - A0 77 64 93 D6 19 78 CF 1w0d: RADIUS: Service-Type [6] 6 Outbound [5] 1w0d: RADIUS: Vendor, Cisco [26] 30 1w0d: RADIUS: Cisco AVpair [1] 24 "ipsec:key-exchange=ike" 1w0d: RADIUS: Vendor, Cisco [26] 40 1w0d: RADIUS: Cisco AVpair [1] 34 "ipsec:key-exchange=preshared-key" 1w0d: RADIUS: Vendor, Cisco [26] 30 1w0d: RADIUS: Cisco AVpair [1] 24 "ipsec:addr-pool=ippool" 1w0d: RADIUS: Vendor, Cisco [26] 23 1w0d: RADIUS: Cisco AVpair [1] 17 "ipsec:inacl=108" 1w0d: RADIUS: Tunnel-Type [64] 6 01:ESP [9] 1w0d: RADIUS: Tunnel-Password [69] 21 * 1w0d: RADIUS: saved authorization data for user 830CAF28 at 83198648 1w0d: RADIUS: cisco AVPair "ipsec:key-exchange=ike" 1w0d: RADIUS: cisco AVPair "ipsec:key-exchange=preshared-key" 1w0d: RADIUS: cisco AVPair "ipsec:addr-pool=ippool" 1w0d: RADIUS: cisco AVPair "ipsec:inacl=108"

1w0d: RADIUS: Tunnel-Type, [01] 00 00 09 1w0d: RADIUS: TAS(1) created and enqueued. 1w0d: RADIUS: Tunnel-Password decrypted, [01] cisco123 1w0d: RADIUS: TAS(1) takes precedence over tagged attributes, tunnel_type=esp 1w0d: RADIUS: free TAS(1) 1w0d: AAA/AUTHOR (66832552): Post authorization status = PASS_REPL 1w0d: ISAKMP: got callback 1 AAA/AUTHOR/IKE: Processing AV key-exchange=ike AAA/AUTHOR/IKE: Processing AV key-exchange=preshared-key AAA/AUTHOR/IKE: Processing AV addr-pool=ippool AAA/AUTHOR/IKE: Processing AV inacl=108 AAA/AUTHOR/IKE: Processing AV tunnel-type*esp AAA/AUTHOR/IKE: Processing AV tunnel-password=cisco123 AAA/AUTHOR/IKE: Processing AV tunnel-tag*1 1w0d: ISAKMP (0:2): SKEYID state generated 1w0d: ISAKMP (0:2): SA is doing pre-shared key authentication plux XAUTH using id type ID_IPV4_ADDR 1w0d: ISAKMP (2): ID payload next-payload : 10 type : 1 protocol : 17 port : 500 length : 8 1w0d: ISAKMP (2): Total payload length: 12 1w0d: ISAKMP (0:2): sending packet to 10.0.0.1 (R) AG_INIT_EXCH 1w0d: ISAKMP (0:2): Input = IKE_MESG_FROM_AAA, PRESHARED_KEY_REPLY Old State = IKE_R_AM_AAA_AWAIT New State = IKE_R_AM2 1w0d: AAA/MEMORY: free_user (0x830CAF28) user='3000client' ruser='null' port='isakmp-id-auth' rem_addr='10.0.0.1' authen_type=none service=login priv=0 1w0d: ISAKMP (0:2): received packet from 10.0.0.1 (R) AG_INIT_EXCH 1w0d: ISAKMP (0:2): processing HASH payload. message ID = 0 1w0d: ISAKMP (0:2): processing NOTIFY INITIAL_CONTACT protocol 1 spi 0, message ID = 0, sa = 831938B0 1w0d: ISAKMP (0:2): Process initial contact, bring down existing phase 1 and 2 SA's 1w0d: ISAKMP (0:2): returning IP addr to the address pool: 10.16.20.1 1w0d: ISAKMP (0:2): returning address 10.16.20.1 to pool 1w0d: ISAKMP (0:2): peer does not do paranoid keepalives. 1w0d: ISAKMP (0:2): SA has been authenticated with 10.0.0.1 1w0d: ISAKMP (0:2): sending packet to 10.0.0.1 (R) QM_IDLE 1w0d: ISAKMP (0:2): purging node -1377537628 1w0d: ISAKMP: Sending phase 1 responder lifetime 86400 1w0d: ISAKMP (0:2): Input = IKE_MESG_FROM_PEER, IKE_AM_EXCH Old State = IKE_R_AM2 New State = IKE_P1_COMPLETE 1w0d: IPSEC(key_engine): got a queue event... 1w0d: IPSEC(key_engine_delete_sas): rec'd delete notify from ISAKMP 1w0d: IPSEC(key_engine_delete_sas): delete all SAs shared with 10.0.0.1 1w0d: ISAKMP (0:2): Need XAUTH 1w0d: AAA: parse name=isakmp idb type=-1 tty=-1 1w0d: AAA/MEMORY: create_user (0x830CAF28) user='null' ruser='null' ds0=0 port='isakmp' rem_addr='10.0.0.1' authen_type=ascii service=login priv=0 initial_task_id='0' 1w0d: ISAKMP (0:2): Input = IKE_MESG_INTERNAL, IKE_PHASE1_COMPLETE Old State = IKE_P1_COMPLETE New State = IKE_XAUTH_AAA_START_LOGIN_AWAIT 1w0d: ISAKMP: got callback 1 1w0d: ISAKMP/xauth: request attribute XAUTH_TYPE_V2 1w0d: ISAKMP/xauth: request attribute XAUTH_MESSAGE_V2 1w0d: ISAKMP/xauth: request attribute XAUTH_USER_NAME_V2 1w0d: ISAKMP/xauth: request attribute XAUTH_USER_PASSWORD_V2 1w0d: ISAKMP (0:2): initiating peer config to 10.0.0.1. ID = -1021889193 1w0d: ISAKMP (0:2): sending packet to 10.0.0.1 (R) CONF_XAUTH 1w0d: ISAKMP (0:2): Input = IKE_MESG_FROM_AAA, IKE_AAA_START_LOGIN Old State = IKE_XAUTH_AAA_START_LOGIN_AWAIT New State = IKE_XAUTH_REQ_SENT 1w0d: ISAKMP (0:1): purging node 832238598 1w0d: ISAKMP (0:1): purging node 1913225491 1w0d: ISAKMP (0:2): received packet from 10.0.0.1 (R) CONF_XAUTH 1w0d: ISAKMP (0:2): processing transaction payload from 10.0.0.1. message ID = -1021889193 1w0d: ISAKMP: Config payload REPLY 1w0d: ISAKMP/xauth: reply attribute XAUTH_TYPE_V2 unexpected 1w0d: ISAKMP/xauth: reply attribute XAUTH_USER_NAME_V2 1w0d: ISAKMP/xauth: reply attribute XAUTH_USER_PASSWORD_V2

1w0d: ISAKMP (0:2): deleting node -1021889193 error FALSE reason "done with xauth request/reply exchange" 1w0d: ISAKMP (0:2): Input = IKE_MESG_FROM_PEER, IKE_CFG_REPLY Old State = IKE_XAUTH_REQ_SENT New State = IKE_XAUTH_AAA_CONT_LOGIN_AWAIT 1w0d: RADIUS: ustruct sharecount=2 1w0d: Radius: radius_port_info() success=0 radius_nas_port=1 1w0d: RADIUS: Send to ISAKMP id 61 172.18.124.96:1645, Access-Request, len 72 1w0d: RADIUS: authenticator 98 12 4F C0 DA B9 48 B8-58 00 BA 14 08 8E 87 C0 1w0d: RADIUS: NAS-IP-Address [4] 6 172.18.124.159 1w0d: RADIUS: NAS-Port-Type [61] 6 Async [0] 1w0d: RADIUS: User-Name [1] 7 "cisco" 1w0d: RADIUS: Calling-Station-Id [31] 15 "10.0.0.1" 1w0d: RADIUS: User-Password [2] 18 * 1w0d: RADIUS: Received from id 61 172.18.124.96:1645, Access-Accept, len 26 1w0d: RADIUS: authenticator 00 03 F4 E1 9C 61 3F 03-54 83 E8 27 5C 6A 7B 6E 1w0d: RADIUS: Framed-IP-Address [8] 6 255.255.255.255 1w0d: RADIUS: saved authorization data for user 830CAF28 at 830F89F8 1w0d: ISAKMP: got callback 1 1w0d: ISAKMP (0:2): initiating peer config to 10.0.0.1. ID = -547189328 1w0d: ISAKMP (0:2): sending packet to 10.0.0.1 (R) CONF_XAUTH 1w0d: ISAKMP (0:2): Input = IKE_MESG_FROM_AAA, IKE_AAA_CONT_LOGIN Old State = IKE_XAUTH_AAA_CONT_LOGIN_AWAIT New State = IKE_XAUTH_SET_SENT 1w0d: AAA/MEMORY: free_user (0x830CAF28) user='cisco' ruser='null' port='isakmp' rem_addr='10.0.0.1' authen_type=ascii service=login priv=0 1w0d: ISAKMP (0:2): received packet from 10.0.0.1 (R) CONF_XAUTH 1w0d: ISAKMP (0:2): processing transaction payload from 10.0.0.1. message ID = -547189328 1w0d: ISAKMP: Config payload ACK 1w0d: ISAKMP (0:2): XAUTH ACK Processed 1w0d: ISAKMP (0:2): deleting node -547189328 error FALSE reason "done with transaction" 1w0d: ISAKMP (0:2): Input = IKE_MESG_FROM_PEER, IKE_CFG_ACK Old State = IKE_XAUTH_SET_SENT New State = IKE_P1_COMPLETE 1w0d: ISAKMP (0:2): Input = IKE_MESG_INTERNAL, IKE_PHASE1_COMPLETE Old State = IKE_P1_COMPLETE New State = IKE_P1_COMPLETE 1w0d: ISAKMP (0:2): received packet from 10.0.0.1 (R) QM_IDLE 1w0d: ISAKMP (0:2): processing transaction payload from 10.0.0.1. message ID = -1911189201 1w0d: ISAKMP: Config payload REQUEST 1w0d: ISAKMP (0:2): checking request: 1w0d: ISAKMP: IP4_ADDRESS 1w0d: ISAKMP: IP4_NETMASK 1w0d: ISAKMP: IP4_DNS 1w0d: ISAKMP: IP4_NBNS 1w0d: ISAKMP: ADDRESS_EXPIRY 1w0d: ISAKMP: APPLICATION_VERSION 1w0d: ISAKMP: UNKNOWN Unknown Attr: 0x7000 1w0d: ISAKMP: UNKNOWN Unknown Attr: 0x7001 1w0d: ISAKMP: DEFAULT_DOMAIN 1w0d: ISAKMP: SPLIT_INCLUDE 1w0d: ISAKMP: UNKNOWN Unknown Attr: 0x7007 1w0d: ISAKMP: UNKNOWN Unknown Attr: 0x7008 1w0d: ISAKMP: UNKNOWN Unknown Attr: 0x7005 1w0d: AAA: parse name=isakmp-group-auth idb type=-1 tty=-1 1w0d: AAA/MEMORY: create_user (0x830CAF28) user='3000client' ruser='null' ds0=0 port='isakmp-group-auth' rem_addr='10.0.0.1' authen_type=none service=login priv=0 initial_task_id='0' 1w0d: ISAKMP (0:2): Input = IKE_MESG_FROM_PEER, IKE_CFG_REQUEST Old State = IKE_P1_COMPLETE New State = IKE_CONFIG_AUTHOR_AAA_AWAIT 1w0d: ISAKMP-GROUP-AUTH AAA/AUTHOR/CRYPTO AAA(3098118746): Port='ISAKMP-GROUP-AUTH' list='groupauthor' service=net 1w0d: AAA/AUTHOR/CRYPTO AAA: ISAKMP-GROUP-AUTH(3098118746) user='3000client' 1w0d: ISAKMP-GROUP-AUTH AAA/AUTHOR/CRYPTO AAA(3098118746): send AV service=ike 1w0d: ISAKMP-GROUP-AUTH AAA/AUTHOR/CRYPTO AAA(3098118746): send AV protocol=ipsec 1w0d: ISAKMP-GROUP-AUTH AAA/AUTHOR/CRYPTO AAA(3098118746): found list "groupauthor" 1w0d: ISAKMP-GROUP-AUTH AAA/AUTHOR/CRYPTO AAA(3098118746): Method=radius (radius) 1w0d: RADIUS: authenticating to get author data 1w0d: RADIUS: ustruct sharecount=3 1w0d: Radius: radius_port_info() success=0 radius_nas_port=1 1w0d: RADIUS: Send to ISAKMP-GROUP-AUTH id 62 172.18.124.96:1645,

Access-Request, len 83 1w0d: RADIUS: authenticator 32 C5 32 FF AB B7 E4 68-9A 68 5A DE D5 56 0C BE 1w0d: RADIUS: NAS-IP-Address [4] 6 172.18.124.159 1w0d: RADIUS: NAS-Port-Type [61] 6 Async [0] 1w0d: RADIUS: User-Name [1] 12 "3000client" 1w0d: RADIUS: Calling-Station-Id [31] 15 "10.0.0.1" 1w0d: RADIUS: User-Password [2] 18 * 1w0d: RADIUS: Service-Type [6] 6 Outbound [5] 1w0d: RADIUS: Received from id 62 172.18.124.96:1645, Access-Accept, len 176 1w0d: RADIUS: authenticator DF FA FE 21 07 92 4F 10-75 5E D6 96 66 70 19 27 1w0d: RADIUS: Service-Type [6] 6 Outbound [5] 1w0d: RADIUS: Vendor, Cisco [26] 30 1w0d: RADIUS: Cisco AVpair [1] 24 "ipsec:key-exchange=ike" 1w0d: RADIUS: Vendor, Cisco [26] 40 1w0d: RADIUS: Cisco AVpair [1] 34 "ipsec:key-exchange=preshared-key" 1w0d: RADIUS: Vendor, Cisco [26] 30 1w0d: RADIUS: Cisco AVpair [1] 24 "ipsec:addr-pool=ippool" 1w0d: RADIUS: Vendor, Cisco [26] 23 1w0d: RADIUS: Cisco AVpair [1] 17 "ipsec:inacl=108" 1w0d: RADIUS: Tunnel-Type [64] 6 01:ESP [9] 1w0d: RADIUS: Tunnel-Password [69] 21 * 1w0d: RADIUS: saved authorization data for user 830CAF28 at 83143E64 1w0d: RADIUS: cisco AVPair "ipsec:key-exchange=ike" 1w0d: RADIUS: cisco AVPair "ipsec:key-exchange=preshared-key" 1w0d: RADIUS: cisco AVPair "ipsec:addr-pool=ippool" 1w0d: RADIUS: cisco AVPair "ipsec:inacl=108" 1w0d: RADIUS: Tunnel-Type, [01] 00 00 09 1w0d: RADIUS: TAS(1) created and enqueued. 1w0d: RADIUS: Tunnel-Password decrypted, [01] cisco123 1w0d: RADIUS: TAS(1) takes precedence over tagged attributes, tunnel_type=esp 1w0d: RADIUS: free TAS(1) 1w0d: AAA/AUTHOR (3098118746): Post authorization status = PASS_REPL 1w0d: ISAKMP: got callback 1 AAA/AUTHOR/IKE: Processing AV key-exchange=ike AAA/AUTHOR/IKE: Processing AV key-exchange=preshared-key AAA/AUTHOR/IKE: Processing AV addr-pool=ippool AAA/AUTHOR/IKE: Processing AV inacl=108 AAA/AUTHOR/IKE: Processing AV tunnel-type*esp AAA/AUTHOR/IKE: Processing AV tunnel-password=cisco123 AAA/AUTHOR/IKE: Processing AV tunnel-tag*1 1w0d: ISAKMP (0:2): attributes sent in message: 1w0d: Address: 0.2.0.0 1w0d: ISAKMP (0:2): allocating address 10.16.20.2 1w0d: ISAKMP: Sending private address: 10.16.20.2 1w0d: ISAKMP: Unknown Attr: IP4_NETMASK (0x2) 1w0d: ISAKMP: Sending ADDRESS_EXPIRY seconds left to use the address: 86395 1w0d: ISAKMP: Sending APPLICATION_VERSION string: Cisco Internetwork Operating System Software IOS (tm) C2600 Software (C2600-JK9O3S-M), Version 12.2(8)T, RELEASE SOFTWARE (fc2) TAC Support: http://www.cisco.com/tac Copyright (c) 1986-2002 by cisco Systems, Inc. Compiled Thu 14-Feb-02 16:50 by ccai 1w0d: ISAKMP: Unknown Attr: UNKNOWN (0x7000) 1w0d: ISAKMP: Unknown Attr: UNKNOWN (0x7001) 1w0d: ISAKMP: Sending split include name 108 network 14.38.0.0 mask 255.255.0.0 protocol 0, src port 0, dst port 0 1w0d: ISAKMP: Unknown Attr: UNKNOWN (0x7007) 1w0d: ISAKMP: Unknown Attr: UNKNOWN (0x7008) 1w0d: ISAKMP: Unknown Attr: UNKNOWN (0x7005) 1w0d: ISAKMP (0:2): responding to peer config from 10.0.0.1. ID = -1911189201 1w0d: ISAKMP (0:2): sending packet to 10.0.0.1 (R) CONF_ADDR 1w0d: ISAKMP (0:2): deleting node -1911189201 error FALSE reason "" 1w0d: ISAKMP (0:2): Input = IKE_MESG_FROM_AAA, IKE_AAA_GROUP_ATTR Old State = IKE_CONFIG_AUTHOR_AAA_AWAIT New State = IKE_P1_COMPLETE 1w0d: AAA/MEMORY: free_user (0x830CAF28) user='3000client' ruser='null' port='isakmp-group-auth' rem_addr='10.0.0.1' authen_type=none service=login priv=0 1w0d: ISAKMP (0:2): received packet from 10.0.0.1 (R) QM_IDLE 1w0d: ISAKMP (0:2): processing HASH payload. message ID = 132557281 1w0d: ISAKMP (0:2): processing SA payload. message ID = 132557281 1w0d: ISAKMP (0:2): Checking IPSec proposal 1 1w0d: ISAKMP: transform 1, ESP_3DES 1w0d: ISAKMP: attributes in transform:

1w0d: ISAKMP: authenticator is HMAC-MD5 1w0d: ISAKMP: encaps is 1 1w0d: ISAKMP: SA life type in seconds 1w0d: ISAKMP: SA life duration (VPI) of 0x0 0x20 0xC4 0x9B 1w0d: IPSEC(validate_proposal): transform proposal (prot 3, trans 3, hmac_alg 1) not supported 1w0d: ISAKMP (0:2): atts not acceptable. Next payload is 0 1w0d: ISAKMP (0:2): skipping next ANDed proposal (1) 1w0d: ISAKMP (0:2): Checking IPSec proposal 2 1w0d: ISAKMP: transform 1, ESP_3DES 1w0d: ISAKMP: attributes in transform: 1w0d: ISAKMP: authenticator is HMAC-SHA 1w0d: ISAKMP: encaps is 1 1w0d: ISAKMP: SA life type in seconds 1w0d: ISAKMP: SA life duration (VPI) of 0x0 0x20 0xC4 0x9B 1w0d: ISAKMP (0:2): atts are acceptable. 1w0d: ISAKMP (0:2): Checking IPSec proposal 2 1w0d: ISAKMP (0:2): transform 1, IPPCP LZS 1w0d: ISAKMP: attributes in transform: 1w0d: ISAKMP: encaps is 1 1w0d: ISAKMP: SA life type in seconds 1w0d: ISAKMP: SA life duration (VPI) of 0x0 0x20 0xC4 0x9B 1w0d: IPSEC(validate_proposal): transform proposal (prot 4, trans 3, hmac_alg 0) not supported 1w0d: ISAKMP (0:2): atts not acceptable. Next payload is 0 1w0d: ISAKMP (0:2): Checking IPSec proposal 3 1w0d: ISAKMP: transform 1, ESP_3DES 1w0d: ISAKMP: attributes in transform: 1w0d: ISAKMP: authenticator is HMAC-MD5 1w0d: ISAKMP: encaps is 1 1w0d: ISAKMP: SA life type in seconds 1w0d: ISAKMP: SA life duration (VPI) of 0x0 0x20 0xC4 0x9B 1w0d: IPSEC(validate_proposal): transform proposal (prot 3, trans 3, hmac_alg 1) not supported 1w0d: ISAKMP (0:2): atts not acceptable. Next payload is 0 1w0d: ISAKMP (0:2): Checking IPSec proposal 4 1w0d: ISAKMP: transform 1, ESP_3DES 1w0d: ISAKMP: attributes in transform: 1w0d: ISAKMP: authenticator is HMAC-SHA 1w0d: ISAKMP: encaps is 1 1w0d: ISAKMP: SA life type in seconds 1w0d: ISAKMP: SA life duration (VPI) of 0x0 0x20 0xC4 0x9B 1w0d: ISAKMP (0:2): atts are acceptable. 1w0d: IPSEC(validate_proposal_request): proposal part #1, (key eng. msg.) INBOUND local= 10.1.1.1, remote= 10.0.0.1, local_proxy= 10.1.1.1/255.255.255.255/0/0 (type=1), remote_proxy= 10.16.20.2/255.255.255.255/0/0 (type=1), protocol= ESP, transform= esp-3des esp-sha-hmac, lifedur= 0s and 0kb, spi= 0x0(0), conn_id= 0, keysize= 0, flags= 0x4 1w0d: ISAKMP (0:2): processing NONCE payload. message ID = 132557281 1w0d: ISAKMP (0:2): processing ID payload. message ID = 132557281 1w0d: ISAKMP (0:2): processing ID payload. message ID = 132557281 1w0d: ISAKMP (0:2): asking for 1 spis from ipsec 1w0d: ISAKMP (0:2): Node 132557281, Input = IKE_MESG_FROM_PEER, IKE_QM_EXCH Old State = IKE_QM_READY New State = IKE_QM_SPI_STARVE 1w0d: IPSEC(key_engine): got a queue event... 1w0d: IPSEC(spi_response): getting spi 245824456 for SA from 10.1.1.1 to 10.0.0.1 for prot 3 1w0d: ISAKMP: received ke message (2/1) 1w0d: ISAKMP (0:2): sending packet to 10.0.0.1 (R) QM_IDLE 1w0d: ISAKMP (0:2): Node 132557281, Input = IKE_MESG_FROM_IPSEC, IKE_SPI_REPLY Old State = IKE_QM_SPI_STARVE New State = IKE_QM_R_QM2 1w0d: ISAKMP (0:2): received packet from 10.0.0.1 (R) QM_IDLE 1w0d: ISAKMP (0:2): Creating IPSec SAs 1w0d: inbound SA from 10.0.0.1 to 10.1.1.1 (proxy 10.16.20.2 to 10.1.1.1) 1w0d: has spi 0xEA6FBC8 and conn_id 2000 and flags 4 1w0d: lifetime of 2147483 seconds 1w0d: outbound SA from 10.1.1.1 to 10.0.0.1 (proxy 10.1.1.1 to 10.16.20.2 ) 1w0d: has spi 1009463339 and conn_id 2001 and flags C 1w0d: lifetime of 2147483 seconds 1w0d: ISAKMP (0:2): deleting node 132557281 error FALSE reason "quick mode done (await()" 1w0d: ISAKMP (0:2): Node 132557281, Input = IKE_MESG_FROM_PEER, IKE_QM_EXCH Old State = IKE_QM_R_QM2 New State = IKE_QM_PHASE2_COMPLETE 1w0d: IPSEC(key_engine): got a queue event...

1w0d: IPSEC(initialize_sas):, (key eng. msg.) INBOUND local= 10.1.1.1, remote= 10.0.0.1, local_proxy= 10.1.1.1/0.0.0.0/0/0 (type=1), remote_proxy= 10.16.20.2/0.0.0.0/0/0 (type=1), protocol= ESP, transform= esp-3des esp-sha-hmac, lifedur= 2147483s and 0kb, spi= 0xEA6FBC8(245824456), conn_id= 2000, keysize= 0, flags= 0x4 1w0d: IPSEC(initialize_sas):, (key eng. msg.) OUTBOUND local= 10.1.1.1, remote= 10.0.0.1, local_proxy= 10.1.1.1/0.0.0.0/0/0 (type=1), remote_proxy= 10.16.20.2/0.0.0.0/0/0 (type=1), protocol= ESP, transform= esp-3des esp-sha-hmac, lifedur= 2147483s and 0kb, spi= 0x3C2B302B(1009463339), conn_id= 2001, keysize= 0, flags= 0xC 1w0d: IPSEC(create_sa): sa created, (sa) sa_dest= 10.1.1.1, sa_prot= 50, sa_spi= 0xEA6FBC8(245824456), sa_trans= esp-3des esp-sha-hmac, sa_conn_id= 2000 1w0d: IPSEC(create_sa): sa created, (sa) sa_dest= 10.0.0.1, sa_prot= 50, sa_spi= 0x3C2B302B(1009463339), sa_trans= esp-3des esp-sha-hmac, sa_conn_id= 2001 1w0d: ISAKMP: received ke message (4/1) 1w0d: ISAKMP: Locking CONFIG struct 0x830BF118 for crypto_ikmp_config_handle_kei_mess, count 3 1w0d: ISAKMP (0:1): purging SA., sa=83196748, delme=83196748 1w0d: ISAKMP: Unlocking CONFIG struct 0x830BF118 on return of attributes, count 2 1w0d: ISAKMP (0:2): received packet from 10.0.0.1 (R) QM_IDLE 1w0d: ISAKMP (0:2): processing HASH payload. message ID = -1273332908 1w0d: ISAKMP (0:2): processing SA payload. message ID = -1273332908 1w0d: ISAKMP (0:2): Checking IPSec proposal 1 1w0d: ISAKMP: transform 1, ESP_3DES 1w0d: ISAKMP: attributes in transform: 1w0d: ISAKMP: authenticator is HMAC-MD5 1w0d: ISAKMP: encaps is 1 1w0d: ISAKMP: SA life type in seconds 1w0d: ISAKMP: SA life duration (VPI) of 0x0 0x20 0xC4 0x9B 1w0d: IPSEC(validate_proposal): transform proposal (prot 3, trans 3, hmac_alg 1) not supported 1w0d: ISAKMP (0:2): atts not acceptable. Next payload is 0 1w0d: ISAKMP (0:2): skipping next ANDed proposal (1) 1w0d: ISAKMP (0:2): Checking IPSec proposal 2 1w0d: ISAKMP: transform 1, ESP_3DES 1w0d: ISAKMP: attributes in transform: 1w0d: ISAKMP: authenticator is HMAC-SHA 1w0d: ISAKMP: encaps is 1 1w0d: ISAKMP: SA life type in seconds 1w0d: ISAKMP: SA life duration (VPI) of 0x0 0x20 0xC4 0x9B 1w0d: ISAKMP (0:2): atts are acceptable. 1w0d: ISAKMP (0:2): Checking IPSec proposal 2 1w0d: ISAKMP (0:2): transform 1, IPPCP LZS 1w0d: ISAKMP: attributes in transform: 1w0d: ISAKMP: encaps is 1 1w0d: ISAKMP: SA life type in seconds 1w0d: ISAKMP: SA life duration (VPI) of 0x0 0x20 0xC4 0x9B 1w0d: IPSEC(validate_proposal): transform proposal (prot 4, trans 3, hmac_alg 0) not supported 1w0d: ISAKMP (0:2): atts not acceptable. Next payload is 0 1w0d: ISAKMP (0:2): Checking IPSec proposal 3 1w0d: ISAKMP: transform 1, ESP_3DES 1w0d: ISAKMP: attributes in transform: 1w0d: ISAKMP: authenticator is HMAC-MD5 1w0d: ISAKMP: encaps is 1 1w0d: ISAKMP: SA life type in seconds 1w0d: ISAKMP: SA life duration (VPI) of 0x0 0x20 0xC4 0x9B 1w0d: IPSEC(validate_proposal): transform proposal (prot 3, trans 3, hmac_alg 1) not supported 1w0d: ISAKMP (0:2): atts not acceptable. Next payload is 0 1w0d: ISAKMP (0:2): Checking IPSec proposal 4 1w0d: ISAKMP: transform 1, ESP_3DES 1w0d: ISAKMP: attributes in transform: 1w0d: ISAKMP: authenticator is HMAC-SHA 1w0d: ISAKMP: encaps is 1 1w0d: ISAKMP: SA life type in seconds 1w0d: ISAKMP: SA life duration (VPI) of 0x0 0x20 0xC4 0x9B 1w0d: ISAKMP (0:2): atts are acceptable. 1w0d: IPSEC(validate_proposal_request): proposal part # vpn2611#1, (key eng. msg.) INBOUND local= 10.1.1.1, remote= 10.0.0.1, local_proxy= 14.38.0.0/255.255.0.0/0/0 (type=4), remote_proxy= 10.16.20.2/255.255.255.255/0/0 (type=1), protocol= ESP, transform= esp-3des esp-sha-hmac,

lifedur= 0s and 0kb, spi= 0x0(0), conn_id= 0, keysize= 0, flags= 0x4 1w0d: ISAKMP (0:2): processing NONCE payload. message ID = -1273332908 1w0d: ISAKMP (0:2): processing ID payload. message ID = -1273332908 1w0d: ISAKMP (0:2): processing ID payload. message ID = -1273332908 1w0d: ISAKMP (0:2): asking for 1 spis from ipsec 1w0d: ISAKMP (0:2): Node -1273332908, Input = IKE_MESG_FROM_PEER, IKE_QM_EXCH Old State = IKE_QM_READY New State = IKE_QM_SPI_STARVE 1w0d: IPSEC(key_engine): got a queue event... 1w0d: IPSEC(spi_response): getting spi 593097454 for SA from 10.1.1.1 to 10.0.0.1 vpn2611# vpn2611#2 for prot 3 1w0d: ISAKMP: received ke message (2/1) 1w0d: ISAKMP (0:2): sending packet to 10.0.0.1 (R) QM_IDLE 1w0d: ISAKMP (0:2): Node -1273332908, Input = IKE_MESG_FROM_IPSEC, IKE_SPI_REPLY Old State = IKE_QM_SPI_STARVE New State = IKE_QM_R_QM2 1w0d: ISAKMP (0:2): received packet from 10.0.0.1 (R) QM_IDLE 1w0d: ISAKMP (0:2): Creating IPSec SAs 1w0d: inbound SA from 10.0.0.1 to 10.1.1.1 (proxy 10.16.20.2 to 14.38.0.0) 1w0d: has spi 0x2359F2EE and conn_id 2002 and flags 4 1w0d: lifetime of 2147483 seconds 1w0d: outbound SA from 10.1.1.1 to 10.0.0.1 (proxy 14.38.0.0 to 10.16.20.2 ) 1w0d: has spi 1123818858 and conn_id 2003 and flags C 1w0d: lifetime of 2147483 seconds 1w0d: ISAKMP (0:2): deleting node -1273332908 erro vpn2611#un ar FALSE reason "quick mode done (await()" 1w0d: ISAKMP (0:2): Node -1273332908, Input = IKE_MESG_FROM_PEER, IKE_QM_EXCH Old State = IKE_QM_R_QM2 New State = IKE_QM_PHASE2_COMPLETE 1w0d: IPSEC(key_engine): got a queue event... 1w0d: IPSEC(initialize_sas):, (key eng. msg.) INBOUND local= 10.1.1.1, remote= 10.0.0.1, local_proxy= 172.18.124..0/255.255.255.0/0/0 (type=4), remote_proxy= 10.16.20.2/0.0.0.0/0/0 (type=1), protocol= ESP, transform= esp-3des esp-sha-hmac, lifedur= 2147483s and 0kb, spi= 0x2359F2EE(593097454), conn_id= 2002, keysize= 0, flags= 0x4 1w0d: IPSEC(initialize_sas):, (key eng. msg.) OUTBOUND local= 10.1.1.1, remote= 10.0.0.1, local_proxy= 172.18.124.0/255.255.255.0/0/0 (type=4), remote_proxy= 10.16.20.2/0.0.0.0/0/0 (type=1), protocol= ESP, transform= esp-3des esp-shll All possible debugging has been turned off vpn2611#a-hmac, lifedur= 2147483s and 0kb, spi= 0x42FC1D6A(1123818858), conn_id= 2003, keysize= 0, flags= 0xC 1w0d: IPSEC(create_sa): sa created, (sa) sa_dest= 10.1.1.1, sa_prot= 50, sa_spi= 0x2359F2EE(593097454), sa_trans= esp-3des esp-sha-hmac, sa_conn_id= 2002 1w0d: IPSEC(create_sa): sa created, (sa) sa_dest= 10.0.0.1, sa_prot= 50, sa_spi= 0x42FC1D6A(1123818858), sa_trans= esp-3des esp-sha-hmac, sa_conn_id= 2003 Logs de client Lancez le LogViewer sur le client vpn afin de visualiser les logs. Assurez-vous que le filtre est placé à la haute pour toutes les classes configurées. C'est un log témoin sorti : 1 16:48:10.203 03/05/02 Sev=Info/6 DIALER/0x63300002 Initiating connection. 2 16:48:10.203 03/05/02 Sev=Info/4 CM/0x63100002 Begin connection process 3 16:48:10.223 03/05/02 Sev=Info/4 CM/0x63100004 Establish secure connection using Ethernet 4 16:48:10.223 03/05/02 Sev=Info/4 CM/0x63100026 Attempt connection with server "10.1.1.1" 5 16:48:10.223 03/05/02 Sev=Info/6 IKE/0x6300003B

Attempting to establish a connection with 10.1.1.1. 6 16:48:10.273 03/05/02 Sev=Info/4 IKE/0x63000013 SENDING >>> ISAKMP OAK AG (SA, KE, NON, ID, VID, VID, VID) to 10.1.1.1 7 16:48:10.273 03/05/02 Sev=Info/4 IPSEC/0x63700014 Deleted all keys 8 16:48:10.994 03/05/02 Sev=Info/5 IKE/0x6300002F Received ISAKMP packet: peer = 10.1.1.1 9 16:48:10.994 03/05/02 Sev=Info/4 IKE/0x63000014 RECEIVING <<< ISAKMP OAK AG (SA, VID, VID, VID, VID, KE, ID, NON, HASH) from 10.1.1.1 10 16:48:10.994 03/05/02 Sev=Info/5 IKE/0x63000059 Vendor ID payload = 12F5F28C457168A9702D9FE274CC0100 11 16:48:10.994 03/05/02 Sev=Info/5 IKE/0x63000001 Peer is a Cisco-Unity compliant peer 12 16:48:10.994 03/05/02 Sev=Info/5 IKE/0x63000059 Vendor ID payload = AFCAD71368A1F1C96B8696FC77570100 13 16:48:10.994 03/05/02 Sev=Info/5 IKE/0x63000001 Peer supports DPD 14 16:48:10.994 03/05/02 Sev=Info/5 IKE/0x63000059 Vendor ID payload = 2D275A044215F48F531958AB2578EB2D 15 16:48:10.994 03/05/02 Sev=Info/5 IKE/0x63000059 Vendor ID payload = 09002689DFD6B712 16 16:48:11.025 03/05/02 Sev=Info/4 IKE/0x63000013 SENDING >>> ISAKMP OAK AG *(HASH, NOTIFY:STATUS_INITIAL_CONTACT) to 10.1.1.1 17 16:48:11.045 03/05/02 Sev=Info/5 IKE/0x6300002F Received ISAKMP packet: peer = 10.1.1.1 18 16:48:11.045 03/05/02 Sev=Info/4 IKE/0x63000014 RECEIVING <<< ISAKMP OAK INFO *(HASH, NOTIFY:STATUS_RESP_LIFETIME) from 10.1.1.1 19 16:48:11.045 03/05/02 Sev=Info/5 IKE/0x63000044 RESPONDER-LIFETIME notify has value of 86400 seconds 20 16:48:11.045 03/05/02 Sev=Info/5 IKE/0x63000046 This SA has already been alive for 1 seconds, setting expiry to 86399 seconds from now 21 16:48:11.075 03/05/02 Sev=Info/5 IKE/0x6300002F Received ISAKMP packet: peer = 10.1.1.1 22 16:48:11.075 03/05/02 Sev=Info/4 IKE/0x63000014 RECEIVING <<< ISAKMP OAK TRANS *(HASH, ATTR) from 10.1.1.1 23 16:48:11.075 03/05/02 Sev=Info/4 CM/0x63100015 Launch xauth application 24 16:48:14.920 03/05/02 Sev=Info/4 CM/0x63100017 xauth application returned 25 16:48:14.920 03/05/02 Sev=Info/4 IKE/0x63000013 SENDING >>> ISAKMP OAK TRANS *(HASH, ATTR) to 10.1.1.1 26 16:48:14.990 03/05/02 Sev=Info/5 IKE/0x6300002F Received ISAKMP packet: peer = 10.1.1.1 27 16:48:14.990 03/05/02 Sev=Info/4 IKE/0x63000014 RECEIVING <<< ISAKMP OAK TRANS *(HASH, ATTR) from 10.1.1.1 28 16:48:14.990 03/05/02 Sev=Info/4 CM/0x6310000E Established Phase 1 SA. 1 Phase 1 SA in the system 29 16:48:15.000 03/05/02 Sev=Info/4 IKE/0x63000013 SENDING >>> ISAKMP OAK TRANS *(HASH, ATTR) to 10.1.1.1 30 16:48:15.010 03/05/02 Sev=Info/5 IKE/0x6300005D Client sending a firewall request to concentrator 31 16:48:15.010 03/05/02 Sev=Info/5 IKE/0x6300005C Firewall Policy: Product=Cisco Integrated Client, Capability= (Centralized Policy Push).

32 16:48:15.010 03/05/02 Sev=Info/4 IKE/0x63000013 SENDING >>> ISAKMP OAK TRANS *(HASH, ATTR) to 10.1.1.1 33 16:48:15.141 03/05/02 Sev=Info/5 IKE/0x6300002F Received ISAKMP packet: peer = 10.1.1.1 34 16:48:15.141 03/05/02 Sev=Info/4 IKE/0x63000014 RECEIVING <<< ISAKMP OAK TRANS *(HASH, ATTR) from 10.1.1.1 35 16:48:15.141 03/05/02 Sev=Info/5 IKE/0x63000010 MODE_CFG_REPLY: Attribute = INTERNAL_IPV4_ADDRESS:, value = 10.16.20.2 36 16:48:15.141 03/05/02 Sev=Info/5 IKE/0xA3000017 MODE_CFG_REPLY: The received (INTERNAL_ADDRESS_EXPIRY) attribute and value (86395) is not supported 37 16:48:15.141 03/05/02 Sev=Info/5 IKE/0x6300000E MODE_CFG_REPLY: Attribute = APPLICATION_VERSION, value = Cisco Internetwork Operating System Software IOS (tm) C2600 Software (C2600-JK9O3S-M), Version 12.2(8)T, RELEASE SOFTWARE (fc2) TAC Support: http://www.cisco.com/tac Copyright (c) 1986-2002 by cisco Systems, Inc. Compiled Thu 14-Feb-02 16:50 by ccai 38 16:48:15.141 03/05/02 Sev=Info/5 IKE/0x6300000D MODE_CFG_REPLY: Attribute = MODECFG_UNITY_SPLIT_INCLUDE (# of split_nets), value = 0x00000001 39 16:48:15.141 03/05/02 Sev=Info/5 IKE/0x6300000F SPLIT_NET #1 subnet = 172.18.124.0 mask = 255.255.255.0 protocol = 0 src port = 0 dest port=0 40 16:48:15.141 03/05/02 Sev=Info/4 CM/0x63100019 Mode Config data received 41 16:48:15.151 03/05/02 Sev=Info/5 IKE/0x63000055 Received a key request from Driver for IP address 10.1.1.1, GW IP = 10.1.1.1 42 16:48:15.151 03/05/02 Sev=Info/4 IKE/0x63000013 SENDING >>> ISAKMP OAK QM *(HASH, SA, NON, ID, ID) to 10.1.1.1 43 16:48:15.361 03/05/02 Sev=Info/4 IPSEC/0x63700014 Deleted all keys 44 16:48:15.461 03/05/02 Sev=Info/5 IKE/0x6300002F Received ISAKMP packet: peer = 10.1.1.1 45 16:48:15.461 03/05/02 Sev=Info/4 IKE/0x63000014 RECEIVING <<< ISAKMP OAK QM *(HASH, SA, NON, ID, ID, NOTIFY:STATUS_RESP_LIFETIME) from 10.1.1.1 46 16:48:15.461 03/05/02 Sev=Info/5 IKE/0x63000044 RESPONDER-LIFETIME notify has value of 3600 seconds 47 16:48:15.461 03/05/02 Sev=Info/5 IKE/0x63000045 RESPONDER-LIFETIME notify has value of 4608000 kb 48 16:48:15.461 03/05/02 Sev=Info/4 IKE/0x63000013 SENDING >>> ISAKMP OAK QM *(HASH) to 10.1.1.1 49 16:48:15.461 03/05/02 Sev=Info/5 IKE/0x63000058 Loading IPsec SA (Message ID = 0x07E6A9E1 OUTBOUND SPI = 0x0EA6FBC8 INBOUND SPI = 0x3C2B302B) 50 16:48:15.461 03/05/02 Sev=Info/5 IKE/0x63000025 Loaded OUTBOUND ESP SPI: 0x0EA6FBC8 51 16:48:15.471 03/05/02 Sev=Info/5 IKE/0x63000026 Loaded INBOUND ESP SPI: 0x3C2B302B 52 16:48:15.471 03/05/02 Sev=Info/4 CM/0x6310001A One secure connection established 53 16:48:15.511 03/05/02 Sev=Info/6 DIALER/0x63300003 Connection established. 54 16:48:15.581 03/05/02 Sev=Info/6 DIALER/0x63300008 MAPI32 Information - Outlook not default mail client

55 16:48:16.553 03/05/02 Sev=Info/4 IPSEC/0x63700010 Created a new key structure 56 16:48:16.553 03/05/02 Sev=Info/4 IPSEC/0x6370000F Added key with SPI=0xc8fba60e into key list 57 16:48:16.553 03/05/02 Sev=Info/4 IPSEC/0x63700010 Created a new key structure 58 16:48:16.553 03/05/02 Sev=Info/4 IPSEC/0x6370000F Added key with SPI=0x2b302b3c into key list 59 16:48:26.357 03/05/02 Sev=Info/5 IKE/0x63000055 Received a key request from Driver for IP address 172.18.124.159, GW IP = 10.1.1.1 60 16:48:26.357 03/05/02 Sev=Info/4 IKE/0x63000013 SENDING >>> ISAKMP OAK QM *(HASH, SA, NON, ID, ID) to 10.1.1.1 61 16:48:26.668 03/05/02 Sev=Info/5 IKE/0x6300002F Received ISAKMP packet: peer = 10.1.1.1 62 16:48:26.668 03/05/02 Sev=Info/4 IKE/0x63000014 RECEIVING <<< ISAKMP OAK QM *(HASH, SA, NON, ID, ID, NOTIFY:STATUS_RESP_LIFETIME) from 10.1.1.1 63 16:48:26.668 03/05/02 Sev=Info/5 IKE/0x63000044 RESPONDER-LIFETIME notify has value of 3600 seconds 64 16:48:26.668 03/05/02 Sev=Info/5 IKE/0x63000045 RESPONDER-LIFETIME notify has value of 4608000 kb 65 16:48:26.668 03/05/02 Sev=Info/4 IKE/0x63000013 SENDING >>> ISAKMP OAK QM *(HASH) to 10.1.1.1 66 16:48:26.668 03/05/02 Sev=Info/5 IKE/0x63000058 Loading IPsec SA (Message ID = 0xB41A7B54 OUTBOUND SPI = 0x2359F2EE INBOUND SPI = 0x42FC1D6A) 67 16:48:26.668 03/05/02 Sev=Info/5 IKE/0x63000025 Loaded OUTBOUND ESP SPI: 0x2359F2EE 68 16:48:26.668 03/05/02 Sev=Info/5 IKE/0x63000026 Loaded INBOUND ESP SPI: 0x42FC1D6A 69 16:48:26.668 03/05/02 Sev=Info/4 CM/0x63100022 Additional Phase 2 SA established. Informations connexes Request For Comments (RFC) Exemples et notes techniques de configuration 1992-2010 Cisco Systems Inc. Tous droits réservés. Date du fichier PDF généré: 17 octobre 2015 http://www.cisco.com/cisco/web/support/ca/fr/109/1094/1094478_ipsec_radius_config.html