07-12-2023 11:00 AM
Hi Team:
Am currently deploying some FTD 1120 in redundancy mode but am having some issues with anyconnect. Currently am able to browse the net but I cannot access my internal nodes that I want to access via the tunnel. I can see my anyconnect profile has the private network on the secure path but am not reaching them. Any thoughts why this is happening? What am i configuring wrong? Also in the FTD configuring RA VPN via FDM shouldn't it create a nat in Policies>NAT? I ask cause am not seeing it
Solved! Go to Solution.
07-12-2023 11:05 AM - edited 07-12-2023 01:07 PM
@jebanks you will need a NAT exemption rule to ensure traffic is not unintentially translated behind the outside interface. Example:
07-12-2023 11:05 AM - edited 07-12-2023 01:07 PM
@jebanks you will need a NAT exemption rule to ensure traffic is not unintentially translated behind the outside interface. Example:
07-12-2023 11:40 AM
@Rob Ingram Is it a bug or something that when using the process of creating a connection profile on the FTD via FDM that it does not create the nat exemption? cause i thought it would
07-12-2023 11:44 AM
It no bug
How FTD your internal subnet that you want to access so that it automatically add NAT.
That why you need manually add it
07-12-2023 11:44 AM
@jebanks well it's certainly part of the wizard when configuring the connection profile.
Even if you don't configure the NAT exemption rule as part of the wizard, you can create NAT rule as per the first example I provided.
07-12-2023 01:01 PM
would this be correct for exempt nat in FTD
07-12-2023 01:10 PM - edited 07-12-2023 01:14 PM
@jebanks it looks incorrect. I assume "ALLOWED_ANYCO" represents the internal network? And "AnyConnect_Pool" is the RAVPN IP address pool.
In which case change the original destination address to "AnyConnect_Pool" and change the source address of the translated packet to "ALLOWED_ANYCO".
FYI -
The source address of the original packet is the LAN networks
The destination address of the original packet is the RAVPN network
The source address of the translated packet is the LAN network
The destination address of the translated packet is the RAVPN network.
The source interface is inside and the destination interface is outside, which are correct in your screenshot.
07-12-2023 02:15 PM
@Rob Ingram @MHM Cisco World thank you. That is what i was doing in the beginning but was getting an error. had to delete and add it back and now its accepted but I still cannot ping the private addresses when i remote vpn
I was trying to added some ACL to see if that is the issue but seems its not. Atleast i know my nat is good now.
07-12-2023 02:48 PM - edited 07-12-2023 02:49 PM
do you have valid RA licenses?
07-12-2023 02:50 PM
Yes i do. Have the Plus
07-12-2023 02:58 PM
so in smart license it green enabled.
show vpn-sessiondb anyconnect <<- share this please
07-13-2023 09:18 AM
07-13-2023 09:29 AM
That ok' your anyconnect is get IP and active.
Now
Only config two acl
Inside to outside
And
Outside to inside
Allow internal to connect to anyconnect vpn and vpn to connect to internal
07-13-2023 09:31 AM
Yes did that but I think its my routing and windows firewall. I have one way ping at the moment. Checking those at the moment
07-13-2023 09:33 AM
Glad this issue finally solved
Have a nice day friend
MHM
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