pppd shutdown problem

Hello,

I use pppd to connect to my ISP with my bluetooth modem.
When I shutdown the link by killing the pppd, my modem
tries to send "NO CARRIER", but since the link gets down
immediately, the modem seems to buffer that output.
The next time I connect and send "ATZ", I first get back
"NO CARRIER" and my chatscript aborts. My workaround was
to change the ABORT line in my chatscript, so it won't
abort on "NO CARRIER". Is there a better way to fix that
problem?

best regards
--
Raphael

Raphael Wegmann <(E-Mail Removed)> wrote:
> Hello,

> I use pppd to connect to my ISP with my bluetooth modem.
> When I shutdown the link by killing the pppd, my modem
> tries to send "NO CARRIER", but since the link gets down
> immediately, the modem seems to buffer that output.
> The next time I connect and send "ATZ", I first get back
> "NO CARRIER" and my chatscript aborts. My workaround was
> to change the ABORT line in my chatscript, so it won't
> abort on "NO CARRIER". Is there a better way to fix that
> problem?

Use SIGTERM (or SIGHUP with demand pppd) rather than SIGKILL?

If you aren't using SIGKILL then try starting the chat script
with, e.g.,

"" "\d+++\d\dATH"
OK ATZ

(More escapes may be necessary unless the chat script is in a file
specified by the chat -f option.)

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"

Raphael Wegmann <(E-Mail Removed)> writes:

>Hello,

>I use pppd to connect to my ISP with my bluetooth modem.
>When I shutdown the link by killing the pppd, my modem
>tries to send "NO CARRIER", but since the link gets down

How do you kill pppd? By kill -9 ? If do dont. Just killall pppd
allows pppd to carry out housekeeping.


>immediately, the modem seems to buffer that output.
>The next time I connect and send "ATZ", I first get back

Terrible thing to send to the modem. Send the "Factor default" signal (AT&F
maybe).

>"NO CARRIER" and my chatscript aborts. My workaround was

I do not believe that this is the case, unless you have a sick modem, or
unless your ATZ contains some weird setting, which it could and which is
why you should not use ATZ.

>to change the ABORT line in my chatscript, so it won't
>abort on "NO CARRIER". Is there a better way to fix that
>problem?

You could just institute the "No Carrier" abort after the first command.
It should not send you NO CARRIER as a response to ATZ anyway.



>best regards
>--
>Raphael

Unruh schrieb:
> Raphael Wegmann <(E-Mail Removed)> writes:
>
>>I use pppd to connect to my ISP with my bluetooth modem.
>>When I shutdown the link by killing the pppd, my modem
>>tries to send "NO CARRIER", but since the link gets down
>
>
> How do you kill pppd? By kill -9 ? If do dont. Just killall pppd
> allows pppd to carry out housekeeping.
>

Well I use the debian standard ifupdown scripts,
which shouldn't use SIGKILL I suppose.

/e/n/interfaces:
iface tele2 inet ppp
provider tele2

>
>>"NO CARRIER" and my chatscript aborts. My workaround was
>
>
> I do not believe that this is the case, unless you have a sick modem, or
> unless your ATZ contains some weird setting, which it could and which is
> why you should not use ATZ.
>

I guess, it is a sick modem. It's a
TYPHOON BLUETOOTHâ„¢ 56K WIRELESS MODEM
http://www.anubisline.com/de/art.php?p=810

When I switch off/on the modem after a previous ppp-session,
I don't get "NO CARRIER" after a reconnect. If I don't reset
the modem after a previous ppp-session, I get:

Oct 19 19:09:24 smsgw pppd[28254]: pppd 2.4.2 started by root, uid 0
Oct 19 19:09:28 smsgw hcid[27008]: link_key_request
(sba=00:10:60:AB:14:F8, dba=00:10:60:29:CDF)
Oct 19 19:09:29 smsgw chat[28258]: abort on (BUSY)
Oct 19 19:09:29 smsgw chat[28258]: abort on (VOICE)
Oct 19 19:09:29 smsgw chat[28258]: abort on (NO DIALTONE)
Oct 19 19:09:29 smsgw chat[28258]: abort on (NO DIAL TONE)
Oct 19 19:09:29 smsgw chat[28258]: abort on (NO ANSWER)
Oct 19 19:09:29 smsgw chat[28258]: abort on (DELAYED)
Oct 19 19:09:29 smsgw chat[28258]: send (\d\d\d\d\d\dATZ^M)
Oct 19 19:09:35 smsgw chat[28258]: expect (OK)
Oct 19 19:09:35 smsgw chat[28258]: ^M
Oct 19 19:09:35 smsgw chat[28258]: NO CARRIER^M
Oct 19 19:09:36 smsgw chat[28258]: ATZ^M^M
Oct 19 19:09:36 smsgw chat[28258]: OK
Oct 19 19:09:36 smsgw chat[28258]: -- got it
Oct 19 19:09:36 smsgw chat[28258]: send (ATM0^M)
Oct 19 19:09:36 smsgw chat[28258]: expect (OK)
Oct 19 19:09:36 smsgw chat[28258]: ^M
Oct 19 19:09:36 smsgw chat[28258]: ATM0^M^M
Oct 19 19:09:36 smsgw chat[28258]: OK
Oct 19 19:09:36 smsgw chat[28258]: -- got it
Oct 19 19:09:36 smsgw chat[28258]: send (ATDT1005019271000^M)

>
>>to change the ABORT line in my chatscript, so it won't
>>abort on "NO CARRIER". Is there a better way to fix that
>>problem?
>
>
> You could just institute the "No Carrier" abort after the first command.
> It should not send you NO CARRIER as a response to ATZ anyway.
>

Here is my chatscript:

ABORT BUSY ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO DIAL TONE' ABORT
'NO ANSWER' ABORT DELAYED
'' "\d\d\d\d\d\dATZ"
# ^^^ I can change this to AT&F, but I don't think
# it will change anything.
OK "ATM0"
# Can I add an "ABORT 'NO CARRIER'" line here?
OK-AT-OK "ATDT1005019271000"
CONNECT \d\c

best regards
--
Raphael Wegmann

Unruh <unruh-(E-Mail Removed)> wrote:
> Raphael Wegmann <(E-Mail Removed)> writes:

>>to change the ABORT line in my chatscript, so it won't
>>abort on "NO CARRIER". Is there a better way to fix that
>>problem?

> You could just institute the "No Carrier" abort after the first command.
> It should not send you NO CARRIER as a response to ATZ anyway.

Good point. The chat script ` ABORT "NO CARRIER" ' should be placed
after ATDT<phone_number>.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"