ProfitPress Mega CDROM2 Shareware Freeware (MSDOS)(1992)(Eng)

home *** CD-ROM | disk | FTP | other *** search

/ ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng) / ProfitPress-MegaCDROM2.B6I / MISC / NETWORK / PCRTE222.ZIP / SLIP.EXA < prev next >

Wrap

Text File | 1991-12-11 | 12.8 KB | 275 lines

EXAMPLE INSTALLATION OF PCROUTE SLIP - ETHERNET Here we will do an example installation of PCroute. The network configuration we will assume that we have is 129.105.49.X 129.105.5.X 255.255.255.0 255.255.255.0 /---------------------/ /--------------------------/ Thin A | 1 19.2K Line | 3 Thick B | 5 +---+---+ 129.105.2.X +-------+ | +-------+ | PC #1 +-------------+ PC #2 | +---+ GW | +-------+ 1 2 +-------+ +-------+ LOG HOST 129.105.35.2 That is we are trying to connect two ethernets together via a 19.2 KBaud async communication line. We are using a class B number (129.105) but we are subneting it so that the first three tuples are the network part. Network A was assigned the network number 129.105.49.X network B was assigned the network number 129.105.5.X and we assigned the SLIP line the network number 129.105.2.X. The first router is given the address 129.105.49.1 on network A and 129.105.2.1 on the SLIP line. The second router is given the address 129.105.5.3 on network B and 129.105.2.2 on the SLIP line. Network A is thin ethernet (uses the BNC connector) and network B is thick (uses the DSub 15 connector) There is a gateway on network B that will be the default. Finally their is a UNIX host running syslogd whose IP address is 129.105.35.2 that will act as a logging host. I wish to stress at this time that the serial line has its OWN network number. This is the way it should be. PLEASE don't try to 'borrow' part of the address space of one of the ethernets. I know that some SLIP software does this, but it causes nothing but grief. PLEASE do not try it. Step 1 Compiling software: Since the distribution comes with a executable that is configured for a slip-ethernet router (Ether I/O address 280H, Slip COM1), it is not necessary to recompile the source code. Simply rename slip.exe to pcroute.exe, for both routers. Step 2 Configuring hardware For both PCs the factory setting for the WD8003E of I/O address 280H, and IRQ 3 (the IRQ setting is irrelevant) is fine, however, since network B is a thick ethernet we must change the jumpers for the WD8003E card for PC #2 so that thick ethernet is selected. Then install the cards in the PCs. Next we install async serial cards for both PCs that are configured for COM1 (I/O address=3F8H, IRQ=4). Step 3 Software configuration Copy pcroute.exe, and config.exe to a two BOOTABLE floppies. Create and autoexec.bat file that has the single line 'PCROUTE' in it and place the file on both floppies. Insert the floppy for PC #1, set your default drive to the floppy and type 'CONFIG'. The dialog to the config program for PC #1 looks like ------------------------------------------------------------------------ This program creates/edits the pcroute.cfg file Configuring an interface Address for the interface [0.0.0.0] ? 129.105.49.1 Subnet mask for the interface [0.0.0.0] ? 255.255.255.0 Flag Meanings (if set) Bit 0 (1h) - Don't send routing updates out this interface Bit 1 (2h) - Don't listen to routing updates from this interface Bit 2 (4h) - Proxy Arp for all subnets Bit 3 (8h) - Turn off directed broadcasts Bit 4 (10h) - Turn off the issuing of ICMP redirects Bit 5 (20h) - Broadcast using old (0's) format Flags (HEX) for the interface [0H] ? 8 Routing Metric (HEX) for the interface [1H] ? 1 Configuring an interface Address for the interface [0.0.0.0] ? 129.105.2.1 Subnet mask for the interface [0.0.0.0] ? 255.255.255.0 Flag Meanings (if set) Bit 0 (1h) - Don't send routing updates out this interface Bit 1 (2h) - Don't listen to routing updates from this interface Bit 2 (4h) - Proxy Arp for all subnets Bit 3 (8h) - Turn off directed broadcasts Bit 4 (10h) - Turn off the issuing of ICMP redirects Flags (HEX) for the interface [0H] ? B Routing Metric (HEX) for the interface [1H] ? 1 Enter speed for this interface (ex. 96000 192000, ...) [9600] 19200 If you wish to configure static routes do so here. To stop type a '.' Flag Meanings (if set) Bit 0 (1h) - Local route, do not propagate it Bit 1 (2h) - Transient route, subject to RIP protocol Network [0.0.0.0] ? 0.0.0.0 Gateway [0.0.0.0] ? 129.105.2.2 Metric (HEX) [9H] ? 2 Flags (HEX) [0H] ? 0 Network [0.0.0.0] ? . If you wish to forward bootp packets please enter the address of the address to forward it to. This address can be a directed broadcast. 0.0.0.0 means don't forward Address to forward bootp packets [0.0.0.0] ? 0.0.0.0 Once PCroute boots up, it sends all log messages to a network host running a BSD UNIX syslogd daemon. To disable logging enter 0.0.0.0 Host to send logging info to [0.0.0.0] ? 129.105.35.2 Mask Meanings (0 = Log, 1 = Don't log) Bit 0 (1h) - System Bit 1 (2h) - Routing Bit 2 (4h) - Monitor Bit 3 (8h) - Localtalk Logging mask for this router [0H] ? 0 There are 8 routing 'levels' supported 0 - Emergency 1 - Alert 2 - Critical 3 - Error 4 - Warning 5 - Notice 6 - info 7 - Debug Only messages with a level less than the logging level are sent Logging level [0H] ? 7 ------------------------------------------------------------------------ ------------------------------------------------------------------------ The dialog for the configuration of PC #2 looks like. ------------------------------------------------------------------------ This program creates/edits the pcroute.cfg file Configuring an interface Address for the interface [0.0.0.0] ? 129.105.5.3 Subnet mask for the interface [0.0.0.0] ? 255.255.255.0 Flag Meanings (if set) Bit 0 (1h) - Don't send routing updates out this interface Bit 1 (2h) - Don't listen to routing updates from this interface Bit 2 (4h) - Proxy Arp for all subnets Bit 3 (8h) - Turn off directed broadcasts Bit 4 (10h) - Turn off the issuing of ICMP redirects Bit 5 (20h) - Broadcast using old (0's) format Flags (HEX) for the interface [0H] ? 8 Routing Metric (HEX) for the interface [1H] ? 1 Configuring an interface Address for the interface [0.0.0.0] ? 129.105.2.2 Subnet mask for the interface [0.0.0.0] ? 255.255.255.0 Flag Meanings (if set) Bit 0 (1h) - Don't send routing updates out this interface Bit 1 (2h) - Don't listen to routing updates from this interface Bit 2 (4h) - Proxy Arp for all subnets Bit 3 (8h) - Turn off directed broadcasts Bit 4 (10h) - Turn off the issuing of ICMP redirects Flags (HEX) for the interface [0H] ? B Routing Metric (HEX) for the interface [1H] ? 1 Enter speed for this interface (ex. 96000 192000, ...) [9600] 19200 If you wish to configure static routes do so here. To stop type a '.' Flag Meanings (if set) Bit 0 (1h) - Local route, do not propagate it Bit 1 (2h) - Transient route, subject to RIP protocol Network [0.0.0.0] ? 0.0.0.0 Gateway [0.0.0.0] ? 129.105.5.5 Metric (HEX) [9H] ? 9 Flags (HEX) [0H] ? 2 Network [0.0.0.0] ? 129.105.49.0 Gateway [0.0.0.0] ? 129.105.2.1 Metric (HEX) [9H] ? 2 Flags (HEX) [0H] ? 0 Network [0.0.0.0] ? . If you wish to forward bootp packets please enter the address of the address to forward it to. This address can be a directed broadcast. 0.0.0.0 means don't forward Address to forward bootp packets [0.0.0.0] ? 0.0.0.0 Once PCroute boots up, it sends all log messages to a network host running a BSD UNIX syslogd daemon. To disable logging enter 0.0.0.0 Host to send logging info to [0.0.0.0] ? 129.105.35.2 Mask Meanings (0 = Log, 1 = Don't log) Bit 0 (1h) - System Bit 1 (2h) - Routing Bit 2 (4h) - Monitor Bit 3 (8h) - Localtalk Logging mask for this router [0H] ? 0 There are 8 routing 'levels' supported 0 - Emergency 1 - Alert 2 - Critical 3 - Error 4 - Warning 5 - Notice 6 - info 7 - Debug Only messages with a level less than the logging level are sent Logging level [0H] ? 7 ------------------------------------------------------------------------ The configuration procedure first describes each interface in the router, giving its IP address and network mask. The flags should normally be 0, but if you have any old (pre 1988) software), you should probably set flag bit 3 and bit 4 (in this example we set bit 3). Next we set the routes. In this example we rely on RIP to provide routing information to hosts, however, we choose not to use rip for the serial line (because of the overhead). Thus we use static routing there. Note that this is only reasonable if there are only a small (and not growing) number of nets on the 'Network A' side of the slip line. If this is not the case, RIP should be used, regardless of the overhead. (which really isn't that much anyway) Thus in our configuration PC#1 is given a default route that it will propagate to network A via RIP, but not to the slip line. PC#2 is also given a default route, but unlike PC#1's default route, this route has bit 1 set which makes it expire in 90 seconds. This route is useful so that the PC#2 can reach the logging host even before it has received RIP information from any host (presumably host 129.105.5.5). PC#2 is also given a static route that routes packets destined for network A to PC#1. This route is propagated on network B via RIP (but again not the SLIP line). Note that if more networks are added on the 'network A' side of the SLIP line, more routes will have to be added the PC#2. It is VERY easy to forget such routes, and network problems will result. Thus if that side of the network is likely to grow, it is STRONGLY suggested to run RIP on the SLIP line and let it take care of it. Since we do not need BOOTP forwarding, we disable it by entering the address 0.0.0.0. Finally we set the logging information. We set the logging host to 129.105.35.2 and we set the logging filters to send everything that is not a debugging message. This is a good setting for a production machine. Since in this example we are assuming that RIP is being used, we should make sure that 129.105.5.5 is generating RIP packets. Finally we should log on to the logging host and (assuming it is a BSD 4.3 system), and edit the /etc/syslog.conf file so it included the following line local0.debug /usr/adm/pcroute Note that in this example we log all messages to the file /usr/adm/pcroute. If you want them to go elsewhere consult the UNIX manual and change /etc/syslog.conf accordingly. Don't forget to kill -HUP the syslogd process, to tell it that the configuration file has changed. Step 4 Running and Testing. When config completes, insert the floppies into the PC that the where configured for and boot both machines. Log on to some host on net A and try to PING 129.105.49.1. Also log on to net B and try pinging 129.105.5.3. If these work, try pinging 129.105.49.1 from net B and 129.105.5.3 from net A. If these work try telneting from the host on net A to the host on net B. Try telneting from net A to arbitrary hosts. Finally log on to the logging host and check to see if both PCrouters sent the message that it is 'coming up' to the logging host. If all these tests succeed, congratulations! you have installed your first PCrouters. If some of these tests fail, refer to the document TROUBLE.DOC and follow the instructions there.