pemurray@miavx1.acs.muohio.edu (Peter Murray) (07/18/90)
I have what appears to be a network routing problem. If not, please point me in the right direction. We just hooked up a SLIP connection between an IBM PC running KA9Q (the release is a couple of months old, I'm not sure of the version number) and a MicroVAX II running Ultrix 3.1. Believe it or not, the connection from the PC to the MicroVAX works! (It took many long weeks to get there.) :-) This is the problem: packets sent from the PC to anywhere but the MicroVAX do not appear to be forwarded to the ethernet network. Packets from the network do not appear to be forwarded to the PC. It seems like the connection is only valid for the PC and the MicroVAX. The setup: we have a Class B network with a broadcast of 134.53.3.255 and a subnet mask of 255.255.255.0. The Ultrix box is the domain name server for the subnet, but the PC's address is not in the tables. I've been using it's IP address to test the connections. We are running 'routed' (this was suggested by someone here as a possible problem). Solutions already tried: A friend of mine suggested that there was a problem with the SLIP protocol that was fixed if the SLIP machine was on a subnet by itself. I changed the IP address of the SLIP connection so that it was in a different (unused) subnet, but this did not help. I also looked for RFCs, but the only one I found dealing with SLIP (RFC 1055; "A Nonstandard for Transmission of IP Datagrams over Serial Lines: SLIP") was of no help. DEC does not support SLIP, so the Ultrix manuals haven't been very good. I would very much like to hear how this has been solved at other sites. SLIP seems to be a popular problem, and I will post a step-by-step method of how I did it when (IF?) I can solve this one last problem. Thanks in advance for your help... Peter -- Peter Murray Neat UNIX Stunts #4: pemurray@miavx1.bitnet 215 Foxfire Dr #308 csh> \(- murrayp@apsvax.aps.muohio.edu Oxford, OH 45056 NeXT Mail: pmurray@next4.acs.muohio.edu 513/523-5994