Rule NAT VPN problem

Hello people, I had a lot of trouble trying to solve this problem, but hoping someone here can enlighten me.

I have a remote site that hosts a number of services that we manage remotely with an IPSec VPN connection. When connecting to the site connect us very well and can make most of the actions like RDP and connect to servers for maintenance, but a service fails to connect unless I have add a NAT rule exempt to the configuration of the router (ASA 5505).

Once this rule in place service work, but other services that initially worked work stoppage. In short, this rule must be in place while doing a single task, but then contracted for other tasks. I hope that there is some sort of rule or behavior, I can add to the ASDM configuration makes it so I don't have to manually add this rule whenever I connect.

Here are the details of the rule:

access-list 1 permit line outside_nat0_outbound extended ip 192.168.15.192 255.255.255.192 192.168.15.0 255.255.255.0

NAT (outside) 0 outside_nat0_outbound list access outside tcp udp 0 0 0

When the connection is established without the rule in place the ASDM syslog shows these warnings:

Deny tcp src inside: outside:10.100.32.203/135 dst61745 by access-group "inside_access_in" [0x0, 0x0]

The strange thing is 10.100.32.203 is IP internal my host computer. This is not yet the external IP address of the network I connect from.

Is it possible a problem with the VPN pool using a subset of the subnet of the VIRTUAL LAN inside? Inside VLAN is 192.168.15.0/24 and the VPN is 192.168.15.200 - 250. I am ready to reconfigure the VPN address pool but need to do remotely, and am unaware of how to do this reconfiguration safely without losing my remote access, since physical access to the router itself is currently very difficult.

If more details are needed, I am happy to give them.

Hi GrahamB,

Yes, the problem with too much running in subnet.

There are a lot of private-address available, so please create a new group policy and tunnel-group and fill

pool separate to value ip address and remote with it, when the new cluster to solve your problem, can safely remove the old one.

I hope this helps.

Thank you

Rizwan Muhammed.

Tags: Cisco Security

Similar Questions

  • Bizzare vShield Edge-NAT/VPN problem Post - 5.1 upgrade

    Hoping someone can shed some light on this issue for us - the TLDR is that NAT rules seem to be causing unexpected behavior on the VPN traffic after a vCloud 1.5 to 5.1 upgrade.

    Background: We work with a hosting provider to manage our vCloud environment. Quite simple - 2 ESXi hosts, a few NFS data stores. They have recently updated us of 1.5 and 5.1. For most of our committees, we have just one network of vSE/Routed that connects a subnet to a network of "WAN" and pulls a public IP address from a pool. Send us (NAT network address) and leave (firewall) ports (for example port 3389 for RDP) to the virtual machines selected. Most of these networks also have a VPN tunnel from site to site with a physical Firewall through the internet. After the upgrade, we went and converted our rules to match the period of initial and active INVESTIGATION "multiple interfaces" - effectively subtracts to compatibility mode. Everything was going well (even for devices of vSE always in compatibility mode)

    Question: We first noticed this, when a customer reported that they are unable to access a virtual machine via RDP using it is internal (protected VSE) IP through a VPN tunnel but could access the virtual machine via RDP using its public hostname/IP address. Allow us all traffic between the VPN (firewall has a whole: a rule for VPN traffic). When we connected to troubleshoot (just thinking that the VPN was down), we found that we could connect to any port on the computer through the VPN tunnel except 3389remote virtual. I can ping from the local subnet to the VM troubled on the VAPP network without problem. I was able to connect to other ports that have been opened on the remote virtual machine without problem. I couldn't connect to 3389 through the VPN.

    We thought he could be isolated, but found the question on each VSE we have: If there were a the DNAT rule to translate the inbound for a particular port, this port would be insensitive when traffic through the VPN tunnel that is meant to be the target of the DNAT rule.

    Someone has an idea what could be the cause?

    Looks like it is a problem experienced during the upgrade. These hidden firewall rules will not disappear until the firewall configuration is updated in some way. So go as - upgrade

    (1) upgrade VCD

    (2) update VSM

    (3) to redeploy the entry door to upgrade the edge of the gateway to version 5.1

    (4) convert the firewall rules to the new format (where firewall rules have no management interface or traffic)

    (5) to change the properties of the bridge and the multiple interface mode

    (6) change the specification of the firewall somehow, that is to add a dummy firewall and remove it, turn off, then turn on the firewall, etc..

    Which should cause the deny rule go away

  • pix 501 vpn problem

    Can connect, I see not all network resources.

    The Vpn Client, worm: 5.0.01, is running on an xp machine.

    It connects to the network is behind a 6.3 (5) pix501-worm.

    When the connection is established the remote client gets an address assigned to the pool 192.168.2.10 vpn - 192.168.2.25:

    The vpn client log shows:

    Line: 45 18:07:27.898 12/08/09 Sev = Info/4 CM / 0 x 63100034

    The virtual card has been activated:

    IP=192.168.2.10/255.255.255.0

    DNS = 0.0.0.0 0.0.0.0

    WINS = 0.0.0.0 0.0.0.0

    Area =

    Split = DNS names

    It is followed by these lines:

    46 18:07:27.968 12/08/09 Sev = WARNING/2 CVPND/0xE3400013

    AddRoute cannot add a route: code 87

    Destination 192.168.1.255

    Subnet mask 255.255.255.255

    Gateway 192.168.2.1

    Interface 192.168.2.10

    47 18:07:27.968 12/08/09 Sev = WARNING/2 CM/0xA3100024

    Failed to add the route. Network: c0a801ff, subnet mask: ffffffff, Interface: c0a8020a Gateway: c0a80201.

    48 18:07:28.178 12/08/09 Sev = Info/4 CM / 0 x 63100038

    Were saved successfully road to file changes.

    49 18:07:28.198 12/08/09 Sev = Info/6 CM / 0 x 63100036

    The routing table has been updated for the virtual card

    50 18:07:29.760 12/08/09 Sev = Info/4 CM/0x6310001A

    A secure connection established

    * ...

    I can ping the remote client, on an inside ip behind the same pix

    When I get the 'route add failure' above, but I cannot ping the computer name.

    I activated traversal of NAT using the PDM, but when I connect with this option, I get the error that the "remote endpoint is NOT behind a NAT device this end is behind a NAT device" and ping fails.

    Behind the pix are a few computers with no central server, so I'm failed a WINS server for remote clients.

    I created the vpn with the wizard.

    The configuration file is attached.

    Any suggestion would be appreciated.

    Kind regards

    Hugh

    Hugh, sure you can classify based on the whole conversation, but you don't have to do but be certainly provide assessments.

    To sum up the shrinking global problems, the main objective was to ensure configuration VPN RA on the PIX501 has been corrected.

    1. we have enabled NAT - T on the firewall - even if it wasn't the question, but need it either it should you RA other places - travseral NAT VPN sensitizes the firewall on the other ends NAT devices - here is some good information on NAT - T for reference in the future

    http://www.Microsoft.com/technet/community/columns/cableguy/cg0802.mspx

    2. we fixed the VPN-POOL/28 network as well as the access list and acl to be coherent crypto sheep.

    Here is a link for future reference with many PIX configuration scenarios

    http://www.Cisco.com/en/us/products/HW/vpndevc/ps2030/prod_configuration_examples_list.html

    Finally, your only question remaining, we can say is purely isolated with the customer software vpn and MAC machine.

    You could maybe try a different version of the client in the MAC, or also look at the release notes for the open caveats to avoid cisco cleint managing versions and MAC versions if there are problems.

    http://www.Cisco.com/en/us/products/sw/secursw/ps2308/prod_release_notes_list.html

    Concerning

  • % 305013-5-ASA: rules asymmetrical NAT matched for flows forward and backward; Connection refused because of the failure of the path opposite. NAT VPN clients problems after that put 8.3.2 to level.

    I've recently updated to 8.3.2 and I have been informed of these NAT changes, but even after reading the https://supportforums.cisco.com/docs/DOC-12569 I am still unable to rectify the communication network 192.168.100.0 VPN with hosts on 172.16.1.0 and 172.16.9.0. VPN clients connect to the external interface, and I try to ping inside and the demilitarized zone, respectable 172.16.1.0 and 172.16.9.0 hosts. VPN client shows that the two previously mentioned networks such as roads of security, but still not to the ping pong.

    # sh nat

    Manual NAT policies (Section 1)

    1 (inside) to the (whole) source static obj - 172.16.9.0 obj - 172.16.9.0 destination static obj - obj - unidirectional 192.168.100.0 192.168.100.0

    translate_hits = 0, untranslate_hits = 0

    2 (inside) to the (whole) source static obj - 172.16.1.0 obj - 172.16.1.0 destination static obj - obj - unidirectional 192.168.100.0 192.168.100.0

    translate_hits = 0, untranslate_hits = 0

    3 (inside) to the (whole) source static obj - 172.16.1.0 obj - 172.16.1.0 destination static obj - 172.16.12.0 obj - one-way 172.16.12.0

    translate_hits = 0, untranslate_hits = 0

    4 (dmz) to (outside) source static obj - 172.16.9.0 obj - 172.16.9.0 destination static obj - obj - unidirectional 192.168.100.0 192.168.100.0

    translate_hits = 0, untranslate_hits = 0

    5 (dmz) to (outside) source static obj - 172.16.9.0 obj - 172.16.9.0 destination static obj - 172.16.12.0 obj - one-way 172.16.12.0

    translate_hits = 0, untranslate_hits = 0

    Auto NAT policies (Section 2)

    1 (dmz), to the source (external) static obj - 172.16.9.5 interface tcp www www service

    translate_hits = 0, untranslate_hits = 142

    2 (dmz) (outdoor) source static obj - 172.16.9.5 - 01 interface service tcp 3389 3389

    translate_hits = 0, untranslate_hits = 2

    3 (dmz) (outdoor) source static obj - 172.16.9.5 - 02 interface tcp ldap ldap service

    translate_hits = 0, untranslate_hits = 0

    4 (dmz) (outdoor) source static obj interface - 172.16.9.5 - 03 service ftp ftp tcp

    translate_hits = 0, untranslate_hits = 0

    5 (dmz) to (outside) of the source static obj - 172.16.9.5 - 04 interface tcp smtp smtp service

    translate_hits = 0, untranslate_hits = 267

    6 (inside) source static obj - 172.16.9.0 172.16.9.0 (dmz)

    translate_hits = 4070, untranslate_hits = 224

    7 (inside) to (dmz) source static obj - 10.1.0.0 10.1.0.0

    translate_hits = 0, untranslate_hits = 0

    8 (inside) to (dmz) source static obj - 172.16.0.0 172.16.0.0

    translate_hits = 152, untranslate_hits = 4082

    9 (dmz) to dynamic interface of the obj - 172.16.9.0 - 01 source (outdoor)

    translate_hits = 69, untranslate_hits = 0

    10 (inside) to the obj_any interface dynamic source (external)

    translate_hits = 196, untranslate_hits = 32

    I think you must following two NAT config

    NAT (inside, outside) source static obj - 172.16.1.0 obj - 172.16.1.0 destination static obj - 192.168.100.0 obj - 192.168.100.0
    NAT (dmz, external) source static obj - 172.16.9.0 obj - 172.16.9.0 destination static obj - 192.168.100.0 obj - 192.168.100.0

    Please configure them and remove any additional NAT configuration and then try again.

  • Networks VPN NAT l2l problem-Dup-HELP!

    I use a router IOS as a VPN L2L device to connect my site to several different customer locations, some of them use the same internal IP addresses.  These VPNS have been working well.

    I recently added another client to this system and I am now having a problem with the new configuration.  With this configuration, I have NAT my internal addresses.  NAT works correctly, but it NAT my bad common NAT addresses and therefore do not generate the tunnel.

    My internal IP 10.10.x.x

    incorrect NAT pool 10.129.x.x

    decent NAT pool 10.99.x.x

    Help... :))

    Thank you

    The problem is simple. You have almost an identical ACL for two guests. As the first NAT rule has been added previously, it comes into play. To resolve this issue, you must set explicit host/subnet destination match instead of 'none' keyword.

    For example like this:

    ip access-list extended ME-CRYPTO-ACL

      permit ip 10.129.40.0 0.0.0.255 host 10.10.131.63

    ip access-list extended ME-NAT-ACL

      permit ip 10.10.10.0 0.0.0.255 host 10.10.131.63

    ip access-list extended SA-CRYPTO-ACL

      permit ip 10.96.21.0 0.0.0.255 host 10.99.2.95

    ip access-list extended SA-NAT-ACL

      permit ip 10.10.10.0 0.0.0.255 host 10.99.2.95

    Another solution is more complex and harder to understand (and explain), you can use Virtual models with tunnel-protection for each customer, VRF and NAT for common services.

    ___

    HTH. Please rate this post if this has been helpful. If it solves your problem, please mark this message as "right answer".

  • IOS IPSEC VPN with NAT - translation problem

    I'm having a problem with IOS IPSEC VPN configuration.

    /*

    crypto ISAKMP policy 10

    BA 3des

    preshared authentication

    Group 2

    ISAKMP crypto keys TEST123 address 205.xx.1.4

    !

    !

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

    !

    !

    Map 10 CRYPTO map ipsec-isakmp crypto

    the value of 205.xx.1.4 peer

    transformation-CHAIN game

    match address 115

    !

    interface FastEthernet0/0

    Description FOR the EDGE ROUTER

    IP address 208.xx.xx.33 255.255.255.252

    NAT outside IP

    card crypto CRYPTO-map

    !

    interface FastEthernet0/1

    INTERNAL NETWORK description

    IP 10.15.2.4 255.255.255.0

    IP nat inside

    access-list 115 permit 192.xx.xx.128 0.0.0.3 ip 172.xx.1.0 0.0.0.3

    */

    (This configuration is incomplete / NAT configuration needed)

    Here is the solution that I'm looking for:

    When a session is initiated from the "internal network" to the "distance IPSEC - 172.xx.1.0/30 ' network I want the address scheme '10.15.0.0/16' NAT translation deals with '192.xx.xx.128/30' before forwarding via the IPSEC VPN Tunnel.

    For more information, see "SCHEMA ATTACHED".

    Any help is greatly appreciated!

    Thank you

    Clint Simmons

    Network engineer

    You can try the following NAT + route map approach (method 2 in this link)

    http://www.Cisco.com/en/us/Tech/tk648/tk361/technologies_tech_note09186a0080093fca.shtml

    Thank you

    Raja K

  • RV082 v4.0.0.07 individuals and access rules NAT problem

    Hello

    I just bought two RV082 to run a 20 computer and office web server 4. I use special NAT to public IPs are mapped on different servers and our monitoring system and it seems to work very well. For each address of individuals using a NAT, I created the following access rules:

    Allow HTTP WAN1 everything [PA]

    Allow SSH WAN1 everything [PA]

    Refuse all WAN1 everything [PA]

    Allow rules are of a higher priority so my experience with other firewalls suggests that they should be applied first blocks access to all ports and ports HTTP and SSH then would be open. What seems to be the case is very disconcerting, with any rules applied Allow refusal rules are removed completely open all ports. If I move the priority of rule Deny it blocks all ports, as expected.

    My question is how can I prevent access to all ports except ports HTTP and SSH with the router in NAT mode specific.

    When an access rule is set on a NAT 1 rule at 1, you want to change the public ip address to the private IP which is mapped to the public ip address.

    Allow to use HTTP WAN1 everything [private address]

    Allow SSH WAN1 everything [private address]

    Refuse all WAN1 everything [private address]

  • ASA VPN Site to Site (WITH the NAT) ICMP problem

    Hi all!

    I need traffic PAT 192.168.1.0/24 (via VPN) contact remote 151.1.1.0/24, through 192.168.123.9 router in the DMZ (see diagram)

    It works with this configuration, with the exception of the ICMP.

    This is the error: Deny icmp src dmz:151.1.1.1 dst foreign entrants: 192.168.123.229 (type 0, code 0)

    Is there a way to do this?

    Thank you all!

    Marco

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

    ASA Version 8.2 (2)
    !
    ciscoasa hostname
    domain default.domain.invalid
    activate 8Ry2YjIyt7RRXU24 encrypted password
    2KFQnbNIdI.2KYOU encrypted passwd
    names of
    name 192.168.1.0 network-remote control
    !
    interface Vlan1
    nameif inside
    security-level 100
    IP 192.168.200.199 255.255.255.0
    !
    interface Vlan2
    nameif outside
    security-level 0
    the IP 10.0.0.2 255.255.255.0
    !
    interface Vlan3
    prior to interface Vlan1
    nameif dmz
    security-level 0
    192.168.123.1 IP address 255.255.255.0
    !
    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
    switchport access vlan 3
    !
    passive FTP mode
    DNS server-group DefaultDNS
    domain default.domain.invalid
    the DM_INLINE_NETWORK_1 object-group network
    object-network 151.1.1.0 255.255.255.0
    object-network 192.168.200.0 255.255.255.0
    outside_1_cryptomap list extended access allowed object-group DM_INLINE_NETWORK_1 remote ip 255.255.255.0 network
    inside_nat0_outbound to access extended list ip 192.168.200.0 allow 255.255.255.0 255.255.255.0 network-remote control
    VPN_NAT list extended access allow remote-network ip 255.255.255.0 151.1.1.0 255.255.255.0
    dmz_access_in list extended access permit icmp any one
    outside_access_in list extended access permit icmp any one
    pager lines 24
    Enable logging
    notifications of logging asdm
    Within 1500 MTU
    Outside 1500 MTU
    MTU 1500 dmz
    ICMP unreachable rate-limit 1 burst-size 1
    ICMP allow all dmz
    ASDM image disk0: / asdm - 625.bin
    don't allow no asdm history
    ARP timeout 14400
    Global 1 interface (outside)
    Global (dmz) 5 192.168.123.229
    NAT (inside) 0-list of access inside_nat0_outbound
    NAT (inside) 1 192.168.200.0 255.255.255.0
    NAT (outside) 5 VPN_NAT list of outdoor access
    Access-group outside_access_in in interface outside
    Access-group dmz_access_in in dmz interface
    Route outside 0.0.0.0 0.0.0.0 10.0.0.100 1
    Dmz route 151.1.1.0 255.255.255.0 192.168.123.9 1
    Timeout xlate 03:00
    Timeout conn 01:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
    Sunrpc timeout 0:10:00 h323 0:05:00 h225 mgcp from 01:00 0:05:00 mgcp-pat 0:05:00
    Sip timeout 0:30:00 sip_media 0:02:00 prompt Protocol sip-0: 03:00 sip - disconnect 0:02:00
    Timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
    timeout tcp-proxy-reassembly 0:01:00
    dynamic-access-policy-registration DfltAccessPolicy
    Enable http server
    http 0.0.0.0 0.0.0.0 inside
    remote control-network http 255.255.255.0 inside
    No snmp server location
    No snmp Server contact
    Server enable SNMP traps snmp authentication linkup, linkdown cold start
    Crypto ipsec transform-set esp-SHA-ESP-3DES-3des esp-sha-hmac
    life crypto ipsec security association seconds 28800
    Crypto ipsec kilobytes of life - safety 4608000 association
    card crypto outside_map 1 match address outside_1_cryptomap
    card crypto outside_map 1 set pfs Group1
    card crypto outside_map 1 set peer 10.0.0.1
    card crypto outside_map 1 set of transformation-ESP-3DES-SHA
    outside_map interface card crypto outside
    crypto ISAKMP allow outside
    crypto ISAKMP policy 10
    preshared authentication
    3des encryption
    sha hash
    Group 2
    life 86400
    Telnet timeout 5
    SSH timeout 5
    Console timeout 0
    dhcpd outside auto_config
    !

    a basic threat threat detection
    Statistics-list of access threat detection
    no statistical threat detection tcp-interception
    WebVPN
    tunnel-group 10.0.0.1 type ipsec-l2l
    tunnel-group 10.0.0.1 ipsec-attributes
    pre-shared key *.
    !
    class-map inspection_default
    match default-inspection-traffic
    !
    !
    type of policy-card inspect dns preset_dns_map
    parameters
    maximum message length automatic of customer
    message-length maximum 512
    Policy-map global_policy
    class inspection_default
    inspect the preset_dns_map dns
    inspect the ftp
    inspect h323 h225
    inspect the h323 ras
    inspect the rsh
    inspect the rtsp
    inspect esmtp
    inspect sqlnet
    inspect the skinny
    inspect sunrpc
    inspect xdmcp
    inspect the sip
    inspect the netbios
    inspect the tftp
    Review the ip options
    !
    global service-policy global_policy
    context of prompt hostname
    call-home
    Profile of CiscoTAC-1
    no active account
    http https://tools.cisco.com/its/service/oddce/services/DDCEService destination address
    email address of destination [email protected] / * /
    destination-mode http transport
    Subscribe to alert-group diagnosis
    Subscribe to alert-group environment
    Subscribe to alert-group monthly periodic inventory
    monthly periodicals to subscribe to alert-group configuration
    daily periodic subscribe to alert-group telemetry
    ------------------------------------------------------------------------------------

    Review the link, you have two ways to leave outgoing icmp, good acl or icmp inspection

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

  • VLAN and VPN problem

    Madam, Sir, I have the following problem:

    ASA ClientVPN---Internet--ASA--VLAN1(192.168.1.0/24)

    | -VLAN2

    | -VLAN3

    VPN = 192.168.10.0/24

    When you create the VPN connection with the wizard, the list of networks to the tunnel,

    This does not connect and displays the following message:

    No group of translation not found for tcp src outside:192.168.10.2/48257 dst

    192.168.1.2/80

    This message is the same as it throws when trying to communicate a VLAN on the SAA,

    That's why create the following rules:

    static (outdoors, VLAN1) 192.168.10.0 192.168.10.0 255.255.255.0

    static (VLAN1, outside) 192.168.1.0 192.168.1.0 255.255.255.0

    which allows communication between the VPN and the VLAN1, but I lose internet

    access from VLAN1 please help

    Julio,

    You need to add nat are subtracted to your VLAN internal to your VPN address pool, something like this:

    access-list allowed sheep ip 192.168.1.0 255.255.255.0 192.168.10.0 255.255.255.0

    NAT (inside) 0 access-list sheep

    which will allow communication from inside 192.168.1.0/24 vpn client, you must add the remaining lines for the VLAN left and apply them on the required VLANs if they are on different interfaces, of course.

  • nat VPN question.

    Try to find what happened.  I had the remote end raise the tunnel, as they can ping resources on my side.  I am unable to ping 10.90.238.148 through this tunnel.  I used to be able to until the interface of K_Inc has been added.  The network behind this interface is 10/8.

    I asked a question earlier in another post and advises him to play opposite road of Cryptography.  And who did it.  I was able to ping 10.90.238.148 of 192.168.141.10, with the config below.

    I am at a loss to why I can't all of a sudden.  A bit of history, given routes have not changed.  By adding the command set opposite road to cryptography, I find myself with a static entry for the 10.90.238.0 network is what fixed it initially so I don't think it's a problem of route.  The remote end had an overlap with the 192.168.141.0/24 that is why my side is natted on the 10.40.27.0.  None of the nats have changed so if adding the reverse route worked for a day, it should still work.  Any thoughts?

    interface GigabitEthernet0/3.10

    VLAN 10

    nameif K_Inc

    security-level 100

    IP address 192.168.10.254 255.255.255.0

    interface GigabitEthernet0/3.141

    VLAN 141

    cold nameif

    security-level 100

    IP 192.168.141.254 255.255.255.0

    (Cold) NAT 0 access-list sheep

    NAT (cold) 1 192.168.141.0 255.255.255.0

    Access extensive list ip 192.168.141.0 CSVPNOFFSITE allow 255.255.255.0 10.90.238.0 255.255.255.0

    Access extensive list ip 10.40.27.0 CSVPNOFFSITE allow 255.255.255.0 10.90.238.0 255.255.255.0

    Access extensive list ip 192.168.141.0 CSVPNNAT allow 255.255.255.0 10.90.238.0 255.255.255.0

    IP 10.40.27.0 allow Access-list extended sheep 255.255.255.0 10.90.238.0 255.255.255.0

    static 10.40.27.0 (cold, outside) - CSVPNNAT access list

    card crypto Outside_map 5 corresponds to the address CSVPNOFFSITE

    card crypto Outside_map 5 the value reverse-road

    card crypto Outside_map 5 set pfs

    card crypto Outside_map 5 set peer 20.x.x.3

    Outside_map 5 transform-set ESP-3DES-MD5 crypto card game

    card crypto Outside_map 5 defined security-association life seconds 28800

    card crypto Outside_map 5 set security-association kilobytes of life 4608000

    tunnel-group 20.x.x.3 type ipsec-l2l

    20.x.x.3 Group of tunnel ipsec-attributes

    pre-shared-key *.

    Route outside 0.0.0.0 0.0.0.0 7.x.x.1 1

    Route 10.0.0.0 K_Inc 255.192.0.0 192.168.10.252 1

    Route K_Inc 10.64.0.0 255.224.0.0 192.168.10.252 1

    Route K_Inc 10.100.100.0 255.255.255.0 192.168.10.252 1

    Route K_Inc 10.128.0.0 255.128.0.0 192.168.10.252 1

    Tunnel is up:

    14 peer IKE: 20.x.x.243

    Type: L2L role: answering machine

    Generate a new key: no State: MM_ACTIVE

    EDIT:

    I just noticed when tracer packet i run I don't get a phase VPN or encrypt:

    Packet-trace entry cold tcp 192.168.141.10 80 80 10.90.238.148 det

    Phase: 1

    Type: FLOW-SEARCH

    Subtype:

    Result: ALLOW

    Config:

    Additional information:

    Not found no corresponding stream, creating a new stream

    Phase: 2

    Type:-ROUTE SEARCH

    Subtype: entry

    Result: ALLOW

    Config:

    Additional information:

    in 10.90.238.0 255.255.255.0 outside

    Phase: 3

    Type: IP-OPTIONS

    Subtype:

    Result: ALLOW

    Config:

    Additional information:

    Direct flow from returns search rule:

    ID = 0xad048d08, priority = 0, sector = option-ip-enabled, deny = true

    hits = 2954624, user_data = 0 x 0, cs_id = 0 x 0, reverse, flags = 0 x 0 = 0 protocol

    SRC ip = 0.0.0.0 mask 0.0.0.0, port = 0 =

    DST ip = 0.0.0.0 mask = 0.0.0.0, port = 0, dscp = 0 x 0

    Phase: 4

    Type: QOS

    Subtype:

    Result: ALLOW

    Config:

    Additional information:

    Direct flow from returns search rule:

    ID = 0xb2ed4b80, priority = 72, domain = qos by class, deny = false

    hits = 2954687, user_data = 0xb2ed49d8, cs_id = 0 x 0, reverse, flags = 0 x 0 = 0 protocol

    SRC ip = 0.0.0.0 mask 0.0.0.0, port = 0 =

    DST ip = 0.0.0.0 mask = 0.0.0.0, port = 0, dscp = 0 x 0

    Phase: 5

    Type: FOVER

    Subtype: Eve-updated

    Result: ALLOW

    Config:

    Additional information:

    Direct flow from returns search rule:

    ID = 0xad090180, priority = 20, area = read, deny = false

    hits = 618776, user_data = 0 x 0, cs_id = 0 x 0, flags = 0 x 0, Protocol = 6

    SRC ip = 0.0.0.0 mask 0.0.0.0, port = 0 =

    DST ip = 0.0.0.0 mask = 0.0.0.0, port = 0, dscp = 0 x 0

    Phase: 6

    Type: NAT

    Subtype:

    Result: ALLOW

    Config:

    static (ColdSpring, external) 74.x.x.50 192.168.141.10 netmask 255.255.255.255

    match ip host 192.168.141.10 ColdSpring outside of any

    static translation at 74.x.x.50

    translate_hits = 610710, untranslate_hits = 188039

    Additional information:

    Definition of static 192.168.141.10/0 to 74.112.122.50/0 using subnet mask 255.255.255.255

    Direct flow from returns search rule:

    ID = 0xac541e50, priority = 5, area = nat, deny = false

    hits = 610742, user_data = 0xac541c08, cs_id = 0 x 0, flags = 0 x 0 = 0 protocol

    SRC ip = 192.168.141.10, mask is 255.255.255.255, port = 0

    DST ip = 0.0.0.0 mask = 0.0.0.0, port = 0, dscp = 0 x 0

    Phase: 7

    Type: NAT

    Subtype: host-limits

    Result: ALLOW

    Config:

    static (ColdSpring, dmz) 192.168.141.0 192.168.141.0 netmask 255.255.255.0

    match ip ColdSpring 192.168.141.0 255.255.255.0 dmz all

    static translation at 192.168.141.0

    translate_hits = 4194, untranslate_hits = 20032

    Additional information:

    Direct flow from returns search rule:

    ID = 0xace2c1a0, priority = 5, area = host, deny = false

    hits = 2954683, user_data = 0xace2ce68, cs_id = 0 x 0, reverse, flags = 0 x 0 = 0 protocol

    SRC ip = 192.168.141.0, mask is 255.255.255.0, port = 0

    DST ip = 0.0.0.0 mask = 0.0.0.0, port = 0, dscp = 0 x 0

    Phase: 8

    Type: IP-OPTIONS

    Subtype:

    Result: ALLOW

    Config:

    Additional information:

    Reverse flow from returns search rule:

    ID = 0xaacbcb90, priority = 0, sector = option-ip-enabled, deny = true

    hits = 282827537, user_data = 0 x 0, cs_id = 0 x 0, reverse, flags = 0 x 0 = 0 protocol

    SRC ip = 0.0.0.0 mask 0.0.0.0, port = 0 =

    DST ip = 0.0.0.0 mask = 0.0.0.0, port = 0, dscp = 0 x 0

    Phase: 9

    Type: QOS

    Subtype:

    Result: ALLOW

    Config:

    Additional information:

    Reverse flow from returns search rule:

    ID = 0xb2ed5c78, priority = 72, domain = qos by class, deny = false

    hits = 4749562, user_data = 0xb2ed5ad0, cs_id = 0 x 0, reverse, flags = 0 x 0 = 0 protocol

    SRC ip = 0.0.0.0 mask 0.0.0.0, port = 0 =

    DST ip = 0.0.0.0 mask = 0.0.0.0, port = 0, dscp = 0 x 0

    Phase: 10

    Type: CREATING STREAMS

    Subtype:

    Result: ALLOW

    Config:

    Additional information:

    New workflow created with the 339487904 id, package sent to the next module

    Information module for forward flow...

    snp_fp_inspect_ip_options

    snp_fp_tcp_normalizer

    snp_fp_translate

    snp_fp_adjacency

    snp_fp_fragment

    snp_fp_tracer_drop

    snp_ifc_stat

    Information for reverse flow...

    snp_fp_inspect_ip_options

    snp_fp_translate

    snp_fp_tcp_normalizer

    snp_fp_adjacency

    snp_fp_fragment

    snp_fp_tracer_drop

    snp_ifc_stat

    Phase: 11

    Type:-ROUTE SEARCH

    Subtype: output and contiguity

    Result: ALLOW

    Config:

    Additional information:

    found 7.x.x.1 of next hop using ifc of evacuation outside

    contiguity Active

    0007.B400.1402 address of stretch following mac typo 51982146

    Result:

    input interface: cold

    entry status: to the top

    entry-line-status: to the top

    output interface: outside

    the status of the output: to the top

    output-line-status: to the top

    Action: allow

    What version are you running to ASA?

    My guess is that your two static NAT is configured above policy nat you have configured for the VPN?  If this is the case, move your above these static NAT NAT policy and you should see the traffic start to flow properly.

    --

    Please note all useful posts

  • 8.4 ASA using NAT VPN issue.

    Hello

    I'm working on a customer site and they have a problem with one of their VPN (we have other works well), but it is a major issue and I think it's because we use manual NAT and NAT of the object on the same server for different things.

    Traffic between indoors and outdoors:

    It works with a specific manual NAT rule of source from the server 10.10.10.10 object

    Inside

    SRC-> DST

    10.10.10.10-> 1.1.2.10 1.1.1.10-> 1.1.2.10 SNAT = VPN =-> 1.1.2.10 1.1.1.10 1.1.1.10-> 1.1.2.10 <3rd party="" fw="">

    It works with a specific using the NAT on the server of 10.10.10.10 object

    Remote

    SRC-> DST

    1.1.1.10-> 1.1.2.10 1.1.1.10-> 1.1.2.10 <3rd party="" fw="">= VPN =-> 1.1.2.10 1.1.1.10 1.1.1.10-> DNAT 10.10.10.10

    If we have the manual NAT and NAT object it does anyway.

    So the question is (as I am new to zip code 8.3 ASA) should not mix the 2 types of NAt and look at configuring it all with manual NAT or NAT object?

    With the NAT object out it does not work as it is taken in ouside NAT inside all:

    Dynamic NAT (inside, outside) source no matter what interface (this NAT to 1.1.1.1 then does not match the card encryption for VPN)

    and I tried a no - nat above that, but that does not work either.

    Straws and hugging come to mind try to configure a different config. Any pointers in the right direction would be great.

    Kind regards

    Z

    Hello

    I'm not sure that installing even with the explanation. Each NAT configuration I did for VPN used Section 1 Manual / NAT twice.

    You have configured the rule by default PAT that you use as Section 1 NAT rule. NAT rules in the new software are divided into 3 sections

    • Section 1: Manual / twice by NAT
    • Section 2: Purpose NAT
    • Section 3: Manual / double NAT (moved to section 3 using the setting "auto after")
    • The Sections are passed by from 1 to 2 and 3 in order to find a match.

    You should also notice that the Section 1 and Section 3 NAT has "line number" similar to the ACL parameter type. So if you have a default existing PAT rule configured for Section 1 and just add another Section 1 NAT rule without line/order number (VPN NAT) then it will just fall under the existing rule, making the new useless rule.

    I would advice against the use of the rule by default PAT as Section 1 NAT rule. Finally, this means that you be constantly watch and edit its configuration when you try to configure more specific rules.

    As a general rule 3 of the Section the PAT above default configuration would be the following

    NAT (inside, outside) after the automatic termination of dynamic source no matter what interface

    This would mean that you need to remove the old. That would mean as naturally as the change would temporarily dismantling all the current connections through "inside", "Outside" while you change the NAT rule format.

    If after this configure a NAT twice to the VPN (wihtout the setting "auto after"), it will be the rule in article 1 while the default PAT will be Section 3. Of course, Section 1 will be matched first.

    I'm not quite sure of what your setup of the foregoing have understood.

    You're just source NAT?

    I guess that the configuration you do is something like this?

    network of the LAN-REAL object

    10.10.10.0 subnet 255.255.255.0

    purpose of the MAPPED in LAN network

    1.1.1.0 subnet 255.255.255.0

    being REMOTE-LAN network

    1.1.2.0 subnet 255.255.255.0

    NAT static destination of LAN LAN-REAL-MAPPED Shared source (indoor, outdoor) REMOTE - LAN LAN

    If the network 1.1.1.0/24 is supposed to be one that is connected directly to your "external" to the format interface may need to be anything else.

    -Jouni

  • NAT VPN outside-&gt; dmz

    Hi all

    I have some problems with nat/sheep on a pix 515e.

    the pix is connected to a tunnel of site2site on the external interface.

    the problem is to ping the vpn tunnel to the hosts of the demilitarized zone.

    I think it should with a static entry as follows:

    static (outside, dmz) 10.43.26.0 10.43.26.0 netmask 255.255.254.0

    but in the newspaper, I always get the message:

    305005: no outside group translation not found for icmp src: 10.43.27.250 dmz:10.43.100.3 (type 8, code 0) dst

    I also tried a nat rule 0 without success.

    Then I attached a config performed:

    access-list allowed sheep ip 10.0.0.0 255.0.0.0 10.0.0.0 255.0.0.0

    access-list allowed sheep ip 10.0.0.0 255.0.0.0 192.168.0.0 255.255.0.0

    access-list allowed sheep ip 10.0.0.0 255.0.0.0 200.1.58.0 255.255.255.0

    access-list allowed sheep ip 10.0.0.0 255.0.0.0 172.16.0.0 255.255.0.0

    IP outdoor 199.99.99.2 255.255.254.0

    IP address inside the 10.43.8.12 255.255.240.0

    10.43.100.2 dmz IP address 255.255.255.0

    Global (outside) 1 199.99.99.11 netmask 255.255.255.255

    Global (outside) 1 199.99.99.14 netmask 255.255.255.255

    Global (dmz) 1 10.43.100.50 - 10.43.100.98 netmask 255.255.255.0

    Global (dmz) 1 10.43.100.99 netmask 255.255.255.0

    NAT (inside) 0 access-list sheep

    NAT (inside) 1 10.43.0.44 255.255.255.255 0 0

    NAT (inside) 1 10.43.8.0 255.255.255.0 0 0

    NAT (inside) 1 10.43.9.0 255.255.255.0 0 0

    static (inside, outside) 199.99.99.2 tcp telnet 10.43.8.52 telnet netmask 255.255.255.255 0 0

    static (inside, dmz) 10.43.8.29 10.43.8.29 netmask 255.255.255.255 0 0

    static (inside, dmz) 10.43.8.20 10.43.8.20 netmask 255.255.255.255 0 0

    static (dmz, external) 199.99.99.6 10.43.100.6 netmask 255.255.255.255 0 0

    public static 199.99.99.7 (Interior, exterior) 10.43.9.56 netmask 255.255.255.255 0 0

    public static 199.99.99.5 (Interior, exterior) 10.43.8.53 netmask 255.255.255.255 0 0

    static (dmz, external) 199.99.99.4 10.43.100.4 netmask 255.255.255.255 0 0

    static (dmz, external) 199.99.99.3 10.43.100.3 netmask 255.255.255.255 0 0

    static (outside, dmz) 10.43.26.0 10.43.26.0 netmask 255.255.254.0 0 0

    Access-group acl_out in interface outside

    acl_in access to the interface inside group

    Access-group acl_dmz in dmz interface

    any tips?

    Thank you

    Armin

    Without seeing the rest of the config it is difficult to tell you exactly what's happening (IE ACL, sysopt connection ipsec permits etc.)

    However, you will need to have a sheep for the DMZ traffic back through the VPN:

    IP 10.43.100.0 allow Access-list sheep-dmz 255.255.255.0 10.43.27.0 255.255.255.0

    NAT (dmz) access-list sheep-dmz

    Also remove the 10.43.26.0 static (outside, dmz) 10.43.26.0 netmask 255.255.254.0 0 0. I see no reason for you to destination NAT.

    HTH

  • 8.3 Cisco ASA VPN problem

    Hi all

    I have some problems with the implementation of a VPN using IPSEC to establish a connection from Site to Site.

    What I'm trying to Setup is the following, his IP address of a site can reach the beaches on site B and visa versa.

    Site A                                                       Site B

    192.168.10.0 172.16.0.0

    192.168.20.0 IPSEC tunnel - 172.17.0.0 -.

    192.168.30.0 172.18.0.0

    I tested with one subnet to another subnet that works. However, when I try to group the objects it fails.

    As an example I can set up a VPN of 192.168.20.0 to 172.18.0.0 that I can pass the traffic through but its unable to reach other subnets.

    Excerpts from the config.

    crypto ISAKMP allow outside

    ACL

    list of allowed outside_1_cryptomap ip access dmz LAN object dmz-network-remote

    Tunnel group

    tunnel-group type ipsec-l2l

    IPSec-attributes tunnel-group

    pre-shared key

    ISAKMP retry threshold 10 keepalive 2

    Phase 1

    part of pre authentication isakmp crypto policy 10

    crypto ISAKMP policy 10 3des encryption

    crypto ISAKMP policy hash 10 sah

    10 crypto isakmp policy group 2

    crypto ISAKMP policy life 10 86400

    Phase 2

    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

    map 1 set outside_map crypto peer

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

    outside_map interface card crypto outside

    NAT

    NAT (inside, outside) 1 static source local-network-dmz dmz LAN destination static remote-network-dmz dmz-network distance

    Any advice would be greatly appreciated.

    Thank you.

    Andrew,

    Accroding to your config, each network is behind a different interface of the SAA, so you will need to change the NAT rule for each of them, for example:

    NAT (DMZ_Zone, outside) 1 static source ad-network-local ad-network-local destination static obj obj-remote control-remote control

    NAT (DB_Zone, outside) 1 static source local-network-db db-network-local destination static obj obj-remote control-remote control

    NAT (AD_Zone, outside) 1 static source local-network-dmz dmz LAN destination static obj obj-remote-distance

    Please review and give it a try.

    I hope hear from you soon.

  • VPN problem when local lan IP is IP LAN Corp.

    Hello

    I'm having a problem to access corporate services when an example of one of our servers IP address matches an IP address of a local host from the local network, accessed from.

    Is there a way to bypass and or solve this problem?

    I use split tunnel, I send you all DNS requests through the tunnel and assigning the DNS name.

    I inherited this network which is a 192.168.0.0/23 with many services on 192.168.1.x that match easily private local lans.

    Hello Michael,

    To resolve the overlap, you need hide the remote with a NAT rule network, so that VPN clients point to an address using a NAT on the SAA.

    Can I know the version of your ASA?

    Thank you.

    Portu.

  • VPN problem taking in charge the VRF CSR

    Hello community,

    I am currently evaluating CSR at AWS (60 day trial) and already around the usual problems and specialty architecture network AWS design.

    I can't open a TAC case, because we purchased no license. We will, once this last problem is solved.

    Current configuration:

    • Two councillors in a VPC in two AZs
    • Transit between two advisers of the GRE tunnel
    • running supports the BGP VRF
    • using door VRF
    • the RSC is connected to several AWS VPC (customers) via the AWS VPN feature - route entirely mesh based VPN--a VRF customer - all running with BGP
    • Link to local is done in the same way: entirely mesh route based VPN - using door VRF - all running with BGP
    • VRF import/export rules

    It works fine - no problems here. All HA tests work as expected. So far, so good.

    Now, we had to create a VPN connection to a special local location of our society. We should create a policy based VPN location (no support for VPN road based there). It is a two-to-one VPN. Two advisors of the connection to a gateway onPrem. The two tunnels, run the same field of encryption. OnPrem routing is based on the State of the tunnel. We put this tunnel in the VRF door of entry. Routes are injected to the door VRF routing table by VPN process (reverse-way static in crypto map). To get these exported to consumer VRF routes, there is a network statement in door VRF BGP process.

    Well, this also works fine if we do this only with CSR A. Reachablity is out. CSR B the delivery of the CSR due to taking work supported the VRF VPN. However, if we establish the second CSR B tunnel, there is something strange happens.

    Tunnel is very well implemented. Traffic through the tunnel at CSR B is accepted and routed to the destination. Created at door VRF on CSR B traffic is routed in its own VPN very well. However, traffic from a VRF client who reached CSR B (traceroute proved that) is not routed through the VPN tunnel, despite the VPN client routing table is to say. CSR A running the same configuration, there is no problem. Only on the CSR B.

    I don't understand this. If remove us the configuration of the tunnel of CSR and create only tunnel on CSR B, it still does not. I don't understand why, because I did a comparison of config and found no difference.

    Someone at - it an idea, whats going on?

    How can I debug this problem?

    CSR - A:

    B 172.29.13.176/28 [20/0] via 1.1.119.182 (vrf - default), 3w4d

    CSR - B:

    with route (doesn't work is not for the customer VRF)
    B 172.29.13.176/28 [20/0] via 1.1.119.182 (vrf - default), 00:00:02

    No itinerary (work, because only sent by public transit to the CSR - A)
    B 172.29.13.176/28 [20/0] via 192.168.254.53 (vrf - default), 00:38:23

    This problem is hard to describe, I would really appriciate discuss with a TAC engineer in a WebEx. Is this possible?

    Thank you.

    Hello Tobias,.

    The problem you describe is going to be outside our CSR platform expertise. Looks like the CSR works well and HA works as well, and now you're trying to find a solution to a problem of network/VPN that you are facing.

    Our team is led to find an internal resource to resolve your issue, please allow us a day or two to get back to you with an answer

    Concerning

    Tony

Maybe you are looking for

  • Upgrade of RAM MacBook Pro 13 (end 2011) (Crucial Vs Corsair)

    Hey guys,. I want to upgrade RAM from my Macbook Pro 13 (end of 2011). Currently, I came across 2 brands i.e. Corsair & Crucial. Can someone help chose me between the two. To upgrade RAM Apple support page: https://support.apple.com/en-in/HT201165 Ke

  • A problem of user login, in the Standby Mode

    I'm the only user on my Mac. When I go to Preferences system, users and groups, my name is listed and guest said off. My question is when I turn on the computer, I automatically connect. But, when I put the computer in mode 'sleep', get out of standb

  • Satellite A100-163 low wireless signal

    I just bought a Satellite A100-163, and while wireless, it works to the full 54 members of Parliament he said that the signal is very weak. My old 2430 402, who is sitting beside her said the signal is very strong and I have recently set up a satelli

  • Widows 10 windows 7

    I have 1 installation, without success and switched back to 7, the keyboard and mouse stop working and I can not enter password to continue, also wireless keyboard and mouse do not work, Microsoft had no answer, THX Marty Any ideas?

  • How to set the clock on a HP Officejet 6700?

    Faxes need a postmark date/time in an office environment. Mounting printed HP6700 guide, or the installed help files and the keyboard have no provision for setting the clock of the 6700's time. How is something as simple as a clock turned on and set