Results 1 to 4 of 4

Thread: Access control list and Virtual Local Area Networks Maps

  1. #1
    Join Date
    Nov 2008
    Posts
    45

    Access control list and Virtual Local Area Networks Maps

    The 3750 Command Reference states: "There can be only one VLAN map per VLAN and it is applied as packets are received by a VLAN."

    Does "received by a VLAN" mean a packet that the 3750 forwards from one SVI to another or does it mean a packet that comes into a Gigabit Ethernet port that's a member of the VLAN? For access-groups, do the keywords IN and OUT always refer to physical ports (and never to SVIs or to the process of forwarding packets from one VLAN to another)?

  2. #2
    Join Date
    May 2008
    Posts
    181

    Re: Access control list and Virtual Local Area Networks Maps

    Quote Originally Posted by Nobleman View Post
    The 3750 Command Reference states: "There can be only one VLAN map per VLAN and it is applied as packets are received by a VLAN."

    Does "received by a VLAN" mean a packet that the 3750 forwards from one SVI to another or does it mean a packet that comes into a Gigabit Ethernet port that's a member of the VLAN? For access-groups, do the keywords IN and OUT always refer to physical ports (and never to SVIs or to the process of forwarding packets from one VLAN to another)?
    Since a Vlan is Logical, It Means Comes IN and is processed by a Logical Vlan interface, which would be at any number of physical ingress points based on trunks or access ports. Since I really didn't answer your bigger question, an access-list is 'routed' traffic being processed by the SVI. The VACL or vlan map will impact intra-vlan traffic which an access-list does not. L2 vs L3.

  3. #3
    Join Date
    Nov 2008
    Posts
    333

    Re: Access control list and Virtual Local Area Networks Maps

    Quote Originally Posted by Marco-D View Post
    Since a Vlan is Logical, It Means Comes IN and is processed by a Logical Vlan interface, which would be at any number of physical ingress points based on trunks or access ports. Since I really didn't answer your bigger question, an access-list is 'routed' traffic being processed by the SVI. The VACL or vlan map will impact intra-vlan traffic which an access-list does not. L2 vs L3.
    It seems to me that forwarding process from say, VLAN 10 to VLAN 20 would be another ingress point for VLAN 20.If this is not true, why not?

  4. #4
    Join Date
    May 2008
    Posts
    181

    Re: Access control list and Virtual Local Area Networks Maps

    Quote Originally Posted by The Edge View Post
    It seems to me that forwarding process from say, VLAN 10 to VLAN 20 would be another ingress point for VLAN 20.If this is not true, why not?
    I would agree with that, so I would assume that in that case, a vacl and an acl would both apply to that traffic.However, if it is vlan 10 to vlan 10, only a vacl would impact that traffic.I have never tried both at the same time, as I use ACLs for layer 3, and VACLs for sniffer ports, etc.Perhaps someone can correct me if a VACL only applies to intra-vlan traffic.

Similar Threads

  1. Windows 7 does not recognize any devices on local networks
    By Rajani^kanta in forum Networking & Security
    Replies: 5
    Last Post: 10-01-2011, 07:17 PM
  2. Can't access "local area connection properties" on Windows Vista
    By AK_Chopra in forum Networking & Security
    Replies: 3
    Last Post: 03-06-2009, 11:04 PM
  3. ACL ( Access Control List ) entry allowing tracert and traceroute
    By Daljeet in forum Networking & Security
    Replies: 3
    Last Post: 02-12-2008, 06:37 PM
  4. Replies: 2
    Last Post: 28-06-2008, 11:22 PM
  5. Local Area Connection > Local Only
    By Ashish Goenkar in forum Windows Vista Network
    Replies: 3
    Last Post: 29-01-2008, 12:19 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,914,217.34099 seconds with 16 queries