ppp-handshake klappt nicht

Hi, nachdem meine Teledat 150 nun endlich läuft, stehen die nächsten Probleme an. Hier ein Auszug aus meiner /var/log/messages ----------------------------------------------------------------------------- Aug 25 09:51:19 Kurt kernel: ISDN subsystem Rev: 1.44.2.9/1.41.2.11/1.48.2.27/1.28.2.2/1.8.2.2 loaded Aug 25 09:51:19 Kurt kernel: HiSax: Linux Driver for passive ISDN cards Aug 25 09:51:19 Kurt kernel: HiSax: Version 3.1 (module) Aug 25 09:51:19 Kurt kernel: HiSax: Layer1 Revision 1.15.2.19 Aug 25 09:51:19 Kurt kernel: HiSax: Layer2 Revision 1.10.2.11 Aug 25 09:51:19 Kurt kernel: HiSax: TeiMgr Revision 1.8.2.7 Aug 25 09:51:19 Kurt kernel: HiSax: Layer3 Revision 1.10.2.6 Aug 25 09:51:19 Kurt kernel: HiSax: LinkLayer Revision 1.30.2.13 Aug 25 09:51:19 Kurt kernel: HiSax: Approval certification valid Aug 25 09:51:19 Kurt kernel: HiSax: Approved with ELSA Quickstep series cards Aug 25 09:51:19 Kurt kernel: HiSax: Approval registration numbers: Aug 25 09:51:19 Kurt kernel: HiSax: German D133361J CETECOM ICT Services GmbH Aug 25 09:51:19 Kurt kernel: HiSax: EU (D133362J) CETECOM ICT Services GmbH Aug 25 09:51:19 Kurt kernel: HiSax: Total 1 card defined Aug 25 09:51:19 Kurt kernel: HiSax: Card 1 Protocol EDSS1 Id=HiSax (0) Aug 25 09:51:19 Kurt kernel: HiSax: AVM PCI/ISAPnP driver Rev. 1.1.2.8 Aug 25 09:51:19 Kurt kernel: AVM PnP: Class A Rev 2 Aug 25 09:51:19 Kurt kernel: AVM PCI/PnP: reset Aug 25 09:51:19 Kurt kernel: AVM PCI/PnP: S1 0 Aug 25 09:51:19 Kurt kernel: HiSax: AVM Fritz!PnP config irq:12 base:0x6000 Aug 25 09:51:19 Kurt kernel: AVM PnP: ISAC version (0): 2086/2186 V1.1 Aug 25 09:51:19 Kurt kernel: AVM Fritz PnP/PCI: IRQ 12 count 0 Aug 25 09:51:19 Kurt kernel: AVM Fritz PnP/PCI: IRQ 12 count 3 Aug 25 09:51:19 Kurt kernel: HiSax: DSS1 Rev. 1.16.2.8 Aug 25 09:51:19 Kurt kernel: HiSax: 2 channels added Aug 25 09:51:19 Kurt kernel: HiSax: module installed Aug 25 09:51:19 Kurt kernel: HiSax: debugging flags card 1 set to 4 [...] Aug 25 09:51:52 Kurt kernel: ippp0: dialing 1 xxxxx... Aug 25 09:51:52 Kurt isdnlog: (HiSax driver detected) Aug 25 09:51:52 Kurt isdnlog: Aug 25 09:51:52 * tei 85 calling ? with myself1 CPN +49511350xxxx Aug 25 09:51:52 Kurt isdnlog: Aug 25 09:51:52 * tei 85 calling Provider with myself1 RING (Data) Aug 25 09:51:54 Kurt isdnlog: Aug 25 09:51:54 tei 85 calling Provider with myself1 Time:Wed Aug 25 09:52:00 1999 Aug 25 09:51:54 Kurt isdnlog: Aug 25 09:51:54 tei 85 calling Provider with myself1 CONNECT (Data) Aug 25 09:51:54 Kurt isdnlog: Aug 25 09:51:54 tei 85 calling Provider with myself1 NEXT CHARGEINT IN 0:01:30 (Vormittag, Werktag, CityCall) Aug 25 09:51:54 Kurt kernel: isdn_net: ippp0 connected Aug 25 09:51:54 Kurt kernel: isdn_net: chargetime of ippp0 now 7348 Aug 25 09:51:54 Kurt ipppd[108]: Local number: 350xxxx, Remote number: xxxxx, Type: outgoing Aug 25 09:51:54 Kurt ipppd[108]: PHASE_WAIT -> PHASE_ESTABLISHED, ifunit: 0, linkunit: 0, fd: 7 Aug 25 09:51:54 Kurt ipppd[108]: sent [0][LCP ConfReq id=0x1 ] Aug 25 09:52:21 Kurt last message repeated 9 times Aug 25 09:52:24 Kurt kernel: isdn_net: local hangup ippp0 Aug 25 09:52:24 Kurt kernel: ippp0: Chargesum is 0 Aug 25 09:52:24 Kurt ipppd[108]: LCP: timeout sending Config-Requests Aug 25 09:52:24 Kurt ipppd[108]: Connection terminated. Aug 25 09:52:24 Kurt ipppd[108]: taking down PHASE_DEAD link 0, linkunit: 0 Aug 25 09:52:24 Kurt ipppd[108]: LCP is down Aug 25 09:52:24 Kurt ipppd[108]: closing fd 7 from unit 0 Aug 25 09:52:24 Kurt ipppd[108]: link 0 closed , linkunit: 0 Aug 25 09:52:24 Kurt ipppd[108]: reinit_unit: 0 Aug 25 09:52:24 Kurt ipppd[108]: Connect[0]: /dev/ippp0, fd: 7 Aug 25 09:52:24 Kurt isdnlog: Aug 25 09:52:24 tei 85 calling Provider with myself1 Normal call clearing (User) Aug 25 09:52:25 Kurt isdnlog: Aug 25 09:52:24 tei 85 calling Provider with myself1 HANGUP (1 EH DM 0.12 0:00:30 I= 0.0 b O=180.0 b) [Hier habe ich PID 108 gekillt...] Aug 25 09:52:28 Kurt ipppd[108]: Terminating on signal 15. Aug 25 09:52:28 Kurt ipppd[108]: LCP is down Aug 25 09:52:28 Kurt ipppd[108]: closing fd 7 from unit 0 Aug 25 09:52:28 Kurt ipppd[108]: link 0 closed , linkunit: 0 Aug 25 09:52:28 Kurt ipppd[108]: Exit. ------------------------------------------------------------------------------------- Bei Suse habe ich gelesen, dass die Meldung "LCP: timeout sending Config-Requests" kommt, wenn die Gegenstelle kein synchrones ppp anbietet, was in meinem Fall nicht zutrifft. Welche anderen Ursachen kann das noch haben? Unter Win95 gibt es keine Probleme ( was ein Wunder ;-) ) -- H. Wilms Homepage schering.si.uni-hannover.de/hugo email wilms@stud.fh-hannover.de