On Fri, Nov 05, 1999 at 10:55:41PM -0800, Space Case wrote:
> OK.  After getting that business with noauth straightened out, and getting
> the chat scripts correct, I now have run into a problem that I am finding
> to be very frustrating.
> 
> I have three different service providers to connect to, and a couple
> different phone lines, and the problem happens with all combinations.
> It also occurs with a 1.4K kernel built last August, and a 1.4M kernel
> build at the end of October.
> 
> What happens is that I'll get the system connected, and start a job, sup
> for example.  It'll run for some period of time, say five minutes or an
> hour, then traffic stops going over the modem.  About a minute later, the
> modem disconnects.
> 
> Below is a sample from the messages file.
> 
> Can anyone enlighten me as to what the problem might be and what I can do
> about it?
> 
> This is the mac68k port, on a Quadra 650, if that matters...
> 
> Thanks,
> ~Steve
> 
> 
> Nov  5 22:27:05 c610 pppd[348]: Connect: ppp0 <--> /dev/tty00
> Nov  5 22:27:07 c610 pppd[348]: local  IP address 216.148.197.36
> Nov  5 22:27:07 c610 pppd[348]: remote IP address 199.108.218.243
> Nov  5 22:27:07 c610 /netbsd: ppp0: no compressor for [1 2 fe], 2
> Nov  5 22:28:13 c610 /netbsd: ppp0: bad fcs ea45
> Nov  5 22:28:13 c610 /netbsd: ppp0: bad fcs f25
> Nov  5 22:28:13 c610 /netbsd: ppp0: missing UI (0x3), got 0x24
> Nov  5 22:28:28 c610 /netbsd: ppp0: bad fcs 3118
> Nov  5 22:28:28 c610 /netbsd: ppp0: bad fcs 142e
> Nov  5 22:28:28 c610 /netbsd: ppp0: missing UI (0x3), got 0x67
> Nov  5 22:28:29 c610 /netbsd: ppp0: bad fcs c944
> Nov  5 22:28:29 c610 /netbsd: ppp0: missing UI (0x3), got 0x67
> Nov  5 22:28:44 c610 /netbsd: ppp0: bad fcs 53e2
> Nov  5 22:28:44 c610 /netbsd: ppp0: bad fcs f031
> Nov  5 22:28:44 c610 /netbsd: ppp0: bad fcs ca1d
> Nov  5 22:28:44 c610 /netbsd: ppp0: bad fcs d651
> Nov  5 22:28:44 c610 /netbsd: ppp0: bad fcs 1178
> Nov  5 22:28:44 c610 /netbsd: ppp0: bad fcs 60e
> Nov  5 22:28:44 c610 /netbsd: ppp0: bad fcs c3e9
> Nov  5 22:28:44 c610 /netbsd: ppp0: missing UI (0x3), got 0x67
> Nov  5 22:28:51 c610 /netbsd: ppp0: bad fcs dbb8
> Nov  5 22:28:51 c610 /netbsd: ppp0: missing UI (0x3), got 0x67
> Nov  5 22:28:59 c610 /netbsd: ppp0: bad fcs c403
> Nov  5 22:28:59 c610 /netbsd: ppp0: missing UI (0x3), got 0x67
> Nov  5 22:29:13 c610 /netbsd: zstty0: 22 silo overflows, 3 ibuf floods
> Nov  5 22:29:26 c610 /netbsd: ppp0: bad fcs 7657
> Nov  5 22:29:26 c610 /netbsd: ppp0: missing UI (0x3), got 0x67
> Nov  5 22:29:28 c610 /netbsd: ppp0: bad fcs 96a6
> Nov  5 22:29:28 c610 /netbsd: ppp0: missing UI (0x3), got 0x67
> Nov  5 22:29:32 c610 /netbsd: ppp0: bad fcs 3212
> Nov  5 22:29:32 c610 /netbsd: ppp0: bad fcs 29a3
> Nov  5 22:29:32 c610 /netbsd: ppp0: bad fcs 6822
> Nov  5 22:29:32 c610 /netbsd: ppp0: bad fcs 17c2

to me, this sounds like a handshaking problem.

You probably know that, but you have to

- check that your pppd uses crtscts, (or maybe it is cdtrcts for your sort
  of Mac?)

- check that your modem is set up to use crtscts

- check that you have 8 wires running in between the two: lines 2,3,4,5,6,7,20
  on a 25pin connector.

As a sanity check, put a cheapo rs232 analyzer in between and check  that the
rts and cts lines actually *switch* sometimes.

Regards,
	-is