After I was told pppd would be working well for others, I cleaned
and made all userland, reconfigured and made a new kernel; all from
May 30 sources.

With this new setup, pppd still won't work. I enabled the kdebug option
and got this:

Jun  2 09:26:31 euterpe pppd[309]: pppd 2.1.1 started by root, uid 0
Jun  2 09:27:10 euterpe pppd[310]: Connect: ppp0 <--> /dev/tty01
Jun  2 09:27:10 euterpe /netbsd: ppp0 output: ff03c021010100120104100005062deefc6307020802 
Jun  2 09:27:10 euterpe /netbsd: ppp0: got 18 bytes
Jun  2 09:27:10 euterpe /netbsd: ff03c0210101000e02060000000007020802 
Jun  2 09:27:10 euterpe /netbsd: ppp0 output: ff03c0210201000e02060000000007020802 
Jun  2 09:27:13 euterpe /netbsd: ppp0 output: ff03c021010100120104100005062deefc6307020802 
Jun  2 09:27:13 euterpe /netbsd: ppp0: got 8 bytes
Jun  2 09:27:13 euterpe /netbsd: ff03c02101020004 
Jun  2 09:27:13 euterpe /netbsd: ppp0 output: ff03c02102020004 
Jun  2 09:27:13 euterpe /netbsd: ppp0: got 14 bytes
Jun  2 09:27:13 euterpe /netbsd: ff03c0210401000a05062deefc63 
Jun  2 09:27:13 euterpe /netbsd: ppp0 output: ff03c0210102000c0104100007020802 
Jun  2 09:27:13 euterpe /netbsd: ppp0: got 12 bytes
Jun  2 09:27:13 euterpe /netbsd: ff03c02103020008010405dc 
Jun  2 09:27:13 euterpe /netbsd: ppp0 output: ff03c0210103000c010405dc07020802 
Jun  2 09:27:13 euterpe /netbsd: ppp0: got 16 bytes
Jun  2 09:27:13 euterpe /netbsd: ff03c0210203000c010405dc07020802 
Jun  2 09:27:13 euterpe /netbsd: ppp0 output: ff038021010100100306c1ae0b2a0206002d0f01 
Jun  2 09:27:13 euterpe /netbsd: ppp0: got 14 bytes
Jun  2 09:27:13 euterpe /netbsd: ff0380210301000a030681462401|
Jun  2 09:27:13 euterpe /netbsd: ppp0 output: ff038021010200100306814624010206002d0f01 
Jun  2 09:27:13 euterpe /netbsd: ppp0: got 20 bytes
Jun  2 09:27:13 euterpe /netbsd: ff038021020200100306814624010206002d0f01|
Jun  2 09:27:16 euterpe /netbsd: ppp0: got 20 bytes
Jun  2 09:27:16 euterpe /netbsd: ff038021010300100206002d0f01030681460410|
Jun  2 09:27:16 euterpe /netbsd: ppp0 output: ff038021020300100206002d0f01030681460410 
Jun  2 09:27:16 euterpe pppd[310]: local  IP address 129.70.36.1
Jun  2 09:27:16 euterpe pppd[310]: remote IP address 129.70.4.16
Jun  2 09:27:34 euterpe /netbsd: ppp0: got 20 bytes
Jun  2 09:27:34 euterpe /netbsd: ff038021010400100206002d0f01030681460410|
Jun  2 09:27:34 euterpe /netbsd: ppp0 output: ff038021010300100306c1ae0b2a0206002d0f01 
Jun  2 09:27:34 euterpe /netbsd: ppp0 output: ff038021020400100206002d0f01030681460410 
Jun  2 09:27:34 euterpe /netbsd: ppp0: got 20 bytes
Jun  2 09:27:34 euterpe /netbsd: ff038021010500100206002d0f01030681460410|
Jun  2 09:27:34 euterpe /netbsd: ppp0 output: ff038021020500100206002d0f01030681460410 
Jun  2 09:27:34 euterpe /netbsd: ppp0: got 20 bytes
Jun  2 09:27:34 euterpe /netbsd: ff038021010600100206002d0f01030681460410|
Jun  2 09:27:34 euterpe /netbsd: ppp0 output: ff038021020600100206002d0f01030681460410 
Jun  2 09:27:34 euterpe /netbsd: ppp0: got 20 bytes
Jun  2 09:27:34 euterpe /netbsd: ff038021010700100206002d0f01030681460410|
Jun  2 09:27:34 euterpe /netbsd: ppp0 output: ff038021020700100206002d0f01030681460410 
Jun  2 09:27:34 euterpe /netbsd: ppp0: got 20 bytes
Jun  2 09:27:34 euterpe /netbsd: ff038021010800100206002d0f01030681460410|
Jun  2 09:27:35 euterpe /netbsd: ppp0 output: ff038021020800100206002d0f01030681460410 
Jun  2 09:27:35 euterpe /netbsd: ppp0: got 20 bytes
Jun  2 09:27:35 euterpe /netbsd: ff038021010900100206002d0f01030681460410|
Jun  2 09:27:35 euterpe /netbsd: ppp0 output: ff038021020900100206002d0f01030681460410 
Jun  2 09:27:35 euterpe /netbsd: ppp0: got 14 bytes
Jun  2 09:27:35 euterpe /netbsd: ff0380210303000a030681462401|
Jun  2 09:27:35 euterpe /netbsd: ppp0 output: ff038021010400100306814624010206002d0f01 
Jun  2 09:27:35 euterpe /netbsd: ppp0: got 20 bytes
Jun  2 09:27:35 euterpe /netbsd: ff038021020400100306814624010206002d0f01|
Jun  2 09:27:34 euterpe pppd[310]: local  IP address 129.70.36.1
Jun  2 09:27:34 euterpe pppd[310]: remote IP address 129.70.4.16
Jun  2 09:28:54 euterpe /netbsd: ppp0 output: ff0300214500005400f10000ff018ff38146240181460437080008f33c010000368aed2d97500d0008090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f3031323334353637 
Jun  2 09:28:55 euterpe /netbsd: ppp0 output: ff0300214500005400f20000ff018ff28146240181460437080076fc3c010100378aed2d27470d0008090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f3031323334353637 
Jun  2 09:28:56 euterpe /netbsd: ppp0: bad fcs
Jun  2 09:28:56 euterpe /netbsd: ppp0: bad fcs
Jun  2 09:28:56 euterpe /netbsd: ppp0 output: ff0300214500005400f30000ff018ff18146240181460437080089fc3c010200388aed2d12470d0008090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f3031323334353637 
Jun  2 09:28:57 euterpe /netbsd: ppp0: bad fcs

Whatever "bad fcs" means, all incoming packets are counted as errors
by pppstats:

    in   pack   comp uncomp    err |    out   pack   comp uncomp     ip
  2895     23      0      0      7 |   2723     42      0      0     42

The same link, with the same options, worked with sources from May 9, and
still works with (shudder!) MS-Windows-Software, so I'm afraid it
is not the other sides' fault.

Any hints would be greatly apreciated


Martin

P.S.: this is on an i486, if that matters.

------------------------------------------------------------------------------