Hi Dan,
Dan Hensley wrote:
> After spending several hours with it on two separate occasions, I'm
> about to give up getting diald to work. I've tried everything I can
> think of, and I'm stumped. Basically, my ISP uses CHAP
> authentication,
> so I've got my username and password in /etc/chap-secrets. Here's the
> command I use to connect:
>
> /usr/sbin/pppd name "[EMAIL PROTECTED]" -d connect
> '/usr/sbin/chat -t 45 -v ABORT BUSY "" ATDT0005551212 CONNECT ""'
> /dev/ttyS0 115200 noipdefault modem defaultroute crtscts
>
> This works fine. However, I cannot get diald to understand this.
I had no trouble using diald with worldnet. Though here it used PAP instead
of CHAP.
There is not enough information being logged to tell what the error is.
Most likely you are being bit by one of two common problems.
1. You forget to set the noauth option for pppd (it must be set if dialing
with a default route in place). This is not needed when starting pppd from
the command line since there is no existing default route but it is needed
when using diald because there is an existing default route to the proxy
device.
2. There is an implicit ^M sent with the 'CONNECT ""' section of your chat
command. It often doesn't matter when pppd invokes chat but with the delay
in diald starting pppd after chat terminates it's often enough time that the
remote side has switched to prompted login mode.
Do you have anything at all set in /etc/ppp/options?
> Here's my /etc/diald.conf file:
>
> mode ppp
>
> pppd-options name "[EMAIL PROTECTED]"
pppd-options noauth name "[EMAIL PROTECTED]"
> connect '/usr/sbin/chat -t 45 -v ABORT BUSY "" ATDT0005551212 CONNECT ""'
connect '/usr/sbin/chat -t 45 -v ABORT BUSY "" ATDT0005551212 CONNECT "\\c"'
# note: the "\c" for no ^M to be sent must be escaped
# (since it will be sent as a shell command)
# so it becomes "\\c" in the command.
# see man chat for more information
> device /dev/ttyS0
> speed 115200
> modem
> lock
> crtscts
>
> local 192.168.0.1
> remote 192.168.0.2
> dynamic
>
> defaultroute
> include /usr/lib/diald/standard.filter
>
>
> Whenever I connect successfully by manually entering my
> connect command,
> my /var/log/messages gives me this:
> Mar 25 14:02:23 danlinux pppd[948]: pppd 2.3.10 started by root, uid 0
> Mar 25 14:02:24 danlinux chat[951]: abort on (BUSY)
> Mar 25 14:02:24 danlinux chat[951]: send (ATDT0005551212^M)
> Mar 25 14:02:25 danlinux chat[951]: expect (CONNECT)
> Mar 25 14:02:43 danlinux chat[951]: ATDT0005551212^M^M
> Mar 25 14:02:43 danlinux chat[951]: CONNECT
> Mar 25 14:02:43 danlinux chat[951]: -- got it
> Mar 25 14:02:43 danlinux chat[951]: send (^M)
> Mar 25 14:02:43 danlinux pppd[948]: Serial connection established.
> Mar 25 14:02:43 danlinux pppd[948]: Using interface ppp0
> Mar 25 14:02:43 danlinux pppd[948]: Connect: ppp0 <--> /dev/ttyS0
> Mar 25 14:02:46 danlinux pppd[948]: Remote message: ^@
> Mar 25 14:02:46 danlinux kernel: PPP BSD Compression module registered
> Mar 25 14:02:46 danlinux kernel: PPP Deflate Compression module
> registered
> Mar 25 14:02:47 danlinux pppd[948]: local IP address 12.74.83.9
> Mar 25 14:02:47 danlinux pppd[948]: remote IP address 199.69.163.104
> Mar 25 14:02:49 danlinux pppd[948]: local IP address 12.74.83.9
> Mar 25 14:02:49 danlinux pppd[948]: remote IP address 199.69.163.104
>
> However, when I try to connect using diald, I get this:
> Mar 25 23:48:31 danlinux diald[13066]: start sl0: SIOCSIFMETRIC:
> Operation not supported
> Mar 25 23:48:32 danlinux diald[13066]: Trigger: udp
> 192.168.0.1/1093 204.127.160.1/53
> Mar 25 23:48:32 danlinux diald[13066]: Calling site 192.168.0.2
> Mar 25 23:48:33 danlinux chat[13089]: abort on (BUSY)
> Mar 25 23:48:33 danlinux chat[13089]: send (ATDT0005551212^M)
> Mar 25 23:48:34 danlinux chat[13089]: expect (CONNECT)
> Mar 25 23:48:52 danlinux chat[13089]: ATDT0005551212^M^M
> Mar 25 23:48:52 danlinux chat[13089]: CONNECT
> Mar 25 23:48:52 danlinux chat[13089]: -- got it
> Mar 25 23:48:52 danlinux chat[13089]: send (^M)
> Mar 25 23:48:52 danlinux diald[13066]: Connected to site 192.168.0.2
> Mar 25 23:48:52 danlinux diald[13066]: Running pppd (pid = 13097).
> Mar 25 23:48:52 danlinux modprobe: can't locate module char-major-108
> Mar 25 23:48:52 danlinux pppd[13097]: pppd 2.3.10 started by
> root, uid 0
>
> Mar 25 23:48:52 danlinux pppd[13097]: Using interface ppp0
> Mar 25 23:48:52 danlinux pppd[13097]: Connect: ppp0 <--> /dev/ttyS0
> Mar 25 23:48:54 danlinux pppd[13097]: Remote message: ^@
> Mar 25 23:48:58 danlinux pppd[13097]: Hangup (SIGHUP)
> Mar 25 23:48:58 danlinux pppd[13097]: Modem hangup
> Mar 25 23:48:58 danlinux pppd[13097]: Connection terminated.
> Mar 25 23:48:58 danlinux pppd[13097]: Exit.
> Mar 25 23:48:58 danlinux diald[13066]: start sl0: SIOCSIFMETRIC:
> Operation not supported
> Mar 25 23:48:58 danlinux diald[13066]: start sl0: SIOCADDRT:
> File exists
>
> Mar 25 23:48:58 danlinux diald[13066]: start sl0: SIOCDELRT: No such
> process
> Mar 25 23:48:58 danlinux diald[13066]: start sl0: SIOCADDRT:
> File exists
>
> Mar 25 23:48:58 danlinux diald[13066]: stop ppp0: SIOCDELRT: No such
> process
> Mar 25 23:48:59 danlinux kernel: ppp: ppp0 not active
> Mar 25 23:48:59 danlinux diald[13066]: stop ppp0: SIOCSIFFLAGS: Device
> not configured
> Mar 25 23:49:00 danlinux diald[13066]: Delaying 30 seconds
> before clear
> to dial.
>
>
> I suspect that the "name" option for pppd is not being used correctly,
> but I'm not sure. Can anyone provide input?
>
> Thanks,
> Dan
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-diald" in
> the body of a message to [EMAIL PROTECTED]
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
