PC Online 1996 October

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

/ PC Online 1996 October / PCO_10.ISO / filesbbs / papi020.arj / PAPI0.20 / README.EUN < prev next >

Wrap

Text File | 1993-10-06 | 12.9 KB | 374 lines

When connecting to a POP of the EUNET in Germany their are two choices. First choice use the ka9q stuff: Be sure to fulfill the copyright requirements! Suppose the PAPI packet driver is in directory c:\capi and is called papi.exe Suppose the ka9q net program is in c:\ka9q and is called net.exe The termin program comes with the packet driver set together with wd8003e and other packet drivers for ethernet cards. ----------- Start of EUNET.bat: -------------------- call c:\telescom\starts0.bat c:\capi\papi -v -n <Telno of POP> -o 2 -w 240 c:\bin\wd8003e 0x61 -o 5 0x240 0xdc00 c:\ka9q\net -d c:\ka9q c:\ka9q\autoexec.net c:\ka9q\termin 0x60 c:\ka9q\termin 0x61 c:\telescom\stops0 ------------- end ---------------------------------- Where <Telno of POP> is the number of the POP i n c l u d i n g their "EAZ". Ask them for the full number. Which is usually ending in a 2. Assume your network has the IP-address 199.198.197 Your gateway has the name gate and the IP-address 199.198.197.1 You got the IP-address 139.138.137.2 from EUNET. And the IP-address of the EUNET POP is 139.138.137.1 Your domain name server is 199.198.197.2 If you do not have a domain name server forget the line starting domain ... Then the following is a working example of an autoexec.net for KA9Q. It is not optimized! ----------- Start of autoexec.net ------------------ hostname gate domain suffix your_domain.de ip address [199.198.197.1] attach packet 0x60 slip 8 1500 attach packet 0x61 eth 8 1500 route add default slip 139.138.137.1 route add [199.198.197]/24 eth ip ttl 32 tcp mss 1500 tcp window 15000 ifconfig slip ip 139.138.137.2 ifconfig slip mtu 1500 smtp gateway 199.198.197.2 domain addserver 199.198.197.2 log c:\ka9q\net.log start ftp start echo start discard # THE END If you have a NICCY 3008 the maximal supported buffer size is 1024. Please ask EUNET to set the buffersize to 1020. And use the following templates: ----------- Start of EUNET.bat: -------------------- call c:\telescom\starts0.bat c:\capi\papi -v -n <Telno of POP> -o 2 -w 240 -s 1024 c:\bin\wd8003e 0x61 -o 5 0x240 0xdc00 c:\ka9q\net -d c:\ka9q c:\ka9q\autoexec.net c:\ka9q\termin 0x60 c:\ka9q\termin 0x61 c:\telescom\stops0 ------------- end ---------------------------------- and ----------- Start of autoexec.net ------------------ hostname gate domain suffix your_domain.de ip address [199.198.197.1] attach packet 0x60 slip 8 1020 attach packet 0x61 eth 8 1500 route add default slip 139.138.137.1 route add [199.198.197]/24 eth ip ttl 32 tcp mss 1500 tcp window 15000 ifconfig slip ip 139.138.137.2 ifconfig slip mtu 1020 smtp gateway 199.198.197.2 domain addserver 199.198.197.2 log c:\ka9q\net.log start ftp start echo start discard # THE END ------------- end ---------------------------------- ------------- end of first choice ka9q ------------- Another and in the mean time preferred choice is pcroute. Pay attention pcroute is a - very - black box. You do not get output on display. Finally I prefer programs like that. You have to make a bootable floppy disk. Install the ISDN-CAPI lets suppose in a:/teles copy config.exe and pkts.exe of the pcroute binaries to a: copy your preferred ethernet packet driver to a: PLEASE test before you go on that the packet driver is configured right. It is hard to debug pcroute when you are in reality debugging the ethernet driver or the configuration of the ethernet card. make an autoexec.bat following this scheme: ----------- Start of autoexec.bat ------------------ @echo off COMMAND /C a:\teles\starts0.bat a:\papi -V 0 -v -p 0x61 -n <Telno of POP> -o 2 -w 240 cls a:\wd8003e 0x60 -o 10 0x240 0xc800 cls a:\pcroute ------------- end ---------------------------------- Where <Telno of POP> is the number of the POP i n c l u d i n g their "EAZ". Ask them for the full number. Which is usually ending in a 2. papi is configured to give a status message in the first line of the display. Assume your network has the IP-address 199.198.197 Your gateway has the IP-address 199.198.197.1 You got the IP-address 139.138.137.2 from EUNET. And the IP-address of the EUNET POP is 139.138.137.1 Now you have to go to a: and run config and start a dialog ----------- Start of config ------------------------ a: cd \ config This program creates/edits the pcroute.cfg file Configuring an interface Address for the interface [0.0.0.0] ? 199.198.197.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] ? 5 Routing Metric (HEX) for the interface [1H] ? 1 Configuring an interface Address for the interface [0.0.0.0] ? 139.138.137.2 Subnet mask for the interface [0.0.0.0] ? 255.255.255.252 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] ? b Routing Metric (HEX) for the interface [1H] ? 1 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] ? 139.138.137.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] ? 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 loging info to [0.0.0.0] ? 199.198.197.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 ------------- end ---------------------------------- Test the boot disk by resetting the pc. After some time their will be an empty screen. Reset the machine and look at the contents of pcroute.log It should look like this - only the "Ethenet" Address and the values chosen for your environment will be different. ----------- Start of pcroute.log ------------------- ******* PCroute starting ******* Interface 1 (ethernet) Address 199.198.197.1 NetMask 255.255.255.0 Flags 0005H Metric 0001H The Ethenet Address 0000H The Ethenet Address C0B3H The Ethenet Address 3D24H Interface 2 (packet slip) Address 139.138.137.2 NetMask 255.255.255.252 Flags 000BH Metric 0001H STATIC ROUTES Route to network 0.0.0.0 Through gateway 139.138.137.1 Metric 0002H Flags 0000H Forwarding BOOTP requests to 0.0.0.0 Logging messages to SYSLOGD on host 199.198.197.2 Logging level 0000H Logging mask 0007H ******* PCroute closing log file ******* ------------- end ---------------------------------- Running and Testing. When config completes, insert the floppy into the PC that is was configured for and boot it. Log on to some host on your net and try to PING 199.198.197.1. If this works, try pinging 139.138.137.2 from your host, and next 139.138.137.1 If these work try ftp from your host on your net to some host on the remote net. Finally log on to the logging host and check to see if PCrouter sent the message that it is 'coming up' to the logging host. If all works your are done. If some of these tests fail, refer to the document TROUBLE.DOC and follow the instructions there. TROUBLE.DOC from the pcroute collection: IN CASE OF TROUBLE Here is a list of common problems and their solutions as well as some very useful debugging techniques. Using these techniques should enable you to find most problems. Please let me know if this guide is insufficient. In general there are three sources of good information for debugging PCroute they are. PCROUTE.LOG - This file is created and written to when PCroute first starts up. PCroute writes out all its configuration data to insure that is it what you think it is, and to make sure the hardware is working properly. Logging host - Once PCroute boots up, it sends diagnostic information to the logging host. This is useful for debugging dynamic problems. 3rd Party - Much information can be gained by using PING (either to or though the router) traceroute (if you have it) and examine the routing tables (for RIP problems). ---------------------------------------------------------------------------- PROBLEM: Can't PING PCroute from either local net (PCroute seems dead). The first thing to check is the PCROUTE.LOG file on the floppy. PCROUTE.LOG does not exist Make sure the floppy is not write protected. Make sure the floppy is bootable and that PCroute is run in the autoexec file. If necessary install a monitor and check the boot sequence If PCROUTE.LOG says the configuration file is corrupt, you must rerun config.exe. If that does not work make sure you are using the config.exe that came with the version of PCroute that you are running. If that does not work, delete PCROUTE.CFG and rerun config.exe from scratch. Check the ethernet addresses in the PCROUTE.LOG file. If any are FFFFFFFFF, that means the card does not have the I/O address set properly, and the software cannot find the card. Check that the IP addresses in PCROUTE.LOG are correct. Remember for the precompiled PCroute.exe interface 1 is the card with I/O address 280H, and interface 2 is the card with I/O address 2A0H. Make sure they are not mixed up. Check the ethernet card to make sure it is set for the correct type of ethernet (THIN or THICK) Check the cabling to the ethernet. ---------------------------------------------------------------------------- PROBLEM: The network comes to a halt when PCroute is brought up This symptom indicates a broadcast storm. This is caused not by PCroute but by some other (OLD) IP host. Try turning off directed broadcasts on all interfaces of PCroute (Bit 3 of the interface flags) This usually stops the problem, but the real solution is to update all old networking software. ---------------------------------------------------------------------------- PROBLEM: PCroute can be pinged, but no messages are received by the logging host. Check PCROUTE.LOG to make sure that the logging host IP address is correct. Try Pinging PCroute from the logging host, if you cannot there is a routing problem (see below). If possible, chose a logging host that is on a local network. Maybe you simply filtered out all of the messages, so that PCroute SHOULD send nothing. Good production settings for the filter parameters are (mask 0, priority 7), for debugging you should use (mask 0, priority 8) and if you set it to (mask 0 priority 9) PCroute will send 'I'M ALIVE' messages every minute. Make sure that the /etc/syslog.conf file is set up properly it should be listening for logging messages from facility 'local0' and priority 'debug' (everything). ---------------------------------------------------------------------------- PROBLEM: PCroute can be pinged from a local net, but not a remote net. This is either a a routing problem or a subnetting problem, to test if it is a subnet problem, ping a host OUTSIDE your subnet from a host that must route through PCroute to get there. In the example, pinging any host that does NOT begin with 129.105 from a host on net A will do the job. If this ping succeeds, the subnetting mask is wrong and needs to be changed. If it is a routing problem, try inserting a static route, it that solves the problem, make sure that the other gateways are broadcasting RIP properly.