November 1999 - openSUSE ISDN (Deutsch)

Permanente Einwahl
by Markus Wenke 12 Nov '99

12 Nov '99

Hallo, ich habe unter Linux ISDN mit automatischer Einwahl installiet, und ca. alle 2-5 min. wählt sich Linux automatisch ein, ich habe davon schon gehört, aber ich habe den Grund dafür natürlich wieder vergessen. Weiß einer warum Linux das macht, und wie man das abstellen kann? Noch was, wer kann mir eine billige, von Linux unterstützte 100Mbit eth-Karte empfehlen?? MfG Markus Wenke

4 3

Oops: Kernel-Nullpointer in isdn_net_unreachable()
by Blauth Joachim 11 Nov '99

11 Nov '99

Hallo Karsten, IMHO war es Dein Vorschlag, Oops-Meldungen in die Developer-Liste zu forwarden. Da mir die Adresse dazu fehlt, und Du eh schon fast der richtige Ansprechpartner bist :-), eine BCC an Dich mit der Bitte um die entsprechende Weiterleitung ... Danke. Hallo Liste, Problem: -------- MPPP: Beim Hinzunehmen des Slave-Channels gibt es eine Nullpointer- Dereferenzierung in __skb_dequeue() durch den Aufruf in isdn_net_unreachable(). Erwuenschte Loesungen: ---------------------- a) Fix des Bugs - wozu ich nicht in der Lage bin, da ich mit dem ISDN-Code nur sehr oberflaechlich vertraut bin. b) Empfehlung einer anderen i4k - Variante fuer Kernel 2.0.38, die moeglichst nahe am aktuellen i4k-Entwicklungs- stand ist und dieses Problem nicht aufweist. Folgende Konfiguration: ----------------------- 1) Kernel 2.0.38 2) isdn4k-utils v3.1beta1 3) isdn4linux (i4k) von ftp.suse.com/pub/isdn4linux/v2.0/isdn: lermen users 489404 Oct 18 02:06 isdn-9910180206.tar.gz 4) okapi 0.04-patch fuer i4k von Michael Hipp 5) drivers/isdn/hisax/hisax.h, line 238: #define MAX_HEADER_LEN 9 /* originally 4 */ Letzteres hilft gegen "isdn_ppp_skb_push: under 4 5" und "isdn_ppp_skb_push: under 0 2". Der hier mehrfach gepostete Patch ( z.B. http://www.deja.com/getdoc.xp?AN=511984655&fmt=text ) hilft beim Kernel 2.0.38 nicht, da er noch kein skb_realloc_headroom() kennt. Ohne die Erweiterung der MAX_HEADER_LEN verliert ipppd Pakete. Die Veraenderung ist NICHT ursaechlich fuer den Oops - er tritt auch mit der originalen Laenge von 4 auf. ISDN-Interface: MPPP mit ibod Current setup of interface 'ippp0': Encapsulation: syncppp Slave Interface: ippp1 Master Interface: None Pre-Bound to: Nothing PPP-Bound to: 0 Current setup of interface 'ippp1': Encapsulation: syncppp Slave Interface: None Master Interface: ippp0 Pre-Bound to: Nothing PPP-Bound to: 1 Logfiles und Sourcecode: ------------------------ /var/adm/debug: Nov 11 20:01:40 Challenge kernel: DCONN: 0 Nov 11 20:01:40 Challenge kernel: BCONN: 0 Nov 11 20:01:40 Challenge kernel: isdn_net: ippp0 connected || ....... Nov 11 20:01:41 Challenge ibod[155]: added new link Nov 11 20:01:41 Challenge ipppd[154]: Remote message: Login Succeeded Nov 11 20:01:41 Challenge ipppd[154]: MPPP negotiation, He: Yes We: Yes Nov 11 20:01:41 Challenge ipppd[154]: local IP address 194.64.xxx.xxx Nov 11 20:01:41 Challenge ipppd[154]: remote IP address 194.64.xxx.xxx || ....... Nov 11 20:02:08 Challenge kernel: ippp1: dialstate=1 (isdn_net.c 760) Nov 11 20:02:08 Challenge kernel: ippp1: dialing 0 ............. Nov 11 20:02:08 Challenge kernel: dial: d=0 c=1 Nov 11 20:02:08 Challenge kernel: ippp1: dialstate=4 (isdn_net.c 760) Nov 11 20:02:08 Challenge ibod[155]: added new link Nov 11 20:02:08 Challenge kernel: ippp1: dialstate=4 (isdn_net.c 760) Nov 11 20:02:15 Challenge last message repeated 50 times Nov 11 20:02:15 Challenge kernel: ippp1: dialstate=3 (isdn_net.c 760) Nov 11 20:02:15 Challenge kernel: Nov 11 20:02:15 Challenge kernel: ===> dial timed out <=== Nov 11 20:02:15 Challenge kernel: Nov 11 20:02:15 Challenge kernel: Nov 11 20:02:15 Challenge kernel: isdn_net: ippp1: dial: timed out ----- Nov 11 20:02:15 Challenge kernel: isdn_net_unreachable(): isdn_net.c: 334, dev=00886590, skb=00000000 Nov 11 20:02:15 Challenge kernel: isdn_net_unreachable(): before check for &dev->buffs[i] Nov 11 20:02:15 Challenge kernel: isdn_net_unreachable(): before skb_dequeue(), i=0 Nov 11 20:02:15 Challenge kernel: inline __skb_dequeue(): next == NULL, (/usr/src/linux-2.0.38_VC/include/linux/skbuff.h 302) Nov 11 20:02:15 Challenge kernel: Unable to handle kernel NULL pointer dereference at virtual address c0000000 Nov 11 20:02:15 Challenge kernel: current->tss.cr3 = 00101000, ^Lr3 = 00101000 Nov 11 20:02:15 Challenge kernel: *pde = 00102067 Nov 11 20:02:15 Challenge kernel: *pte = 00000000 Nov 11 20:02:15 Challenge kernel: Oops: 0000 Nov 11 20:02:15 Challenge kernel: CPU: 0 Nov 11 20:02:15 Challenge kernel: EIP: 0010:[<01038c01>] Nov 11 20:02:15 Challenge kernel: EFLAGS: 00010097 Nov 11 20:02:15 Challenge kernel: eax: 0000005f ebx: 0088661c ecx: 00196790 edx: 00b98810 Nov 11 20:02:15 Challenge kernel: esi: 00000000 edi: 00000000 ebp: 00000000 esp: 00194824 Nov 11 20:02:15 Challenge kernel: ds: 0018 es: 0018 fs: 002b gs: 0018 ss: 0018 Nov 11 20:02:15 Challenge kernel: Process swapper (pid: 0, process nr: 0, stackpage=001929e4) Nov 11 20:02:15 Challenge kernel: Stack: 00886590 0009eb1d 010497be 00886414 00000212 01039802 00886590 00000000 Nov 11 20:02:15 Challenge kernel: 01049801 010497e1 00000030 01034380 00000015 001948ec 00194864 00000000 Nov 11 20:02:15 Challenge kernel: 00000000 0000000c 00000001 001948e8 01024557 00000206 00000000 00000246 Nov 11 20:02:15 Challenge kernel: Call Trace: [<010497be>] [<01039802>] [<01049801>] [<010497e1>] [<01034380>] [<01024557>] [ip_rcv+1031/1336] Nov 11 20:02:16 Challenge kerneld: error: exit: Identifier removed Nov 11 20:02:15 Challenge kernel: [<010343d4>] [timer_bh+765/844] [do_bottom_half+59/96] [handle_bottom_half+11/32] [schedule+115/652] [schedule+651/652] [sys_idle+108/112] [system_call+85/128] Nov 11 20:02:15 Challenge kernel: [init+0/624] [scan_bus+752/896] [start_kernel+458/468] Nov 11 20:02:15 Challenge kernel: Code: 8b 37 85 f6 75 17 68 37 01 00 00 68 f2 92 04 01 68 54 93 04 Nov 11 20:02:15 Challenge kernel: Aiee, killing interrupt handler Nov 11 20:02:16 Challenge kernel: DHUP: 1 Nov 11 20:02:16 Challenge kernel: ippp1: remote abort (3) Nov 11 20:02:16 Challenge kernel: idx=1 drv=0 ch=1 Nov 11 20:02:16 Challenge kernel: kfree of non-kmalloced memory: 00194a2c, next= 00000000, order=0 Nov 11 20:02:16 Challenge kernel: kfree of non-kmalloced memory: 00194a1c, next= 00000000, order=0 Nov 11 20:02:16 Challenge kernel: kfree of non-kmalloced memory: 00194f30, next= 00000000, order=0 Nov 11 20:02:16 Challenge kernel: idle task may not sleep Nov 11 20:02:16 Challenge last message repeated 4 times /usr/src/linux/drivers/isdn/isdn_net.c: 305 static void 306 isdn_net_unreachable(struct device *dev, struct sk_buff *skb, || char *reason) 307 { 308 int i; 309 310 if(skb != NULL) { || ..... 327 } 328 else { /* dial not triggered by rawIP packet */ || ..... 332 } 333 334 printk(KERN_DEBUG "isdn_net_unreachable(): %s: %d, dev=%p, || skb=%p\n", __FILE__, __LINE__, dev, skb ); 335 336 337 for(i = 0; i < DEV_NUMBUFFS; i++) { 338 struct sk_buff *skb; 339 340 while(1) { 341 void *p; 342 343 printk(KERN_DEBUG "isdn_net_unreachable(): || before check for &dev->buffs[i]\n"); 344 345 p = &dev->buffs[i]; 346 347 if ( p == NULL ) 348 printk(KERN_ERR "\nisdn_net_unreachable(): || &dev->buffs[i] is NULL !!!\n\n"); 349 350 printk(KERN_DEBUG "isdn_net_unreachable(): || before skb_dequeue(), i=%d\n", i); 351 skb = skb_dequeue(&dev->buffs[i]); || || ==================> OBEN KRACHT ES, die folgende Zeile wird || ==================> nicht mehr erreicht ... || 353 printk(KERN_DEBUG "isdn_net_unreachable(): || after skb_dequeue(), i=%d\n", i); 354 if ( ! skb ) 355 break; 356 357 if(ntohs(skb->protocol) == ETH_P_IP) { /usr/src/linux/include/linux/skbuff.h: 286 extern __inline__ struct sk_buff *__skb_dequeue(struct sk_buff_head *list) 287 { 288 struct sk_buff *next, *prev, *result; 289 290 if (list == NULL) 291 printk(KERN_ERR "inline __skb_dequeue(): list == NULL\n"); 292 293 prev = (struct sk_buff *) list; 294 next = prev->next; 295 296 if (prev == NULL) 297 printk(KERN_ERR "inline __skb_dequeue(): prev == NULL, (%s %d)\n", 298 __FILE__, __LINE__); 299 300 if (next == NULL) 301 printk(KERN_ERR "inline __skb_dequeue(): next == NULL, (%s %d)\n", 302 __FILE__, __LINE__); || ==========> HIER ist next NULL 303 304 result = NULL; 305 if (next != prev) { 306 result = next; 307 next = next->next; || ==========> next ist NULL, prev != NULL, und next->next || ==========> ist die Dereferenzierung des NULLPOINTERS! Oops !!!! 308 309 if (next == NULL) 310 printk(KERN_ERR "inline __skb_dequeue(): next == NULL, (%s %d)\n", 311 __FILE__, __LINE__); 312 313 list->qlen--; 314 next->prev = prev; 315 prev->next = next; 320 result->next = NULL; 321 result->prev = NULL; 322 result->list = NULL; 323 } 324 return result; 325 } Beste Grüße / best regards Joachim Blauth Please note: I try hard to send internet standard compatible emails only, but don't always succeed. I have to use Microsoft software at work. --- Joachim Blauth, VideoCon AG, Munich, Germany Email: j.blauth(a)videocon.de WWW: http://www.videocon.de Phone: +49 (089) 689593-25 Fax: +49 (089) 689593-68

1 0

Keine Verbindung zum ISP (die zweite!)
by Miklas Neugebauer 11 Nov '99

11 Nov '99

Hi Liste, sorry wegen der vielen Mails, aber Probleme mit Windoof ... habe bis jetzt alle geposteten Möglichkeiten probiert, aber keine Chance ... Kann sein, daß ich mich zu bloed anstelle !!!! Ich danke für weitere Hilfe schon mal im voraus !!! Hier nun nochmal meine Dateien gepostet: >> ls -l /etc/ppp total 21 lrwxrwxrwx 1 root root 7 Oct 14 01:41 auth-down -> auth-up -rwxr-x--x 1 root root 469 Mar 6 1998 auth-up -rw------- 1 root root 177 Nov 11 18:25 chap-secrets -rw-r--r-- 1 root root 0 Nov 11 19:08 dir -rw-r--r-- 1 root root 1897 Apr 4 1999 ibod.cf -rw-r----- 1 root root 281 Nov 11 03:54 ioptions -rw-r----- 1 root root 1395 Nov 11 05:08 ioptions.YaST lrwxrwxrwx 1 root root 5 Oct 14 01:41 ip-down -> ip-up -rwxr-x--x 1 root root 3031 Jul 18 1998 ip-up -rw-r--r-- 1 root root 5908 Apr 4 1999 options -rw-r----- 1 root root 1395 Nov 11 04:30 options.ippp0 -rw------- 1 root root 1145 Nov 11 18:26 pap-secrets -rw------- 1 root root 0 Oct 28 21:24 pap-secrets.new drwxr-xr-x 2 root root 1024 Oct 14 01:44 peers >> /etc/ppp/chap-secrets # Secrets for authentication using CHAP # client server secret IP addresses "micky2309(a)planet-interkom.de" * "xxxxxxxx" "*" micky2309(a)planet-interkom.de "xxxxxxxxx" >> /etc/ppp/pap-secrets # Secrets for authentication using PAP # client server secret IP addresses # OUTBOUND CONNECTIONS # Here you should add your userid password to connect to your providers via # pap. The * means that the password is to be used for ANY host you connect # to. Thus you do not have to worry about the foreign machine name. Just # replace password with your password. # If you have different providers with different passwords then you better # remove the following line. #hostname * password # INBOUND CONNECTIONS #client hostname <password> 192.168.1.1 # If you add "auth login -chap +pap" to /etc/mgetty+sendfax/login.config, # all users in /etc/passwd can use their password for pap-authentication. # # Every regular user can use PPP and has to use passwords from /etc/passwd #* hostname "" # UserIDs that cannot use PPP at all. Check your /etc/passwd and add any # other accounts that should not be able to use pppd! Replace hostname # with your local hostname. #guest hostname "*" - #master hostname "*" - #root hostname "*" - #support hostname "*" - #stats hostname "*" - "suse" * "linux" "micky2309(a)planet-interkom.de" * "xxxxxxxxxx" >> /etc/ppp/ioptions # /etc/ppp/ioptions # for isdn4linux/syncPPP global options for ipppd # # # Klaus Franken, kfr(a)suse.de # Version: 15.05.97 (5.0) # # lock # Set 'debug' to create a lot of information in /var/log/messages debug # Set '+pwlog' for logging passwords in /var/log/messages +pwlog >> /etc/ppp/ioptions.YAST # /etc/ppp/options.ippp? # # for isdn4linux/syncPPP and dynamic IP-numbers # # # Klaus Franken, kfr(a)suse.de # Version: 27.08.97 (5.1) # # This file is copy by YaST from /etc/ppp/ioptions.YaST # to options.<device> # The device(s) # for more than one device try: # /dev/ippp0 /dev/ippp1 ... /dev/ippp0 # The IP addresses: <local>:<remote> # just "0.0.0.0:" or nothing for dynamic IP #0.0.0.0: # my user name user "micky2309(a)planet-interkom.de" # my system name (only for CHAP!) # name my_system_name # accept IP addresses from peer # use with dynamic IP ipcp-accept-local ipcp-accept-remote noipdefault # try to get IP address from interface # option specific to ipppd (as opposed to pppd) # use only with static IP #useifip # disable all header-compression -vj -vjccomp -ac -pc -bsdcomp # sometimes you need this: #noccp # max receive unit mru 1524 # max transmit unit mtu 1500 # If this machine is a server, force authentication by uncommenting one # of the following. However, if this machine is a client, doing this will # prevent a succesful connection! (message "peer refused to authenticate"). # So, only uncomment on a server. # "+pap" / "+chap" NUR AKTIVIEREN, WENN DIES EIN SERVER IST!!! #+pap #+chap # if you have problems with handshaking (no response for first # lcp-package) try to decrease the retry-cycle. Default is 3 sec, # try for example 2 sec: # lcp-restart 2 >> /etc/ppp/options # to <n>. #remotename <n> # Add an entry to this system's ARP [Address Resolution Protocol] # table with the IP address of the peer and the Ethernet address of this # system. {proxyarp,noproxyarp} noproxyarp # Use the system password database for authenticating the peer using # PAP. Note: mgetty already provides this option. If this is specified # then dialin from users using a script under Linux to fire up ppp wont work. #login # If this option is given, pppd will send an LCP echo-request frame to # the peer every n seconds. Under Linux, the echo-request is sent when # no packets have been received from the peer for n seconds. Normally # the peer should respond to the echo-request by sending an echo-reply. # This option can be used with the lcp-echo-failure option to detect # that the peer is no longer connected. #lcp-echo-interval 30 # If this option is given, pppd will presume the peer to be dead if n # LCP echo-requests are sent without receiving a valid LCP echo-reply. # If this happens, pppd will terminate the connection. Use of this # option requires a non-zero value for the lcp-echo-interval parameter. # This option can be used to enable pppd to terminate after the physical # connection has been broken (e.g., the modem has hung up) in # situations where no hardware modem control lines are available. #lcp-echo-failure 4 # Specifies that pppd should disconnect if the link is idle for n seconds. #idle 600 # Disable the IPXCP and IPX protocols. noipx # Disable VJ novj novjccomp # ---<End of File>--- >> /etc/ppp/options.ippp0 # /etc/ppp/options.ippp? # # for isdn4linux/syncPPP and dynamic IP-numbers # # # Klaus Franken, kfr(a)suse.de # Version: 27.08.97 (5.1) # # This file is copy by YaST from /etc/ppp/ioptions.YaST # to options.<device> # The device(s) # for more than one device try: # /dev/ippp0 /dev/ippp1 ... /dev/ippp0 # The IP addresses: <local>:<remote> # just "0.0.0.0:" or nothing for dynamic IP #0.0.0.0: # my user name user "micky2309(a)planet-interkom.de" # my system name (only for CHAP!) # name my_system_name # accept IP addresses from peer # use with dynamic IP ipcp-accept-local ipcp-accept-remote noipdefault # try to get IP address from interface # option specific to ipppd (as opposed to pppd) # use only with static IP #useifip # disable all header-compression -vj -vjccomp -ac -pc -bsdcomp # sometimes you need this: #noccp # max receive unit mru 1524 # max transmit unit mtu 1500 # If this machine is a server, force authentication by uncommenting one # of the following. However, if this machine is a client, doing this will # prevent a succesful connection! (message "peer refused to authenticate"). # So, only uncomment on a server. # "+pap" / "+chap" NUR AKTIVIEREN, WENN DIES EIN SERVER IST!!! #+pap #+chap # if you have problems with handshaking (no response for first # lcp-package) try to decrease the retry-cycle. Default is 3 sec, # try for example 2 sec: # lcp-restart 2

2 1

RE: [suse-isdn] Keine Verbindung zum ISP
by Post, Wolfgang 11 Nov '99

11 Nov '99

hallo miklas! einmal reicht ;-) (die mail) > Ich habe auch die PAP- und CHAP-Secrets Dateien laut beschreibung geändert. was will denn dein provider? pap oder chap? fuer eins von beidem muesstest du dich schon entscheiden. > Wie aus der /var/log/messages (siehe unten) ersichtlich bekomme ich zwar eine > Verbindung zustande, aber die Benutzerabfrage läuft schief !!! eben! du versuchst eine chap-autentifizierung, aber die gegenseite versteht das wohl nicht. > Danach wird die Verbindung ununterbrochen versucht weiter herzustellen und es > fallen somit immer Telefongebühren an!!! sicher, so ist das wohl eingestellt, dass nach einem fehlversuch eine neuanwahl erfolgen sol. evtl. in der konfiguration aendern. > Hier der Auszug meiner /var/log/messages >> /var/log/messages Nov 11 05:13:14 board kernel: ippp0: dialing 1 010900191700... Nov 11 05:13:15 board isdnlog: (HiSax driver detected) Nov 11 05:13:15 board isdnlog: Nov 11 05:13:15 * tei 98 calling +49 /191700, Germany with My Home RING (Data) Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /191700, Germany with My Home Time:Thu Nov 11 05:21:00 1999 Nov 11 05:13:16 board isdnlog: !!! Problem with AreaCode: Input string is not a number or empty Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /30D970, Germany with My Home COLP +49 /30D970, Germany Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /30D970, Germany with My Home CONNECT (Data) Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /30D970, Germany with My Home CHARGE: Oppps: No charge infos for provider 90, Zone -1 Nov 11 05:13:16 board kernel: isdn_net: ippp0 connected Nov 11 05:13:16 board kernel: isdn_net: chargetime of ippp0 now 150072 Nov 11 05:13:16 board ipppd[83]: Local number: 56498615, Remote number: 010900191700, Type: outgoing Nov 11 05:13:16 board ipppd[83]: PHASE_WAIT -> PHASE_ESTABLISHED, ifunit: 0, linkunit: 0, fd: 7 Nov 11 05:13:16 board ipppd[83]: sent [0][LCP ConfReq id=0x1 <mru 1524> <magic 0x47f2d9a1>] Nov 11 05:13:16 board ipppd[83]: rcvd [0][LCP ConfReq id=0x1 <auth chap md5> <magic 0x768be4d7>] Nov 11 05:13:16 board ipppd[83]: sent [0][LCP ConfAck id=0x1 <auth chap md5> <magic 0x768be4d7>] Nov 11 05:13:19 board ipppd[83]: sent [0][LCP ConfReq id=0x1 <mru 1524> <magic 0x47f2d9a1>] Nov 11 05:13:19 board ipppd[83]: rcvd [0][LCP ConfAck id=0x1 <mru 1524> <magic 0x47f2d9a1>] Nov 11 05:13:19 board ipppd[83]: lcp layer is UP Nov 11 05:13:19 board ipppd[83]: rcvd [0][CHAP Challenge id=0x2 <210df9e6d3c0ad9a8774614e3b281502>, name = "chap"] Nov 11 05:13:19 board ipppd[83]: ChapReceiveChallenge: Rcvd id 2. Nov 11 05:13:19 board ipppd[83]: ChapReceiveChallenge: received name field: 'chap' Nov 11 05:13:19 board ipppd[83]: No CHAP secret found for authenticating us to chap da stehts! chap wird wohl nicht unterstuetzt, oder es fehlt etwas fuer chap. Nov 11 05:13:19 board ipppd[83]: sent [0][CHAP Response id=0x2 <bd6ce8a3f978f3e49ea2bec4afc4c01c>, name = "board"] Nov 11 05:13:21 board ipppd[83]: rcvd [0][CHAP Failure id=0x2 ""] Nov 11 05:13:21 board ipppd[83]: ChapReceiveFailure: Rcvd id 2. Nov 11 05:13:21 board ipppd[83]: CHAP authentication failed und da nochmal im klartext! Nov 11 05:13:21 board ipppd[83]: rcvd [0][LCP TermReq id=0x3] Nov 11 05:13:21 board ipppd[83]: LCP terminated by peer [...usw....] nimm chap raus als autentifizierung, mit pap sollte es funktionieren. gruss wolfgang

1 0

Keine Verbindung zum ISP
by Miklas Neugebauer 11 Nov '99

11 Nov '99

HI Liste, Ich habe Probleme mit dem Verbindungsaufbau zu meinem ISP "Planet-Interkom". Die Konfiguation habe ich über YAST und manuell mit Beschreibung durchgeführt. Ich habe auch die PAP- und CHAP-Secrets Dateien laut beschreibung geändert. Die Verbindung versuche ich per "telnet 195.182.96.29" herzustellen. Wie aus der /var/log/messages (siehe unten) ersichtlich bekomme ich zwar eine Verbindung zustande, aber die Benutzerabfrage läuft schief !!! Danach wird die Verbindung ununterbrochen versucht weiter herzustellen und es fallen somit immer Telefongebühren an!!! Abbrechen kann ich es nur mit Restart oder download des ISDN-Driver's. Was mache ich falsch??? Kann mir BITTE jemannd helfen ?!?! Hier meine Soft-/Hardware: * SUSE LINUX 6.1 * ISDN Fritz Classic Karte * Hardware funktioniert aber perfekt * Weitere Informationen nach näherer Beschreibung Hier der Auszug meiner /var/log/messages >> /var/log/messages Nov 11 05:13:14 board kernel: ippp0: dialing 1 010900191700... Nov 11 05:13:15 board isdnlog: (HiSax driver detected) Nov 11 05:13:15 board isdnlog: Nov 11 05:13:15 * tei 98 calling +49 /191700, Germany with My Home RING (Data) Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /191700, Germany with My Home Time:Thu Nov 11 05:21:00 1999 Nov 11 05:13:16 board isdnlog: !!! Problem with AreaCode: Input string is not a number or empty Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /30D970, Germany with My Home COLP +49 /30D970, Germany Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /30D970, Germany with My Home CONNECT (Data) Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /30D970, Germany with My Home CHARGE: Oppps: No charge infos for provider 90, Zone -1 Nov 11 05:13:16 board kernel: isdn_net: ippp0 connected Nov 11 05:13:16 board kernel: isdn_net: chargetime of ippp0 now 150072 Nov 11 05:13:16 board ipppd[83]: Local number: 56498615, Remote number: 010900191700, Type: outgoing Nov 11 05:13:16 board ipppd[83]: PHASE_WAIT -> PHASE_ESTABLISHED, ifunit: 0, linkunit: 0, fd: 7 Nov 11 05:13:16 board ipppd[83]: sent [0][LCP ConfReq id=0x1 <mru 1524> <magic 0x47f2d9a1>] Nov 11 05:13:16 board ipppd[83]: rcvd [0][LCP ConfReq id=0x1 <auth chap md5> <magic 0x768be4d7>] Nov 11 05:13:16 board ipppd[83]: sent [0][LCP ConfAck id=0x1 <auth chap md5> <magic 0x768be4d7>] Nov 11 05:13:19 board ipppd[83]: sent [0][LCP ConfReq id=0x1 <mru 1524> <magic 0x47f2d9a1>] Nov 11 05:13:19 board ipppd[83]: rcvd [0][LCP ConfAck id=0x1 <mru 1524> <magic 0x47f2d9a1>] Nov 11 05:13:19 board ipppd[83]: lcp layer is UP Nov 11 05:13:19 board ipppd[83]: rcvd [0][CHAP Challenge id=0x2 <210df9e6d3c0ad9a8774614e3b281502>, name = "chap"] Nov 11 05:13:19 board ipppd[83]: ChapReceiveChallenge: Rcvd id 2. Nov 11 05:13:19 board ipppd[83]: ChapReceiveChallenge: received name field: 'chap' Nov 11 05:13:19 board ipppd[83]: No CHAP secret found for authenticating us to chap Nov 11 05:13:19 board ipppd[83]: sent [0][CHAP Response id=0x2 <bd6ce8a3f978f3e49ea2bec4afc4c01c>, name = "board"] Nov 11 05:13:21 board ipppd[83]: rcvd [0][CHAP Failure id=0x2 ""] Nov 11 05:13:21 board ipppd[83]: ChapReceiveFailure: Rcvd id 2. Nov 11 05:13:21 board ipppd[83]: CHAP authentication failed Nov 11 05:13:21 board ipppd[83]: rcvd [0][LCP TermReq id=0x3] Nov 11 05:13:21 board ipppd[83]: LCP terminated by peer Nov 11 05:13:21 board ipppd[83]: sent [0][LCP TermAck id=0x3] Nov 11 05:13:21 board isdnlog: Nov 11 05:13:21 tei 98 calling +49 /30D970, Germany with My Home Normal call clearing (User) Nov 11 05:13:21 board kernel: isdn: HiSax,ch0 cause: E0010 Nov 11 05:13:21 board kernel: ippp0: remote hangup Nov 11 05:13:21 board kernel: ippp0: Chargesum is 0 Nov 11 05:13:21 board kernel: ippp, open, slot: 0, minor: 0, state: 0000 Nov 11 05:13:21 board kernel: ippp_ccp: allocating reset data structure Nov 11 05:13:21 board ipppd[83]: Modem hangup Nov 11 05:13:21 board ipppd[83]: Connection terminated. Nov 11 05:13:21 board ipppd[83]: taking down PHASE_DEAD link 0, linkunit: 0 Nov 11 05:13:21 board ipppd[83]: LCP is down Nov 11 05:13:21 board ipppd[83]: closing fd 7 from unit 0 Nov 11 05:13:21 board ipppd[83]: link 0 closed , linkunit: 0 Nov 11 05:13:21 board ipppd[83]: reinit_unit: 0 Nov 11 05:13:21 board ipppd[83]: Connect[0]: /dev/ippp0, fd: 7 Nov 11 05:13:21 board isdnlog: Nov 11 05:13:21 tei 98 calling +49 /30D970, Germany with My Home HANGUP ( 0:00:05) Normal call clearing (User)

2 1

Keine Verbindung zum ISP
by Miklas Neugebauer 11 Nov '99

11 Nov '99

HI Liste, Ich habe Probleme mit dem Verbindungsaufbau zu meinem ISP "Planet-Interkom". Die Konfiguation habe ich über YAST und manuell mit Beschreibung durchgeführt. Ich habe auch die PAP- und CHAP-Secrets Dateien laut beschreibung geändert. Die Verbindung versuche ich per "telnet 195.182.96.29" herzustellen. Wie aus der /var/log/messages (siehe unten) ersichtlich bekomme ich zwar eine Verbindung zustande, aber die Benutzerabfrage läuft schief !!! Danach wird die Verbindung ununterbrochen versucht weiter herzustellen und es fallen somit immer Telefongebühren an!!! Abbrechen kann ich es nur mit Restart oder download des ISDN-Driver's. Was mache ich falsch??? Kann mir BITTE jemannd helfen ?!?! Hier meine Soft-/Hardware: * SUSE LINUX 6.1 * ISDN Fritz Classic Karte * Hardware funktioniert aber perfekt * Weitere Informationen nach näherer Beschreibung Hier der Auszug meiner /var/log/messages >> /var/log/messages Nov 11 05:13:14 board kernel: ippp0: dialing 1 010900191700... Nov 11 05:13:15 board isdnlog: (HiSax driver detected) Nov 11 05:13:15 board isdnlog: Nov 11 05:13:15 * tei 98 calling +49 /191700, Germany with My Home RING (Data) Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /191700, Germany with My Home Time:Thu Nov 11 05:21:00 1999 Nov 11 05:13:16 board isdnlog: !!! Problem with AreaCode: Input string is not a number or empty Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /30D970, Germany with My Home COLP +49 /30D970, Germany Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /30D970, Germany with My Home CONNECT (Data) Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /30D970, Germany with My Home CHARGE: Oppps: No charge infos for provider 90, Zone -1 Nov 11 05:13:16 board kernel: isdn_net: ippp0 connected Nov 11 05:13:16 board kernel: isdn_net: chargetime of ippp0 now 150072 Nov 11 05:13:16 board ipppd[83]: Local number: 56498615, Remote number: 010900191700, Type: outgoing Nov 11 05:13:16 board ipppd[83]: PHASE_WAIT -> PHASE_ESTABLISHED, ifunit: 0, linkunit: 0, fd: 7 Nov 11 05:13:16 board ipppd[83]: sent [0][LCP ConfReq id=0x1 <mru 1524> <magic 0x47f2d9a1>] Nov 11 05:13:16 board ipppd[83]: rcvd [0][LCP ConfReq id=0x1 <auth chap md5> <magic 0x768be4d7>] Nov 11 05:13:16 board ipppd[83]: sent [0][LCP ConfAck id=0x1 <auth chap md5> <magic 0x768be4d7>] Nov 11 05:13:19 board ipppd[83]: sent [0][LCP ConfReq id=0x1 <mru 1524> <magic 0x47f2d9a1>] Nov 11 05:13:19 board ipppd[83]: rcvd [0][LCP ConfAck id=0x1 <mru 1524> <magic 0x47f2d9a1>] Nov 11 05:13:19 board ipppd[83]: lcp layer is UP Nov 11 05:13:19 board ipppd[83]: rcvd [0][CHAP Challenge id=0x2 <210df9e6d3c0ad9a8774614e3b281502>, name = "chap"] Nov 11 05:13:19 board ipppd[83]: ChapReceiveChallenge: Rcvd id 2. Nov 11 05:13:19 board ipppd[83]: ChapReceiveChallenge: received name field: 'chap' Nov 11 05:13:19 board ipppd[83]: No CHAP secret found for authenticating us to chap Nov 11 05:13:19 board ipppd[83]: sent [0][CHAP Response id=0x2 <bd6ce8a3f978f3e49ea2bec4afc4c01c>, name = "board"] Nov 11 05:13:21 board ipppd[83]: rcvd [0][CHAP Failure id=0x2 ""] Nov 11 05:13:21 board ipppd[83]: ChapReceiveFailure: Rcvd id 2. Nov 11 05:13:21 board ipppd[83]: CHAP authentication failed Nov 11 05:13:21 board ipppd[83]: rcvd [0][LCP TermReq id=0x3] Nov 11 05:13:21 board ipppd[83]: LCP terminated by peer Nov 11 05:13:21 board ipppd[83]: sent [0][LCP TermAck id=0x3] Nov 11 05:13:21 board isdnlog: Nov 11 05:13:21 tei 98 calling +49 /30D970, Germany with My Home Normal call clearing (User) Nov 11 05:13:21 board kernel: isdn: HiSax,ch0 cause: E0010 Nov 11 05:13:21 board kernel: ippp0: remote hangup Nov 11 05:13:21 board kernel: ippp0: Chargesum is 0 Nov 11 05:13:21 board kernel: ippp, open, slot: 0, minor: 0, state: 0000 Nov 11 05:13:21 board kernel: ippp_ccp: allocating reset data structure Nov 11 05:13:21 board ipppd[83]: Modem hangup Nov 11 05:13:21 board ipppd[83]: Connection terminated. Nov 11 05:13:21 board ipppd[83]: taking down PHASE_DEAD link 0, linkunit: 0 Nov 11 05:13:21 board ipppd[83]: LCP is down Nov 11 05:13:21 board ipppd[83]: closing fd 7 from unit 0 Nov 11 05:13:21 board ipppd[83]: link 0 closed , linkunit: 0 Nov 11 05:13:21 board ipppd[83]: reinit_unit: 0 Nov 11 05:13:21 board ipppd[83]: Connect[0]: /dev/ippp0, fd: 7 Nov 11 05:13:21 board isdnlog: Nov 11 05:13:21 tei 98 calling +49 /30D970, Germany with My Home HANGUP ( 0:00:05) Normal call clearing (User)

1 0

Keine Verbindung zum ISP
by Miklas Neugebauer 11 Nov '99

11 Nov '99

HI Liste, Ich habe Probleme mit dem Verbindungsaufbau zu meinem ISP "Planet-Interkom". Die Konfiguation habe ich über YAST und manuell mit Beschreibung durchgeführt. Ich habe auch die PAP- und CHAP-Secrets Dateien laut beschreibung geändert. Die Verbindung versuche ich per "telnet 195.182.96.29" herzustellen. Wie aus der /var/log/messages (siehe unten) ersichtlich bekomme ich zwar eine Verbindung zustande, aber die Benutzerabfrage läuft schief !!! Danach wird die Verbindung ununterbrochen versucht weiter herzustellen und es fallen somit immer Telefongebühren an!!! Abbrechen kann ich es nur mit Restart oder download des ISDN-Driver's. Was mache ich falsch??? Kann mir BITTE jemannd helfen ?!?! Hier meine Soft-/Hardware: * SUSE LINUX 6.1 * ISDN Fritz Classic Karte * Hardware funktioniert aber perfekt * Weitere Informationen nach näherer Beschreibung Hier der Auszug meiner /var/log/messages >> /var/log/messages Nov 11 05:13:14 board kernel: ippp0: dialing 1 010900191700... Nov 11 05:13:15 board isdnlog: (HiSax driver detected) Nov 11 05:13:15 board isdnlog: Nov 11 05:13:15 * tei 98 calling +49 /191700, Germany with My Home RING (Data) Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /191700, Germany with My Home Time:Thu Nov 11 05:21:00 1999 Nov 11 05:13:16 board isdnlog: !!! Problem with AreaCode: Input string is not a number or empty Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /30D970, Germany with My Home COLP +49 /30D970, Germany Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /30D970, Germany with My Home CONNECT (Data) Nov 11 05:13:16 board isdnlog: Nov 11 05:13:16 tei 98 calling +49 /30D970, Germany with My Home CHARGE: Oppps: No charge infos for provider 90, Zone -1 Nov 11 05:13:16 board kernel: isdn_net: ippp0 connected Nov 11 05:13:16 board kernel: isdn_net: chargetime of ippp0 now 150072 Nov 11 05:13:16 board ipppd[83]: Local number: 56498615, Remote number: 010900191700, Type: outgoing Nov 11 05:13:16 board ipppd[83]: PHASE_WAIT -> PHASE_ESTABLISHED, ifunit: 0, linkunit: 0, fd: 7 Nov 11 05:13:16 board ipppd[83]: sent [0][LCP ConfReq id=0x1 <mru 1524> <magic 0x47f2d9a1>] Nov 11 05:13:16 board ipppd[83]: rcvd [0][LCP ConfReq id=0x1 <auth chap md5> <magic 0x768be4d7>] Nov 11 05:13:16 board ipppd[83]: sent [0][LCP ConfAck id=0x1 <auth chap md5> <magic 0x768be4d7>] Nov 11 05:13:19 board ipppd[83]: sent [0][LCP ConfReq id=0x1 <mru 1524> <magic 0x47f2d9a1>] Nov 11 05:13:19 board ipppd[83]: rcvd [0][LCP ConfAck id=0x1 <mru 1524> <magic 0x47f2d9a1>] Nov 11 05:13:19 board ipppd[83]: lcp layer is UP Nov 11 05:13:19 board ipppd[83]: rcvd [0][CHAP Challenge id=0x2 <210df9e6d3c0ad9a8774614e3b281502>, name = "chap"] Nov 11 05:13:19 board ipppd[83]: ChapReceiveChallenge: Rcvd id 2. Nov 11 05:13:19 board ipppd[83]: ChapReceiveChallenge: received name field: 'chap' Nov 11 05:13:19 board ipppd[83]: No CHAP secret found for authenticating us to chap Nov 11 05:13:19 board ipppd[83]: sent [0][CHAP Response id=0x2 <bd6ce8a3f978f3e49ea2bec4afc4c01c>, name = "board"] Nov 11 05:13:21 board ipppd[83]: rcvd [0][CHAP Failure id=0x2 ""] Nov 11 05:13:21 board ipppd[83]: ChapReceiveFailure: Rcvd id 2. Nov 11 05:13:21 board ipppd[83]: CHAP authentication failed Nov 11 05:13:21 board ipppd[83]: rcvd [0][LCP TermReq id=0x3] Nov 11 05:13:21 board ipppd[83]: LCP terminated by peer Nov 11 05:13:21 board ipppd[83]: sent [0][LCP TermAck id=0x3] Nov 11 05:13:21 board isdnlog: Nov 11 05:13:21 tei 98 calling +49 /30D970, Germany with My Home Normal call clearing (User) Nov 11 05:13:21 board kernel: isdn: HiSax,ch0 cause: E0010 Nov 11 05:13:21 board kernel: ippp0: remote hangup Nov 11 05:13:21 board kernel: ippp0: Chargesum is 0 Nov 11 05:13:21 board kernel: ippp, open, slot: 0, minor: 0, state: 0000 Nov 11 05:13:21 board kernel: ippp_ccp: allocating reset data structure Nov 11 05:13:21 board ipppd[83]: Modem hangup Nov 11 05:13:21 board ipppd[83]: Connection terminated. Nov 11 05:13:21 board ipppd[83]: taking down PHASE_DEAD link 0, linkunit: 0 Nov 11 05:13:21 board ipppd[83]: LCP is down Nov 11 05:13:21 board ipppd[83]: closing fd 7 from unit 0 Nov 11 05:13:21 board ipppd[83]: link 0 closed , linkunit: 0 Nov 11 05:13:21 board ipppd[83]: reinit_unit: 0 Nov 11 05:13:21 board ipppd[83]: Connect[0]: /dev/ippp0, fd: 7 Nov 11 05:13:21 board isdnlog: Nov 11 05:13:21 tei 98 calling +49 /30D970, Germany with My Home HANGUP ( 0:00:05) Normal call clearing (User)

1 0

Frage: Teles 16.3c1 unter Linux?
by Werner M. Mayer 11 Nov '99

11 Nov '99

Hi Leute! Ich habe zwei Teles-Karten, eine 16.3 und eine 16.3c1. Beide scheinen PnP zu sein. Während die 16.3 einwandfrei geht und als Datenportbreite 32 bzw. 64 Byte anzeigt, sind es bei der 16.3c1 nur 2 Byte. Ist die Karte defekt, kann pnpdump unter Suse-6.2 die Register der 16.3c1 nicht richtig auswerten, oder hat die Karte nur einen so kleinen Datenport? Sollte die Karte nicht für Linux geeignet sein, gibt es hier jemanden in der Liste, der sie evtl. mit mir tauscht, weil er noch einen Windows-Rechner hat, wo sie gehen würde, oder er kennt jemanden mit Windows, der evtl. gern auch tauscht? Ciao, Werner.

1 0

Anderer Telefonanbieter
by Peter Bossy 11 Nov '99

11 Nov '99

Halloele! Wie bringe ich i4l bei, daß ich eine andere Telefongesellschaft (Telebel) als Telekom benutze? Ich würde gerne in isdnrep gerne richtige Beträge sehen. Gruß Peter

2 2

DynIP und Routing-Table
by Ulf Münzner 11 Nov '99

11 Nov '99

Hallo, ich habe einen Einzel-PC mit AVM-Fritz-Card. Hardware funktioniert. Verbindung kommt zustande, ist stabil und baut sich wieder ab, entsprechend dem ISDN-HowTo habe ich mal die Ausgaben von ifconfig und route geprüft. Während bei ifconfig alles normal aussieht, steht in der Kernel-Routing-Table ein doppelter Eintrag. Warum? Kann ich das ignorieren? Wie kann ich es verhindern? Hier ein Ausschnitt aus route -n nach einem Verbindungsaufbau: Zeilen 2 und 3 sind identisch. Ist vor dem Verbindungsaufbau nicht!? NACH DER VERBINDUNG: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.11.11 0.0.0.0 255.255.255.255 UH 0 0 0 ippp0 !!! 192.168.11.11 0.0.0.0 255.255.255.255 UH 0 0 0 ippp0 !!! 192.168.11.10 0.0.0.0 255.255.255.255 UH 1 0 0 dummy0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.11.11 0.0.0.0 UG 0 0 0 ippp0

2 1