Another kppp problem
Posts: 1
hi, i just started using linux and mepis in particular. i'm doing ok so far but i have a problem getting online. i have a 56k external us robotics modem. modem dials ok, but when trying to logon (i guess) i get??an error message. ??here are all the messages i get:
----------------modem command---------------------------
AT
OK
ATDT8962555555
CONNECT 45333/ARQ
-------------------error message------------------
The pppd daemon died unexpectedly!
Exit status: 16
See 'man pppd' for an explanation of the error codes or take a look at
the kppp FAQ on http://devel-home.kde.org/~kppp/index.html
------------------------debug log------------
Mar 3 18:08:33 mepis1 pppd[7700]: pppd 2.4.2b3 started by root, uid 0
Mar 3 18:08:33 mepis1 pppd[7700]: using channel 4
Mar 3 18:08:33 mepis1 pppd[7700]: Using interface ppp0
Mar 3 18:08:33 mepis1 pppd[7700]: Connect: ppp0 <--> /dev/ttyS0
Mar 3 18:08:33 mepis1 pppd[7700]: sent [LCP ConfReq id=0x1 <asyncmap
0xa0000> <magic 0xfc64becb> <pcomp> <accomp>]
Mar 3 18:08:48 mepis1 pppd[7700]: Hangup (SIGHUP)
Mar 3 18:08:48 mepis1 pppd[7700]: Modem hangup
Mar 3 18:08:48 mepis1 pppd[7700]: Connection terminated.
Mar 3 18:08:48 mepis1 pppd[7700]: Exit.
-----------------options file------------------------------
root@0[root]# egrep -v '#|^ *$' /etc/ppp/options
asyncmap 0
noauth
crtscts
lock
hide-password
modem
noipdefault
passive
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx
=========================
any help is welcome.
sorry for??my english...,
dimitris??
pppd died... here's really why!
Posts: 1
Despite the fact many people say "pppd daemon died unexpectedly" could be because of "use lock file" option, 'lock' in /etc/ppp/options, or whatever, I just discover the REAL cause in my case!
Solution: do NOT use 'PPP' authentication, instead select in kppp the 'PPP/CHAP' one!
Don't set CHAP only, simply chose 'PPP/CHAP'! And, of course, uncheck the "use lock file" option, just in case.
Try this
Posts: 8
Firstly, it is very important that if you ask a question you should follow it through to let people know whether it is fixed or not!
Anyway, I had the same problem with kubuntu and I solved it by going to /etc/ppp/peers/kppp options.txt and replacing #noauth with noauth (ie Delete the #) and all is now good. Hope this helps others
wanger123
What to do
Posts: 10
Just solved this two nights ago. Here we go.
1) open etc/ppp/peers/kppp-options and remove the # in front
of noauth if it is there.
2) open etc/ppp/pap-secrets and make sure your isp username
and password are there, again with no # in front of the line.
3) open etc/ppp/peers/provider and first make sure the correct
modem is listed, mine is on com port 2 so my line reads
/dev/ttyS1. Then this is the biggie because this line was very
wrong on mine. The chat script line should read :
connect "/usr/sbin/chat -v -f /etc/ppp/peers/provider"
That should do it.
By the way when putting settings in kppp (click configure button)
i used PAP and CR/LF and CRTSCTS and 115200 and /dev/ttyS1(which in
my case is com port 2).
Also do not use lock and do everything logged in as root.
hii have got exactly! the s
Posts: 1
hi
i have got exactly! the same problem (simply mephis 2004.2) with external serial usr modem!!!
i does not work when executed with superuser rights either.
No problems with knoppix!
any ideas?
Markus