As the subject states I believe that PPP in 2.1.109 is trashed. I have
spoken to several ppl on irc and have heard a report of one person's kernel
"sending fragmented packets from random ip sources". While I have not had
this problem, my problem with 2.1.109 is worse... I can't even connect.
The same exact script and config files that work perfect (ie: first time,
99% of the time) with 2.1.106 work 0.001% of the time with 2.1.109.
It's _not_ the script!!!! :)
The following is a snippet from my /var/log/messages file:
Jul 17 15:47:26 capsize kernel: CSLIP: code copyright 1989 Regents of the Unive
Jul 17 15:47:26 capsize kernel: PPP: version 2.3.3 (demand dialling)
Jul 17 15:47:26 capsize kernel: PPP line discipline registered.
Jul 17 15:47:26 capsize kernel: registered device ppp0
Jul 17 15:47:26 capsize pppd[370]: pppd 2.3.5 started by root, uid 0
Jul 17 15:47:27 capsize chat[375]: abort on (BUSY)
Jul 17 15:47:27 capsize chat[375]: abort on (ERROR)
Jul 17 15:47:27 capsize chat[375]: abort on (NO CARRIER)
Jul 17 15:47:27 capsize chat[375]: abort on (NO DIALTONE)
Jul 17 15:47:27 capsize chat[375]: abort on (Invalid Login)
Jul 17 15:47:27 capsize chat[375]: abort on (Login incorrect)
Jul 17 15:47:27 capsize chat[375]: send (ATZ^M)
Jul 17 15:47:27 capsize chat[375]: expect (OK)
Jul 17 15:47:28 capsize chat[375]: ATZ^M^M
Jul 17 15:47:28 capsize chat[375]: OK
Jul 17 15:47:28 capsize chat[375]: -- got it
Jul 17 15:47:28 capsize chat[375]: send (ATDT2232000^M)
Jul 17 15:47:28 capsize chat[375]: expect (CONNECT)
Jul 17 15:47:28 capsize chat[375]: ^M
Jul 17 15:47:50 capsize chat[375]: ATDT2232000^M^M
Jul 17 15:47:50 capsize chat[375]: CONNECT
Jul 17 15:47:50 capsize chat[375]: -- got it
Jul 17 15:47:50 capsize chat[375]: send (^M)
Jul 17 15:47:50 capsize pppd[370]: Serial connection established.
Jul 17 15:47:51 capsize pppd[370]: Using interface ppp0
Jul 17 15:47:51 capsize pppd[370]: Connect: ppp0 <--> /dev/ttyS2
Jul 17 15:48:21 capsize pppd[370]: LCP: timeout sending Config-Requests
[... then it hangs up ...]
The following is my modems entry in /etc/isapnp.conf
# Card 2: (serial identifier de 58 bf 1d 64 00 34 49 0a)
# BRI3400 Serial No 1488919908 [checksum de]
# ANSI string -->Boca Research 33,600 ACF Modem <--
# Version 1.0, Vendor version 0.0
#
# Logical device id BRI3400
# Device support I/O range check register
#
(CONFIGURE BRI3400/1488919908 (LD 0
(IO 0 (BASE 0x03e8))
(INT 0 (IRQ 9 (MODE +L)))
(ACT Y)
))
The card initializes fine upon reboot.
Then in my /etc/rc.d/rc.local file I have the following:
setserial /dev/ttyS2 irq 9 port 0x3e8 uart 16550
Again this setup works absolutly fine in 2.1.106 (and the 2.0.x kernel that
comes with redhat 5.0 the last time I tried it)
My system is a P166MMX, 64mb of ram, with RedHat 5.1 installed.
I have tried netcfg, linuxconfig, and a modified version of my ISP's dip
script to no avail. It seems to me that 2.1.109's PPP support is screwed.
(BTW, I havn't tested this on 2.1.107/8 because of the black-on-black
console problem)
Thanks for your time...
----------------------------------------------------------------------
Bruce A. Locke blocke@lizard.org
http://www.lizard.org/blocke/
http://www.lizard.org/dragonlinux
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html