Showing results for 
Search instead for 
Did you mean: 

How do I block Traffic between VPN users?


We have a few VPN-Servers (Firepower 1140).

When a User connects he gets a static IP via RADIUS (e.g. or a address from a Adress-Pool configured on the server (e.g.

With our current configuration this allows traffic between the users ( <->

How can we prevent that?

On a Wireless LAN Controller C9800 I can set P2P Blocking Action to Drop.

Is there something similar for the ASA?

We mostly use AnyConnect, but there are a few users that use their own IPsec-Client.


11 Replies 11

Rising star
Rising star

On an ASA you can create two different zones for these networks and apply policy rules.


Sorry, I guess my issue is simpler than my example.

I also want to block traffic between and

you need all user can not talk to all users or specific one?

Yes, no one should be able to talk to any other vpn user.

You can use VPN filter, 
deny VPN pool1 -> VPN Pool2
permit VPN pool1 -> LAN (Inside)


To block traffic between VPN users on a Firepower 1140, you can create an access control policy and apply it to the VPN users.

  1. Go to Configuration > Firewall > Access Control and create a new policy.
  2. In the policy, create a rule that denies traffic between the VPN user subnet (e.g. and the VPN address pool subnet (e.g.
  3. Apply this policy to the VPN users by going to Configuration > Remote Access VPN > AnyConnect > Group Policy and selecting the policy in the "Access Control Policy" field.

Additionally, you can also use the "same-security-traffic permit inter-interface" command under the VPN configuration to block traffic between VPN users.

This will block all traffic between VPN users, regardless of the VPN connection type (AnyConnect or IPsec).

Please note that this will only work if VPN users are assigned IP addresses from different subnets.

Please rate this and mark as solution/answer, if this resolved your issue
All the best,

@khorram1998 wrote:

Please note that this will only work if VPN users are assigned IP addresses from different subnets.

I think that is not good enough for me.

@fhk-cwempe try using VPN Filter applied to the Remote Access VPN group policy to first deny traffic between the anyconnect user IP networks, then permit the rest of the required traffic.




Thank you all for the answers.

But I think configuring access lists/policies based in IP adresses/subnetzs is to complex for us, because we would need many exceptions.

no you just need two vpn-filter 

access-list VPNfilter1 extended deny ip VPN Pool1 VPN pool2 
access-list VPNfilter1 extended permit ip any any 

access-list VPNfilter2 extended deny ip VPN Pool2 VPN pool1
access-list VPNfilter2 extended permit ip any any 

then config these VPNfilter's under group-policy 
this make VPN pool1 can not connect to VPN pool2


I do need more exceptions, than I mentioned here.

Like different IT personell (via VPN or not) accessing user devices connected via VPN.

We also got several VPN-IP-Pools for different business units.


But thanks for your answers.
No I know what the solution would be if we decide to go this way.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: