> Seems everything be good.. but why this SIGHUP?
You may be using the wrong authentication method, or your ISP may want to
see a return at the end of the chat (most don't). To test the latter try
changing
CONNECT \d\c
at the end of the chatscript to
CONNECT \d
--
John Hasler
[EMAIL PROTECT
Jaye Inabnit ke6sls writes:
> btw - I have had prob's with pppconfig - it will not delete the older
> file and pulls password out of the wrong file - I remove them by hand.
Could you explain this problem in more detail, preferably in a bug report?
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Da
Hi all
If i try to connect to the intenet(with pon) I get the following in the
messages file:
Dec 12 20:43:29 debian pppd[345]: pppd 2.3.11 started by root, uid 0
Dec 12 20:43:30 debian chat[346]: abort on (BUSY)
Dec 12 20:43:30 debian chat[346]: abort on (NO CARRIER)
Dec 12 20:43:30 debian chat[
Carefully re-run pppconfig. Looks like your modems were talking but your
isp didn't connect - that means either username or password are not correct.
btw - I have had prob's with pppconfig - it will not delete the older file
and pulls password out of the wrong file - I remove them by hand. Safe b
Hi all
If i try to connect to the intenet(with pon) I get the following in the
messages file:
Dec 12 20:43:29 debian pppd[345]: pppd 2.3.11 started by root, uid 0
Dec 12 20:43:30 debian chat[346]: abort on (BUSY)
Dec 12 20:43:30 debian chat[346]: abort on (NO CARRIER)
Dec 12 20:43:30 debian chat[
5 matches
Mail list logo
