Table of Contents
Advertisement
Configuring IPX Routing
Configuring IPX routing connections
Peer dial-in for routing to NetWare clients
Dial-in NetWare clients do not have IPX network addresses. To establish an IPX routing
connection to the local network, such a client must dial in with PPP software and the
Connection profile must specify Peer=Dialin. In addition, the MAX must have a virtual IPX
network defined for assignment to these clients (as described in "IPX Pool #" on page 11-5).
Peer=Dialin causes the MAX unit to assign the virtual IPX network number to the dial-in
client during PPP negotiation. If the client does not provide its own unique node number, the
MAX unit also assigns a unique node number to the client. The unit does not send RIP and
SAP advertisements across the connection, and it ignores RIP and SAP advertisements
received from the far end. However, it does respond to RIP and SAP queries received from
dial-in clients. (For example, see "Configuring a dial-in client connection" on page 11-11.)
Controlling RIP and SAP transmissions across the WAN connection
You can set IPX RIP to Both (the default) indicating that RIP broadcasts will be exchanged in
both directions. You can also disable the exchange of RIP broadcasts across a WAN connection
or specify that the MAX only send or only receive RIP broadcasts on the connection.
Setting IPX SAP to Both (the default) specifies that SAP broadcasts will be exchanged in both
directions. If you enable SAP to both send and receive broadcasts on the WAN interface, the
MAX broadcasts its entire SAP table to the remote network and listens for SAP table updates
from that network. Eventually, both networks have a full table of all services on the WAN. To
control which services are advertised and where, you can disable the exchange of SAP
broadcasts across a WAN connection, specify that the MAX only send or only receive SAP
broadcasts on that connection, or use IPX SAP filters.
Dial Query for bringing up a connection on the basis of service queries
Setting the Dial Query parameter to Yes configures the MAX to bring up a connection when it
receives a SAP query for service type 0004 (File Server) and that service type is not present in
the MAX SAP table. If the MAX has no SAP table entry for service type 0004, it brings up
every connection that has Dial Query set. If 20 Connection profiles have Dial Query set, the
MAX brings up all 20 connections in response to the query.
Note: If the MAX unit has a static IPX route for even one remote server, it brings up that
connection instead of choosing the more costly solution of bringing up every connection that
has Dial Query set.
Netware t/o watchdog spoofing
The Netware t/o parameter defines the number of minutes the MAX enables clients to remain
logged in after losing a connection. NetWare servers send out NCP watchdog packets to
determine which logins are active, so that they can log out inactive clients. Only clients that
respond to watchdog packets remain logged in.
Watchdog packets can cause a WAN connection to stay up unnecessarily. But if the MAX
simply filtered them, the remote server would drop active as well as inactive client logins. To
prevent unwanted client logouts while enabling WAN connections to be brought down in times
of inactivity, the MAX local to IPX servers responds to NCP watchdog requests as a proxy for
clients on the other side of an IPX routing or IPX bridging connection. Responding to such
requests is commonly called watchdog spoofing.
11-10
MAX 6000/3000 Network Configuration Guide
Advertisement
Chapters
Table of Contents
