Avaya Configuring Traffic Filters and Protocol Prioritization Instrukcja Użytkownika Pobierz pdf (Strona 145)

Configuring IP Inbound Traffic Filters Using the BCC

308645-14.00 Rev 00

8-13

Example - Destination TCP Port

This example specifies destination TCP ports 30, 90, and 50 through 53 as match

criteria:

match/template/telnet-in# dest-tcp-port {30 90 50-53}

match/template/telnet-in#

Example - Source UDP Port

This example specifies source UDP port 162 as match criteria:

match/template/telnet-in# src-udp-port 162

match/template/telnet-in#

Example - Destination UDP Port

This example specifies destination UDP port 69 as match criteria:

match/template/telnet-in# dest-udp-port 69

match/template/telnet-in#

Example - Destination TCP and UDP Ports

This example specifies both destination TCP and UDP ports 53 as match criteria:

match/template/dest_tcp_udp# dest-tcp-udp-port 53

match/template/dest_tcp_udp#

Example - Source TCP and UDP Ports

This example specifies both source TCP and UDP ports 53 as match criteria:

match/template/source_tcp_udp# src-tcp-udp-port 53

match/template/source_tcp_udp#

Specifying Protocol Identifiers As Match Criteria

Internet Protocol Version 4 (IPv4) specifies an 8-bit protocol field to identify the

next-level protocol. You can use the protocol field to identify traffic that you want

to accept or drop.

Note:

If you filter on a TCP or UDP source or destination, the software

automatically changes the value to the protocol number associated with TCP

or UDP.

1 2 ... 140 141 142 143 144 145 146 147 148 149 150 ... 183 184

Brak uwag

Avaya Configuring Traffic Filters and Protocol Prioritization Instrukcja Użytkownika Strona 145