cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Bookmark
|
Subscribe
|
1280
Views
0
Helpful
11
Replies

Split Tunnel somehow not working

JesseRely
Level 1
Level 1

Hello,

At our client I configured Split Tunneling on an ASA but somehow it doesn't seem to function.

I have the feeling I'm missing something but I don't see what.

Situation as followed:

Network: 10.38.11.192 255.255.255.224

group-policy VPNCLIENTS attributes

dns-server value 10.38.11.203

split-tunnel-policy tunnelspecified

split-tunnel-network-list value Split_Tunnel_VDDnew

access-list Split_Tunnel_VDD standard permit 10.38.11.192 255.255.255.224

ip local pool VPNDHCP 10.38.12.1-10.38.12.100

I don't see what is wrong here since the same setup is used at other clients.

Hope someone can help.

Greetings Jesse

11 Replies 11

andrea.meconi
Level 2
Level 2

Please verify your ACL name.

Andrea

Woops, copied an old ACL, correct split-tunnel list:

access-list Split_Tunnel_VDDnew extended permit ip 10.38.11.192 255.255.255.224 10.38.12.0 255.255.255.0

Hello Jesse.

You can use the standard ACL to specify the network behind the ASA.

Can you remove the NAT statement, please?

Sorry, should have mentioned it before but I'm fairly new to this.

Isn't the NAT statement mandatory since my external adres is bound to it?

Also what do you mean with standard ACL, or does NAT look at the standard ACL once you remove it?

Again sorry, I started doing ASA's and PIX's recently and find them awefully cryptic sometimes.

Hi Andrea,

That's the ironic part, I followed that manual exactly. I even had our Senior Network Engineer take a loot at it and also said "Weird... it should work".

Therefor I have the feeling I'm missing something.

Can you provide all VPN configuration?

Have you set the default group policy when define the tunnel-group?

tunnel-group XXXXXXX general-attributes

default-group-policy VPNCLIENTS

Ok, thanks for the response, I am currently unable to log onto the ASA. I'll get back to you once I'm able to.

Hello Jesse,

Andrea advise ( Default-group-policy) should do it.

If that does not make a difference please post entire configuration.

Regards,

Julio Carvajal
Senior Network Security and Core Specialist
CCIE #42930, 2xCCNP, JNCIP-SEC

Hi Jesse,

The config looks fine. When you say it is not working - what exctly the issue? VPN clients unable to access the internal network? Few things you need to check...

1. nat 0 access-list for internal network to remote von client subnet.

2. same security traffic permit intra/inter interface allowed. (check the syntax for this command).

3. Route on internal routers that points the traffic to VPN subnets to ASA inside interface. (default should do as well).

hth

MS

Sorry for the long response, I'm at a different client today and not able to provide answers untill tomorrow.

Review Cisco Networking for a $25 gift card