Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Computing > Cisco > ip access-group name in - does it apply to systems on the same subnet?

Reply
Thread Tools

ip access-group name in - does it apply to systems on the same subnet?

 
 
Adam Przestroga
Guest
Posts: n/a
 
      06-09-2009
Hi all,

Perhaps a dumb question, but I need clarification.

I have an ACL defined on a Catalyst 3560 VLAN interface. Does it apply
to systems which reside within this VLAN and communicate with one
another? Or perhaps, this ACL works only when the VLAN systems
communicate with systems on another subnet?

Thanks,
APrzestroga
 
Reply With Quote
 
 
 
 
Trendkill
Guest
Posts: n/a
 
      06-10-2009
On Jun 9, 6:52*pm, Adam Przestroga <aprzestr...@op.pl> wrote:
> Hi all,
>
> Perhaps a dumb question, but I need clarification.
>
> I have an ACL defined on a Catalyst 3560 VLAN interface. Does it apply
> to systems which reside within this VLAN and communicate with one
> another? Or perhaps, this ACL works only when the VLAN systems
> communicate with systems on another subnet?
>
> Thanks,
> APrzestroga


You apply an access-list in or out on a vlan or interface. If you
apply it 'in' on vlan X, the access-list will only impact traffic it
receives from Vlan X to the vlan interface. More importantly to your
question, the only time a node on vlan X would send traffic to the
vlan interface, is when it is sending traffic to its default gateway
to be routed somewhere else. Conversely, applying it 'out' on vlan X,
will only impact traffic that the router is putting onto Vlan X from
another network. No access-list will impact traffic within a vlan
since that will be handled by arps on the local machines/servers and
switched...not routed. Access-lists are strictly layer 3, unless you
start looking at vacls and other layer 2 related options.
 
Reply With Quote
 
 
 
 
Adam Przestroga
Guest
Posts: n/a
 
      06-10-2009
Trendkill wrote:
> You apply an access-list in or out on a vlan or interface. If you
> apply it 'in' on vlan X, the access-list will only impact traffic it
> receives from Vlan X to the vlan interface. More importantly to your
> question, the only time a node on vlan X would send traffic to the
> vlan interface, is when it is sending traffic to its default gateway
> to be routed somewhere else. Conversely, applying it 'out' on vlan X,
> will only impact traffic that the router is putting onto Vlan X from
> another network. No access-list will impact traffic within a vlan
> since that will be handled by arps on the local machines/servers and
> switched...not routed. Access-lists are strictly layer 3, unless you
> start looking at vacls and other layer 2 related options.


Thank you for the clarification. I have applied L2 ACL (access-map) and
it seems to do the job.

BTW. The "out" ACL applied on the gateway interface of VLAN X is a bit
misleading...

Regards,
APrzestroga
 
Reply With Quote
 
Trendkill
Guest
Posts: n/a
 
      06-10-2009
On Jun 10, 6:43*pm, Adam Przestroga <aprzestr...@op.pl> wrote:
> Trendkill wrote:
> > You apply an access-list in or out on a vlan or interface. *If you
> > apply it 'in' on vlan X, the access-list will only impact traffic it
> > receives from Vlan X to the vlan interface. *More importantly to your
> > question, the only time a node on vlan X would send traffic to the
> > vlan interface, is when it is sending traffic to its default gateway
> > to be routed somewhere else. *Conversely, applying it 'out' on vlan X,
> > will only impact traffic that the router is putting onto Vlan X from
> > another network. *No access-list will impact traffic within a vlan
> > since that will be handled by arps on the local machines/servers and
> > switched...not routed. *Access-lists are strictly layer 3, unless you
> > start looking at vacls and other layer 2 related options.

>
> Thank you for the clarification. I have applied L2 ACL (access-map) and
> it seems to do the job.
>
> BTW. The "out" ACL applied on the gateway interface of VLAN X is a bit
> misleading...
>
> Regards,
> APrzestroga


Yes, the terminology has always carried some confusion. Best way to
think of it is as a router on a stick. Picture the router as having
one interface to a switch where all the nodes on the vlan are. If the
router puts packets out onto the vlan (i.e. destined to a server/node
on that network from another network), then that matches 'out' access
lists. If the router receives a packet in on that vlan interface
(i.e. destined to another network from one of the servers/nodes) then
it matches 'in' access lists. Then just scale that up to many
switched virtual interfaces (SVIs) or vlans on a 6500 series router/
msfc....works the same way with just more interfaces...and some happen
to be logical instead of physical.
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Voip PBX,Private Phone Systems,PBX Telephone Systems, Business Phone Systems broadbandera@gmail.com UK VOIP 9 07-24-2006 03:44 PM
Re: Voip PBX,Private Phone Systems,PBX Telephone Systems, Bu George Orwell UK VOIP 0 07-23-2006 05:35 PM
Any computer systems match good home systems? Richard DVD Video 7 08-24-2004 02:54 AM
java as a systems administration/systems programming language? Mike Java 2 06-17-2004 03:33 PM
[XSLT] could not apply "apply-templates" Stefan Siegl XML 1 07-18-2003 09:43 AM



Advertisments
 



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57