Lew Pitcher
2011-09-27 01:42:43 UTC
On September 26, 2011 20:59, in comp.os.linux.networking,
this problem.
Your PPP configuration is ancient, and expects to talk to a Hayes-compatable
internal modem. You don't have one of those.
Instead, your "fixed-wireless-modem" just converts from "serial" (on the
computer side) to wifi or phone (on the wireless side). That hash you see
at the expect is the PPP negotiation signal from the other end.
Get rid of the expect scripts. In fact, use something like the setup for
pppoe, which doesn't talk to a "modem" at all.
I vaguely remember the explanation ten years ago for a ppp-trace
You could confirm it by decoding the bits -- or something?
I'm very enthusiastic and optimistic that I can finally use
my fixed-wireless-modem from linux instead of the pain of
M$-Win7.
=================== Here's a log of my tests:-
-> edit my old chap-script from 199? to:---
pppd lcp-echo-interval 300 lcp-echo-failure 4 connect '
chat -v "" ATZ OK ATX OK ATM2DT#777 CONNECT "" TIMEOUT 99 ' \
/dev/ttyUSB1 115200 debug crtscts modem \
-> run Slak13:pppsetup which sets /etc/ppp/chap-secrets
but doesn't know about ttyUSB1
-> re-run chap-script == '/dev/modem unrecognised'
-> ls -l /dev/modem == No such file or directory
-> ln -s /dev/ttyUSB1 /dev/modem
-> re-run chap-script == Wireless-modem LCD indicates <connecting>
-> tail -f /var/log/messages ==
Sep 26 23:43:58 labeas pppd[6513]: pppd 2.4.4 started by root, uid 0
Sep 26 23:43:59 labeas chat[6514]: send (ATZ^M)
Sep 26 23:43:59 labeas chat[6514]: expect (OK)
}!}"} }9}!}$}%\}"}&} } } } }#}%B#}%}%}&F^ZOc\U~~^?}
Sep 26 23:44:44 labeas chat[6514]: alarm
Sep 26 23:44:44 labeas chat[6514]: Failed
Sep 26 23:44:45 labeas pppd[6513]: Exit.
============= end of trace log:--------
OK, if you haven't touched PPP since the 1990's, then you might be forgivenYou could confirm it by decoding the bits -- or something?
I'm very enthusiastic and optimistic that I can finally use
my fixed-wireless-modem from linux instead of the pain of
M$-Win7.
=================== Here's a log of my tests:-
-> edit my old chap-script from 199? to:---
pppd lcp-echo-interval 300 lcp-echo-failure 4 connect '
chat -v "" ATZ OK ATX OK ATM2DT#777 CONNECT "" TIMEOUT 99 ' \
/dev/ttyUSB1 115200 debug crtscts modem \
-> run Slak13:pppsetup which sets /etc/ppp/chap-secrets
but doesn't know about ttyUSB1
-> re-run chap-script == '/dev/modem unrecognised'
-> ls -l /dev/modem == No such file or directory
-> ln -s /dev/ttyUSB1 /dev/modem
-> re-run chap-script == Wireless-modem LCD indicates <connecting>
-> tail -f /var/log/messages ==
Sep 26 23:43:58 labeas pppd[6513]: pppd 2.4.4 started by root, uid 0
Sep 26 23:43:59 labeas chat[6514]: send (ATZ^M)
Sep 26 23:43:59 labeas chat[6514]: expect (OK)
}!}"} }9}!}$}%\}"}&} } } } }#}%B#}%}%}&F^ZOc\U~~^?}
Sep 26 23:44:44 labeas chat[6514]: alarm
Sep 26 23:44:44 labeas chat[6514]: Failed
Sep 26 23:44:45 labeas pppd[6513]: Exit.
============= end of trace log:--------
this problem.
Your PPP configuration is ancient, and expects to talk to a Hayes-compatable
internal modem. You don't have one of those.
Instead, your "fixed-wireless-modem" just converts from "serial" (on the
computer side) to wifi or phone (on the wireless side). That hash you see
at the expect is the PPP negotiation signal from the other end.
Get rid of the expect scripts. In fact, use something like the setup for
pppoe, which doesn't talk to a "modem" at all.
--
Lew Pitcher
Master Codewright & JOAT-in-training | Registered Linux User #112576
Me: http://pitcher.digitalfreehold.ca/ | Just Linux: http://justlinux.ca/
---------- Slackware - Because I know what I'm doing. ------
Lew Pitcher
Master Codewright & JOAT-in-training | Registered Linux User #112576
Me: http://pitcher.digitalfreehold.ca/ | Just Linux: http://justlinux.ca/
---------- Slackware - Because I know what I'm doing. ------