Ascend Pipeline Uživatelská příručka stáhnout pdf (Strana 194)

Defining Filters and Firewalls

Working with predefined call filters

Pipeline User’s Guide Preliminary January 30, 1998 6-25

This example SNEP filter is intended to be applied as a data filter on the Ethernet

interface. To create a SNEP data filter for the Ethernet interface of the Pipeline,

create a new Filter profile and define the following Input filters:

In filter 01...Generic...Forward=No

In filter 01...Generic...Offset=30

In filter 01...Generic...Length=2

In filter 01...Generic...Mask=ffff000000000000

In filter 01...Generic...Value=0457000000000000

In filter 01...Generic...Compare=Equals

In filter 01...Generic...More=No

In filter 02...Generic...Forward=No

In filter 02...Generic...Offset=33

In filter 02...Generic...Length=2

In filter 02...Generic...Mask=ffff000000000000

In filter 02...Generic...Value=0457000000000000

In filter 02...Generic...Compare=Equals

In filter 02...Generic...More=No

In filter 03...Generic...Forward=Yes

In filter 03...Generic...Offset=0

In filter 03...Generic...Length=0

In filter 03...Generic...Mask=0000000000000000

In filter 03...Generic...Value=0000000000000000

In filter 03...Generic...Compare=Equals

In filter 03...Generic...More=No

If you have enough Output filters available in the NetWare Call filter (for

example, when you don’t extend the filter to include RIP as described in

“Extending the predefined filter for RIP packets” on page 6-23, or if you’re using

NetWare 4.0 or higher and you don’t need the predefined SAP filters) you could

choose instead to include these SNEP filters as Output filters in the Call Filter.

1 2 ... 189 190 191 192 193 194 195 196 197 198 199 ... 320 321

Žádné komentáře

Ascend Pipeline Uživatelská příručka Strana 194