User`s guide
Table Of Contents
- Ascend Customer Service
- How to use this guide
- What you should know
- Documentation conventions
- How to use the on-board software
- Manual set
- Configuring WAN Connections
- Configuring IP Routing
- Introduction to IP routing on the Pipeline
- Managing the routing table
- Parameters that affect the routing table
- Static and dynamic routes
- Configuring static routes
- Specifying default routes on a per-user basis
- Enabling the Pipeline to use dynamic routing
- Route preferences
- Viewing the routing table
- Fields in the routing table
- Removing down routes to a host
- Identifying Temporary routes in the routing table
- Configuring IP routing connections
- Ascend Tunnel Management Protocol (ATMP)
- IP Address Management
- Connecting to a local IP network
- BOOTP Relay
- DHCP services
- Dial-in user DNS server assignments
- Local DNS host address table
- Network Address Translation (NAT) for a LAN
- Configuring IPX Routing
- How the Pipeline performs IPX routing
- Adding the Pipeline to the local IPX network
- Working with the RIP and SAP tables
- Configuring IPX routing connections
- Configuring the Pipeline as a Bridge
- Defining Filters and Firewalls
- Setting Up Pipeline Security
- Pipeline System Administration
- Pipeline 75 Voice Features
- IDSL Implementations
- APP Server utility
- About the APP Server utility
- APP Server installation and setup
- Configuring the Pipeline to use the APP server
- Using App Server with Axent SecureNet
- Creating banner text for the password prompt
- Installing and using the UNIX APP Server
- Installing and using the APP Server utility for DO...
- Installing and using the APP Server utility for Wi...
- Installing APP Server on a Macintosh
- Troubleshooting
- Upgrading system software
- What you need to upgrade system software
- Displaying the software load name
- The upgrade procedure
- Untitled
Defining Filters and Firewalls
Introduction to filters
6-4 Preliminary January 30, 1998 Pipeline User’s Guide
Call filters for managing connections
Call filters are used to prevent unnecessary connections and to help the Pipeline
distinguish active traffic from “noise.” By default, any traffic to a remote site
triggers a call to that site, and any traffic across an active connection resets the
connection’s idle timer.
Note:
The idle timer is set to 120 seconds by default. If a connection is inactive
for two minutes, the idle timer expires and the Pipeline terminates the
connection.
Call filters define which packets are not considered active traffic on a particular
connection. They identify which packets should not originate a connection or
reset the idle timer. Call filters do not affect which packets are transmitted or
received across active connections.
Figure 6-2. Call filters used to prevent resetting the timer
To define which packets will not reset the idle timer or keep a connection active,
apply a call filter to a Connection or Answer profile using the following steps:
1
Open Ethernet > Connection or Answer > profile
Note:
You can apply a filter in the Answer profile only if the Profile Reqd
parameter is set to No.
2
Open the Session Options submenu.
3
Apply the call filter.
For example:
Call Filter=5
If this parameter is set to zero, the default, no filter is applied.
WAN
Data Filter