Netgear XSM4324FS User Manual - Page 701

M4300 Intelligent Edge Series Fully Managed Stackable Switches • Source IP Address: 192.168.187.0 • Source IP Mask: 255.255.255.0 For additional information about IP ACL rules, see Configure Rules for an IP ACL on page 613. 3. Click the Add button. 4. From the IP Rules page, create a second rule for IP ACL 1 with the following settings: • Rule ID: 2 • Action: Permit • Match Every: True 5. Click the Add button. 6. From the IP Binding Configuration page, assign ACL ID 1 to the interface gigabit ports 2, 3, and 4, and assign a sequence number of 1 (See Configure IP ACL Interface Bindings on page 628). By default, this IP ACL is bound on the inbound direction, so it examines traffic as it enters the switch. 7. Click the Apply button. 8. Use the IP Binding Table page to view the interfaces and IP ACL binding information (See View and Delete IP ACL Bindings in the IP ACL Binding Table on page 629). The IP ACL in this example matches all packets with the source IP address and subnet mask of the Finance department's network and deny it on the Ethernet interfaces 2, 3, and 4 of the switch. The second rule permits all non-Finance traffic on the ports. The second rule is required because there is an explicit deny all rule as the lowest priority rule. Differentiated Services (DiffServ) Standard IP-based networks are designed to provide best effort data delivery service. Best effort service implies that the network deliver the data in a timely fashion, although there is no guarantee that it will. During times of congestion, packets might be delayed, sent sporadically, or dropped. For typical Internet applications, such as e-mail and file transfer, a slight degradation in service is acceptable and in many cases unnoticeable. However, any degradation of service has undesirable effects on applications with strict timing requirements, such as voice or multimedia. Quality of Service (QoS) can provide consistent, predictable data delivery by distinguishing between packets with strict timing requirements from those that are more tolerant of delay. Packets with strict timing requirements are given special treatment in a QoS-capable network. With this in mind, all elements of the network must be QoS-capable. If one node cannot meet the necessary timing requirements, this creates a deficiency in the network path and the performance of the entire packet flow is compromised. Configuration Examples 701 User Manual