Technical Library
|
|
Technical Library |
|
|
|
|
24 Oct 2000 
Certified Hardware and Software
|
 |
Morning Star ExpressRouting with the Morning Star Express for LAN-Dial Setup Instructions
You will need the following hardware to setup your equipment: Using two serial cables is preferred, one to be used as a console to configure the router, and one to connect to the modem. A null modem cable, or null modem adapter is required for the console line (tx and rx are flipped, usually pins 3 and 4). We do not supply these cables. On a PC, some terminal emulation program will be used to configure the router, or an ascii terminal can be used. Connect the console cable to the dumb terminal or PC, communications parameters should be 9600 baud, 8 data bits, no parity and 1 stop bit. With a valid configuration and all cables connected properly you will receive "login:" as a prompt. You can login as "root", just hit return for a password and you will be logged in at the "#" prompt. From here unix commands can be used such as 'ls' to see what files exist. You are now ready to configure the router by editing the files described below, to get familiar with the built-in editor, refer to pages 58 and 59 of the MSE User Guide before you begin. The Morning Star Express (MSE) router operating system is modeled after the UNIX operating system. The console interface is actually a stripped down version of "sh". You can do shell-like things including history, I/O redirection, and create simple shell scripts. When the Morning Star Express router is booted, it checks for the existence of an "rc.boot" file. If found, it executes instructions in this file. There is always an "rc.default" file which contains enough instructions to get the machine up and console ready. This file is hard wired into memory and cannot be changed. It is executed if "rc.boot" is corrupted or not present. The MSE router is not shipped with an "rc.boot" file. Here is a listing of important files on the MSE router:
All of these files reside in FLASH memory on the MSE router. They must be saved after modification or creation or the changes will not be permanent through reboots. There is a rudimentary ed-like editor which you can use to modify or create files in FLASH. You can also download files to FLASH using TFTP or FTP. To get a listing of commands on the MSE router, type "?". For a listing of processes running, type "ps ax". For a listing of files in FLASH, type "ls". Examplerc.boot hostname <NAME-OF-ROUTER> console tty2 version ifconfig lo0 127.1 getty tty2 9600 nowait respawn ifconfig enet0 <CUSTOMER-LAN-IP-ADDR> netmask <CUSTOMER-NETMASK> pppd xxx.xxx.xxx.xxx:yyy.yyy.yyy.yyy auto idle 900 route add default YYY inetd
XXX = serial ip of the router Example systems yyy.yyy.yyy.yyy Any ACU 38400 1234567 in--in: LD0333 word: pppppppp
yyy = POP router ip Example devices HAYES-9600 tty1 38400 crtscts Example Auth LDXXXXX mypassword Replace LDXXXXX with your account ID and mypassword with the password that goes with your account ID. Example gated.conf This is a very simple config file which simply turns on RIP and broadcasts RIP out every interface: rip yes ; gated will announce directly connected networks and other networks it has learned of via RIP. Example resolv.conf
domain <PROPER-DOMAIN> Note: This file uses the exact same syntax as the UNIX BIND resolv.conf file. Example inetd.conf # cat inetd.conf # @(#)inetd.conf 1.23 90/01/03 SMI # # Configuration file for inetd(8). See inetd.conf(5). # # To re-configure the running inetd process, edit this file, then # send the inetd process a SIGHUP. # # Ftp and telnet are standard Internet services. # ftp stream tcp nowait root ftpd telnet stream tcp nowait root telnetd # #netstat stream tcp nowait root netstat -in #ps stream tcp nowait root ps #debug stream tcp nowait root internal-debug # # Time service is used for clock syncronization. # time stream tcp nowait root internal time dgram udp wait root internal # # Echo, discard, daytime, and chargen are used primarily for testing. # echo stream tcp nowait root internal echo dgram udp wait root internal discard stream tcp nowait root internal discard dgram udp wait root internal daytime stream tcp nowait root internal daytime dgram udp wait root internal chargen stream tcp nowait root internal chargen dgram udp wait root internal Saving Files to Flash When a file is modified, it will be marked as "unsaved": # ls total 14 saved 69 May 5 12:24 acl.parties saved 42 Dec 31 1969 file.crypt saved 940 Dec 31 1969 inetd.conf saved 0 May 5 12:24 manager.families saved 32 Sep 2 14:14 passwd saved 492 Dec 31 1969 protocols unsaved 283 Sep 2 14:58 rc.boot saved 38 Dec 31 1969 resolv.conf saved 1912 Dec 31 1969 services saved 221 Dec 31 1969 smp.parties saved 1705 Dec 31 1969 snmpd.config saved 746 Dec 31 1969 tz saved 67 Dec 31 1969 view.parties To save a file, type "save <filename>". It will be marked as "saved". # save rc.boot # # ls total 14 saved 69 May 5 12:24 acl.parties saved 42 Dec 31 1969 file.crypt saved 940 Dec 31 1969 inetd.conf saved 0 May 5 12:24 manager.families saved 32 Sep 2 14:14 passwd saved 492 Dec 31 1969 protocols saved 283 Sep 2 14:58 rc.boot saved 38 Dec 31 1969 resolv.conf saved 1912 Dec 31 1969 services saved 221 Dec 31 1969 smp.parties saved 1705 Dec 31 1969 snmpd.config saved 746 Dec 31 1969 tz saved 67 Dec 31 1969 view.parties Editing a File The editor is a line editor and not a full-screen editor. You can get help by typing "?". Here is an example session using the line editor: # edit rc.boot rc.boot: read 11 lines, 283 characters hostname test1 edit> ? Commands are:
Leave append mode with ^D or a dot (`.') on a line by itself. Leave edit mode with a return. A line number can be a number, a dot (current line), a minus sign (`-', previous line), a plus sign (`+', next line), or a dollar sign (`$', last line). A range is either a line number or two line numbers separated by a `-'. edit> w rc.boot: wrote 11 lines, 283 characters edit> q # After writing and quitting out of the editor, you must SAVE the file to FLASH using the "save" command. Using TFTP to Modify or Create Files Given the state of the line editor on the MSE router, it is often easier to create or modify your MSE router files on a UNIX machine with your editor of choice and use TFTP to transfer the files to the MSE router: # # tftp 192.33.4.253 tftp> get rc.boot rc.boot Received 285 bytes in 0.6 seconds tftp> tftp> get inetd.conf inetd.conf Received 1150 bytes in 0.7 seconds tftp> tftp> get resolv.conf resolv.conf Received 40 bytes in 0.1 seconds tftp> tftp> get gated.conf gated.conf Received 10 bytes in 0.2 seconds tftp> tftp> quit # # save rc.boot # save inetd.conf # save resolv.conf # save gated.conf # Once this is done, you can reboot the router with the new configuration. Example "netstat" Output from a Working LAN-Dial Connection # netstat -r -n Routing tables Destination Gateway Flags Refs Use Interface Route Tree for Protocol Family 2: (root node) => default 38.2.211.1 UG 2 102736 tty0 38.2.211 38.2.211.254 U 1 11 tty0 127 127.0.0.1 UR 0 0 lo0 127.0.0.1 127.0.0.1 UH 0 0 lo0 192.77.191 192.77.191.1 U 0 0 enet0 224.0.0.9 127.0.0.1 UH 0 0 lo0 (root node)      |
