Black Box LRA001A-R2 152, CONFIG.NET Example, CONFIG.NET file supporting TCP/IP and IPX routing

ASYNC ROUTER AR-P, AR-5, AND SYNC ROUTER REFERENCE MANUAL

•dialup modemX dial_log—Use to view the types of packets that caused the last 5 dials.

•history—Use history to check and verify all commands entered since you logged on.

•ifconfig iface—Use ifconfig to view the status of the interfaces.

•performance—Displays performance statistics, dynamically updated every ten seconds.

•ping IP_address—For TCP/IP sites only. When trying to determine if an IP routing problem exists, use ping first. Use ping to verify that you can connect out (of your network). For example, try “ping rns.com.” Ping sends an ICMP echo-request packet to a remote host. A successful ping means that the packet was able to get to the remote host, and the remote host knew how to send the packet back to the Router.

•ppp iface—Use ppp to display and configure Point-To-Point Protocol (PPP) statistics. The Router uses PPP to establish communication with remote devices. When used without optional parameters, ppp iface displays information about the current state of authentication, and the status of the PPP connection. Also use ppp to provide local and remote IP addresses, and to show if the line is connected or not.

•tip iface—For TCP/IP sites only. Use tip to enter modem commands directly, i.e., to send modem commands directly to the modem interfaces. Use tip when trying to determine if a particular modem is functioning properly and responding to Router commands. Tip is similar to a “Terminal Mode” session on a communications program, and can only can be used on an inactive modem interface. To make an interface inactive, type “dialup modemX inactive,” where modemX is the interface desired. After your tip session, bring the modem interface back up by issuing either a “dialup modemX demand” or “dialup modemX demand_backoff” if the line is configured for LAN-to-LAN, or “dialup modemX client” if the line is configured for User-to-LAN.

•trace iface—Use trace to view packet traffic across the Router, as it happens. Trace also displays the headers of all packets seen on that interface, which is useful when determining which types of packets are moving across a specific interface. Packets are shown with their origin and destination addresses.

•traceroute IP_address—For TCP/IP sites only. Use traceroute to show you the route taken to reach an IP address. Try “traceroute rns.com.” Traceroute displays each individual device that the Router is sending packets through, to get to the remote ip_address. Use traceroute to determine if packets are being routed correctly by the Router and the other routers on your network.

•update [iface] now—Use update to dial the modem or ISDN line and connect to the remote system on a particular dialup interface. Use update to test the Router’s dialer script. Using update now with no interface specified will dial all modem and ISDN lines.

1.7.3 CONFIG.NET EXAMPLE

At boot time, the Router executes the CONFIG.NET file on the Router boot diskette (much like a DOS batch file). Each line in the CONFIG.NET file is a command that you can execute manually from the system console (or telnet session, or terminal emulator).

The following CONFIG.NET file represents a simple Router configuration. If you decide to use parts of it, make sure you use your own IP addresses and IPX network numbers.

CONFIG.NET file (supporting TCP/IP and IPX routing)

hostname Router ip address 0.0.0.0 ifconfig console mtu 1500

ifconfig eth0 netmask 255.255.255.0 broadcast 0.0.0.255 mtu 1500

152