Configuring IPX RIP/SAP Filtering
Page 27-25
As another example, to display a list of all global RIP Input filters, you would enter:
ipxf ri global
A screen similar to the following displays:
Displaying all global RIP INPUT filters:
GP:VL (s/p/vc)
#
Type
Net/Mask
Node/Mask
Svc Md
(Peer ID)
------
------------ ---------------------- -----------------------------------
------ ---- --------------------
3
RIP IN
67/ffffffff
B
global
IPX RIP/SAP Filter Precedence
Whenever you use multiple “allow” filters you must first define a filter to block all RIPs or
SAPs. Then, all of the seceding “allow” filters of the same type must be
at least
as specific in
all areas in order for the filters to work. Note that filtering precedence is related only to
“allow” filters. Multiple “block” filters can be defined with varying specificity in each of the
areas of the filter. The filtering done by the configurable parameters (Net/Mask, Node/Mask,
Service/Mode) in the “allow” filter must be at least as specific as the filtering defined in the
“block” filter.
As an example, consider a switch that knows of multiple Type 4 SAPs on various networks,
including a network with an address of “40.” The switch also knows of various types of SAPs
on Network 40. For this example, you want to block all SAPs coming from Network 40, but
you want to allow all Type 4 SAPs, including the ones that come from Network 40.
To meet these objectives, you must configure the filters like this:
#
Type
Net/Mask
Node/Mask
Svc
Md GP:VL
------ ------------
---------------------- -------------------------------------------------------
----------
1
SAP IN
40/ffffffff
all nodes
ALL
B
global
2
SAP IN
40/ffffffff
all nodes
4
A
global
The filters shown below will
not
work for our example because in Filter 2 the type of service
is
less
specific than the type defined in Filter 1. All Type 4 SAPs will be blocked by the filter.
#
Type
Net/Mask
Node/Mask
Svc
Md GP:VL
------ ------------
---------------------- ---------------------------------------------
------
----
----------
1
SAP IN
All networks
all nodes
4
B
global
2
SAP IN
40/ffffffff
all nodes
ALL
A
global
The following filters will also
not
work because in Filter 2 the network and netmask are
less
specific than the network and netmask defined in Filter 1. All SAPs from Network 40 will be
blocked by the filter.
#
Type
Net/Mask
Node/Mask
Svc
Md GP:VL
------ ------------
---------------------- ---------------------------------------------
------
----
----------
1
SAP IN
40/ffffffff
all nodes
ALL
B
global
2
SAP IN
All networks
all nodes
4
A
global
Summary of Contents for Omni Switch/Router
Page 1: ...Part No 060166 10 Rev C March 2005 Omni Switch Router User Manual Release 4 5 www alcatel com ...
Page 4: ...page iv ...
Page 110: ...WAN Modules Page 3 40 ...
Page 156: ...UI Table Filtering Using Search and Filter Commands Page 4 46 ...
Page 164: ...Using ZMODEM Page 5 8 ...
Page 186: ...Displaying and Setting the Swap State Page 6 22 ...
Page 202: ...Creating a New File System Page 7 16 ...
Page 270: ...Displaying Secure Access Entries in the MPM Log Page 10 14 ...
Page 430: ...OmniChannel Page 15 16 ...
Page 496: ...Configuring Source Route to Transparent Bridging Page 17 48 ...
Page 542: ...Dissimilar LAN Switching Capabilities Page 18 46 ...
Page 646: ...Application Example DHCP Policies Page 20 30 ...
Page 660: ...GMAP Page 21 14 ...
Page 710: ...Viewing the Virtual Interface of Multicast VLANs Page 23 16 ...
Page 722: ...Application Example 5 Page 24 12 ...
Page 788: ...Viewing UDP Relay Statistics Page 26 24 ...
Page 872: ...The WAN Port Software Menu Page 28 46 ...
Page 960: ...Deleting a PPP Entity Page 30 22 ...
Page 978: ...Displaying Link Status Page 31 18 ...
Page 988: ...Displaying ISDN Configuration Entry Status Page 32 10 ...
Page 1024: ...Backup Services Commands Page 34 14 ...
Page 1062: ...Diagnostic Test Cable Schematics Page 36 24 ...
Page 1072: ...Configuring a Switch with an MPX Page A 10 ...
Page 1086: ...Page B 14 ...
Page 1100: ...Page I 14 Index ...