Netgear FS728TPv2 FS728TP Software Administration Manual - Page 174

Configuring Access Control Lists, MAC ACL

Page 174 highlights

FS728TP Smart Switch Software Administration Manual Configuring Access Control Lists Access Control Lists (ACLs) ensure that only authorized users have access to specific resources while blocking off any unwarranted attempts to reach network resources. ACLs are used to provide traffic flow control, restrict contents of routing updates, decide which types of traffic are forwarded or blocked, and above all provide security for the network. FS728TP Smart Switch software supports IPv4 and MAC ACLs. Note: The FS728TP Smart Switch does not support mixed ACLs on same interface. In other words, you can bind MAC ACLs or IP ACLs to an interface, but you cannot bind both ACL types to an interface. To configure an ACL, first create an IPv4-based or MAC-based ACL ID. Then, create a rule and assign it to a unique ACL ID. Next, define the rules, which can identify protocols, source, and destination IP and MAC addresses, and other packet-matching criteria. Finally, use the ID number to assign the ACL to a port or to a LAG. The Security  ACL folder contains links to the following features: • Basic: • MAC ACL on page 174 • MAC Rules on page 175 • MAC Binding Configuration on page 177 • MAC Binding Table on page 178 • Advanced: • IP ACL on page 179 • IP Rules on page 181 • IP Extended Rule on page 182 • IP Binding Configuration on page 185 • IP Binding Table on page 187 MAC ACL A MAC ACL consists of a set of rules which are matched sequentially against a packet. When a packet meets the match criteria of a rule, the specified rule action (Permit/Deny) is taken and the additional rules are not checked for a match. There are multiple steps involved in defining a MAC ACL and applying it to the switch: 1. Use the MAC ACL page to create the ACL ID. 2. Use the MAC Rules page to create rules for the ACL. 3. Use the MAC Binding Configuration page to assign the ACL by its ID number to a port. 174 | Chapter 5: Managing Device Security

  • 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
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261

174
|
Chapter 5:
Managing Device Security
FS728TP Smart Switch Software Administration Manual
Configuring Access Control Lists
Access Control Lists (ACLs) ensure that only authorized users have access to specific
resources while blocking off any unwarranted attempts to reach network resources. ACLs are
used to provide traffic flow control, restrict contents of routing updates, decide which types of
traffic are forwarded or blocked, and above all provide security for the network. FS728TP
Smart Switch software supports IPv4 and MAC ACLs.
Note:
The FS728TP Smart Switch does not support mixed ACLs on same
interface. In other words, you can bind MAC ACLs
or
IP ACLs to an
interface, but you cannot bind both ACL types to an interface.
To configure an ACL, first create an IPv4-based or MAC-based ACL ID. Then, create a rule
and assign it to a unique ACL ID. Next, define the rules, which can identify protocols, source,
and destination IP and MAC addresses, and other packet-matching criteria. Finally, use the
ID number to assign the ACL to a port or to a LAG.
The Security
ACL folder contains links to the following features:
Basic:
MAC ACL
on page
174
MAC Rules
on page
175
MAC Binding Configuration
on page
177
MAC Binding Table
on page
178
Advanced:
IP ACL
on page
179
IP Rules
on page
181
IP Extended Rule
on page
182
IP Binding Configuration
on page
185
IP Binding Table
on page
187
MAC ACL
A MAC ACL consists of a set of rules which are matched sequentially against a packet. When
a packet meets the match criteria of a rule, the specified rule action (Permit/Deny) is taken
and the additional rules are not checked for a match.
There are multiple steps involved in defining a MAC ACL and applying it to the switch:
1.
Use the
MAC ACL
page to create the ACL ID.
2.
Use the
MAC Rules
page to create rules for the ACL.
3.
Use the
MAC Binding Configuration
page to assign the ACL by its ID number to a port.