Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 568
  • Last Modified:

ACLs on virtual interfaces

I have several VLANs defined on a stack of Cisco Catalyst 3750 switches.  (Layer 3).    IOS version is 12.2(25)SEE2)

I'm trying to do something that seems pretty simple, and I'm hopefully missing something obvious.

I want to prevent one VLAN from having any access to the other.   (ip routing is turned on, and it needs to be on.)   I followed another example I found online, and it seems like it should work.   The config lines are below.  I'm trying to prevent VLAN 99 from accessing VLAN 11 by using an ACL.   Address ranges are:  VLAN 11   10.67.11.0/24    VLAN 99  10.67.99.0/24

 interface Vlan11
 ip address 10.67.11.247 255.255.255.0
 ip access-group BAN_VLAN99 in


interface Vlan99
 ip address 10.67.99.247 255.255.255.0


ip access-list extended BAN_VLAN99
 deny   ip 10.67.99.0 0.0.0.255 any
 permit ip any any


But if I put a VLAN 99 address on a workstation, and plug into a VLAN 99 port, I'm still able to ping addresses on VLAN 11   (10.67.11.1 for example)

This seems embarrassingly simple... what am I missing??
0
asd-dave
Asked:
asd-dave
1 Solution
 
kf4zmtCommented:
Change this:  ip access-group BAN_VLAN99 in
to this: ip access-group BAN_VLAN99 out


Or better yet, modify your ACL and apply it as an inbound ACL on the vlan 99 interface.
0
 
Matt VCommented:
Have you applied the lists to the interfaces?  Also, this seems like a routing issue, the ACL should be applied where the routing is taking place.
0
 
Matt VCommented:
Nevermind, I missed the application on the interface.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
kf4zmtCommented:
Like this

ip access-list extended BAN_VLAN99
 deny   ip any 10.67.11.0 0.0.0.255
 permit ip any any

interface Vlan99
 ip access-group BAN_VLAN99 in
0
 
rfc1180Commented:
or:

interface Vlan99
 ip access-group DENY_VLAN11 in

ip access-list extended DENY_VLAN11
 deny   ip 10.67.99.0 0.0.0.255 10.67.11.0 0.0.0.255
 permit ip any any

Billy
0
 
Jimmy Larsson, CISSP, CEHNetwork and Security consultantCommented:
You have to think the other way around. You have an acl inbound on int Vlan11, which means that you at that point can filter traffic coming INBOUND into the router, FROM that interface. You block 10.67.99.0 source-addresses in that acl but on that interface and in that direction there will never come any traffic source from that addresses.

If you want to stop vlan 99 from accessing vlan 11 you should place an inbound acl on int vlan 99 instead, blocking traffic from vlan 11 ip addresses:

int vlan99
 ip access-group BAN_VLAN11 in
!
ip access-l ext BAN_VLAN11
 deny ip 10.67.11.0 0.0.0.255 any
 permit ip any any
!

Another option is to place the acl outbound instead of outbound, by using the "out"-parameter in the access-group interface-command.

/Kvistofta
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now