OnSite 2800 Series User Manual | 8 • Link scheduler configuration |
|
|
Some types of packets you do not have to tag with ACL. Voice and data packets from of for the OnSite itself are automatically tagged with predefined
•
•
Creating an access control list
The procedure to create an access control list is described in detail in chapter 7, “Access control list configura- tion” on page 79.
At this point a simple example is given, that shows the necessary steps to tag any outbound traffic from a Web server. The scenario is depicted in figure 21. The IP address of the Web server is used as source address in the permit statement of the IP filter rule for the access control list.
172.16.1.0
172.16.1.20/24
| lan |
|
| wan | |||
|
|
| |||||
|
|
| Node |
|
|
| IP Access |
|
|
| Node |
|
|
| Network |
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
| 172.16.1.1/24 | 17.254.0.91/16 |
| ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Figure 21. Scenario with Web server regarded as a single source host
A new access control list has to be created. In the example above, the
Access control list have an implicit “deny all” entry at the very end, so packets that do not match the first crite- ria of outbound Web related traffic will be dropped. That is why a second access control list
This procedure describes creating an access control list for tagging web traffic from the single source host at a certain IP address.
Link scheduler configuration task list | 101 |