Solved

Cisco ASA Object NAT Issue

Posted on 2013-05-11
22
1,254 Views
Last Modified: 2014-10-15
I can't seem to get my Cisco ASA 5505 to publish a security camera server using static nat and an access rule. I'm not sure why it's not working.

Here is a copy of my running config

Result of the command: "show running"

: Saved
:
ASA Version 9.0(2)
!
hostname ***
domain-name ****
enable password **** encrypted
passwd **** encrypted
names
!
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 address 172.21.1.1 255.255.255.0
!
interface Vlan2
 nameif outside
 security-level 0
 ip address 0.0.0.0 255.255.255.0
!
banner motd
banner motd
banner motd Authorized Users Only
banner motd This System Is For the Use of Authorized users only.
boot system disk0:/asa902-k8.bin
ftp mode passive
clock timezone EST -5
clock summer-time EDT recurring
dns domain-lookup inside
dns server-group DefaultDNS
 name-server 172.20.100.3
 name-server 172.20.100.4
 domain-name ******
object network obj_any
 subnet 0.0.0.0 0.0.0.0
object network WAN_Address
 host 0.0.0.1
object service Camera_Web
 service tcp source eq 8000
object network obj-cam_server
 host 172.21.1.100
access-list outside_access_in extended permit tcp any object obj-cam_server eq 8000
access-list inside_access_in extended permit ip any any log disable
pager lines 24
logging enable
logging timestamp
logging buffered warnings
logging trap warnings
logging history warnings
logging asdm warnings
mtu inside 1500
mtu outside 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
icmp permit any echo-reply outside
icmp permit any outside
asdm image disk0:/asdm-712-102.bin
no asdm history enable
arp timeout 14400
no arp permit-nonconnected
!
object network obj_any
 nat (inside,outside) dynamic interface
object network obj-cam_server
 nat (inside,outside) static 0.0.0.1
access-group inside_access_in in interface inside
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 **ISP NEXT HOP*** 1
timeout xlate 3:00:00
timeout pat-xlate 0:00:30
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 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
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
user-identity default-domain LOCAL
aaa authentication http console LOCAL
aaa authentication ssh console LOCAL
aaa authentication enable console LOCAL
http server enable
http 0.0.0.0 0.0.0.0 inside
http 172.20.104.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart warmstart
crypto ipsec security-association pmtu-aging infinite
crypto ca trustpoint _SmartCallHome_ServerCA
 crl configure
crypto ca trustpool policy
crypto ikev1 policy 65535
 authentication pre-share
 encryption 3des
 hash sha
 group 2
 lifetime 86400
telnet timeout 5
ssh 0.0.0.0 0.0.0.0 inside
ssh timeout 5
console timeout 0
management-access inside
vpnclient server ******
vpnclient mode network-extension-mode
vpnclient nem-st-autoconnect
vpnclient vpngroup **** password *****
vpnclient username **** password *****
vpnclient management tunnel 10.0.0.0 255.0.0.0 172.16.0.0 255.240.0.0 192.168.0.0 255.255.0.0
vpnclient enable
dhcpd address 172.21.1.20-172.21.1.51 inside
dhcpd dns 8.8.8.8 4.2.2.1 interface inside
dhcpd domain ***** interface inside
dhcpd enable inside
!
no threat-detection basic-threat
no threat-detection statistics access-list
threat-detection statistics tcp-intercept rate-interval 30 burst-rate 400 average-rate 200
username ***** password ***** encrypted privilege 15
!
class-map inspection_de
class-map inspection_default
!
!
policy-map global_policy
 class inspection_default
  inspect icmp
!
prompt hostname context
call-home reporting anonymous
call-home
 profile CiscoTAC-1
  no active
  destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
  destination address email callhome@cisco.com
  destination transport-method http
  subscribe-to-alert-group diagnostic
  subscribe-to-alert-group environment
  subscribe-to-alert-group inventory periodic monthly
  subscribe-to-alert-group configuration periodic monthly
  subscribe-to-alert-group telemetry periodic daily
Cryptochecksum:****
: end
0
Comment
Question by:JasonPJohnson
  • 11
  • 5
  • 3
  • +1
22 Comments
 
LVL 2

Author Comment

by:JasonPJohnson
ID: 39158273
addresses etc were scrubbed.
0
 
LVL 28

Expert Comment

by:Jan Springer
ID: 39158367
Can you post a "show log" including the lines for that IP?
0
 
LVL 2

Author Comment

by:JasonPJohnson
ID: 39158386
Yes in about an hour
0
 
LVL 28

Expert Comment

by:Jan Springer
ID: 39158454
You'll need to turn logging on the inside so that we can verify the return traffic.
0
 
LVL 2

Author Comment

by:JasonPJohnson
ID: 39158526
Result of the command: "show log"

Syslog logging: enabled
    Facility: 20
    Timestamp logging: enabled
    Standby logging: disabled
    Debug-trace logging: disabled
    Console logging: disabled
    Monitor logging: disabled
    Buffer logging: level warnings, 2987 messages logged
    Trap logging: level warnings, facility 20, 2987 messages logged
    Permit-hostdown logging: disabled
    History logging: level warnings, 2987 messages logged
    Device ID: disabled
    Mail logging: disabled
    ASDM logging: level warnings, 2987 messages logged
88%
May 11 2013 04:58:58: %ASA-4-402116: IPSEC: Received an ESP packet (SPI= 0x670E2228, sequence number= 0xCAF) from 66.249.252.2 (user= 66.249.252.2) to 184.18.219.3.  The decapsulated inner packet doesn't match the negotiated policy in the SA.  The packet specifies its destination as 172.21.1.155, its source as 192.168.1.190, and its protocol as icmp.  The SA specifies its local proxy as 172.21.1.0/255.255.255.0/ip/0 and its remote_proxy as 172.16.0.0/255.240.0.0/ip/0.
May 11 2013 04:59:14: %ASA-4-402116: IPSEC: Received an ESP packet (SPI= 0x670E2228, sequence number= 0xCDE) from 66.249.252.2 (user= 66.249.252.2) to 184.18.219.3.  The decapsulated inner packet doesn't match the negotiated policy in the SA.  The packet specifies its destination as 172.21.1.155, its source as 192.168.1.190, and its protocol as icmp.  The SA specifies its local proxy as 172.21.1.0/255.255.255.0/ip/0 and its remote_proxy as 172.16.0.0/255.240.0.0/ip/0.
May 11 2013 04:59:29: %ASA-4-752010: IKEv2 Doesn't have a proposal specified
May 11 2013 04:59:29: %ASA-4-752010: IKEv2 Doesn't have a proposal specified
May 11 2013 04:59:29: %ASA-4-752010: IKEv2 Doesn't have a proposal specified
May 11 2013 04:59:29: %ASA-4-752010: IKEv2 Doesn't have a proposal specified
May 11 2013 04:59:46: %ASA-4-402116: IPSEC: Received an ESP packet (SPI= 0x670E2228, sequence number= 0xD1E) from 66.249.252.2 (user= 66.249.252.2) to 184.18.219.3.  The decapsulated inner packet doesn't match the negotiated policy in the SA.  The packet specifies its destination as 172.21.1.155, its source as 192.168.1.190, and its protocol as icmp.  The SA specifies its local proxy as 172.21.1.0/255.255.255.0/ip/0 and its remote_proxy as 172.16.0.0/255.240.0.0/ip/0.
May 11 2013 05:00:24: %ASA-4-402116: IPSEC: Received an ESP packet (SPI= 0x670E2228, sequence number= 0xD68) from 66.249.252.2 (user= 66.249.252.2) to 184.18.219.3.  The decapsulated inner packet doesn't match the negotiated policy in the SA.  The packet specifies its destination as 172.21.1.155, its source as 192.168.1.190, and its protocol as icmp.  The SA specifies its local proxy as 172.21.1.0/255.255.255.0/ip/0 and its remote_proxy as 172.16.0.0/255.240.0.0/ip/0.
May 11 2013 05:00:26: %ASA-4-402116: IPSEC: Received an ESP packet (SPI= 0x670E2228, sequence number= 0xD6D) from 66.249.252.2 (user= 66.249.252.2) to 184.18.219.3.  The decapsulated inner packet doesn't match the negotiated policy in the SA.  The packet specifies its destination as 172.21.1.155, its source as 192.168.1.190, and its protocol as icmp.  The SA specifies its local proxy as 172.21.1.0/255.255.255.0/ip/0 and its remote_proxy as 172.16.0.0/255.240.0.0/ip/0.
May 11 2013 05:00:28: %ASA-4-402116: IPSEC: Received an ESP packet (SPI= 0x670E2228, sequence number= 0xD74) from 66.249.252.2 (user= 66.249.252.2) to 184.18.219.3.  The decapsulated inner packet doesn't match the negotiated policy in the SA.  The packet specifies its destination as 172.21.1.155, its source as 192.168.1.190, and its protocol as icmp.  The SA specifies its local proxy as 172.21.1.0/255.255.255.0/ip/0 and its remote_proxy as 172.16.0.0/255.240.0.0/ip/0.
May 11 2013 05:00:31: %ASA-4-402116: IPSEC: Received an ESP packet (SPI= 0x670E2228, sequence number= 0xD78) from 66.249.252.2 (user= 66.249.252.2) to 184.18.219.3.  The decapsulated inner packet doesn't match the negotiated policy in the SA.  The packet specifies its destination as 172.21.1.155, its source as 192.168.1.190, and its protocol as icmp.  The SA specifies its local proxy as 172.21.1.0/255.255.255.0/ip/0 and its remote_proxy as 172.16.0.0/255.240.0.0/ip/0.
May 11 2013 05:00:35: %ASA-4-402116: IPSEC: Received an ESP packet (SPI= 0x670E2228, sequence number= 0xD7D) from 66.249.252.2 (user= 66.249.252.2) to 184.18.219.3.  The decapsulated inner packet doesn't match the negotiated policy in the SA.  The packet specifies its destination as 172.21.1.155, its source as 192.168.1.190, and its protocol as icmp.  The SA specifies its local proxy as 172.21.1.0/255.255.255.0/ip/0 and its remote_proxy as 172.16.0.0/255.240.0.0/ip/0.
0
 
LVL 2

Author Comment

by:JasonPJohnson
ID: 39158529
I did try and hit it a few times while running this command.

it works if i use the VPN address so I know that routing, default gateway on the server etc are working and it is the correct port.
0
 
LVL 28

Expert Comment

by:Jan Springer
ID: 39158552
I can't find the IP 172.16.1.100 in the log data.

So, run packet-tracer:

 packet-tracer input inside tcp 8.8.8.8 4000 172.21.1.100 8000

What are the results?
0
 
LVL 2

Author Comment

by:JasonPJohnson
ID: 39158684
Phase: 1
Type: ACCESS-LIST
Subtype:
Result: ALLOW
Config:
Implicit Rule
Additional Information:
MAC Access list

Phase: 2
Type: ROUTE-LOOKUP
Subtype: input
Result: ALLOW
Config:
Additional Information:
in   172.21.1.0      255.255.255.0   inside

Phase: 3
Type: ACCESS-LIST
Subtype:
Result: DROP
Config:
Implicit Rule
Additional Information:

Result:
input-interface: inside
input-status: up
input-line-status: up
output-interface: inside
output-status: up
output-line-status: up
Action: drop
Drop-reason: (acl-drop) Flow is denied by configured rule
0
 
LVL 2

Author Comment

by:JasonPJohnson
ID: 39158687
Also did one to the outside address (nat'd)

packet-tracer input inside tcp 8.8.8.8 4000 184.18.219.2 8000

Phase: 1
Type: ACCESS-LIST
Subtype:
Result: ALLOW
Config:
Implicit Rule
Additional Information:
MAC Access list

Phase: 2
Type: ROUTE-LOOKUP
Subtype: input
Result: ALLOW
Config:
Additional Information:
in   184.18.219.0    255.255.255.0   outside

Phase: 3
Type: ACCESS-LIST
Subtype: aaa-user
Result: DROP
Config:
Additional Information:

Result:
input-interface: inside
input-status: up
input-line-status: up
output-interface: outside
output-status: up
output-line-status: up
Action: drop
Drop-reason: (acl-drop) Flow is denied by configured rule
0
 
LVL 2

Expert Comment

by:Shoota
ID: 39159460
From looking at your trace results, it seems to be a problem with your acl.  What version of IOS are you running?  in the older ones (prior to 8.3 if I remember right) you had to use the NAT'd address in the acl, whereas the newer ones used the real address the way you are.  If you're running an older acl, that could be your problem.
0
 
LVL 2

Expert Comment

by:Shoota
ID: 39159487
Disregard.  I just saw you're running ver. 9.0.  But it still looks like an issue with the acl because that's where it's being dropped in your trace. Is it possible that you need to create outbound acls for both of your interfaces as well?
0
Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

 
LVL 2

Author Comment

by:JasonPJohnson
ID: 39159519
Ill try, but outbound is any any on outside
0
 
LVL 2

Expert Comment

by:Shoota
ID: 39159599
I'm not sure if the implicit outbound any any doesn't go away once you apply an inbound acl to that interface.  Couldn't hurt to put an explicit one on there.
0
 
LVL 17

Expert Comment

by:MAG03
ID: 39160602
There is nothing blocking the traffic in the outbound direction (out the outside interface), that was only needed when running earlier versions of the PIX firewall.

You say that you can reach the server over the VPN tunnel, does this mean that you are trying to open for traffic that is not passing through the tunnel?  If so, have you configured Easy VPN to allow for split tunneling (this is done on the Easy VPN server).

If you run the packet tracer in ASDM and on the step that fails you will be able to click on a link that says something like "Show rule in rules table", this will take you to the rule that is blocking your traffic.  I am going to guess that it will be the Global ACL rule.

Also, your inside interface any any ACL is disabled.  Though this rule is not needed as traffic will flow freely from a high security level interface to a lower security level interface.  Since inside interface has a security level of 100 and outside has 0 this traffic should flow nicely without the ACL.  However if you decide to keep it then I would recommend enabling it, otherwise remove it all together.
0
 
LVL 2

Author Comment

by:JasonPJohnson
ID: 39161220
Here is a diagram.

I will play with packet tracer, I'm not sure I understand the last comment.

Here is a diagram, I can access the camera server over the VPN tunnel but when I try and get to it via my ISP (from iPhone) It just times out.
0
 
LVL 28

Expert Comment

by:Jan Springer
ID: 39161476
I'd like you to yank the inside access-group statement for the inside_in access list and give it another shot.
0
 
LVL 17

Expert Comment

by:MAG03
ID: 39162192
Just for the purpose of testing, add a permit IP any any to the outside_access_in ACL and see if traffic starts to flow.
0
 
LVL 2

Author Comment

by:JasonPJohnson
ID: 39162202
I added an any any to all interfaces and nothing worked. I also ran the packet tracer and it says it was successful. But it doesn't work still.
0
 
LVL 17

Expert Comment

by:MAG03
ID: 39162209
Could you post the command you ran for the packet tracer as well as the output of the trace.

If you ran the correct parameters on packet tracer and it says the traffic is permitted through the firewall, then there is nothing blocking the traffic and the problem lies elsewhere, maybe on the server.
0
 
LVL 28

Expert Comment

by:Jan Springer
ID: 39162705
You have:

object network obj-cam_server
 nat (inside,outside) static 0.0.0.1

Why does it show 0.0.0.1?

What is the output of "sh xlate"
0
 
LVL 2

Accepted Solution

by:
JasonPJohnson earned 0 total points
ID: 39162756
I scrubbed the ip...
0
 
LVL 2

Author Closing Comment

by:JasonPJohnson
ID: 40381686
thread just died.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

We've been using the Cisco/Linksys RV042 for years as: - an internet Gateway - a site-to-site VPN device - a leased line site-to-site subnet-to-subnet interface (And, here I'm assuming that any RV0xx behaves the same way as an RV042.  So that's …
From Cisco ASA version 8.3, the Network Address Translation (NAT) configuration has been completely redesigned and it may be helpful to have the syntax configuration for both at a glance. You may as well want to read official Cisco published AS…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now