Easy VPN configuration problems

Hello

I have 6.2 (2) Version PIX PIX 515E. I am trying to setup the easy VPN server to this topic. This pix not recognized the next line of the comand.

Crypto-map dynamic 70 outside_dyn_map Road opposite value

Crypto isakmp nat-traversal 70

or isakmp nat-traversal 70

3 tunnel-group

is there a command line I can use inplace of them. I have also attached my config so I would be very grateful if someone could check and advice me what to do to raise this connection.

Thank you

Take a look at this:

http://www.Cisco.com/en/us/products/HW/vpndevc/ps2030/products_configuration_example09186a0080241a0d.shtml

Yes nat - t is available on 6.3.x and above and no it is not enabled by default on the PIX / ASA. It is IOS.

Please note if useful, cordially

Farrukh

Tags: Cisco Security

Hi all

I configured easy VPN on my ASA, but when I type the following command, it gives me this error as indicated:

SA - Gate (config) # crypto ipsec transform-set esp-3des esp-md5-hmac RIGHT
3DES/AES algorithms require an activation key for VPN-3DES-AES.
ASA - Gate (config) # crypto AMFM dynamic-map transform 100-set RIGHT
ERROR: there is no set of transformation with the "RIGHT" tag.

So this question about the features permitted on SAA and if so, what is required to complete the easy VPN configuration.

N.B.: sh version of ASA is attached.

EBIC-2007 a écrit :

Bonjour à tous,

J’ai configuré le VPN facile sur mon ASA, mais, quand je tape la commande suivante, il me donne cette erreur comme indiqué :

SA-Gate(config) # crypto ipsec transform-set MONJEU esp-3des esp-md5-hmac
Les algorithmes 3DES/AES nécessitent une clé d’activation de VPN-3DES-AES.
ASA-Gate(config) # MONJEU crypto dmap dynamique-carte 100 transform-set
ERREUR : ensemble de transformation avec le tag « MONJEU » n’existe pas.

Donc, cette question concernant les fonctionnalités autorisées sur ASA et si donc, ce qui est requis pour terminer la configuration VPN facile.

N.B. : sh version d’ASA est jointe.

Easy VPN with the Tunnel Interface virtual IPSec dynamic

Hi all

I configured easy vpn remote on a cisco 1841 and dynamic server easy vpn with virtual tunnel interface on the server (cisco 7200, 12.4.15T14)

http://www.Cisco.com/en/us/partner/prod/collateral/iosswrel/ps6537/ps6586/ps6635/prod_white_paper0900aecd803645b5.html

It works with easy vpn remote to the client mode and mode network-extesión, but it doesn't seem to work when I configure mode plus network on the client of the cpe, or when I try to have TWO inside the ez crypto interfaces. On the customer's site, I see two associations of security, but on the server PE site only security SA!

Without virtual dynamic tunnel interface, dynamic map configuration is ok... This is a limitation of the virtual tunnnel dynamic interface?

Federica

If one side is DVTI and the other uses a dynamic map, it does support only 1 SA. If the two end uses DVTI or the two end uses dynamic card then it supports several SAs.

Here is the note of documentation for your reference:
```
Note: Multiple inside interfaces are supported only when the Cisco Easy VPN server and the Cisco Easy VPN client have the same type of Easy VPN configuration. In other words, both must use a Legacy Easy VPN configuration, or both must use a DVTI configuration.
```
Here's the URL:

http://www.Cisco.com/en/us/docs/iOS/sec_secure_connectivity/configuration/guide/sec_easy_vpn_rem_ps6441_TSD_Products_Configuration_Guide_Chapter.html#wp1046365

Hope that answers your question.

Easy VPN with IPSec VPN L2L (Site - to - Site) in the same ASA 5505

Hi Experts,

We have an ASA 5505 in our environment, and currently two IPSec VPN L2L tunnels are established. But we intend to connect with VPN (Network Extension Mode) easy to another site as a customer. Is it possible to configure easy VPN configurations by keeping the currently active IPSec L2L VPN(Site-to-Site) tunnels? If not possible is there any work around?

Here's the warning we get then tried to configure the easy VPN Client.

NOCMEFW1 (config) # vpnclient enable

* Delete "nat (inside) 0 S2S - VPN"

* Detach crypto card attached to the outside interface

* Remove the tunnel groups defined by the user

* Remove the manual configuration of ISA policies

CONFLICT of CONFIG: Configuration that would prevent the Cisco Easy VPN Remo success

you

operation was detected and listed above. Please solve the

above a configuration and re - activate.

Thanks and greetings

ANUP sisi

"Dynamic crypto map must be installed on the server device.

Yes, dynamic crypto is configured on the EasyVPN server.

Thank you

The anyconnect vpn easy vpn Remote communication problem

Hi team,

I have a problem of communication of the anyconnect vpn easy vpn Remote I´ll explain better below and see the attachment
topology:

(1) VPN Tunnel between branch HQ - That´s OK
(2) VPN Tunnel between Client AnyConnect to HQ - that s OK

The idea is that the Anyconnect Client is reaching the local Branch Office network, but has not reached.
Communication is established just when I begin a session (icmp or rdp) branch to the AnyConnect Client,.
in this way, the communication is OK, but just for a few minutes.

Could you help me?
Below the IOS version and configurations

ASA5505 Version 8.4 (7) 23 (Headquarters)
ASA5505 Version 7.0000 23 (branch)

Configuration of the server easy VPN (HQ) *.

Crypto dynamic-map DYNAMIC - map 5 set transform-set ESP-AES-256-SHA ikev1
Crypto card outside-link-2_map 1 ipsec-isakmp DYNAMIC-map Dynamics
Crypto map link-outside-2_map-65535-isakmp dynamic ipsec SYSTEM_DEFAULT_CRYPTO_MAP
Crypto map interface outside-link-2_map outside-link-2

ACL_EZVPN list standard access allowed 10.0.0.0 255.255.255.0
ACL_EZVPN list standard access allowed 192.168.1.0 255.255.255.0
ACL_EZVPN list standard access allowed 192.168.50.0 255.255.255.0
ACL_EZVPN list standard access allowed 10.10.0.0 255.255.255.0

internal EZVPN_GP group policy
EZVPN_GP group policy attributes
Split-tunnel-policy tunnelspecified
value of Split-tunnel-network-list ACL_EZVPN
allow to NEM
type tunnel-group EZVPN_TG remote access
attributes global-tunnel-group EZVPN_TG
Group Policy - by default-EZVPN_GP
IPSec-attributes tunnel-group EZVPN_TG
IKEv1 pre-shared-key *.

object-group network Obj_VPN_anyconnect-local
object-network 192.168.1.0 255.255.255.0
object-network 192.168.15.0 255.255.255.0
object-group network Obj-VPN-anyconnect-remote
object-network 192.168.50.0 255.255.255.0
the NAT_EZVPN_Source object-group network
object-network 192.168.1.0 255.255.255.0
object-network 10.10.0.0 255.255.255.0
the NAT_EZVPN_Destination object-group network
object-network 10.0.0.0 255.255.255.0

destination of Obj_VPN_anyconnect local Obj_VPN_anyconnect-local static NAT (inside, outside-link-2) Obj - VPN static source -.

Remote AnyConnect VPN - Obj anyconnect-remote non-proxy-arp-search to itinerary
destination NAT (inside, outside-link-2) static source NAT_EZVPN_Source NAT_EZVPN_Source NAT_EZVPN_Destination static

NAT_EZVPN_Destination no-proxy-arp-search to itinerary
NAT (outside-link-2, outside-link-2) static source Obj-VPN-anyconnect-remote Obj-VPN-anyconnect-remote static destination

NAT_EZVPN_Destination NAT_EZVPN_Destination non-proxy-arp-search route

Configuration VPN AnyConnect (HQ) *.

WebVPN
Select the outside link 2
by default-idle-timeout 60
AnyConnect essentials
AnyConnect image disk0:/anyconnect-win-2.5.2014-k9.pkg 1
AnyConnect profiles Remote_Connection_for_TS_Users disk0: / remote_connection_for_ts_users.xml
AnyConnect enable
tunnel-group-list activate

tunnel of splitting allowed access list standard 192.168.1.0 255.255.255.0
tunnel of splitting allowed access list standard 192.168.15.0 255.255.255.0
tunnel of splitting allowed access list standard 10.0.0.0 255.255.255.0

internal clientgroup group policy
attributes of the strategy of group clientgroup
WINS server no
value of server DNS 192.168.1.41
client ssl-VPN-tunnel-Protocol
Split-tunnel-policy tunnelspecified
Split-tunnel-network-list value split tunnel
ipconnection.com.br value by default-field
WebVPN
AnyConnect Dungeon-Installer installed
time to generate a new key 30 AnyConnect ssl
AnyConnect ssl generate a new method ssl key
AnyConnect value Remote_Connection_for_TS_Users type user profiles
AnyConnect ask flawless anyconnect

type tunnel-group sslgroup remote access
tunnel-group sslgroup General-attributes
address vpnpool pool
authentication-server-group DC03
Group Policy - by default-clientgroup
tunnel-group sslgroup webvpn-attributes
enable IPConnection-vpn-anyconnect group-alias

object-group network Obj_VPN_anyconnect-local
object-network 192.168.1.0 255.255.255.0
object-network 192.168.15.0 255.255.255.0
object-group network Obj-VPN-anyconnect-remote
object-network 192.168.50.0 255.255.255.0
the NAT_EZVPN_Source object-group network
object-network 192.168.1.0 255.255.255.0
object-network 10.10.0.0 255.255.255.0
the NAT_EZVPN_Destination object-group network
object-network 10.0.0.0 255.255.255.0

destination of Obj_VPN_anyconnect local Obj_VPN_anyconnect-local static NAT (inside, outside-link-2) Obj - VPN static source -.

Remote AnyConnect VPN - Obj anyconnect-remote non-proxy-arp-search to itinerary
destination NAT (inside, outside-link-2) static source NAT_EZVPN_Source NAT_EZVPN_Source NAT_EZVPN_Destination static

NAT_EZVPN_Destination no-proxy-arp-search to itinerary
NAT (outside-link-2, outside-link-2) static source Obj-VPN-anyconnect-remote Obj-VPN-anyconnect-remote static destination

NAT_EZVPN_Destination NAT_EZVPN_Destination non-proxy-arp-search route

Hello

communication works when you send the traffic of easyvpn derivation because it froms the IPSEC SA to pool local subnet and anyconnect HQ. The SA formed only when the branch initiates the connection as it's dynamic peer connection to HQ ASA.

When there no SA between branch and HQ for this traffic, HQ ASA has no idea on where to send the anyconnect to network traffic.

I hope this explains the cause.

Kind regards

Averroès.

Easy VPN server on 1811 configuration

I'm trying to configure easy VPN server on my router from 1811 to allow remote users to access resources on our corporate network. I used the wizard to perform the configuration for the easy VPN, but when I test the VPN it fails to check the dependent components. He said to me that AAA authentication, authorization and Global Address Pool are all "not configured." I have configured AAA on MDS under additional tasks, so I don't know where I am going wrong. Any help is greatly appreciated.

Brandon,

the below URL - provide almost all the examples of configuration for the 18xx series.

http://conft.com/en/us/products/ps5853/prod_configuration_examples_list.html

HTH.

Cisco 831 - easy VPN server

Hello

I am trying to create an easy VPN server on Cisco 831. When I "test" the easy VPN he said that it tested successfully, but when I try to VPN in the router of the built in Windows XP VPN client, I'm unable to connect.

Does anyone have recommendations for how to configure easy VPN? I basically just selected all the default options. I was not able to find tutorials in the Cisco online documentation.

Do I need to have the Cisco VPN client to connect to the Cisco router?

Other thoughts?

Your IP address pool you are trying to assign to remote users is part of your local network, which is not the best way to assign the ip address to the VPN Clients, and I've seen a lot of problems in the past were route it not forwards the packets to the client. This allows you to change the POOL of something other than your LAN. E.g. 192.168.1.0/24.

Also, make sure that you re - configure your 102 ACL accordingly.

Once you make changes, try to connect again and let me know how it goes.

Kind regards

Arul

* Please note all useful messages *.

IOS Easy VPN Server / Radius attributes

Hello

I made an easy VPN server installation with a running 12.2 2621XM router (15) output T5. VPN Clients/users are authenticated against Cisco ACS 3.2 by RADIUS.

It works fine, but there is a problem that I can't solve. Each user must have the same VPN assigned IP address whenever it is authenticated.

The ACS sends the right radius attribute (box-IP-Address) back to square of IOS, but this address is not assigned to the client. The customer always gets the next available IP address in the local set on the router.

How can I solve this problem?

You will find the relevant parts of the configuration and a RADIUS "deb" below.

Kind regards

Christian

AAA - password password:

AAA authentication calls username username:

RADIUS AAA authentication login local users group

RADIUS AAA authorization network default local group

crypto ISAKMP policy 1

Group 2

!

crypto ISAKMP policy 3

md5 hash

preshared authentication

Group 2

ISAKMP crypto identity hostname

!

ISAKMP crypto client configuration group kh_vpn

mypreshared key

pool mypool

!

Crypto ipsec transform-set esp-3des esp-sha-hmac shades

!

mode crypto dynamic-map 1

shades of transform-set Set

!

users list card crypto mode client authentication

card crypto isakmp authorization list by default mode

card crypto client mode configuration address respond

dynamic mode 1-isakmp ipsec crypto map mode

!

interface FastEthernet0/1

IP 192.168.100.41 255.255.255.248

crypto map mode

!

IP local pool mypool 172.16.0.2 172.16.0.10!

Server RADIUS attribute 8 include-in-access-req

RADIUS-server host 192.168.100.13 key auth-port 1645 acct-port 1646 XXXXXXXXXXXXXXXX

RADIUS server authorization allowed missing Type of service

deb RADIUS #.

00:03:28: RADIUS: Pick NAS IP for you = tableid 0x83547CDC = 0 cfg_addr = 0.0.0.0 best_a

DDR = 192.168.100.26

00:03:28: RADIUS: ustruct sharecount = 2

00:03:28: RADIUS: success of radius_port_info() = 0 radius_nas_port = 1

00:03:28: RADIUS (00000000): send request to access the id 192.168.100.13:1645 21645.

4, len 73

00:03:28: RADIUS: authenticator 89 EA 97 56 12 B1 C5 C2 - C0 66 59 47 F7 88 96

68

00:03:28: RADIUS: NAS-IP-Address [4] 6 192.168.100.26

00:03:28: RADIUS: NAS-Port-Type [61] Async 6 [0]

00:03:28: RADIUS: username [1] 10 "vpnuser1".

00:03:28: RADIUS: Calling-Station-Id [31] 13 "10.1.14.150".

00:03:28: RADIUS: User-Password [2] 18 *.

00:03:28: RADIUS: receipt of 192.168.100.13:1645, Access-Accept, id 21645/4 l

in 108

00:03:28: RADIUS: authenticator C1 7 29 56 50 89 35 B7 - 92 7 b 1 has 32 87 15 6

A4

00:03:28: RADIUS: Type of Service [6] 6 leavers [5]

00:03:28: RADIUS: connection-ip-addr-host [14] 6 255.255.255.255

00:03:28: RADIUS: Tunnel-Type [64] 6 01:ESP [9]

00:03:28: RADIUS: Tunnel-Password [69] 21 *.

00:03:28: RAY: box-IP-Netmask [9] 6 255.255.255.0

00:03:28: RADIUS: Framed-IP-Address [8] 6 172.16.0.5

00:03:28: RADIUS: [25] the class 37

00:03:28: RADIUS: 43 49 53 43 4F 41 43 53 3 A 30 30 30 30 30 31 30 [CISCOACS:0

000010]

00:03:28: RADIUS: 2F 33 63 30 61 38 36 34 31 61 76 70 75 73 [3/c0a8641a 6F 2F

/vpnus]

00:03:28: RADIUS: 65 72 31 [1]

00:03:28: RADIUS: saved the authorization for user 83547CDC to 83548430 data

00:03:29: RADIUS: authentication for data of the author

00:03:29: RADIUS: Pick NAS IP for you = tableid 0x82A279FC = 0 cfg_addr = 0.0.0.0 best_a

DDR = 192.168.100.26

00:03:29: RADIUS: ustruct sharecount = 3

00:03:29: RADIUS: success of radius_port_info() = 0 radius_nas_port = 1

00:03:29: RADIUS (00000000): send request to access the id 192.168.100.13:1645 21645.

5, len 77

00:03:29: RADIUS: authenticator 13 B2 A6 CE BF B5 DA 7th - 7B F0 F6 0b A2 35 60

E3

00:03:29: RADIUS: NAS-IP-Address [4] 6 192.168.100.26

00:03:29: RADIUS: NAS-Port-Type [61] Async 6 [0]

00:03:29: RADIUS: username [1] 8 'kh_vpn '.

00:03:29: RADIUS: Calling-Station-Id [31] 13 "10.1.14.150".

00:03:29: RADIUS: User-Password [2] 18 *.

00:03:29: RADIUS: Type of Service [6] 6 leavers [5]

00:03:29: RADIUS: receipt of 192.168.100.13:1645, Access-Accept, id 21645/5 l

in 94

00:03:29: RADIUS: authenticator C4 F5 2F C3 EE 56 DA C9 - 05 D6 F5 5 d EF 74 23

AF

00:03:29: RADIUS: Type of Service [6] 6 leavers [5]

00:03:29: RADIUS: connection-ip-addr-host [14] 6 255.255.255.255

00:03:29: RADIUS: Tunnel-Type [64] 6 01:ESP [9]

00:03:29: RADIUS: Tunnel-Password [69] 21 *.

00:03:29: RADIUS: [25] class 35

00:03:29: RADIUS: 43 49 53 43 4F 41 43 53 3 A 30 30 30 30 30 31 30 [CISCOACS:0

000010]

00:03:29: RADIUS: 2F 34 63 30 61 38 36 34 31 61 2F 6 b 5F 68 76 70 [4/c0a8641a

[/ kh_vp]

00:03:29: RADIUS: 6 [n]

00:03:29: RADIUS: saved the authorization for user 82A279FC to 82A27D3C data

Assignment of an IP address via a server Raidus is currently not supported, even if your Radius Server is through an IP address, the router will ignore it and just assign an IP address from the pool locla. In fact, the pool room is the only way to assign IP addresses currently.

On the only way to do what you want right now is to create different groups VPN, each reference to a local IP pool with an address in it. Then ask each user connect to the appropriate by their VPN client group.

Yes, messy, but just try to provide a solution for you.

Help with 1921 SRI Easy VPN remote w / Easy VPN Site-to-Site access

I have two 1921 ISR routers configured with easy site to site VPN. I configured VPN each ISR ACL so that all networks on each site can communicate with the private networks of the other site. I have a 1921 SRI also configured as an easy VPN server.

Problem: when a remote user connects to the easy VPN server, the user can only access private networks on the site of the VPN server. I added the IP network that is used for remote users (i.e. the Easy VPN Server IP pool) to each VPN ACL 1921, but the remote user still cannot access other sites private network via the VPN site to another and vice versa.

Problem: I also have a problem with the easy VPN server, do not place a static host route in its routing table when he established a remote connection to the remote user and provides the remote user with an IP address of the VPN server's IP pool. The VPN server does not perform this task the first time the user connects. If the user disconnects and reconnects the router VPN Server does not have the static host route in its routing table for the new IP address given on the later connection.

Any help is appreciated.

THX,

Greg

Hello Greg,.

The ASAs require the "same-security-traffic intra-interface permits" to allow through traffic but routers allow traversed by default (is there no need for equivalent command).

Therefore, VPN clients can access A LAN but can't access the Remote LAN B on the Site to Site.

You have added the pool of the VPN client to the ACL for the interesting site to Site traffic.

You must also add the Remote LAN B to the ACL of tunneling split for VPN clients (assuming you are using split tunneling).

In other words, the VPN router configuration has for customers VPN should allow remote control B LAN in the traffic that is allowed for the VPN clients.

You can check the above and do the following test:

1. try to connect to the remote VPN the B. LAN client

2. check the "sh cry ips his" for the connection of the VPN client and check if there is a surveillance society being built between the pool and Remote LAN B.

Federico.

How to put all through traffic the easy vpn client VPN server

Hi people

I want to ask you, how to put all of the server the easy vpn client VPN traffic through.

I mean, I have a server vpn at home, and if I connect to the vpn from outside server, to be with an IP address of my home.

There is the configuration up to now. Where is the problem?

ROUTER1 #sh running-config

Building configuration...

Current configuration: 5744 bytes

!

! Last configuration change at 19:51:18 UTC Wed Sep 4 2013 by cska

!

version 15.1

horodateurs service debug datetime msec

Log service timestamps datetime msec

no password encryption service

!

ROUTER1 hostname

!

boot-start-marker

usbflash0:CVO boot-BOOT Setup. CFG

boot-end-marker

!

!

!

AAA new-model

!

!

AAA authentication login ciscocp_vpn_xauth_ml_1 local

AAA authorization ciscocp_vpn_group_ml_1 LAN

!

!

!

!

!

AAA - the id of the joint session

!

Service-module wlan-ap 0 autonomous bootimage

Crypto pki token removal timeout default 0

!

Crypto pki trustpoint TP-self-signed-1604488384

enrollment selfsigned

name of the object cn = IOS - Self - signed - certificate - 1604488384

revocation checking no

!

!

TP-self-signed-1604488384 crypto pki certificate chain

certificate self-signed 01

3082022B 30820194 02020101 300 D 0609 2A 864886 F70D0101 04050030 A0030201

2 060355 04031326 494F532D 53656 C 66 2 AND 536967 6E65642D 43657274 31312F30

69666963 31363034 34383833 6174652D 3834301E 170 3133 30383239 31313539

32395A 17 0D 323030 31303130 30303030 305A 3031 06035504 03132649 312F302D

4F532D53 5369676E 656C662D 43 65727469 66696361 74652 31 36303434 65642D

38383338 3430819F 300 D 0609 2A 864886 01050003, 818, 0030, 81890281 F70D0101

8100CD 57 F1436ED2 8D9E8B99 B6A76D45 FE56716D D99765A9 1722937C F5603F9F

528E27AF 87A24C3D 276FBA1C A5E7C580 CE99748E 39458C 74 862C 2870 16E29F75

7A7930E1 15FA5644 D7ECF257 BF46C470 A3A17AEB 7AB56194 68BFB803 144B7B10

D3722BDD D1FD5E99 8068B77D A1703059 9F0578C7 F7473811 0421490D 627F25C5

4 HAS 250203 010001A 3 53305130 1 130101 FF040530 030101FF 301F0603 0F060355

551 2304 18301680 141B 1326 C111DF7F 9F4ED888 EFE2999A 4C50CDD8 06 12301

03551D0E 04160414 1B1326C1 11DF7F9F 4ED888EF E2999A4C 50CDD812 300 D 0609

2A 864886 04050003 81810096 BD0C2B16 799DB6EE E2C9B7C4 72FEAAAE F70D0101

FF87465C FB7C5248 CFA08E68 522EA08A 4B18BF15 488D D53D9A43 CB400B54 8006

CB21BDFB AA27DA9C C79310B6 BC594A7E D6EDF81D 0DB7D2C1 9EF7251B 19A 75403

211B1E6B 840FE226 48656E9F 67DB4A93 CE75045B A986F0AD 691EE188 7FB86D3F

E43934FA 3D62EC90 8F37590B 618B0C

quit smoking

IP source-route

!

!

!

!

CISCO dhcp IP pool

import all

network 192.168.1.0 255.255.255.0

DNS-server 195.34.133.21 212.186.211.21

default router 192.168.1.1

!

!

IP cef

No ipv6 cef

!

Authenticated MultiLink bundle-name Panel

license udi pid CISCO892W-AGN-E-K9 sn FCZ1530C209

!

!

username privilege 15 secret 5 cska $1$ $8j6G 2sMHqIxJX8MQU6vpr75gp1

!

!

!

!

!

!

crypto ISAKMP policy 1

BA 3des

preshared authentication

Group 2

!

Configuration group customer isakmp crypto VPNGR

vpngroup key

DNS 212.186.211.21 195.34.133.21

WINS 8.8.8.8

domain chello.at

pool SDM_POOL_1

ACL 120

netmask 255.255.255.0

ISAKMP crypto ciscocp-ike-profile-1 profile

match of group identity VPNGR

client authentication list ciscocp_vpn_xauth_ml_1

ISAKMP authorization list ciscocp_vpn_group_ml_1

client configuration address respond

virtual-model 1

!

!

Crypto ipsec transform-set esp-SHA-ESP-3DES-3des esp-sha-hmac

!

Profile of crypto ipsec CiscoCP_Profile1

security association idle time 86400 value

game of transformation-ESP-3DES-SHA

set of isakmp - profile ciscocp-ike-profile-1

!

!

Bridge IRB

!

!

!

!

interface Loopback0

192.168.4.1 IP address 255.255.255.0

IP nat inside

IP virtual-reassembly in

!

interface BRI0

no ip address

encapsulation hdlc

Shutdown

Multidrop ISDN endpoint

!

interface FastEthernet0

!

interface FastEthernet1

!

interface FastEthernet2

!

interface FastEthernet3

!

interface FastEthernet4

!

interface FastEthernet5

!

FastEthernet6 interface

!

interface FastEthernet7

!

interface FastEthernet8

no ip address

Shutdown

automatic duplex

automatic speed

!

type of interface virtual-Template1 tunnel

IP unnumbered Loopback0

ipv4 ipsec tunnel mode

Tunnel CiscoCP_Profile1 ipsec protection profile

!

interface GigabitEthernet0

Description Internet

0023.5a03.b6a5 Mac address

customer_id GigabitEthernet0 dhcp IP address

NAT outside IP

IP virtual-reassembly in

automatic duplex

automatic speed

!

wlan-ap0 interface

description of the Service interface module to manage the embedded AP

192.168.9.2 IP address 255.255.255.0

ARP timeout 0

!

interface GigabitEthernet0 Wlan

Description interface connecting to the AP the switch embedded internal

!

interface Vlan1

no ip address

Bridge-Group 1

Bridge-Group 1 covering-disabled people

!

interface BVI1

IP 192.168.1.1 255.255.255.0

IP nat inside

IP virtual-reassembly in

!

local IP SDM_POOL_1 192.168.4.3 pool 192.168.4.245

IP forward-Protocol ND

!

!

IP http server

local IP http authentication

IP http secure server

overload of IP nat inside source list 110 interface GigabitEthernet0

IP nat inside source static tcp 192.168.1.5 3389 interface GigabitEthernet0 3389

IP nat inside source static udp 192.168.1.5 3389 interface GigabitEthernet0 3389

IP nat inside source static tcp 192.168.1.5 21 interface GigabitEthernet0 21

IP nat inside source static udp 192.168.1.5 21 interface GigabitEthernet0 21

IP nat inside source static tcp 192.168.1.4 3389 interface GigabitEthernet0 3390

IP nat inside source static udp 192.168.1.4 3389 interface GigabitEthernet0 3390

overload of IP nat inside source list 120 interface GigabitEthernet0

IP route 0.0.0.0 0.0.0.0 dhcp

!

exploitation forest esm config

access list 101 ip allow a whole

access-list 110 permit ip 192.168.1.0 0.0.0.255 any

access list 111 permit tcp any any eq 3389

access-list 120 allow ip 192.168.4.0 0.0.0.255 any

!

!

!

!

!

!

!

control plan

!

Bridge Protocol ieee 1

1 channel ip bridge

!

Line con 0

line 2

no activation-character

No exec

preferred no transport

transport of entry all

transport output pad rlogin udptn ssh telnet

line to 0

line vty 0 4

privilege level 15

preferred transport ssh

entry ssh transport

transportation out all

!

Thanks in advance

To do this you must make the following changes:

(1) disable split Tunneling by deleting the ACL of your configuration of the client group.
(2) enable NAT for VPN traffic by adding 'ip nat inside' to your virtual model of the client network to the ACL that controls your PAT.

Edit: Theses are the changes to your config (also with a little cleaning):

Configuration group customer isakmp crypto VPNGR

No 120 LCD

!

type of interface virtual-Template1 tunnel

IP nat inside

!

no nat ip inside the source list 120 interface GigabitEthernet0 overload

!

access-list 110 permit ip 192.168.4.0 0.0.0.255 any

no access-list 120 allow ip 192.168.4.0 0.0.0.255 any

Sent by Cisco Support technique iPad App

Easy VPN configuration problems

Similar Questions

Hi all

Bonjour à tous,

Maybe you are looking for