herbw@wiskit.rain.com (Herb Weiner) (04/15/91)
I did some experiments with SLIP a while back, and it worked just fine (if you ignore speed). That was before I installed A/UX 2.0.1. Well, I tried it again this weekend (with A/UX 2.0.1 installed), and could not get it to work. I'm not yet ready to rule out other problems (like the system at the other end of the line, or modems, or ...), but I'd like to know what, if any, changes (intentional or otherwise) were made in A/UX 2.0.1 that might affect SLIP behavior. If it makes a difference, we're using a netmask of 255.255.255.248 on the ifconfig for the SLIP link. Among other problems (like ping failing), I noticed that my machine is not sending RIP packets. Also, I noticed that routed appeared to add a route from my SLIP link through 127.0.0.1 (loopback interface). The only information that seems at all relevant is this quote from alexis@panix.uucp (Alexis Rosen) in <1991Mar28.074451.4116@panix.uucp>: > 6) inetd > There is something _really_ _wrong_ with this thing. I don't know what, but > I know that if you jam up the mail subsystem, various sendmail processes will > stick around _forever_ (kill -9 won't kill them), untill you kill inetd. Then > they unjam, deliver their mail (which may mean bouncing them- I'm not talking > about the rmail bug directly, here), and terminate normally. In a similar > manner, in.talkd can become unusable. Killing it won't help, until you kill > inetd as well. Then, killing in.talkd will resolve the problem. > I've read about various problems with SLIP in this group. Could there > possibly be some connection there with the inetd problem? Any assistance would be greatly appreciated. Herb Weiner