• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7609
  • Last Modified:

asa 5505 nat rpf-check DROP

Experts, see attached file of my asa config. It is a simple config.
I have an ipsec vpn tunnel established.

Encryption domain:
Local:192.168.3.0 255.255.255.0
Remote:10.75.100.0 255.255.255.0

The tunnel works and my users are able to RDP to 10.75.100.240. They have a preconfigured RDP icon with this IP.
The problem is I need to set their RDP icon to point to IP 19.39.160.240 (there is a specific reason for this not mentioned) without touching the VPN tunnel.
 
I can accomplish this by adding:
static (outside,inside) 19.39.160.240 10.75.100.240 netmask 255.255.255.255

After adding the NAT, I can point their RDP icon to 19.39.160.240 and it works fine. However, when I try to go to RDP to the real IP 10.75.100.240, it doesnt work anymore.

A packet tracer: packet-tracer input inside tcp 192.168.3.24 10000 10.75.100.240 3389 detailed

Phase: 10
Type: NAT
Subtype: rpf-check
Result: DROP
 
When I remove the static NAT, i'm able to RDP to it using 10.75.100.240 again. I'm curious as to why I can't rdp to 10.75.100.240 when the static NAT is in place. I would like the users to have the ability to reach both IPs so that I can put in the static NAT and take my time to repoint the RDP icons one at a time.
Even with the NAT in place, when they go to 10.75.100.240, it should hit the ACL inside_nat0_outbound and go out fine right?
Is traffic going out, but not able to come back?
 

asaEE.txt
0
trojan81
Asked:
trojan81
  • 2
  • 2
1 Solution
 
ullas_unniCommented:
hi trojan 81,

the rpf drop you are getting should be due to the static (outside,inside) 19.39.160.240 10.75.100.240 netmask 255.255.255.255....the outgoing traffic is getting nat exempted by ACL inside_nat0_outbound but the return traffic must be hitting the static.

to clarify this can you please attach the output of your packet-tracer.

if that is the case then you might need to do a nat exempt on the outside interface for the return traffic ie from your remote pvt ip.
0
 
trojan81Author Commented:
Ullas,

I think you are on the right track. Attached is the packet trace showing it working when I RDP to the NAT IP, and not working when I RDP to the real IP.
Is it even possible that both the NAT IP and the REAL IP still work simultaneously?

trace-working.txt
trace-notworking.txt
0
 
ullas_unniCommented:
trojan81,

have a look at this.. this is rpf drop part of your packet tracer output... it shows that the return traffic is hitting the static.. so it makes sense..

Phase: 10
Type: NAT
Subtype: rpf-check
Result: DROP
Config:
static (outside,inside) 19.39.160.240 10.75.100.240 netmask 255.255.255.255
  match ip outside host 10.75.100.240 inside any
    static translation to 19.39.160.240
    translate_hits = 0, untranslate_hits = 2
Additional Information:
 Forward Flow based lookup yields rule:
 out id=0xca4c4c90, priority=5, domain=nat-reverse, deny=false
        hits=6, user_data=0xc987abe0, cs_id=0x0, flags=0x0, protocol=0
        src ip=0.0.0.0, mask=0.0.0.0, port=0
        dst ip=10.75.100.240, mask=255.255.255.255, port=0, dscp=0x0

i can think of one way of achieving your requirement of accessing on both pvt and public ip.. try adding this with the static in place:

access-list reverse_nat_exempt permit ip host 10.75.100.240 192.168.3.0 255.255.255.0 nat (outside) 0 access-list reverse_nat_exempt outside

the above statements will nat exempt the return traffic when you are trying to access the server via pvt ip.. since nat exempt hits before the static the rpf-check should be fine.

so you should be able to access the server on both pvt and public ip.
0
 
trojan81Author Commented:
ullas,

That suggestion did not work. When I attempted to use the public IP it failed RPF check. I will award you the points since I went ahead and made the cut over night so I could make all changes without downtime.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now