***************************************************************** DISCLAIMER Novell, Inc. makes no representations or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of any NetWare software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any NetWare software. Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of re-creating lost data, the cost of any substitute equipment or program, or claims by any party other than you. Novell strongly recommends a backup be made before any software is installed. Technical support for this software may be provided at the discretion of Novell. ***************************************************************** WARNING: -------- This version of IPCONFIG (v2.02) will not work with TCPIP v1.0 or v1.01. Please do NOT install this if you DO NOT have SNMP Agent Update disk v2.0 and TCPIP.NLM (v2.02). CONTENTS -------- IPCONFIG.NLM README.TXT INSTALLATION: ------------- 1. Login to the server from a workstation as Supervisor 2. CD to SYS:\SYSTEM 3. Change IPCONFIG NLM file attributes to write-enabled in the SYSTEM directory. FLAG IPCONFIG.NLM RW 4. Copy the new IPCONFIG.NLM to IPCONFIG.OLD in SYSTEM directory 5. Copy IPCONFIG.NLM v2.02 to SYSTEM directory 6. Change file attributes to read-only and share. FLAG IPCONFIG.NLM RO S 7. Ensure that TCPIP NLM is unloaded and then reloaded prior to loading the new IPCONFIG NLM. USAGE: ------ If you require static routes, you should indicate the static routes in the SYS:\ETC\GATEWAYS file and then load the IPCONFIG NLM after you load the TCPIP NLM and bind IP. It is possible to do static routing as well as static subnet routing with this version of IPCONFIG.NLM (v2.02) along with TCPIP (v2.02). Format of SYS:ETC\GATEWAYS -------------------------- Each line in SYS:ETC\GATEWAYS has the following format: { NET network_name | {network_number[/network_mask]} | HOST host} GATEWAY gateway [METRIC cost] [ {ACTIVE | PASSIVE } ] where: The network_name is the name of a network in SYS:ETC\NETWORKS. The network_number/network_mask is the IP network address and its subnet mask; the subnet mask is optional. If the network_mask is not specified, the subnet mask is derived from the network number, excluding all trailing zeros. The host is the IP address of a host or the name of a host in SYS:ETC\HOSTS. The gateway is the IP address of a gateway on a locally connected network or the name of such a gateway in SYS:ETC\HOSTS. The cost, or measure of expense, is a value greater than or equal to 1 but less than or equal to 15. The active or passive indicates the type of route for routing information. For example: NET 2.0.0.0 GATEWAY 193.1.1.1 HOST 129.1.0.3 GATEWAY 193.1.1.1 PASSIVE NET 130.57.1.0/255.255.255.0 GATEWAY 193.1.1.1 PASSIVE Loading the IPCONFIG NLM ------------------------ To add the static routes in SYS:ETC\GATEWAYS to the routing database, you must load the IPCONFIG NLM. This can be done by entering the LOAD IPCONFIG command at the system console. Normally, you place this command in your SYS:SYSTEM\AUTOEXEC.NCF file after loading tcpip and binding IP to interfaces so that the static routes are added each time the system is loaded. The command is as follows: LOAD IPCONFIG NOTE: If you do not have any static routes to configure, you do not need to load IPCONFIG. IPCONFIG reads SYS:ETC\GATEWAYS, places each route into the routing database, and then exits. While you are "debugging" your GATEWAYS file, problems in the file may cause IPCONFIG to print diagnostic messages. For each route IPCONFIG finds in SYS:ETC\GATEWAYS, IPCONFIG adds a routing entry for the host or network indicated. The first hop in the new routing entry is the provided gateway and the metric is the given cost. If no metric is given, a cost of 1 is used. IPCONFIG will support a static subnet route if the subnet mask is associated with the subnetwork number in /etc/gateway. Placing the keywork active on the line indicates that the route is maintained by the indicated gateway using normal RIP updates. Active routes are subject to normal RIP rules. They may be replaced by routes with lower metric values and they time out and disappear if no RIP updates are received for them. The keyword passive, which is the default if neither active nor passive is specified, indicates a route for which no RIP information will ever be available. Such routes never time out and IP ignores RIP information for them. They can be deleted or modified using TCPCON.