02-27-2024 07:57 AM
Hi all, I have an FTDv in Azure and traffic going towards the public IP is not being natted towards an internal server. I see the traffic hit it in the packet capture but no nat rules are applying and it is not being forwarded inside because of that:
The rule is :
nat (outside,inside) source static any interface destination static interface 10.1.1.1 service SVC_622771026011 SVC_622771026011 no-proxy-arp
The rule is getting 0 hits. In the packet capture with a trace, it is not hitting any nats. The FTD has a route to 10.1.1.1 and it is allowed in the ACP.
thoughts?
02-27-2024 08:04 AM
You need to make your NAT from inside to outside'
Also you dont need to NATing public IP of client want to access Server inside' only what you need is NATing server private IP inside to public IP outside (interface IP)
MHM
02-27-2024 08:28 AM
MHM Cisco World, you respond to all of my posts and you are often wrong. Respectfully, if you are not confident in the solution, please stop replying.
The NAT cannot be inside->outside because this server is to be accessible from the internet - I am not trying to give internet egress connectivity to the server.
02-27-2024 08:36 AM - edited 02-27-2024 08:49 AM
No I respect your opinion' sometime hit sometime not hit but here we share idea' you can take it or not it depends on your view of solution.
Anyway if you are familiar with NAT you must know that static NAT is bidirectional and it can use for client try to access server inside.
Sure you need to use l4 port
This link for more detail about NAT to access server' maybe you need to refresh your info
*****Also dont forget to add acl allow access to server from outside to it private IP.
MHM
02-27-2024 08:57 AM
Yes I do know that static is bidirectional which is why your suggestion to change it from outside -> inside to inside->outside does not make sense. Anyway just for a test I tried this and same result the nat is not being hit:
02-27-2024 09:06 AM
Under which category this NAT add
Auto NAT or before or after ?
MHM
02-27-2024 09:13 AM
It is a before NAT
02-27-2024 09:20 AM
Do packet-tracer from outside to inside and check where the packet drop
Two possiblity either the traffic can not route to server or it hit some other NAT (NAT order issue)
MHM
02-27-2024 09:26 AM
It's not hitting any NAT rules so it thinks to just route it back externally.
Phase: 1
Type: CAPTURE
Subtype:
Result: ALLOW
Config:
Additional Information:
MAC Access list
Phase: 2
Type: ACCESS-LIST
Subtype:
Result: ALLOW
Config:
Implicit Rule
Additional Information:
MAC Access list
Phase: 3
Type: ROUTE-LOOKUP
Subtype: No ECMP load balancing
Result: ALLOW
Config:
Additional Information:
Destination is locally connected. No ECMP load balancing.
Found next-hop [outside ip] using egress ifc identity(vrfid:0)
Phase: 4
Type: NAT
Subtype: per-session
Result: ALLOW
Config:
Additional Information:
Phase: 5
Type: ACCESS-LIST
Subtype:
Result: DROP
Config:
Implicit Rule
Additional Information:
02-27-2024 09:30 AM
It can fake result if you dont use packet-tracer correctly'
Can I see the packet tracer ypu use
MHM
02-27-2024 09:40 AM
Outside interface
Random source IP, Destination is my outside interface IP
TCP21 source and dest
02-27-2024 09:43 AM
The source is any port and destiantion is tcp21 in end you want to access ftp server inside which use that port
02-27-2024 10:16 AM
Yes that is obvious. Setting the source port shouldn't make any difference and I can't select any in a packet tracer so I just copied the dsetination.
02-27-2024 10:52 AM
Ok meaning use any use port 12345 (random ports)
For packet-tracer use
Inside from server (real IP 10.x.x.x) to outside any random ip source port tcp21 and destiantion port 12345
Share packet tracer
MHM
02-27-2024 11:42 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide