Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: Gryf on June 17, 2001, 01:15:53 PM

Title: Getting diald to work
Post by: Gryf on June 17, 2001, 01:15:53 PM
Hi!

I got some problems getting diald to work.

Here is a bit from /var/log/messenges:

diald: calling site 0.0.0.0
chat: abort on (busy)
chat: abort on (error)
chat: abort on (no carrier)
chat: abort on (no dialtone)
chat: abort on (invalid login)
chat: abort on (login incorrect)
chat: report (connect)
chat: send (atz^m)
chat: expect (ok)
chat: atz^m^m
chat: ok
chat: -- got it
chat: send (atm0l0^m)
chat: expect (ok)
chat: ^m
chat: atm0l0^m^m
chat: error
chat: -- failed
chat: failed (error)
diald: connect script failed

i've made to manually type it in so i left time and some on out.
The modem i have to get working is a Diva T/A ISDN Modem connected at com1 on the e-smith server.

Hope you can help.

/gryf
Title: Re: Getting diald to work
Post by: Gert-Jan Verheij on June 17, 2001, 08:40:08 PM
I have the same problem I think,

I use e-smith 4.1.2. met the isdn4es scritp from Klaus J. Mueller (http://internet-sicherheit.net/isdn4es-howto.html), with a pci isdncard type 35 (HFC).

I have two accounts by two different providers.  All is working by the first provider. This provider gives the nameservers dynamish I know (when I use windows..)

The second provider (my own, xs4all) is NOT working and gives not dynamisch the nameservers.

In messages i see the follow:

Ut

Jun 17 13:59:29 e-smith chat[1398]: expect (OK)
Jun 17 13:59:29 e-smith chat[1398]: ATZ^M^M
Jun 17 13:59:29 e-smith chat[1398]: OK
Jun 17 13:59:29 e-smith chat[1398]:  -- got it
Jun 17 13:59:29 e-smith chat[1398]: send (AT&E503133669S14=3^M)
Jun 17 13:59:29 e-smith chat[1398]: expect (OK)
Jun 17 13:59:29 e-smith chat[1398]: ^M
Jun 17 13:59:29 e-smith chat[1398]: AT&E503133669S14=3^M^M
Jun 17 13:59:29 e-smith chat[1398]: OK
Jun 17 13:59:29 e-smith chat[1398]:  -- got it
Jun 17 13:59:29 e-smith chat[1398]: send (ATDT8500080^M)
Jun 17 13:59:30 e-smith chat[1398]: expect (CONNECT)
Jun 17 13:59:30 e-smith chat[1398]: ^M
Jun 17 13:59:32 e-smith chat[1398]: ATDT8500080^M^M
Jun 17 13:59:32 e-smith chat[1398]: CONNECT
Jun 17 13:59:32 e-smith chat[1398]:  -- got it
Jun 17 13:59:32 e-smith diald[744]: connector: chat:  Jun 17 13:59:32 CONNECT 64000/HDLC
Jun 17 13:59:32 e-smith diald[744]: Connected to site 0.0.0.0
Jun 17 13:59:32 e-smith diald[744]: Running pppd (pid = 1399).
Jun 17 13:59:32 e-smith diald[1399]: Running pppd: /usr/sbin/pppd -defaultroute -detach modem crtscts mtu 1500 mru 1500 name m7643703 noauth noipdefault ipparam diald
Jun 17 13:59:32 e-smith kernel: registered device ppp0
Jun 17 13:59:32 e-smith pppd[1399]: pppd 2.4.0 started by root, uid 0
Jun 17 13:59:32 e-smith pppd[1399]: Using interface ppp0
Jun 17 13:59:32 e-smith pppd[1399]: Connect: ppp0 <--> /dev/ttyI0
Jun 17 13:59:34 e-smith kernel: PPP BSD Compression module registered
Jun 17 13:59:34 e-smith kernel: PPP Deflate Compression module registered
Jun 17 13:59:34 e-smith pppd[1399]: local  IP address 130.89.190.122
Jun 17 13:59:34 e-smith pppd[1399]: remote IP address 130.89.239.2
Jun 17 13:59:35 e-smith diald[744]: New addresses: local 130.89.190.122, remote 130.89.239.2, broadcast 0.0.0.0
Jun 17 13:59:35 e-smith diald[744]: start ppp0: SIOCSIFMTU: Invalid argument
Jun 17 13:59:35 e-smith e-smith[1439]: Processing event: ip-change 130.89.190.122
Jun 17 13:59:35 e-smith e-smith[1439]: Running event handler: /etc/e-smith/events/ip-change/S15set-external-ip
Jun 17 13:59:36 e-smith atalkd[1358]: zip_getnetinfo for eth0
Jun 17 13:59:37 e-smith /etc/e-smith/events/ip-change/S15set-external-ip[1441]: /home/e-smith/configuration: OLD ExternalIP=194.109.241.228
Jun 17 13:59:37 e-smith /etc/e-smith/events/ip-change/S15set-external-ip[1441]: /home/e-smith/configuration: NEW ExternalIP=130.89.190.122
Jun 17 13:59:37 e-smith /etc/e-smith/events/ip-change/S15set-external-ip[1441]: /home/e-smith/configuration: OLD UnsavedChanges=yes
Jun 17 13:59:37 e-smith /etc/e-smith/events/ip-change/S15set-external-ip[1441]: /home/e-smith/configuration: NEW UnsavedChanges=no
Jun 17 13:59:37 e-smith e-smith[1439]: Running event handler: /etc/e-smith/events/ip-change/S16restart-masq
Jun 17 13:59:37 e-smith e-smith[1439]: Running event handler: /etc/e-smith/events/ip-change/S47proftpd-conf
Jun 17 13:59:38 e-smith e-smith-bg:
Jun 17 13:59:38 e-smith e-smith-bg: Shutting down IP masquerade and firewall rules:^I^IDone!
Jun 17 13:59:38 e-smith e-smith-bg:
Jun 17 13:59:39 e-smith e-smith[1439]: Running event handler: /etc/e-smith/events/ip-change/S50conf-security
Jun 17 13:59:41 e-smith e-smith[1439]: Running event handler: /etc/e-smith/events/ip-change/S55conf-httpd
Jun 17 13:59:41 e-smith e-smith-bg: Enabling IP masquerading: done
Jun 17 13:59:43 e-smith named[1393]: sysquery: findns error (NXDOMAIN) on ns.xs4all.nl?
Jun 17 13:59:43 e-smith named[1393]: sysquery: findns error (NXDOMAIN) on ns2.xs4all.nl?
Jun 17 13:59:43 e-smith e-smith[1439]: Running event handler: /etc/e-smith/events/ip-change/S75restart-httpd-full
Jun 17 13:59:44 e-smith e-smith[1439]: Running event handler: /etc/e-smith/events/ip-change/S80pptpd-conf
Jun 17 13:59:45 e-smith httpd-e-smith: Shutting down http:  succeeded
Jun 17 13:59:45 e-smith e-smith-bg: Shutting down http:  [   OK   ]^M
Jun 17 13:59:46 e-smith e-smith[1439]: Running event handler: /etc/e-smith/events/ip-change/S85update-dns
Jun 17 13:59:46 e-smith atalkd[1358]: zip_getnetinfo for eth0
Jun 17 13:59:47 e-smith e-smith[1439]: Running event handler: /etc/e-smith/events/ip-change/S90pptpd-restart
Jun 17 13:59:47 e-smith e-smith[1439]: Running event handler: /etc/e-smith/events/ip-change/S90restart-ntpd
Jun 17 13:59:49 e-smith e-smith[1658]: Processing event: ip-up ppp0 /dev/ttyI0 115200 130.89.190.122 130.89.239.2 diald
Jun 17 13:59:49 e-smith e-smith[1658]: Running event handler: /etc/e-smith/events/ip-up/S20email-ipup
Jun 17 13:59:49 e-smith httpd-e-smith: Starting httpd:  succeeded
Jun 17 13:59:49 e-smith e-smith-bg: Starting httpd:  [   OK   ]^M
Jun 17 13:59:50 e-smith e-smith[1658]: fetchmail: couldn't find canonical DNS name of pop.xs4all.nl
Jun 17 13:59:50 e-smith named[1393]: sysquery: findns error (NXDOMAIN) on ns.xs4all.nl?

Xs4all
Jun 17 14:53:21 e-smith chat[2040]: ATZ^M^M
Jun 17 14:53:21 e-smith chat[2040]: OK
Jun 17 14:53:21 e-smith chat[2040]:  -- got it
Jun 17 14:53:21 e-smith chat[2040]: send (AT&E503133669S14=3^M)
Jun 17 14:53:21 e-smith chat[2040]: expect (OK)
Jun 17 14:53:21 e-smith chat[2040]: ^M
Jun 17 14:53:21 e-smith chat[2040]: AT&E503133669S14=3^M^M
Jun 17 14:53:21 e-smith chat[2040]: OK
Jun 17 14:53:21 e-smith chat[2040]:  -- got it
Jun 17 14:53:21 e-smith chat[2040]: send (ATDT0592331278^M)
Jun 17 14:53:21 e-smith chat[2040]: expect (CONNECT)
Jun 17 14:53:21 e-smith chat[2040]: ^M
Jun 17 14:53:24 e-smith chat[2040]: ATDT0592331278^M^M
Jun 17 14:53:24 e-smith chat[2040]: CONNECT
Jun 17 14:53:24 e-smith chat[2040]:  -- got it
Jun 17 14:53:24 e-smith diald[1782]: connector: chat:  Jun 17 14:53:24 CONNECT 64000/HDLC
Jun 17 14:53:24 e-smith diald[1782]: Connected to site 0.0.0.0
Jun 17 14:53:24 e-smith diald[1782]: Running pppd (pid = 2041).
Jun 17 14:53:24 e-smith diald[2041]: Running pppd: /usr/sbin/pppd -defaultroute -detach modem crtscts mtu 1500 mru 1500 name gverheij noauth noipdefault ipparam diald
Jun 17 14:53:24 e-smith pppd[2041]: pppd 2.4.0 started by root, uid 0
Jun 17 14:53:24 e-smith pppd[2041]: Using interface ppp0
Jun 17 14:53:24 e-smith pppd[2041]: Connect: ppp0 <--> /dev/ttyI0
Jun 17 14:53:24 e-smith pppd[2041]: sent [LCP ConfReq id=0x1 ]
Jun 17 14:53:52 e-smith last message repeated 9 times
Jun 17 14:53:55 e-smith pppd[2041]: LCP: timeout sending Config-Requests
Jun 17 14:53:55 e-smith pppd[2041]: Connection terminated.
Jun 17 14:53:55 e-smith pppd[2041]: Exit.
Jun 17 14:53:55 e-smith diald[1782]: start sl0: SIOCSIFMTU: Invalid argument
Jun 17 14:53:55 e-smith diald[1782]: stop ppp0: RTNETLINK answers: No such process
Jun 17 14:53:55 e-smith kernel: ppp: ppp0 not active
Jun 17 14:53:55 e-smith diald[1782]: stop ppp0: SIOCSIFFLAGS: No such device or address
Jun 17 14:53:55 e-smith diald[1782]: Disconnected. Call duration 31 seconds.
Jun 17 14:53:55 e-smith diald[1782]: IP transmitted 2955 bytes and received 0 bytes.
Jun 17 14:53:55 e-smith kernel: isdn: HiSax,ch0 cause: E0010
Jun 17 14:53:56 e-smith diald[1782]: Delaying 10 seconds before clear to dial.
Title: Re: Getting diald to work
Post by: Gryf on June 18, 2001, 12:53:59 PM
Okay .. i got it to work :)

is just removed:

'OK' 'ATM0L0'

from my chat script... and now it works! Dont know what it does but ...

/gryf
Title: Re: Getting diald to work
Post by: guestFF on June 27, 2001, 02:42:08 PM
Any luck yet?
Title: Re: Getting diald to work
Post by: guestFF on June 27, 2001, 06:16:01 PM
Hi all,

Here's my /var/log/messages

It seems that the ppp deamon hangsup for no reason at all??

es4.1.2 / Passive ISDN HOW-TO applied / ppptd update for 4.1.2 installed

Any suggestions?

Jun 27 09:07:48 vandenbrand diald[743]: Delaying 10 seconds before clear to dial.
Jun 27 09:07:58 vandenbrand diald[743]: Calling site 0.0.0.0
Jun 27 09:07:59 vandenbrand chat[1538]: abort on (BUSY)
Jun 27 09:07:59 vandenbrand chat[1538]: abort on (ERROR)
Jun 27 09:07:59 vandenbrand chat[1538]: abort on (NO CARRIER)
Jun 27 09:07:59 vandenbrand chat[1538]: abort on (NO DIALTONE)
Jun 27 09:07:59 vandenbrand chat[1538]: abort on (Invalid Login)
Jun 27 09:07:59 vandenbrand chat[1538]: abort on (Login incorrect)
Jun 27 09:07:59 vandenbrand chat[1538]: report (CONNECT)
Jun 27 09:07:59 vandenbrand chat[1538]: send (ATZ^M)
Jun 27 09:07:59 vandenbrand chat[1538]: expect (OK)
Jun 27 09:07:59 vandenbrand chat[1538]: ATZ^M^M
Jun 27 09:07:59 vandenbrand chat[1538]: OK
Jun 27 09:07:59 vandenbrand chat[1538]:  -- got it
Jun 27 09:07:59 vandenbrand chat[1538]: send (AT&E123456S14=3^M)
Jun 27 09:07:59 vandenbrand chat[1538]: expect (OK)
Jun 27 09:07:59 vandenbrand chat[1538]: ^M
Jun 27 09:07:59 vandenbrand chat[1538]: AT&E123456S14=3^M^M
Jun 27 09:07:59 vandenbrand chat[1538]: OK
Jun 27 09:07:59 vandenbrand chat[1538]:  -- got it
Jun 27 09:07:59 vandenbrand chat[1538]: send (ATDTXXXXXXXXXX^M)
Jun 27 09:07:59 vandenbrand chat[1538]: expect (CONNECT)
Jun 27 09:07:59 vandenbrand chat[1538]: ^M
Jun 27 09:08:01 vandenbrand chat[1538]: ATDT0738800900^M^M
Jun 27 09:08:01 vandenbrand chat[1538]: CONNECT
Jun 27 09:08:01 vandenbrand chat[1538]:  -- got it
Jun 27 09:08:01 vandenbrand diald[743]: connector: chat:  Jun 27 09:08:01 CONNECT 64000/HDLC
Jun 27 09:08:01 vandenbrand diald[743]: Connected to site 0.0.0.0
Jun 27 09:08:01 vandenbrand diald[1539]: Running pppd: /usr/sbin/pppd -defaultroute -detach modem crtscts mtu 1500 mru 1500 name noauth noipdefault ipparam diald
Jun 27 09:08:01 vandenbrand pppd[1539]: pppd 2.4.0 started by root, uid 0
Jun 27 09:08:01 vandenbrand pppd[1539]: Using interface ppp0
Jun 27 09:08:01 vandenbrand pppd[1539]: Connect: ppp0 <--> /dev/ttyI0
Jun 27 09:08:01 vandenbrand diald[743]: Running pppd (pid = 1539).
Jun 27 09:08:10 vandenbrand pppd[1539]: Hangup (SIGHUP)
Jun 27 09:08:10 vandenbrand pppd[1539]: Modem hangup
Jun 27 09:08:10 vandenbrand pppd[1539]: Connection terminated.
Jun 27 09:08:10 vandenbrand pppd[1539]: Exit.
Jun 27 09:08:10 vandenbrand diald[743]: start sl0: SIOCSIFMTU: Invalid argument
Jun 27 09:08:11 vandenbrand diald[743]: stop ppp0: RTNETLINK answers: No such process
Jun 27 09:08:11 vandenbrand diald[743]: stop ppp0: SIOCSIFFLAGS: No such device or address
Jun 27 09:08:11 vandenbrand diald[743]: Disconnected. Call duration 10 seconds.
Jun 27 09:08:11 vandenbrand diald[743]: IP transmitted 135 bytes and received 0 bytes.
Jun 27 09:08:12 vandenbrand diald[743]: Delaying 10 seconds before clear to dial.
Title: Re: Getting diald to work
Post by: Klaus J. Mueller on August 14, 2001, 01:52:02 AM
Hi *,

in a PM RequestedDeletion sent me he pointed out that the following helped him solve the problem:

- don't append "S14=3" to the init-string
- include "L0M0" in the init string

that makes:
/sbin/e-smith/config set ModemInit "L0M0&E123456"

This problem (Hsing Foo called it the "LCP problem") only seems to occur with
some providers. I cannot confirm this solution as I cannot reproduce the problem ;-)

Can anyone who has experienced the LCP problem please test this solution and
let us know here, whether it helped?

In case it does solve the problem I would like to extend my howto by this information.

Thanx to RequestedDeletion for his suggestion.

Regards, K.
Title: Re: Getting diald to work
Post by: Kees Blokland on August 14, 2001, 02:33:52 AM
Fresh from the disk ( like less than an hour ago..)

I finally got my isdn/UK going, learned a lot in the process and have some tips about getting more/better logs.

I just dumped some in-progress docs on my website, have a look

http://www.blokland.co.uk/Kees/docs/e-smith/isdn4es.htm

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

http://www.blokland.co.uk/Kees/docs/e-smith/ISDN-working.htm


hope this gives you some ideas about debugging!

Most important solution to at least my problem was the 'sync'  and the use of a zero in my msn.
I know, I've read every bit of paper that says: UK-MSN=0, BUT with the phonenumber it worked, The connection was there etc. The only 'problem' was that I could only ping my local external ip and the remote ip, nothing else..
This is one to remember!

The docs are work in progress. I mentioned something about ntpd not working properly, it does seem to work now, all due to a silly 0!!!

have fun

kees blokland.


ps.
Klaus, maybe you can add some of this stuff to your pages? I'll try to make it into a more coherent story.. let me know..
Title: Re: Getting diald to work
Post by: Gert-Jan Verheij on October 14, 2001, 09:01:34 PM
Thankx, this is the solution! Sorry for the late reaction...

Anybody who knows how to work with two ISDN lines and E-smith?


Greetings Gert-Jan
Title: Re: Getting diald to work
Post by: guestFF on October 15, 2001, 03:48:51 AM
Hi Gert-Jan,

THIS is a subject that I like to know more about. There was a thead about using multiple ISDN B-channels, it said it was not possible due to the way SME (E-smith) works....

I'm glad you got it working. Can you summarize your problem/solution pls.?

Regards,

RequestedDeletion
Title: Re: Getting diald to work
Post by: Gert-Jan Verheij on October 15, 2001, 12:13:57 PM
Klaus J. Mueller (kjm_AT_internet-sicherheit.net)
Date:   08-13-01 16:52

Hi *,

in a PM RequestedDeletion sent me he pointed out that the following helped him solve the problem:

- don't append "S14=3" to the init-string
- include "L0M0" in the init string

that makes:
/sbin/e-smith/config set ModemInit "L0M0&E123456"

In answer to your question, RequestedDeletion, I have used this remarks of Klaus J. Mueller,

I don't have a solution for ISDN2 on this moment, I will possible search for it in future....

Gert-Jan