Koozali.org: home of the SME Server

isdn

NeL

Re: isdn
« Reply #15 on: February 13, 2002, 11:57:37 AM »
Here is the log file after adding debug option and without sync option:
I have a LCP timeout...


Feb 11 21:48:15 e-smith atalkd[1257]: zip_getnetinfo for eth0
Feb 11 21:48:20 e-smith PAM_unix[1303]: (login) session opened for user root by LOGIN(uid=0)
Feb 11 21:48:20 e-smith  -- root[1303]: ROOT LOGIN ON tty2
Feb 11 21:48:23 e-smith diald[683]: Calling site 0.0.0.0
Feb 11 21:48:24 e-smith chat[1333]: abort on (BUSY)
Feb 11 21:48:24 e-smith chat[1333]: abort on (ERROR)
Feb 11 21:48:24 e-smith chat[1333]: abort on (NO CARRIER)
Feb 11 21:48:24 e-smith chat[1333]: abort on (NO DIALTONE)
Feb 11 21:48:24 e-smith chat[1333]: abort on (Invalid Login)
Feb 11 21:48:24 e-smith chat[1333]: abort on (Login incorrect)
Feb 11 21:48:24 e-smith chat[1333]: report (CONNECT)
Feb 11 21:48:24 e-smith chat[1333]: send (ATZ^M)
Feb 11 21:48:24 e-smith chat[1333]: expect (OK)
Feb 11 21:48:24 e-smith chat[1333]: ATZ^M^M
Feb 11 21:48:24 e-smith chat[1333]: OK
Feb 11 21:48:24 e-smith chat[1333]:  -- got it
Feb 11 21:48:24 e-smith chat[1333]: send (ATL0M0^M)
Feb 11 21:48:24 e-smith chat[1333]: expect (OK)
Feb 11 21:48:24 e-smith chat[1333]: ^M
Feb 11 21:48:24 e-smith chat[1333]: ATL0M0^M^M
Feb 11 21:48:24 e-smith chat[1333]: OK
Feb 11 21:48:24 e-smith chat[1333]:  -- got it
Feb 11 21:48:24 e-smith chat[1333]: send (ATS14=3&EXXXXXX&B512^M)
Feb 11 21:48:25 e-smith chat[1333]: expect (OK)
Feb 11 21:48:25 e-smith chat[1333]: ^M
Feb 11 21:48:25 e-smith chat[1333]: ATS14=3&EXXXXX&B512^M^M
Feb 11 21:48:25 e-smith chat[1333]: OK
Feb 11 21:48:25 e-smith chat[1333]:  -- got it
Feb 11 21:48:25 e-smith chat[1333]: send (ATDT0860922000^M)
Feb 11 21:48:25 e-smith atalkd[1257]: config for no router
Feb 11 21:48:25 e-smith chat[1333]: expect (CONNECT)
Feb 11 21:48:25 e-smith chat[1333]: ^M
Feb 11 21:48:26 e-smith atalkd[1257]: ready 0/0/0
Feb 11 21:48:26 e-smith atalk: atalkd startup succeeded
Feb 11 21:48:27 e-smith chat[1333]: ATDT0860922000^M^M
Feb 11 21:48:27 e-smith chat[1333]: CONNECT
Feb 11 21:48:27 e-smith chat[1333]:  -- got it
Feb 11 21:48:27 e-smith diald[683]: connector: chat:  Feb 11 21:48:27 CONNECT 64000/HDLC
Feb 11 21:48:27 e-smith diald[683]: Connected to site 0.0.0.0
Feb 11 21:48:27 e-smith diald[683]: Running pppd (pid = 1338).
Feb 11 21:48:27 e-smith diald[1338]: Running pppd: /usr/sbin/pppd -defaultroute -detach modem crtscts mtu 1500 mru 1524 name eric.lenezet debug noauth noipdefault ipparam diald
Feb 11 21:48:27 e-smith pppd[1338]: pppd 2.4.0 started by root, uid 0
Feb 11 21:48:27 e-smith pppd[1338]: Using interface ppp0
Feb 11 21:48:27 e-smith pppd[1338]: Connect: ppp0 <--> /dev/ttyI0
Feb 11 21:48:27 e-smith pppd[1338]: sent [LCP ConfReq id=0x1 ]
Feb 11 21:48:38 e-smith atalk: papd startup succeeded
Feb 11 21:48:38 e-smith papd[1348]: restart (1.4b2+asun2.1.3)
Feb 11 21:48:39 e-smith atalk: afpd startup succeeded
Feb 11 21:48:42 e-smith last message repeated 5 times
Feb 11 21:48:45 e-smith afpd[1358]: e-smith-server:AFPServer@* started on 65280.172:254 (1.4b2+asun2.1.3)
Feb 11 21:48:45 e-smith afpd[1358]: ASIP started on 192.168.1.1:548(2) (1.4b2+asun2.1.3)
Feb 11 21:48:45 e-smith pppd[1338]: sent [LCP ConfReq id=0x1 ]
Feb 11 21:48:54 e-smith last message repeated 3 times
Feb 11 21:48:57 e-smith pppd[1338]: LCP: timeout sending Config-Requests
Feb 11 21:48:57 e-smith pppd[1338]: Connection terminated.
Feb 11 21:48:57 e-smith pppd[1338]: Exit.
Feb 11 21:48:57 e-smith diald[683]: start sl0: SIOCSIFMTU: Invalid argument
Feb 11 21:48:57 e-smith diald[683]: stop ppp0: RTNETLINK answers: No such process
Feb 11 21:48:57 e-smith kernel: ppp: ppp0 not active
Feb 11 21:48:57 e-smith diald[683]: stop ppp0: SIOCSIFFLAGS: No such device or address
Feb 11 21:48:57 e-smith diald[683]: Disconnected. Call duration 30 seconds.

If someone can help me ;o)
NeLNeL wrote:
>
> Hello,
>  
> I would like to know why with e-smith 4.1.2 i can't use eicon
> diva pci isdn card and with sme5.1.2 it work fine... Did
> someone can explain to me what's wrong with 4.1.2 and fine
> with 5.1.2? I have alway the same message on 4.1.2: sl0:
> SIOSIFMTU: invalid argument ...where can i change it? I would
> like to understand before passing on 5.1.2 ;o)
> Thanks.
> NeL

Filippo Carletti

Re: isdn
« Reply #16 on: February 13, 2002, 07:10:11 PM »
It seems that you can't talk with remote party.
Have you verified with a manual connection ? Try minicom, issue same commands you see in your log (ATZ, ATS14...)

I think there have been some cases where ISDN cards didn't work with ttyIn.

But, newest 5.1.2 sync ppp should work.

Kees

Re: isdn
« Reply #17 on: February 13, 2002, 11:17:29 PM »
If it helps you any, have a look at some tips for getting lots_of_logfiles on 4.x.x

http://www.blokland.co.uk/Kees/docs/e-smith/debug-modem-howto.htm

But, I think you are making your life very difficult for no reason.
Is there any reason why you do not want to go to 5.x.x. ?
(If you mentioned it before, sorry, I missed it. My ISP seems to have good and bad days, on the bad days they send every email 5 times to make up for the good days, when they forget to forward any..)

kees

NeL

Re: isdn
« Reply #18 on: February 15, 2002, 02:29:40 PM »
i would like to have a technical answer ;o) charlie brady ;o)
Could you explain to me what difference there is ? ( like: the kernel of e-smith 4.1.2 can't use this fonction ..)
NeL

Filippo Carletti

Re: isdn
« Reply #19 on: February 15, 2002, 02:50:38 PM »
ISDN cards work on 4.1.2, 5 and 5.1.2.
On 4 and 5 with async ppp and ttyI, on 5.1.2 with Sync PPP and /dev/ippp.
I upgraded my server all the way from 4 to 5.1.2 and it alsways worked.
But, hisax coming from version 4 (kernel 2.2.16) was a bit more unreliable.

NeL

Re: isdn
« Reply #20 on: February 21, 2002, 12:12:08 PM »
Hi,
I'm still with this problem ;o)
Now i can use ftp, ping ...but if i use lynx it break all and during a few time my network is broken... i post log file if you see somethink wich can help me..please
( sorry for this long post but it's the only one solution that i found ;o)
I don't undertand where is the problem:

/var/log/diald/accounting.log:

Wed Feb 20 09:51:33 2002 EST: Calling site 192.168.254.254.
Wed Feb 20 09:51:36 2002 EST: Connected to site 192.168.254.254.
Wed Feb 20 09:55:13 2002 EST: Disconnected. Call duration 217 seconds.
      IP transmitted 5392 bytes and received 4110 bytes.
Wed Feb 20 09:55:15 2002 EST: Calling site 192.168.254.254.
Wed Feb 20 09:55:19 2002 EST: Connected to site 192.168.254.254.
Wed Feb 20 09:55:47 2002 EST: Disconnected. Call duration 28 seconds.
      IP transmitted 1057 bytes and received 583 bytes.
Wed Feb 20 09:55:58 2002 EST: Calling site 192.168.254.254.
Wed Feb 20 09:56:02 2002 EST: Connected to site 192.168.254.254.


/var/log/message :

Feb 20 09:50:49 e-smith diald[684]: Calling site 192.168.254.254
Feb 20 09:50:51 e-smith chat[2001]: abort on (BUSY)
Feb 20 09:50:51 e-smith chat[2001]: abort on (ERROR)
Feb 20 09:50:51 e-smith chat[2001]: abort on (NO CARRIER)
Feb 20 09:50:51 e-smith chat[2001]: abort on (NO DIALTONE)
Feb 20 09:50:51 e-smith chat[2001]: abort on (Invalid Login)
Feb 20 09:50:51 e-smith chat[2001]: abort on (Login incorrect)
Feb 20 09:50:51 e-smith chat[2001]: report (CONNECT)
Feb 20 09:50:51 e-smith chat[2001]: send (ATZ^M)
Feb 20 09:50:51 e-smith chat[2001]: expect (OK)
Feb 20 09:50:51 e-smith chat[2001]: ATZ^M^M
Feb 20 09:50:51 e-smith chat[2001]: OK
Feb 20 09:50:51 e-smith chat[2001]:  -- got it
Feb 20 09:50:51 e-smith chat[2001]: send (ATL0M0^M)
Feb 20 09:50:51 e-smith chat[2001]: expect (OK)
Feb 20 09:50:51 e-smith chat[2001]: ^M
Feb 20 09:50:51 e-smith chat[2001]: ATL0M0^M^M
Feb 20 09:50:51 e-smith chat[2001]: OK
Feb 20 09:50:51 e-smith chat[2001]:  -- got it
Feb 20 09:50:51 e-smith chat[2001]: send (ATS14=3&E0223350536&B512^M)
Feb 20 09:50:51 e-smith chat[2001]: expect (OK)
Feb 20 09:50:51 e-smith chat[2001]: ^M
Feb 20 09:50:51 e-smith chat[2001]: ATS14=3&E0223350536&B512^M^M
Feb 20 09:50:51 e-smith chat[2001]: OK
Feb 20 09:50:51 e-smith chat[2001]:  -- got it
Feb 20 09:50:51 e-smith chat[2001]: send (ATDT0860922000^M)
Feb 20 09:50:52 e-smith chat[2001]: expect (CONNECT)
Feb 20 09:50:52 e-smith chat[2001]: ^M
Feb 20 09:50:53 e-smith chat[2001]: ATDT0860922000^M^M
Feb 20 09:50:53 e-smith chat[2001]: CONNECT
Feb 20 09:50:53 e-smith chat[2001]:  -- got it
Feb 20 09:50:53 e-smith diald[684]: connector: chat:  Feb 20 09:50:53 CONNECT 64000/HDLC
Feb 20 09:50:53 e-smith diald[684]: Connected to site 192.168.254.254
Feb 20 09:50:53 e-smith diald[684]: Running pppd (pid = 2002).
Feb 20 09:50:53 e-smith diald[2002]: Running pppd: /usr/sbin/pppd -defaultroute -detach modem crtscts mtu 1500 mru 1524 name eric.lenezet sync noauth noipdefault ipparam diald
Feb 20 09:50:53 e-smith pppd[2002]: pppd 2.4.0 started by root, uid 0
Feb 20 09:50:53 e-smith pppd[2002]: Using interface ppp0
Feb 20 09:50:53 e-smith pppd[2002]: Connect: ppp0 <--> /dev/ttyI0
Feb 20 09:51:21 e-smith pppd[2002]: Hangup (SIGHUP)
Feb 20 09:51:21 e-smith pppd[2002]: Modem hangup
Feb 20 09:51:21 e-smith pppd[2002]: Connection terminated.
Feb 20 09:51:21 e-smith pppd[2002]: Exit.
Feb 20 09:51:21 e-smith diald[684]: start sl0: SIOCSIFMTU: Invalid argument
Feb 20 09:51:22 e-smith diald[684]: stop ppp0: RTNETLINK answers: No such process
Feb 20 09:51:22 e-smith diald[684]: stop ppp0: SIOCSIFFLAGS: No such device or address
Feb 20 09:51:22 e-smith diald[684]: Disconnected. Call duration 29 seconds.
Feb 20 09:51:22 e-smith diald[684]: IP transmitted 0 bytes and received 0 bytes.
Feb 20 09:51:23 e-smith diald[684]: Delaying 10 seconds before clear to dial.
Feb 20 09:51:33 e-smith diald[684]: Calling site 192.168.254.254
Feb 20 09:51:34 e-smith chat[2008]: abort on (BUSY)
Feb 20 09:51:34 e-smith chat[2008]: abort on (ERROR)
Feb 20 09:51:34 e-smith chat[2008]: abort on (NO CARRIER)
Feb 20 09:51:34 e-smith chat[2008]: abort on (NO DIALTONE)
Feb 20 09:51:34 e-smith chat[2008]: abort on (Invalid Login)
Feb 20 09:51:34 e-smith chat[2008]: abort on (Login incorrect)
Feb 20 09:51:34 e-smith chat[2008]: report (CONNECT)
Feb 20 09:51:34 e-smith chat[2008]: send (ATZ^M)
Feb 20 09:51:34 e-smith chat[2008]: expect (OK)
Feb 20 09:51:34 e-smith chat[2008]: ATZ^M^M
Feb 20 09:51:34 e-smith chat[2008]: OK
Feb 20 09:51:34 e-smith chat[2008]:  -- got it
Feb 20 09:51:34 e-smith chat[2008]: send (ATL0M0^M)
Feb 20 09:51:34 e-smith chat[2008]: expect (OK)
Feb 20 09:51:34 e-smith chat[2008]: ^M
Feb 20 09:51:34 e-smith chat[2008]: ATL0M0^M^M
Feb 20 09:51:34 e-smith chat[2008]: OK
Feb 20 09:51:34 e-smith chat[2008]:  -- got it
Feb 20 09:51:34 e-smith chat[2008]: send (ATS14=3&E0223350536&B512^M)
Feb 20 09:51:34 e-smith chat[2008]: expect (OK)
Feb 20 09:51:34 e-smith chat[2008]: ^M
Feb 20 09:51:34 e-smith chat[2008]: ATS14=3&E0223350536&B512^M^M
Feb 20 09:51:34 e-smith chat[2008]: OK
Feb 20 09:51:34 e-smith chat[2008]:  -- got it
Feb 20 09:51:34 e-smith chat[2008]: send (ATDT0860922000^M)
Feb 20 09:51:35 e-smith chat[2008]: expect (CONNECT)
Feb 20 09:51:35 e-smith chat[2008]: ^M
Feb 20 09:51:36 e-smith chat[2008]: ATDT0860922000^M^M
Feb 20 09:51:36 e-smith chat[2008]: CONNECT
Feb 20 09:51:36 e-smith chat[2008]:  -- got it
Feb 20 09:51:36 e-smith diald[684]: connector: chat:  Feb 20 09:51:36 CONNECT 64000/HDLC
Feb 20 09:51:36 e-smith diald[684]: Connected to site 192.168.254.254
Feb 20 09:51:36 e-smith diald[684]: Running pppd (pid = 2010).
Feb 20 09:51:36 e-smith diald[2010]: Running pppd: /usr/sbin/pppd -defaultroute -detach modem crtscts mtu 1500 mru 1524 name eric.lenezet sync noauth noipdefault ipparam diald
Feb 20 09:51:36 e-smith pppd[2010]: pppd 2.4.0 started by root, uid 0
Feb 20 09:51:36 e-smith pppd[2010]: Using interface ppp0
Feb 20 09:51:36 e-smith pppd[2010]: Connect: ppp0 <--> /dev/ttyI0
Feb 20 09:51:50 e-smith pppd[2010]: local  IP address 62.147.98.188
Feb 20 09:51:50 e-smith pppd[2010]: remote IP address 192.168.254.254
Feb 20 09:51:50 e-smith e-smith[2029]: Processing event: ip-change 62.147.98.188
Feb 20 09:51:50 e-smith e-smith[2029]: Running event handler: /etc/e-smith/events/ip-change/S15set-external-ip
Feb 20 09:51:51 e-smith diald[684]: New addresses: local 62.147.98.188, remote 192.168.254.254, broadcast 0.0.0.0
Feb 20 09:51:51 e-smith diald[684]: start ppp0: SIOCSIFMTU: Invalid argument
Feb 20 09:51:51 e-smith /etc/e-smith/events/ip-change/S15set-external-ip[2031]: /home/e-smith/configuration: OLD ExternalIP=62.147.96.149
Feb 20 09:51:51 e-smith /etc/e-smith/events/ip-change/S15set-external-ip[2031]: /home/e-smith/configuration: NEW ExternalIP=62.147.98.188
Feb 20 09:51:51 e-smith /etc/e-smith/events/ip-change/S15set-external-ip[2031]: /home/e-smith/configuration: OLD UnsavedChanges=yes
Feb 20 09:51:51 e-smith /etc/e-smith/events/ip-change/S15set-external-ip[2031]: /home/e-smith/configuration: NEW UnsavedChanges=no
Feb 20 09:51:51 e-smith e-smith[2029]: Running event handler: /etc/e-smith/events/ip-change/S16restart-masq
Feb 20 09:51:52 e-smith e-smith[2029]: Running event handler: /etc/e-smith/events/ip-change/S47proftpd-conf
Feb 20 09:51:54 e-smith e-smith-bg:
Feb 20 09:51:54 e-smith e-smith-bg: Shutting down IP masquerade and firewall rules:^I^IDone!
Feb 20 09:51:54 e-smith e-smith-bg:
Feb 20 09:51:54 e-smith e-smith[2029]: Running event handler: /etc/e-smith/events/ip-change/S50conf-security
Feb 20 09:51:57 e-smith e-smith[2029]: Running event handler: /etc/e-smith/events/ip-change/S55conf-httpd
Feb 20 09:52:01 e-smith e-smith[2029]: Running event handler: /etc/e-smith/events/ip-change/S75restart-httpd-full
Feb 20 09:52:02 e-smith e-smith[2029]: Running event handler: /etc/e-smith/events/ip-change/S80pptpd-conf
Feb 20 09:52:03 e-smith e-smith[2029]: Running event handler: /etc/e-smith/events/ip-change/S85update-dns
Feb 20 09:52:04 e-smith httpd-e-smith: Shutting down http:  succeeded
Feb 20 09:52:04 e-smith e-smith-bg: Shutting down http:  [   OK   ]^M
Feb 20 09:52:04 e-smith e-smith-bg: Enabling IP masquerading: done
Feb 20 09:52:05 e-smith e-smith[2029]: Running event handler: /etc/e-smith/events/ip-change/S90pptpd-restart
Feb 20 09:52:07 e-smith e-smith[2029]: Running event handler: /etc/e-smith/events/ip-change/S90restart-ntpd
Feb 20 09:52:08 e-smith e-smith[2241]: Processing event: ip-up ppp0 /dev/ttyI0 115200 62.147.98.188 192.168.254.254 diald
Feb 20 09:52:08 e-smith e-smith[2241]: Running event handler: /etc/e-smith/events/ip-up/S20email-ipup
Feb 20 09:52:10 e-smith httpd-e-smith: Starting httpd:  succeeded
Feb 20 09:52:10 e-smith e-smith-bg: Starting httpd:  [   OK   ]^M
Feb 20 09:52:10 e-smith ntpd: ntpd shutdown failed
Feb 20 09:52:10 e-smith e-smith-bg: Shutting down ntpd: [ FAILED ]^M
Feb 20 09:52:21 e-smith identd[2272]: Successful lookup: 1026 , 21 : root.root
Feb 20 09:52:56 e-smith identd[2274]: Successful lookup: 1027 , 21 : root.root
Feb 20 09:53:29 e-smith identd[2276]: Successful lookup: 1028 , 21 : root.root
Feb 20 09:54:42 e-smith PAM_unix[1995]: (login) session opened for user root by LOGIN(uid=0)
Feb 20 09:54:42 e-smith  -- root[1995]: ROOT LOGIN ON tty2
Feb 20 09:55:07 e-smith pppd[2010]: No response to 2 echo-requests
Feb 20 09:55:07 e-smith pppd[2010]: Serial link appears to be disconnected.
Feb 20 09:55:13 e-smith pppd[2010]: Connection terminated.
Feb 20 09:55:13 e-smith pppd[2010]: Connect time 3.6 minutes.
Feb 20 09:55:13 e-smith pppd[2010]: Sent 650822 bytes, received 4840 bytes.
Feb 20 09:55:13 e-smith pppd[2010]: Exit.
Feb 20 09:55:13 e-smith diald[684]: Link died on remote end.
Feb 20 09:55:13 e-smith diald[684]: start sl0: SIOCSIFMTU: Invalid argument
Feb 20 09:55:13 e-smith diald[684]: stop ppp0: RTNETLINK answers: No such process
Feb 20 09:55:13 e-smith last message repeated 2 times
Feb 20 09:55:13 e-smith diald[684]: stop ppp0: SIOCSIFFLAGS: No such device or address
Feb 20 09:55:13 e-smith diald[684]: Disconnected. Call duration 217 seconds.
Feb 20 09:55:13 e-smith diald[684]: IP transmitted 5392 bytes and received 4110 bytes.
Feb 20 09:55:15 e-smith diald[684]: Calling site 192.168.254.254
Feb 20 09:55:16 e-smith chat[2318]: abort on (BUSY)
Feb 20 09:55:16 e-smith chat[2318]: abort on (ERROR)
Feb 20 09:55:16 e-smith chat[2318]: abort on (NO CARRIER)
Feb 20 09:55:16 e-smith chat[2318]: abort on (NO DIALTONE)
Feb 20 09:55:16 e-smith chat[2318]: abort on (Invalid Login)
Feb 20 09:55:16 e-smith chat[2318]: abort on (Login incorrect)
Feb 20 09:55:16 e-smith chat[2318]: report (CONNECT)
Feb 20 09:55:16 e-smith chat[2318]: send (ATZ^M)
Feb 20 09:55:16 e-smith chat[2318]: expect (OK)
Feb 20 09:55:16 e-smith chat[2318]: ATZ^M^M
Feb 20 09:55:16 e-smith chat[2318]: OK
Feb 20 09:55:16 e-smith chat[2318]:  -- got it
Feb 20 09:55:16 e-smith chat[2318]: send (ATL0M0^M)
Feb 20 09:55:16 e-smith chat[2318]: expect (OK)
Feb 20 09:55:16 e-smith chat[2318]: ^M
Feb 20 09:55:16 e-smith chat[2318]: ATL0M0^M^M
Feb 20 09:55:16 e-smith chat[2318]: OK
Feb 20 09:55:16 e-smith chat[2318]:  -- got it
Feb 20 09:55:16 e-smith chat[2318]: send (ATS14=3&E0223350536&B512^M)
Feb 20 09:55:17 e-smith chat[2318]: expect (OK)
Feb 20 09:55:17 e-smith chat[2318]: ^M
Feb 20 09:55:17 e-smith chat[2318]: ATS14=3&E0223350536&B512^M^M
Feb 20 09:55:17 e-smith chat[2318]: OK
Feb 20 09:55:17 e-smith chat[2318]:  -- got it
Feb 20 09:55:17 e-smith chat[2318]: send (ATDT0860922000^M)
Feb 20 09:55:17 e-smith chat[2318]: expect (CONNECT)
Feb 20 09:55:17 e-smith chat[2318]: ^M
Feb 20 09:55:19 e-smith chat[2318]: ATDT0860922000^M^M
Feb 20 09:55:19 e-smith chat[2318]: CONNECT
Feb 20 09:55:19 e-smith chat[2318]:  -- got it
Feb 20 09:55:19 e-smith diald[684]: connector: chat:  Feb 20 09:55:19 CONNECT 64000/HDLC
Feb 20 09:55:19 e-smith diald[684]: Connected to site 192.168.254.254
Feb 20 09:55:19 e-smith diald[684]: Running pppd (pid = 2319).
Feb 20 09:55:19 e-smith diald[2319]: Running pppd: /usr/sbin/pppd -defaultroute -detach modem crtscts mtu 1500 mru 1524 name eric.lenezet sync noauth noipdefault ipparam diald
Feb 20 09:55:19 e-smith pppd[2319]: pppd 2.4.0 started by root, uid 0
Feb 20 09:55:19 e-smith pppd[2319]: Using interface ppp0
Feb 20 09:55:19 e-smith pppd[2319]: Connect: ppp0 <--> /dev/ttyI0
Feb 20 09:55:31 e-smith PAM_unix[1296]: (login) session closed for user root
Feb 20 09:55:33 e-smith PAM_unix[1995]: (login) session closed for user root
Feb 20 09:55:39 e-smith PAM_unix[2325]: (login) session opened for user root by LOGIN(uid=0)
Feb 20 09:55:39 e-smith  -- root[2325]: ROOT LOGIN ON tty2
Feb 20 09:55:47 e-smith pppd[2319]: Hangup (SIGHUP)
Feb 20 09:55:47 e-smith pppd[2319]: Modem hangup
Feb 20 09:55:47 e-smith pppd[2319]: Connection terminated.
Feb 20 09:55:47 e-smith pppd[2319]: Exit.
Feb 20 09:55:47 e-smith diald[684]: start sl0: SIOCSIFMTU: Invalid argument
Feb 20 09:55:47 e-smith diald[684]: stop ppp0: RTNETLINK answers: No such process
Feb 20 09:55:47 e-smith diald[684]: stop ppp0: SIOCSIFFLAGS: No such device or address
Feb 20 09:55:47 e-smith diald[684]: Disconnected. Call duration 28 seconds.
Feb 20 09:55:47 e-smith diald[684]: IP transmitted 1057 bytes and received 583 bytes.
Feb 20 09:55:48 e-smith diald[684]: Delaying 10 seconds before clear to dial.


Thanks.
NeL

Filippo Carletti

Re: isdn
« Reply #21 on: February 21, 2002, 02:18:20 PM »
I'd say line problems, but it's rare on isdn.
Your logs show one successful connection with some data exchanged.
Then line goes down.

You could try debugging the ISDN bus.
Put an id in modules.conf
options hisax id=hisax1 type=....
then use these commands:

hisaxctrl 1 0x33ff
hisaxctrl 11 0xf4f
cat /dev/isdnctrl0 > /tmp/ilog

where id is the id you put in modules.conf.

You also have strange messages about mtu (SIOCSIFMTU).
Could you restart from a clear install ?

John Crisp

Re: isdn (and subsequent probs)
« Reply #22 on: March 12, 2002, 08:22:56 PM »
Hi,

Just reading through this tread on ISDN as  I have exactly the same problems it appears, but with an external TA. Certainly the logs seem to be the same.

I have done some reading and have tried different IP's with similar results.

I thought it might be to do with the protocols - X75/V120/HDLC etc. I have tried to add 'sync' to the pppd options, all with the same result.

I then run a Freeso 0.2.7 (I think, from memory) box with the same TA and voila, at least with the X75 it works like a dream, and the pppd options are the same as esmith. However, it's not so keen with HDLC - I haven't tried hacking the 'sync' into the options.

However, I have another e-smith box, with a different external TA and that connects with HDLC to another provider without problems.

Any ISDN geniuses out there ?

B. Rgds

John Crisp

Filippo Carletti

Re: isdn (and subsequent probs)
« Reply #23 on: March 12, 2002, 09:58:39 PM »
With an external TA you can't use the new sync ppp feature of SME 5.1.2.
It's simply a config problem on TA.
What TA ?
For some zyxel S87.2=1 to use pap auth.

John Crisp

Re: isdn (and subsequent probs)
« Reply #24 on: March 13, 2002, 04:17:54 AM »
Thanks for replying. I will check and advise - I'm not on site at the minute and can't remember.

I am actually using 5.0 Udpate 4 if that's any use.

B. Rdds
John

John Crisp

Re: isdn (and subsequent probs)
« Reply #25 on: March 13, 2002, 05:24:39 PM »
It's an ELSA Microlink ISDN Internet external TA.

Any thoughts ?

John

Filippo Carletti

Re: isdn (and subsequent probs)
« Reply #26 on: March 13, 2002, 06:01:17 PM »
Elsa has very good reputation.
Could you discover the access server brand on the other side of the connection ?
I'd use HDLC and not X.75.
Have you tried calling a different ISP ?

Toby Seed

Re: isdn (and subsequent probs)
« Reply #27 on: March 14, 2002, 05:00:08 AM »
Hi just been scanning the posts and I read this thread noticing that John Crisp is using a ELSA Microlink ISDN Internet external TA, I have also had the same problem,  In my search for a solution I came to the conclusion that with my limited linux experience I could not solve it with this TA, the only reference to this TA operating under a linux dist. is from suse , now suse uses wvdial to dial and do all the config. This is where my understanding becomes even more blurry, the problem arises where an asyncmap "table/setting/variable" is passed to pppd this particular TA will not accept it, some of the posts I've read on the net suggest using a default/non-specific asyncmap in an /etc/ppp/ioptions I'm not sure where it should go in the e-smith dist. though. (diald.conf ?)


asyncmap 0
default asyncmap


I tried all sorts of init strings and found again the suse site had an apropriate one (AT&F$IBP=HDLCP) but still although it dialed I got a hangup (sighup) in my /var/log/messages -- (asyncmap problem ?)

In the documentation about the revisions of wvdial I did find this paragraph:
"If a modem does not respond on the Init1 String, ATQ0 is sent and then Init1 again. This helped with the ELSA Microlink Internet."

I've not treid : ATQ0"myinitstring" as my new init string though.

As I have said I am a linux newbie really, and this is just a catalog of my attempts at a solution, I realize that what I've stated maybe incorrect and if so please tell me as I'm learning. I hope this information is of use to you all, also the experts on these phorums will be able to tell you where the asyncmap settings above should really go.

If anybody has this TA I would be happy to share my findings, urls, logs attempts etc.

Here are a few URLs which have been of use to me:

---http://hbar.physik.uni-oldenburg.de/jens/linuxtricks/msg00013.html---

---http://translate.google.com/translate?hl=en&sl=de&u=http://lists.suse.com/archive/suse-linux/2001 Oct/1796.html&prev=/search%3Fq%3D%2522elsa%2Bmicrolink%2Bisdn%2B%2522%2Bdefault-asyncmap%26hl%3Den%26sa%3DG---

---http://hbar.physik.uni-oldenburg.de/jens/linuxtricks/msg00013.html----

Filippo Carletti

Re: isdn (and subsequent probs)
« Reply #28 on: March 14, 2002, 08:27:07 PM »
An external TA shouldn't pose any problem.
Could you add "debug" to /etc/ppp/options and send some logs (/var/log/messages) ?

John Crisp

Re: isdn (and subsequent probs)
« Reply #29 on: March 18, 2002, 12:16:17 AM »
Hi all. Sorry - I've had a few days out to chill my brain ;-) It was getting to me !

This TA happily connects through my current provide with X75. Where it seems to fall down is with HDLCP type connections.

I went and had a look at another e-smith server I run that has a Dynalink TA and the provider it connects to is seems to use HDLCP-PPP from the connect strings logged.

That made me think a bit - it's the same provider that I will be using shortly, so I've got to get this one to go !

OK, reading the full AT command for this TA I notice that the command choice for protocol, AT$IBP shows a default fallthrough of X75 - V120 - HDLCP.

However it does have a setting of HDLCP-PPP

What's the difference with the PPP part ? Is this the magic ingredient ?

At the moment I am running the TA with Freesco - it's a doddle to setup. But the logging is minimal. I will try and have a play using the e-smith box or another linux box during the week and report on success.

Another intriguing point is that with a very basic driver install in windoze (as far as I could see, only an ini or inf file I think) the thing works fine with whoever you like. May have a look in the file and see what AT strings they use in there. I am convinced it's a hardware configuration issue rather than software - after all, I am using happily at the moment, albeit with an X75 connection.

Any thoughts, or am I taking B*ll*cks ? ?

B. Rgds

John