User`s guide

Table Of Contents
Defining Filters and Firewalls
Working with predefined call filters
6-24 Preliminary January 30, 1998 Pipeline User’s Guide
Out filter 08...Generic...Compare=Equals
Out filter 08...Generic...More=No
Out filter 09...Generic...Forward=No
Out filter 09...Generic...Offset=0
Out filter 09...Generic...Length=6
Out filter 09...Generic...Mask=ffffffffffff0000
Out filter 09...Generic...Value=ffffffffffff0000
Out filter 09...Generic...Compare=Equals
Out filter 09...Generic...More=Yes
Out filter 10...Generic...Forward=No
Out filter 10...Generic...Offset=27
Out filter 10...Generic...Length=8
Out filter 10...Generic...Mask=ffffffffffffffff
Out filter 10...Generic...Value=ffffffffffff0453
Out filter 10...Generic...Compare=Equals
Out filter 10...Generic...More=No
Out filter 11...Generic...Forward=Yes
Out filter 11...Generic...Offset=0
Out filter 11...Generic...Length=0
Out filter 11...Generic...Mask=0000000000000000
Out filter 11...Generic...Value=0000000000000000
Out filter 11...Generic...Compare=Equals
Out filter 11...Generic...More=No
Defining a SNEP data filter for Ethernet
NetWare’s copy-protection scheme makes use of Serialization Number Exchange
Protocol (SNEP) packets, which are sent and received by all servers on the
network. SNEP packets occur as request/response pairs between servers. When
NetWare servers are supported on both sides of the WAN, these packet exchanges
can keep an IPX connection active unnecessarily.