HI, I am using SuSE 6.3 for some time now and have run into a problem with isdn4linux (HiSAX v 3.3c) version after switching from a Teles card to a Fritz! Classic. This card has been recognized as a AVM A1 card which is OK as far I can see (BTW, I cannot change the card type thru YAST). I also switched provider. After changing the cards I've frequently had the connection drop suddenly without ever recovering later on... before I never had this problem. ------------------------------------------- Jul 17 15:18:14 donkeykong isdnlog: Jul 17 15:18:14 tei 96 calling +31 23/5537000, Vijfhuizen NH with PC ISDN Unknown provider ??? (-1) Jul 17 15:18:14 donkeykong ipppd[96]: Local number: 0235621753, Remote number: 0235537333, Type: outgoing Jul 17 15:18:14 donkeykong ipppd[96]: PHASE_WAIT -> PHASE_ESTABLISHED, ifunit: 0, linkunit: 0, fd: 7 Jul 17 15:18:14 donkeykong kernel: isdn_net: ippp0 connected Jul 17 15:18:14 donkeykong kernel: isdn_net: chargetime of ippp0 now 34965147 Jul 17 15:18:15 donkeykong ipppd[96]: Remote message: Jul 17 15:18:15 donkeykong ipppd[96]: MPPP negotiation, He: No We: No Jul 17 15:18:15 donkeykong ipppd[96]: CCP enabled! Trying CCP. Jul 17 15:18:15 donkeykong ipppd[96]: CCP: got ccp-unit 0 for link 0 (protocol: 0x80fd) Jul 17 15:18:15 donkeykong ipppd[96]: ccp_resetci! Jul 17 15:18:15 donkeykong ipppd[96]: local IP address 195.121.182.160 Jul 17 15:18:15 donkeykong ipppd[96]: remote IP address 193.172.250.49 Jul 17 15:25:53 donkeykong isdnlog: Jul 17 15:25:53 tei 96 calling +31 23/5537000, Vijfhuizen NH with PC ISDN Response to Status enquir Jul 17 15:26:24 donkeykong isdnlog: Jul 17 15:26:24 tei 96 calling +31 23/5537000, Vijfhuizen NH with PC ISDN Response to Status enquir Jul 17 15:27:36 donkeykong ipppd[96]: Modem hangup Jul 17 15:27:36 donkeykong ipppd[96]: Connection terminated. Jul 17 15:27:36 donkeykong ipppd[96]: taking down PHASE_DEAD link 0, linkunit: 0 Jul 17 15:27:36 donkeykong ipppd[96]: closing fd 7 from unit 0 Jul 17 15:27:36 donkeykong ipppd[96]: link 0 closed , linkunit: 0 Jul 17 15:27:36 donkeykong ipppd[96]: reinit_unit: 0 Jul 17 15:27:36 donkeykong ipppd[96]: Connect[0]: /dev/ippp0, fd: 7 Jul 17 15:27:36 donkeykong kernel: isdn: HiSax,ch0 cause: E021B Jul 17 15:27:36 donkeykong kernel: ippp0: remote hangup Jul 17 15:27:36 donkeykong kernel: ippp0: Chargesum is 0 Jul 17 15:27:36 donkeykong kernel: ippp, open, slot: 0, minor: 0, state: 0000 Jul 17 15:27:36 donkeykong kernel: ippp_ccp: allocating reset data structure Jul 17 15:27:36 donkeykong kernel: TCP: zapping lost address 195.121.182.160:4765 -> 195.121.182.160:80 Jul 17 15:27:36 donkeykong kernel: TCP: zapping lost address 195.121.182.160:4763 -> 195.121.182.160:80 Jul 17 15:27:36 donkeykong kernel: TCP: zapping lost address 195.121.182.160:4762 -> 195.121.182.160:80 Jul 17 15:27:36 donkeykong kernel: TCP: zapping lost address 195.121.182.160:4756 -> 195.121.182.160:80 ..here it goes wrong and doesnt establish new connections.... Jul 17 15:27:46 donkeykong kernel: OPEN: 192.168.102.99 -> 212.206.169.150 TCP, port: 4767 -> 80 Jul 17 15:27:46 donkeykong kernel: ippp0: dialing 1 0235537333... Jul 17 15:27:54 donkeykong kernel: ippp0: dialing 2 0235537333... Jul 17 15:28:02 donkeykong kernel: ippp0: dialing 3 0235537333... Jul 17 15:28:10 donkeykong kernel: isdn_net: local hangup ippp0 Jul 17 15:28:10 donkeykong kernel: ippp0: Chargesum is 0 ------------------------------------------- Anybody have an idea what is going wrong? Thanks, Erik ------------------------------------------- Erik Slooff erik@slooff.com -------------------------------------------