3Com 3500 - page 374

374 CHAPTER 15: PACKET FILTERS
bridge packetFilter
✓ 3500
✓ 9000
9400
3900
9300
create custom
For CoreBuilder 9000: Applies to Layer 3 switching modules only.
Creates a custom packet filter using the built-in editor.
Valid Minimum Abbreviation
b pa c c
Important Considerations
■You can create custom filters to add filtering logic based on the
content of the packet.
■The built-in editor is a simple one-line-at-a-time editor that supports a
short list of EMACS-style editing commands.
■Save your work periodically with Ctrl+w. When you press Esc to exit
the built-in editor, the system examines the filter’s syntax. If the syntax
is correct, the filter is loaded into the switch’s non-volatile memory.
Incorrect syntax filters are not loaded into non-volatile memory and
are not saved across editor sessions.
■After you create the filter, edit it using “bridge packetFilter edit” as
described later in this chapter.
■The alternative to creating a custom packet filter using the built-in
editor is to create the packet filter on an external system and transfer
it across the network into the switch. See “bridge packetFilter load”
later in this ch apter.
■You can also use the Filter Builder component of the Web
Management application to create custom filters.
■On CoreBuilder 3500 systems, you can load the f ilter on to the
switch directly from Filter Builder.
■On CoreBuilder 9000 system, you must save the f ilter to an ASCII
file and then download the file to the switch m anually using TFTP
and the “bridge packetFilter load” com mand described later in this
chapter.
■The system only creates the packet filter definitions. You must still
assign the standard filter to ports and filtering paths, as described for
“bridge packetFilter assign” later in this chap ter.