10-02-2017 07:25 AM - edited 03-12-2019 04:35 AM
So I am setting up a brand new VPN for my users on my ASA 5525 using ASDM 7.6(1). I walked throught he wizard to set up the system so my users can connect via AnyConnect. I installed the certs, set up RADIUS for authentication, etc... no issues. I connected and authenticated and instantly I lost all Intenet access and I could not access my LAN. I did read some articles about NAT and ACL setup, but I did not understand them well enough to be able to implememnt the solution to my system. I'd have thought the "Wizard" would have helped configure the VPN so my users could access my LAN.
Anyway, my address pool is 10.254.254.0/24 for the VPN users, I need them to access my inside VLAN object 10.10.1.2 (inside router) which will know how to route them once they are inside the network.
I don't even know what part of the config to provide, I'm guessing that it has to do with the NAT and/or ACL on my ASA, but I don't know what to do. Any help would be greatly appreciated.
Solved! Go to Solution.
10-03-2017 07:48 AM
Hello @MinnesoatGuy,
I checked the configuration and I´m sharing my findings:
group-policy GroupPolicy_HouseVPN internal
group-policy GroupPolicy_HouseVPN attributes
split-tunnel-policy excludespecified >> You have Excludespecified and the ACL is any, it going to drop all the traffic and it will not send any traffic to the ASA.
split-tunnel-network-list value Local_LAN_Access_VPN
access-list Local_LAN_Access_VPN remark Allows for VPN access to local LAN
access-list Local_LAN_Access_VPN standard permit host 0.0.0.0
I also found a static route to the inside for that traffic, that means if the ASA receives the traffic from the inside it will send it back through the same interface and not to the outside
route inside 10.254.254.0 255.255.255.0 10.10.1.2
My sugestions to copy and paste:
access-list Local_LAN_Access_VPN standard permit host 10.10.1.2
no access-list Local_LAN_Access_VPN standard permit host 0.0.0.0
group-policy GroupPolicy_HouseVPN attributes
split-tunnel-policy tunnelspecified
exit
no route inside 10.254.254.0 255.255.255.0 10.10.1.2 1
no nat (outside,inside) after-auto source static NETWORK_OBJ_10.254.254.0_24 NETWORK_OBJ_10.254.254.0_24 no-proxy-arp
nat (inside,outside) source static 10.10.1.2 10.10.1.2 destination static NETWORK_OBJ_10.254.254.0_24 NETWORK_OBJ_10.254.254.0_24 no-proxy-arp route-lookup
Apply the changes and let me know, i will be waiting for any reply.
HTH
Gio
10-02-2017 07:55 AM
10-02-2017 01:30 PM
10-02-2017 02:10 PM
10-03-2017 07:48 AM
Hello @MinnesoatGuy,
I checked the configuration and I´m sharing my findings:
group-policy GroupPolicy_HouseVPN internal
group-policy GroupPolicy_HouseVPN attributes
split-tunnel-policy excludespecified >> You have Excludespecified and the ACL is any, it going to drop all the traffic and it will not send any traffic to the ASA.
split-tunnel-network-list value Local_LAN_Access_VPN
access-list Local_LAN_Access_VPN remark Allows for VPN access to local LAN
access-list Local_LAN_Access_VPN standard permit host 0.0.0.0
I also found a static route to the inside for that traffic, that means if the ASA receives the traffic from the inside it will send it back through the same interface and not to the outside
route inside 10.254.254.0 255.255.255.0 10.10.1.2
My sugestions to copy and paste:
access-list Local_LAN_Access_VPN standard permit host 10.10.1.2
no access-list Local_LAN_Access_VPN standard permit host 0.0.0.0
group-policy GroupPolicy_HouseVPN attributes
split-tunnel-policy tunnelspecified
exit
no route inside 10.254.254.0 255.255.255.0 10.10.1.2 1
no nat (outside,inside) after-auto source static NETWORK_OBJ_10.254.254.0_24 NETWORK_OBJ_10.254.254.0_24 no-proxy-arp
nat (inside,outside) source static 10.10.1.2 10.10.1.2 destination static NETWORK_OBJ_10.254.254.0_24 NETWORK_OBJ_10.254.254.0_24 no-proxy-arp route-lookup
Apply the changes and let me know, i will be waiting for any reply.
HTH
Gio
10-03-2017 08:48 AM
10-03-2017 03:13 PM
10-04-2017 12:47 PM
10-05-2017 06:24 AM
Hello @MinnesoatGuy,
The traffic is being sent through the inside interface but the reply is not received on the ASA, you need to check the internal routing in order to see if the subnet 10.254.254.0/24 is being sent elsewhere.
How is the topology behind the ASA? You have a Layer 3 Switch but do you have something else?
HTH
Gio
10-05-2017 07:42 AM
10-05-2017 08:38 AM
Hello @MinnesoatGuy,
Since you don´t know what is that ip, you can check doing "show cdp neighbors" or "show arp" in order to know if that IP is active or not. Since you have a static route to that IP, the change should be removing that static route and apply the route to send the traffic to the ASA.
If the default route goes to the ASA, you should only remove that route and it will work. Let me know how it goes.
HTH
Gio
10-05-2017 12:59 PM
10-05-2017 01:22 PM
Hello @MinnesoatGuy,
Regarding the default gateway, you are not going to see anything to the ASA just the subnets or host you applied on the ACL for the Split-Tunnel so the DW remains the LAN or Wifi GW.
On the other hand, I saw the route and I think you applied the wrong one since you added the subnet 10.255.255.0/24 and you are using 10.254.254.0/24, maybe this was the problem :)
HTH
Gio
10-06-2017 04:06 AM
10-06-2017 06:33 AM
Well, if you added the route correctly and it is not working, according to your question the split-tunnel is working as expected since the traffic is traversing the ASA since you can see the traffic on the previous capture. The issue is when the traffic reaches your internal network since it doesn´t send the traffic back to the ASA, if the routing is off the table then it should be something blocking the reply.
Maybe we can try to enable a computer on the split-tunnel and place a wireshark in order to verify first if the traffic is reaching the device and what is happening with the reply.
HTH
Gio
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