NAT-XLATE-FAILURE on the VPN from Site to site connection.

Similar Questions

• How can I block a VPN from site to Site traffic

  I configured a VPN from Site to Site, the wizard on a

  ASA 5510 and it works.

  However, I want to restrict http traffic only.

  I tried to change the ACL entry that allows ip traffic to allow only http traffic, but that seems to block all traffic and translates into a journal entry:

  Inbound TCP connection doesn't deny x to Y/80 SYN flags on the incoming interface.

  I managed to block pings by entering an ACL rule to specifically deny icmp, but I would like to deny all except http.

  Any advice on how to achieve this appreciated.

  William.

  Hello

  Guess that's what you're looking for. See the Bidirectional VPN filter configuration section.

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

• Limit remote traffic in a VPN from Site to Site

  I have a setup VPN from Site to Site in a lab using two ASA5505s environment.  VPN site to Site is functional however, what I wanted to do is to deny all traffic between the Remote LAN and not allow a single host to access the local network. Is it convenient or can it be done? If so, what Miss me the following ACL do not seem to effect?

  Remote LAN: 172.16.1.0/24
  LAN: 192.168.1.0/24

  outside_access_in list extended access permitted tcp 172.16.1.100 host 192.168.1.100 lytic 5000 10000
  outside_access_in list extended access deny ip 172.16.1.0 255.255.255.0 192.168.1.0 255.255.255.0
  Access-group outside_access_in in interface outside

  Appreciate any help that anyone can give.

  Hi tsabsuavyaj,

  By default, the sysopt connection VPN-enabled command is enabled which will bypass your list of access-interface referenced for all VPN traffic.

  To resolve this problem, you can:

  • Run the command No sysopt connection VPN-enabled. Caution with this, because it has global effect, which means it will interrogate ACL interface for all incoming VPN traffic.
  • Change your proxy-ACL (aka ACL interesting traffic) so that your remote control network is simply the address of the host that you would like to have access to your network. In so doing, nothing else is routed through your tunnel L2L at the remote end. This ACL must be mirrored on the other side (remote), so that the proxy-ACL must change so that its share of the 'Local network' is only the appropriate host and nothing else.

  Please let me know if you have further questions/clarification.

  Kind regards

  Kevin

  * Do not forget to note the useful messages but also to mark it as 'responded' once your problem is solved. This will help others find your solution more quickly.

• SA520W VPN from Site to Site with several VLANs

  Hello

  I have a customer here with several VLANS in their places who wants to set up a VPN from Site to site between 2 devices SA520W. Unfortunately I can not find a way to set it up. In the VPN policy, I can choose between everything (which is not what I want, I want only traffict between subnets the routed via VPN), IP address unique, a beach (in a subnet) and a subnet itself - but only one. I don't find a way to configure several subnets in the selection of local traffic and remotely. Adding another IKE policy between the 2 sites does not either (which is good normally).

  Any ideas? Anything I'm doing wrong?

  Thank you for your help.

  Best regards

  Thomas

  I know that if you have an ASA or a router, you can define as VLANS to pass through the tunnel.

  Do not have access to a SA520W to test...

  A recommendation might be to post the question on the SMB community where they answered questions related to this product, just to check what other people did.

  Federico.

• ASA (v9.1) VPN from Site to Site with IKEv2 and certificates CEP/NDE MS

  Hi all

  I am currently a problem with VPN Site to Site with IKEv2 and certifiactes as an authentication method.

  Here is the configuration:

  We have three locations with an any to any layer 2 connection. I created each ASA (ASA5510 worm 9.1) to establish one VPN of Site connection to the other for the other two places. Setting this up with pre shared keys and certificates that are signed by the CA MS administrator manually work correctly.

  But when we try to enroll these certificates through the Protocol, CEP/NDE his does not work.

  Here are my steps:

  1 configure the CA Turstpoint to apply to the certification authority

  2. request that the CA through the SCEP protocol works fine

  3. set up a Trustpoint and a pair of keys for the S2S - VPN connection

  4. registration form identity certificate CA via the SCEP Protocol with a one time password works fine

  5. set the trustpoint created as for the S2S - VPN IKEv2 authentication method.

  Now I did it also for the other site of the VPN Tunnel. But when I ping on a host that is on a different location to make appear the Tunnel VPN - the VPN session is not established. In the debugs I see that there are a few problems during authentication of the remote peer.

  On the MS that I see that the certifactes of identity for both ASAs are communicated and not revoked or pending state. The certificate based on the model of the "IPSec (Offline).

  When the CA-Admin and a certificate me manually based on a copy of the model of "Domaincontroller" connection is successfully established.

  So I would like to know which is the correct certificate for IP-Sec peers template to use for the Protocol, CEP and MS Enterprise CA (its server 2008R2 of Microsoft Enterprise)?

  Anyone done this before?

  ASA requires that the local and Remote certificate contains EKU IP Security Tunnel Endpoint (1.3.6.1.5.5.7.3.6) (aka IP Security Tunnel termination). You can create a Microsoft CA model to add.

  If you absolutely must go with the 'bad' cert, there is a command

  ignore-ipsec-keyusage

  but it is obsolete and not recommended.

  Meanwhile at the IETF:

  RFC 4809

  3.1.6.3 extended Key use

  Extended Key Usage (EKU) indications are not required.  The presence
  or lack of an EKU MUST NOT cause an implementation to fail an IKE
  connection.
  

• How could I give priority to my network connections, (without turning off the strap attached, as it took), so that it uses the internet from my main network connection?

  Prioritize network connections

  OK, here's the situation.
  I have a regular ethernet connection that provides me with a network and the internet.
  I have also a tablet PC which I attach to my PC so I can use it as a controller. (Not that it is important, but it's for a DAW/Midi controller)

  My problem is that whenever I place my tablet, PC starts by ignoring my normal connection and taking the internet from my Tablet (even when it is not connected to the internet). As a result, my internet is de-energized once I tie it, if I'm not as under the wifi on my tablet.

  My question is, how could I give priority to my network connections, (without turning off the strap attached, as it took), so that it uses the internet from my main network connection?

  Hello

  As well as the troubleshooting provided by Boumediene steps, you can also try the steps in this link. Some screenshots are also available on the link for a better understanding.

  http://www.howtogeek.com/HOWTO/27994/how-to-change-the-priority-of-wiredwireless-network-cards-in-Windows/

  Hope you will find this is useful.

• Inside Source NAT from the remote host and VPN from Site to Site

  Hi all

  I was in charge of the construction of a vpn tunnel with a firewall PIX of our business partner company and ASA of the other company of the firewall.  Traffic will be A partner business users will access my company Citrix server.  I want to source-pat the user traffic partner company to PIX of my business within the interface to its entry in my LAN to access my company Citrix server.  The partner company will be PAT'ing their traffic from users to a single ip address - Let's say for discussion end is 65.99.100.101.  There is the site to site vpn configuration, and configure nat be performed to allow this traffic in accordance with the above provisions.

  I'm more concerned about the accuracy of the configuration of the domain encryption because NAT is involved in this whole upward.  My goal is to NAT (of the other company company a) ip address to a routable ip address in my company network.

  The fundamental question here is should I include the ip address of real source (65.99.100.101) of the company the user or IP natted (10.200.11.9) in the field of encryption.

  In other words should the encryption field looks like this

  OPTION A.

  permit ip host 10.200.11.103 65.99.100.101

  OR

  OPTION B

  permit ip host 10.200.11.103 10.200.11.9

  I'm inclined to think it should look like OPTION A.  Here's the part of MY complete SOCIETY of the VPN configuration.  I've also attached a diagram illustrating this topology.

  Thanks in advance,

  Adil

  CONFIG BELOW

  ------------------------------------------------

  #################################################

  Object-group Config:

  #################################################

  the COMPANY_A_NETWORK object-group network

  Description company network access my company A firm Citrix

  host of the object-Network 65.99.100.101

  the MYCOMPANY_CITRIX_FARM object-group network

  Description farm Citrix accessible Takata by Genpact

  host of the object-Network 10.200.11.103

  ################################################

  Config of encryption:

  ################################################

  crypto ISAKMP policy 20

  preshared authentication

  3des encryption

  sha hash

  Group 2

  life 86400

  ********************************

  CRYPTO MAP

  ********************************

  crypto Outside_map 561 card matches the address Outside_561_cryptomap

  card crypto Outside_map 561 set peer 55.5.245.21

  Outside_map 561 transform-set ESP-3DES-SHA crypto card game

  ********************************

  TUNNEL GROUP

  ********************************

  tunnel-group 55.5.245.21 type ipsec-l2l

  IPSec-attributes tunnel-group 55.5.245.21

  pre-shared-key * 55.5.245.21

  *******************************

  FIELD OF CRYPTO

  *******************************

  Outside_561_cryptomap list extended access permitted ip object-group MYCOMPANY_CITRIX_FARM-group of objects COMPANY_A_NETWORK

  ###########################################

  NAT'ing

  ###########################################

  Global (inside) 9 10.200.11.9

  NAT (9 genpact_source_nat list of outdoor outdoor access)

  genpact_source_nat list extended access permit ip host 65.99.100.101 all

  genpact_source_nat list extended access permit ip host 65.99.100.102 all

  ! For not natting ip address of the Citrix server

  Inside_nat0 list extended access permitted ip object-group MYCOMPANY_CITRIX_FARM-group of objects COMPANY_A_NETWORK

  You must include pre - nat ip 65.99.x.x in your crypto-card, like you did.

  For me, config you provided here looks good and meets your needs.

  One thing, I do not see here the nat rule real 0, but there is the ACL that NAT. probably, you just forgot this rule.

  65.99.100.101 #sthash.mQm0FIOM.dpuf

• Need of the ACL kung fu for VPN from Site to Site ACL problem

  Group,

  Have a little problem I know is related to ACL. I wanted to have a few experts to take a look at my config please. Here's the question:

  Attempt to create a site between two offices, but for some reason any that they cannot ping each other. It is a strange thing.

  97.XX.231.22 <-->71.xx.160.123

  I can ping both firewalls from the outside using a computer to another, but from the internal firewall utilities, they cannot ping each other. At the same time I can ping to their respective gateways.

  Secondly, I did an interior outside translation as you can see here for 80 & 443 preventing me from browsing http and https via VPN for Remote LAN, can it be modified to allow access? I can access when I dial in via VPN client but not via permanent VPN tunnel. Here is the config.

  no ip nat service sip 5060 udp port

  IP nat inside source map route SDM_RMAP_1 interface GigabitEthernet0/0 overload

  IP nat inside source static tcp 10.41.14.103 80 71.xx.160.123 80 extensible

  IP nat inside source static tcp 10.41.14.103 71.xx.160.123 expandable 443 443

  IP route 0.0.0.0 0.0.0.0 71.xx.160.121

  IP route 10.67.188.32 255.255.255.224 10.41.14.99 6 permanent

  IP route 10.67.188.96 255.255.255.224 10.41.14.99 8 permanent

  IP route 10.200.107.0 255.255.255.0 10.41.14.99 9 permanent

  IP route 10.200.110.0 255.255.254.0 10.41.14.99 7 permanent

  IP route 74.200.107.0 255.255.255.0 10.41.14.99 5 permanent

  IP route 74.200.110.0 255.255.254.0 10.41.14.99 4 permanent

  IP route 208.67.188.32 255.255.255.224 10.41.14.99 2 Permanent

  IP route 208.67.188.96 255.255.255.224 10.41.14.99 3 permanent

  !

  auto discovering IP sla

  Logging trap errors

  host 192.168.10.29 record

  access-list 2 Note HTTP access class

  Note access-list category 2 CCP_ACL = 1

  Note access-list 2 Platinum LAN

  access-list 2 permit 10.41.14.0 0.0.0.255

  access-list 2 refuse any

  Access-list 101 remark rules Master

  Note access-list 101 category CCP_ACL = 1

  Note access-list 101 FaxFinder WWW traffic

  access-list 101 permit tcp any host 71.xx.160.123 eq www

  Note access-list 101 traffic HTTPS FaxFinder

  access-list 101 permit tcp any host 71.xx.160.123 eq 443

  Note access-list 101 NTP Time Protocol

  access-list 101 permit udp any host 71.xx.160.123 eq ntp

  Access-list 101 remark IPSEC protocols

  access-list 101 permit udp any host 71.xx.160.123 eq non500-isakmp

  Access-list 101 remark IPSEC protocols

  access-list 101 permit udp any host 71.xx.160.123 eq isakmp

  Note access-list 101 traffic ESP

  access-list 101 permit esp any host 71.xx.160.123

  Note the access list 101 General License

  access list 101 ip allow a whole

  Note access-list 102 CCP_ACL category = 2

  access-list 102 deny ip 10.41.14.0 0.0.0.255 192.168.76.0 0.0.0.255

  Note access-list 102 IPSec rule

  access-list 102 deny ip 10.41.14.0 0.0.0.255 10.0.2.0 0.0.0.255

  Note access-list 102 IPSec rule

  access-list 102 deny ip 10.41.14.0 0.0.0.255 192.168.10.0 0.0.0.31

  Access-list 102 remark Platinum LAN NAT rule

  access-list 102 permit ip 10.41.14.0 0.0.0.255 any

  Note category from the list of access-104 = 4 CCP_ACL

  Note access-list 104 IPSec rule

  access-list 104. allow ip 10.41.14.0 0.0.0.255 192.168.10.0 0.0.0.31

  Note access-list 108 CCP_ACL category = 4

  access-list 108 allow ip 10.41.14.0 0.0.0.255 any

  Note access-list 109 IPSec rule

  Note access-list 109 CCP_ACL category = 4

  access-list 109 allow ip 10.41.14.0 0.0.0.255 192.168.76.0 0.0.0.255

  Note access-list 110 CCP_ACL category = 4

  Note access-list 110 IPSec rule

  access-list 110 permit ip 10.41.14.0 0.0.0.255 10.0.2.0 0.0.0.255

  not run cdp

  !

  allowed SDM_RMAP_1 1 route map

  corresponds to the IP 102

  There is more then one way how you can achieve this goal.

  (1) the best way is possible if the two VPN counterparts are IOS routers. Then you can migrate to virtual VPN - tunnel interfaces (VTI). With this, the external interface doesn't mix - and non-VPN-traffic VPN.

  (2) if VTI is not possible, you can restrict the translation to only non - VPN traffic using a roadmap:

  object-group network RFC1918

  10.0.0.0 255.0.0.0

  172.16.0.0 255.240.0.0

  192.168.0.0 255.255.0.0

  NAT-SERVER - 10.41.14.103 allowed 10 route map

  corresponds to the TRAFFIC-NAT-SERVER IP - 10.41.14.103

  TRAFFIC-NAT-SERVER extended IP access list - 10.41.14.103

  deny ip host 10.41.14.103 object-group RFC1918

  permit tcp host 10.41.14.103 eq 80 a

  allow a host EQ 10.41.14.103 tcp 443

  IP nat inside source static 10.41.14.103 71.xx... map route NAT-SERVER - 10.41.14.103

  What makes that?

  When your server communicates with a system with an address in the range RFC1918, then the road map does not correspond and the translation is not used. It is you, the VPN scenario. But if the server communicates with a non-RFC1918 address, then the translation is used and the server can be reached.

  --
  Don't stop once you have upgraded your network! Improve the world by lending money to low-income workers:
  http://www.Kiva.org/invitedBy/karsteni

• IPSEC VPN from Site to Site - NAT problem with address management

  Hi all

  I have two Cisco ASA 5505 performing of IPSEC Site to Site VPN. All traffic inside each firewall through the VPN tunnel and I have full connectivity. From site A, I can connect to the inside address of the ASA at the site B and launch of the ASDM or SSH, etc.

  The problem I have is when I'm logged on the ASA site B management traffic is given the external address. I created this as interesting traffic to get it to go through the VPN but I need to use the inside address of ASA B. The following is possible:

  • If I can make the ASA Site B to use inside interface as its address management (I already have management access to the inside Interface)
  • I have NAT can address external interfaces to Site B before moving through the VPN tunnel management traffic so that it appears to come from Site B inside the address
  • I can NAT VPN traffic as it appears in the Site A for management traffic to Site B on the right address.

  The problem is that my PRACTICE Please also come from this address and I need the application before being on an internal address to even if my CA.

  Thanks for any help.

  Ian

  Thanks, I understand what you are trying to achieve now.

  However, I think that I don't have good news for you. Unfortunately PEIE request can be initiated of the SAA within the interface, as there is no option to start the query from the inside interface. With other features of management such as AAA, logging, you have an option to specify what ASA desired originally to demand from interface, but CEP doesn't have this option.

  Here's how you can configure under the trustpoint crypto, but unfortunately by specifying the interface doesn't not part of option:

  http://www.Cisco.com/en/us/docs/security/ASA/asa84/command/reference/C5.html#wp2262210

• Refuse the remote user VPN to access PC using VPN from Site users to partner Site

  Hi Experts,

  Installation program:

  We have configured IPSEC Site - Site VPN between Cisco ASA 5510 and Sonicwall.

  Tunnel is in place and working well, we are able to access the remote workstation to partner and Vis Versa.

  
  

  Requirment: We want to deny remote VPN users, who are our partners access to the workstation.

  Example:

  Remote IP address range: 192.168.200.x/2r4

  Local IP address range: 192.168.10.x/24

  Deny traffic from 192.168.200.x/24 to 192.168.10.x/24

  Thanks in advance

  Kiran Kumar CH

  Hi Kiran,

  You want to deny certain IP addresses of the Remote LAN (of the L2L tunnel), to connect to your workstation?

  Thus, if the remote network 192.168.200.0/24, want to deny some of these machines to connect to 192.168.10.x?

  If this is the case, you can create ACL VPN (VPN filters) on the SAA to restrictive traffic through the tunnel from the IPs.

  Please clarify if I have misunderstood.

  Federico.

• How to install the VPN Client and the tunnel from site to site on Cisco 831

  How can I configure a Cisco 831 router (Branch Office) so that it will accept incoming VPN Client connections and initiate tunneling IPSec site to site on our hub site that uses a VPN 3005 concentrator?  I could get the tunnel to work by configuring it in a dynamic encryption card, but interesting traffic side Cisco 831 would not bring the tunnel upward.  I could only put on the side of the hub.  If I use a static encryption card and apply it to the external interface of the 831 I can get this working but then I couldn't get the VPN Client to work.

  Thank you.

  The dynamic map is called clientmap
  The static map is called mymap

  You should have:

  no card crypto not outmap 10-isakmp ipsec dynamic dynmap
  map mymap 10-isakmp ipsec crypto dynamic clientmap

  interface Ethernet1
  crypto mymap map

  Federico.

• VPN from Site to Site of 2600 NSA does not work after upgrade to 6.2.0.1/6.2.2.0 6.2.0.0 SonicOS

  Site to Site VPN using policy based or VPN type road works very well in NSA 2600 with SonicOS Enhanced 6.2.0.0 - 20n. However, in order to correct the poodle attacks on SSLv3, we improve our SonicOS to 6.2.0.1 - 24n and this make the VPN does not. We tried SonicOS 6.2.2.0 - 7n with the same result. However, the VPN works remotely locally, but not the reverse, i.e. one meaning outside of the local network. Here are the details of the VPN deployment:

  Distance: NetScreen SSG-5 or GSU - 320 M

  Local: SonicWall NSA-2600

  Policy type: Tunnel Interface

  Auth. method: IKE using preshared Secret

  IKE Phase 1 proposal: Main Mode, group 2, 3DES, SHA1

  Proposal of IPSec Phase 2: ESP 3DES SHA1

  Please advice if it is linked to the SSLv3 disabled on Ipsec or any setting that we can make the VPN works on SonicOS after 6.2.0.1, again thank you!

  After reading the Release Notes for Early Release SonicOS 6.2.2.0 - 12n NSA-2600, we have solved the problem easily. Here's the important part:

  IMPORTANT: SonicOS 6.2.2.0 includes a design change added in recent versions for the treatment of the traffic via the Interfaces of the VPN Tunnel. By default, NAT policies are now applied to this traffic. In SonicOS 6.2.0.0 and SonicOS 6.1.1.9 and 6.1.1.x earlier, traffic on the Interfaces of the VPN Tunnel was exempt from policies NAT. Transition one of these earlier versions to 6.2.2.0 may require configuration changes.

  In fact, the truth is since 6.2.0.1, they already have policies NAT for the Interfaces of the VPN Tunnel. So the solution, regardless of usage 6.2.0.1 or 6.2.2.0, is just to write your policy NAT there is source and services NAT to network strategy involved VPN Tunnel Interface, that will be fine. To be simple, just

  Original of the CBC	Definition of the CBC	Original dest	Definition of dest	SVC Original	Definition of SVC
  Any	Source language	Remote VPN network	Source language	Any	Source language

• Tunnel VPN remote Internet and VPN remote VPN from Site to Site traffic?

  Hello

  We try to remote traffic from our users VPN tunnel through our ASA 5510 as well as to allow the only access for remote user VPN traffic to the other end of the all our VPN site-to-site connected to the same ASA. Basically, we who want to VPN in the network in order to access all of our networks business. We try to get away with this without using split Tunneling.

  I can currently get internal traffic from the remote user VPN to reach all other vpn site-to-site tunnels without the internet in tunnel. The problem is when I add the following statement to the NAT:

  NAT (outside) 1 10.10.19.0 255.255.255.0 * 10.10.19.0 is the address of the remote VPN Client

  Internet traffic to the remote VPN starts to get in the tunnel, but I lose the opportunity to reach one of the other tunnels from site to site by the remote VPN tunnel.

  I also begin to receive the following errors in the journal of the ASA

  3 July 1, 2009 12:34:18 305005 10.10.19.255 137 no group of translation not found for udp src outside:10.10.19.3/137 dst outside:10.10.19.255/137

  Any help with how NAT statements must be defined for this work would be appreciated.

  Thank you

  Will be

  Will,

  the link of this post for your scenario of vpn hub & speak reference, you problem may be on exempt nat rules.

  Have a second look at your sheep rules.

  Be sure to eliminate tunnel rules related to rheumatoid arthritis, as appropriate, to not let him get in the way of splitting.

  http://forums.Cisco.com/eForum/servlet/NetProf?page=NetProf&Forum=security&topic=firewalling&TopicId=.ee6e1fa&fromOutline=true&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.2cc2e0f6/4

  If always emits discribe topology for l2ls and info logic RA and sanatized hub config asa... but I think if you look at the thread above, you should be able to solve.

  Concerning

• Configuration VPN from Site to Site on two ASA5505

  I have two ASA5505 ver 8.4 (6) and ver 9.0 (2) configured for a laboratory site to site vpn, but without success.  I could do everything outside address from two ASA ping, but could not ping the LAN on the other end of the ASA.  Here is the error message when you try to check if the VPN tunnel is established. For reference, the configurations are provided below.  Any help is very appreciated.

  ASA1 # show crypto isakmp his

  There are no SAs IKEv1

  There are no SAs IKEv2

  ASA1 # show crypto ipsec his

  There is no ipsec security associations

  ASA1:

  crypto ISAKMP allow outside

  the local object of net network

  subnet 192.168.1.0 255.255.255.0

  net remote object network

  Subnet 192.168.2.0 255.255.255.0

  !

  outside_1_cryptomap list of allowed ip object local net net access / remote

  tunnel-group 200.200.200.1 type ipsec-l2l

  IPSec-attributes tunnel-group 200.200.200.1

  pre-shared-key pass1234

  ISAKMP retry threshold 10 keepalive 2

  !

  part of pre authentication isakmp crypto policy 10

  crypto ISAKMP policy 10 3des encryption

  crypto ISAKMP policy 10 sha hash

  10 crypto isakmp policy group 2

  crypto ISAKMP policy life 10 86400

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

  card crypto outside_map 1 match address outside_1_cryptomap

  card crypto outside_map 1 set pfs Group1

  peer set card crypto outside_map 1 200.200.200.1

  card crypto outside_map 1 set of transformation-ESP-3DES-SHA

  outside_map interface card crypto outside

  !

  NAT (inside, outside) 1 local static source net net-local destination static remote net net / remote

  output

  ASA2:

  crypto ISAKMP allow outside

  the local object of net network

  Subnet 192.168.2.0 255.255.255.0

  net remote object network

  subnet 192.168.1.0 255.255.255.0

  !

  outside_1_cryptomap list of allowed ip object local net net access / remote

  tunnel-group 100.100.100.1 type ipsec-l2l

  IPSec-attributes tunnel-group 100.100.100.1

  pre-shared-key pass1234

  ISAKMP retry threshold 10 keepalive 2

  !

  part of pre authentication isakmp crypto policy 10

  crypto ISAKMP policy 10 3des encryption

  crypto ISAKMP policy 10 sha hash

  10 crypto isakmp policy group 2

  crypto ISAKMP policy life 10 86400

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

  card crypto outside_map 1 match address outside_1_cryptomap

  card crypto outside_map 1 set pfs Group1

  peer set card crypto outside_map 1 100.100.100.1

  card crypto outside_map 1 set of transformation-ESP-3DES-SHA

  outside_map interface card crypto outside

  !

  NAT (inside, outside) 1 local static source net net-local destination static remote net net / remote

  output

  ASA1 # sh run int

  !

  interface Ethernet0/0

  switchport access vlan 2

  !

  interface Ethernet0/1

  !

  interface Ethernet0/2

  !

  interface Ethernet0/3

  !

  interface Ethernet0/4

  !

  interface Ethernet0/5

  !

  interface Ethernet0/6

  !

  interface Ethernet0/7

  !

  interface Vlan1

  nameif inside

  security-level 100

  IP 192.168.1.1 255.255.255.0

  !

  interface Vlan2

  nameif outside

  security-level 0

  IP address dhcp setroute

  ASA1 #.

  ASA1 # ping 192.168.2.1

  Type to abort escape sequence.

  Send 5, echoes ICMP 100 bytes 192.168.2.1, time-out is 2 seconds:

  ?????

  Success rate is 0% (0/5)

  ASA1 # ping google.com

  Type to abort escape sequence.

  Send 5, echoes ICMP 100 bytes to 173.194.46.71, wait time is 2 seconds:

  !!!!!

  Success rate is 100 per cent (5/5), round-trip min/avg/max = 12/10/20 ms

  ASA1 #.

  ASA2 # sh run int

  !

  interface Ethernet0/0

  switchport access vlan 2

  !

  interface Ethernet0/1

  !

  interface Ethernet0/2

  Shutdown

  !

  interface Ethernet0/3

  Shutdown

  !

  interface Ethernet0/4

  Shutdown

  !

  interface Ethernet0/5

  Shutdown

  !

  interface Ethernet0/6

  Shutdown

  !

  interface Ethernet0/7

  Shutdown

  !

  interface Vlan1

  nameif inside

  security-level 100

  IP 192.168.2.1 255.255.255.0

  !

  interface Vlan2

  nameif outside

  security-level 0

  IP address dhcp setroute

  ASA2 # ping 192.168.1.1

  Type to abort escape sequence.

  Send 5, echoes ICMP 100 bytes to 192.168.1.1, time-out is 2 seconds:

  ?????

  Success rate is 0% (0/5)

  !

  ASA2 # ping google.com

  Type to abort escape sequence.

  Send 5, echoes ICMP 100 bytes to 173.194.46.64, wait time is 2 seconds:

  !!!!!

  Success rate is 100 per cent (5/5), round-trip min/avg/max = 14/10/20 ms

  ASA2 #.

  If you see any debugs the SAA, there is no encryption of any kind negoiations.

  The problem may be that you need to generate an interesting to match the ACL traffic.  I don't know if you on a physical laboratory or on GNS3.  If you use a physical laboratory, attach a laptop computer inside the interface and configure an IP address for this subnet.  You may need to do this for the other ASA.  Then iniatiate a ping to the other network.

• VPN from Site to Site and easy 871W

  I have a problem with the configuration of Site to site and easy both together on the same router 871W

  Something is working, but not everything.

  x.x.x.x - address IP WAN
  a.a.a.a - gw for WAN IP address
  z.z.z.z - IP address of the VPN Site-to Site
  192.168.201.0/25 - LAN
  192.168.200.0/24 - easy VPN address
  192.168.151.0/24 - Site-Site LAN

  Site-to-site work properly, everythings fine, but no easy VPN.

  Configuration of Cisco VPN Client:

  Home - x.x.x.x, group auth name - RemoteGroup, pass *.
  user test, pass *.

  I have a successful connection of Cisco VPN Client (I see a closed lock - connected status)

  Connection gave me the address 192.168.200.5.

  But I can't see LAN or LAN from Site to Site.

  And I don't have any idea what may be wrong.

  Finalny config:

  Quote:

  Current configuration: 8860 bytes ! version 12.4 no service button horodateurs service debug datetime msec Log service timestamps datetime msec encryption password service sequence numbers service ! hostname moj-waw-rtr ! boot-start-marker boot-end-marker ! logging buffered debugging 52000 Select the secret *. ! AAA new-model ! ! AAA authentication login default local AAA authentication login local remoteusers AAA authorization exec default local AAA authorization RemoteGroup LAN ! AAA - the id of the joint session ! resources policy ! IP subnet zero IP cef ! ! no ip domain search IP domain name waw.moj.pl name of the IP-server 194.204.152.34 name of the IP-server 193.178.240.2 ! ! Crypto pki trustpoint TP - self - signed-*. enrollment selfsigned the object cn = IOS-Self-Signed - Certificate name- revocation checking no rsakeypair TP - self - signed-*. ! ! crypto TP - self - signed pki certificate chain-*. certificate self-signed 01 quit smoking privilege secret 15 user username username secret privilege test 4 *. ! ! ! crypto ISAKMP policy 1 BA 3des preshared authentication Group 2 ISAKMP crypto key * address y.y.y.y the local address TOVPNPOOL pool-crypto isakmp client configuration ! ISAKMP crypto client configuration group RemoteGroup key *. pool TOVPNPOOL ISAKMP crypto vpnclient profile RemoteGroup group identity match function identity address 192.168.201.111 255.255.255.255 client authentication list remoteusers ISAKMP authorization list RemoteGroup client configuration address respond ! ! Crypto ipsec transform-set esp-3des esp-sha-hmac vpntowaw Crypto ipsec transform-set esp-3des esp-md5-hmac vpnwaw ! Crypto dynamic-map DYNAMICS 10 Set transform-set vpnwaw vpnclient Set isakmp-profile market arriere-route ! ! vpn_wro_waw 1 ipsec-isakmp crypto map defined peer y.y.y.y Set transform-set vpntowaw PFS Group1 Set match address 104 vpn_wro_waw card crypto 65535-isakmp ipsec dynamic DYNAMICS ! Bridge IRB ! ! interface FastEthernet0 spanning tree portfast

  
  !
  interface FastEthernet1
  spanning tree portfast
  !
  interface FastEthernet2
  spanning tree portfast
  !
  interface FastEthernet3
  spanning tree portfast
  !
  interface FastEthernet4
  Description $ETH - LAN$
  IP x.x.x.x 255.255.255.0
  IP access-group 102 to
  Check IP unicast reverse path
  no ip redirection
  no ip unreachable
  no ip proxy-arp
  NAT outside IP
  IP virtual-reassembly
  route IP cache flow
  automatic duplex
  automatic speed
  vpn_wro_waw card crypto
  !
  interface Dot11Radio0
  no ip address
  no ip redirection
  no ip unreachable
  no ip proxy-arp
  route IP cache flow
  !
  algorithms for encryption tkip encryption mode
  !
  encryption vlan 1 tkip encryption mode
  !
  SSID TO - WAW
  VLAN 1
  open authentication
  authentication wpa key management
  Comments-mode
  WPA - psk ascii *.
  !
  base speed - 1.0 2.0 basic basic-5, 5 6.0 9.0 basic-11, 0 12.0 18.0 24.0 36.0 48.0 54.0
  root of station-role
  No dot11 extensions aironet
  !
  interface Dot11Radio0.1
  encapsulation dot1Q 1 native
  no link-status of snmp trap
  No cdp enable
  Bridge-Group 1
  Bridge-group subscriber-loop-control 1
  Bridge-Group 1 covering-disabled people
  Bridge-Group 1 block-unknown-source
  No source of bridge-Group 1-learning
  unicast bridge-Group 1-floods
  !
  interface Vlan1
  Description $ETH - SW - LAUNCH, INTF-INFO-HWIC $$ $4ESW
  no ip address
  no ip redirection
  no ip unreachable
  no ip proxy-arp
  IP virtual-reassembly
  route IP cache flow
  IP tcp adjust-mss 1452
  Bridge-Group 1
  !
  interface BVI1
  IP 192.168.201.1 255.255.255.128
  IP access-group 101 in
  IP nat inside
  IP virtual-reassembly
  !
  local IP TOVPNPOOL 192.168.200.2 pool 192.168.200.101
  IP classless
  IP route 0.0.0.0 0.0.0.0 a.a.a.a
  !
  IP http server
  1 class IP http access
  local IP http authentication
  IP http secure server
  IP http timeout policy slowed down 60 life 86400 request 10000
  IP nat inside source static tcp 192.168.201.3 80 80 FastEthernet4 interface
  IP nat inside source overload map route SDM_RMAP_1 interface FastEthernet4
  !
  Remark SDM_ACL category of access list 1 = 1
  access-list 1 permit 192.168.201.0 0.0.0.127
  access-list 1 permit 192.168.151.0 0.0.0.255
  access-list 1 deny all
  Access-list 100 category SDM_ACL = 2 Note
  Note access-list 100 IPSec rule
  access-list 100 deny ip 192.168.201.0 0.0.0.127 192.168.3.0 0.0.0.255
  access-list 100 deny ip 192.168.201.0 0.0.0.127 192.168.2.0 0.0.0.255
  access-list 100 deny ip 192.168.201.0 0.0.0.127 192.168.151.0 0.0.0.255
  access-list 100 deny ip 192.168.201.0 0.0.0.127 192.168.200.0 0.0.0.255
  access-list 100 permit ip 192.168.201.0 0.0.0.127 all
  access list 101 remark self-generated by the configuration of the firewall SDM
  Note access-list 101 = 1 SDM_ACL category
  access-list 101 deny ip x.x.x.x 0.0.0.255 everything
  access-list 101 deny ip 255.255.255.255 host everything
  access-list 101 deny ip 127.0.0.0 0.255.255.255 everything
  access list 101 ip allow a whole
  Allow Access - list 101 tcp a whole
  access list 101 allow udp a whole
  access-list 101 permit icmp any one
  access-list 102 permit icmp any host x.x.x.x
  access-list 102 permit udp host 194.204.152.34 eq field host x.x.x.x
  access-list 102 permit udp host 193.178.240.2 eq field host x.x.x.x
  access-list 102 permit udp host host eq non500-isakmp x.x.x.x y.y.y.y
  access-list 102 permit udp host host eq isakmp x.x.x.x y.y.y.y
  access-list 102 permit esp host host x.x.x.x y.y.y.y
  access-list 102 permit ahp host host x.x.x.x y.y.y.y
  access-list 102 permit ip 192.168.151.0 0.0.0.255 192.168.201.0 0.0.0.127
  access-list 102 permit ip 192.168.200.0 0.0.0.255 192.168.201.0 0.0.0.127
  access-list 102 permit ip 192.168.2.0 0.0.0.255 192.168.201.0 0.0.0.127
  access-list 102 permit ip 192.168.3.0 0.0.0.255 192.168.201.0 0.0.0.127
  access-list 102 permit ip 192.168.201.0 0.0.0.127 all
  access-list 102 deny ip 10.0.0.0 0.255.255.255 everything
  access-list 102 deny ip 172.16.0.0 0.15.255.255 all
  access-list 102 deny ip 192.168.0.0 0.0.255.255 everything
  access-list 102 deny ip 127.0.0.0 0.255.255.255 everything
  access-list 102 deny ip 192.168.201.0 0.0.0.127 all
  access-list 102 refuse host ip 255.255.255.255 everything
  access-list 102 refuse host ip 0.0.0.0 everything
  access ip-list 102 permit a whole
  access-list 103 allow ip 192.168.200.0 0.0.0.255 any
  access-list 103 allow ip 192.168.151.0 0.0.0.255 any
  access-list 103 allow ip 192.168.201.0 0.0.0.127 all
  access-list 103 permit ip 192.168.2.0 0.0.0.255 any
  access-list 103 allow ip 192.168.3.0 0.0.0.255 any
  access-list 103 allow y.y.y.y ip 0.0.0.7 one
  access-list 103 deny ip any one
  Remark SDM_ACL category from the list of access-104 = 4
  Note access-list 104 IPSec rule
  access-list 104. allow ip 192.168.201.0 0.0.0.127 192.168.151.0 0.0.0.255
  access-list 104 allow 192.168.201.0 ip 0.0.0.127 192.168.2.0 0.0.0.255
  access-list 104 allow 192.168.201.0 ip 0.0.0.127 192.168.3.0 0.0.0.255
  access-list 104 allow 192.168.201.0 ip 0.0.0.127 192.168.200.0 0.0.0.255
  not run cdp
  allowed SDM_RMAP_1 1 route map
  corresponds to the IP 100
  !
  !
  control plan
  !
  Bridge Protocol ieee 1
  1 channel ip bridge
  !
  Line con 0
  no activation of the modem
  line to 0
  line vty 0 4
  access-series 103 in
  privilege level 15
  entry ssh transport
  !
  max-task-time 5000 Planner
  end

  Bartosz,

  If you want to ping on the other side of the IPsec-L2L tunnel system you must change your 104 ACL.

  to read

  IP RA_VPN_POOL subnet REMOTE_SUBNET_MASK to allow REMOTE_SUBNET.

  access-list 104 allow 192.168.201.0 ip 0.0.0.127 192.168.200.0 0.0.0.255<---- this="" means="" ..="" put="" into="" the="" static="" l2l ="" tunnel="" traffic="" from="" my="" local="" subnet="" going="" to="" my="" remote="" access="" vpn="" ...="" seems="">

  Marcin