Specifications
Configuring and Managing VLANs
RoamAbout Mobility System Software Configuration Guide 4-19
Restricting Layer 2 Forwarding Among Clients
Bydefault,clientswithinaVLANareabletocommunicatewithoneanotherdirectlyatLayer2.
YoucanenhancenetworksecuritybyrestrictingLayer2forwardingamongclientsinthesame
VLAN.WhenyourestrictLayer2forwardinginaVLAN,MSSallowsLayer2forwardingonly
betweenaclient
andasetofMACaddresses,generallytheVLAN’sdefaultrouters.Clientswithin
theVLANarenotpermittedtocommunicateamongthemselvesdirectly.Tocommunicatewith
anotherclient,theclientmustuseoneofthespecifieddefaultrouters.
TorestrictLayer2forwardinginaVLAN,usethefollowingcommand:
set security l2-restrict vlan vlan-id
[mode {enable | disable}] [permit-mac mac-addr [mac-addr]]
Youcanspecifymultipleaddressesbylistingthemonthesamecommandlineorbyentering
multiplecommands.
RestrictionofclienttrafficdoesnotbeginuntilyouenablethepermittedMA C list.Usethemode
enableoptionwiththiscommand.
TochangeaMACaddress,usetheclearsecurityl2‐restrict
commandtoremove it,thenusethe
setsecurityl2‐restrictcommandtoaddthecorrectaddress.
clear security l2-restrict vlan vlan-id
[permit-mac mac-addr [mac-addr] | all]
TodisplayconfigurationinformationandstatisticsforLayer2forwardingrestriction,usethe
followingcommand:
show security l2-restrict [vlan vlan-id | all]
Examples
ThefollowingcommandsrestrictLayer2forwardingofclientdatainVLANabc_airtothedefault
routerswithMACaddressaa:bb:cc:dd:ee:ffand11:22:33:44:55:66,anddisplayrestriction
informationandstatistics:
set security l2-restrict vlan abc_air mode enable permit-mac aa:bb:cc:dd:ee:ff
11:22:33:44:55:66
success: change accepted.
show security l2-restrict
VLAN Name En Drops Permit MAC
Hits
---------- ---------------- ------- ---------- -------------------------- ------
----
1 abc_air Y 0
aa:bb:cc:dd:ee:ff 5947
Note: For networks with IP-only clients, you can restrict client-to-client forwarding using ACLs. (See
“Restricting Client-To-Client Forwarding Among IP-Only Clients” on page 15-28.)
Note: There can be a slight delay before functions such as pinging between clients become
available again after Layer 2 restrictions are lifted. Even though packets are passed immediately
once Layer 2 restrictions are gone, it can take 10 seconds or more for upper-layer protocols to
update their ARP caches and regain their functionality.