Hi! I have tried to make diald work with no success. I don't get any errors when connecting to my ISP, it just doesn't log in it gets to the state where it puts the errors I attached in the file diald.log in syslog My /etc/diald.conf and /etc/diald/connect are also attached. (password and username have ben deleted ofcourse). I hope someone can help me. THX in advance! <HR> <UL> <LI>text/plain attachment: onnect_ </UL> <HR> <UL> <LI>text/plain attachment: diald.conf </UL> <HR> <UL> <LI>text/plain attachment: diald.log </UL> -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On 13-Apr-2000 Bostjan Muller wrote:
Hi!
I have tried to make diald work with no success. I don't get any errors when connecting to my ISP, it just doesn't log in it gets to the state where it puts the errors I attached in the file diald.log in syslog
My /etc/diald.conf and /etc/diald/connect are also attached. (password and username have ben deleted ofcourse).
I hope someone can help me.
THX in advance!
I'm not that hot on diald but it might help to turn on debug in /etc/ppp/options so that we can get some more information on where ppp is failing. I think the debug messages end up in /var/log/messages not sure if they are also placed in the diald log file. Does your ISP use PAP or CHAP for authorisation? Can you log on using KPPP or other software? Regards, Graham Smith ---------------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
* On 13-04-00 at 19:17 Graham Smith (gqs@zip.com.au) wrote: +----Here quoted text begins----+
I'm not that hot on diald but it might help to turn on debug in /etc/ppp/options so that we can get some more information on where ppp is failing. I think the debug messages end up in /var/log/messages not sure if they are also placed in the diald log file. I tried wvdial, and the error is attached
Does your ISP use PAP or CHAP for authorisation? PAP (/etc/pap-secrets has everything set up properly)
Can you log on using KPPP or other software? Yes i allways use ppp-up and ppp-off scripts (some slack scripts) and I have used pppsetup for configuration (with some added manual tweaking - mru and such). +----and here the quote ends----+
The wvdial's error output is attached. Bostjan <HR> <UL> <LI>text/plain attachment: wvdial.err </UL> -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On 13-Apr-2000 Bostjan Muller wrote:
* On 13-04-00 at 19:17 Graham Smith (gqs@zip.com.au) wrote: +----Here quoted text begins----+
I'm not that hot on diald but it might help to turn on debug in /etc/ppp/options so that we can get some more information on where ppp is failing. I think the debug messages end up in /var/log/messages not sure if they are also placed in the diald log file. I tried wvdial, and the error is attached
Can you try turning on the debug in /etc/ppp/options and giving us the output of the pppd messages in /var/log/messages. The other log files do not contain what is happening with pppd so until I get this I can't help you. To turn on debug edit the /etc/ppp/options file and add the following line. debug
Does your ISP use PAP or CHAP for authorisation?
PAP (/etc/pap-secrets has everything set up properly)
Can you log on using KPPP or other software?
Yes i allways use ppp-up and ppp-off scripts (some slack scripts) and I have used pppsetup for configuration (with some added manual tweaking - mru and such). +----and here the quote ends----+
The wvdial's error output is attached.
Bostjan
Regards Graham Smith ---------------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
* On 13-04-00 at 20:35 Graham Smith (gqs@zip.com.au) wrote: +----Here quoted text begins----+
Can you try turning on the debug in /etc/ppp/options and giving us the output of the pppd messages in /var/log/messages. The other log files do not contain what is happening with pppd so until I get this I can't help you.
To turn on debug edit the /etc/ppp/options file and add the following line. debug
+----and here the quote ends----+
The only thing I found is this:
Apr 13 20:36:12 maja pppd[8826]: sent [LCP ConfReq id=0x1
I found out that there was some problem with /etc/ppp/options, that only let that ppp-go script work. When I removed it wvdial started to wrk too. Now I would like to use wvdial.dod, but It doesn't seem to work for me (I did copy the one from the german site) but it just sits there and does nothing. Is there anything else that has to be done (apart from starting the scritpt itself?). THX in advance! Bostjan -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I gues I wasn't watching close enough previous time, did it again and found
this:
Apr 13 20:46:38 maja pppd[8914]: pppd 2.3.10 started by root, uid 0
Apr 13 20:46:38 maja pppd[8914]: Using interface ppp0
Apr 13 20:46:38 maja pppd[8914]: Connect: ppp0 <--> /dev/ttyS1
Apr 13 20:46:38 maja pppd[8914]: sent [LCP ConfReq id=0x1
Can you try turning on the debug in /etc/ppp/options and giving us the output of the pppd messages in /var/log/messages. The other log files do not contain what is happening with pppd so until I get this I can't help you.
To turn on debug edit the /etc/ppp/options file and add the following line. debug
+----and here the quote ends----+ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On 14-Apr-2000 Bostjan Muller wrote:
I gues I wasn't watching close enough previous time, did it again and found this: Apr 13 20:46:38 maja pppd[8914]: pppd 2.3.10 started by root, uid 0 Apr 13 20:46:38 maja pppd[8914]: Using interface ppp0 Apr 13 20:46:38 maja pppd[8914]: Connect: ppp0 <--> /dev/ttyS1 Apr 13 20:46:38 maja pppd[8914]: sent [LCP ConfReq id=0x1
<pcomp> <accomp>] Apr 13 20:46:41 maja pppd[8914]: sent [LCP ConfReq id=0x1 <pcomp> <accomp>] Apr 13 20:46:44 maja pppd[8914]: sent [LCP ConfReq id=0x1 <pcomp> <accomp>] Apr 13 20:47:00 maja last message repeated 5 times
The ISP is not responding to your requests. You should receive something like
this back from them
Apr 10 22:58:45 merlin pppd[32638]: rcvd [LCP ConfReq id=0x1 < 00 04 00 00>
Apr 13 20:47:03 maja pppd[8914]: Hangup (SIGHUP) Apr 13 20:47:03 maja pppd[8914]: sent [LCP ConfReq id=0x1
<pcomp> <accomp>] Apr 13 20:47:03 maja pppd[8914]: write: warning: Input/output error (5) Apr 13 20:47:03 maja pppd[8914]: Modem hangup Apr 13 20:47:03 maja pppd[8914]: Connection terminated. Apr 13 20:47:03 maja pppd[8914]: Exit. I hope this is any better than the previous.
Bostjan
Unfortunately I deleted your previous messages, but from what I can remember you had quite a number of options setup in diald.conf which may be in conflict with /etc/ppp/options or not required. I'm pretty sure your problem is in the diald.conf file. I would suggest commenting out all the configuration options from the diald.conf file. You will have to check with "man pppd" to find which variables belong to the ppp options file. This would be why you can connect normally but diald fails. If you can't find anything wrong please repost the diald.conf and /etc/ppp/options file & I'll have a look at them. Hope this helps. Graham Smith ---------------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I know that ISP "should" talk back, but it from some to me completely unknown reason doesn't :(( I have tried to comment as much as possible in diald.conf file, but the same errors occured. I have checked out the man pages and couldn't find anything to fix my problem, so I am sending the config files to the list. Appended are: /etc/ppp/options /etc/ppp/pppscript /etc/diald.conf THX in advance! Bostjan * On 15-04-00 at 10:10 Graham Smith (gqs@zip.com.au) wrote: +----Here quoted text begins----+
Unfortunately I deleted your previous messages, but from what I can remember you had quite a number of options setup in diald.conf which may be in conflict with /etc/ppp/options or not required.
I'm pretty sure your problem is in the diald.conf file. I would suggest commenting out all the configuration options from the diald.conf file. You will have to check with "man pppd" to find which variables belong to the ppp options file.
This would be why you can connect normally but diald fails. If you can't find anything wrong please repost the diald.conf and /etc/ppp/options file & I'll have a look at them.
Hope this helps.
Graham Smith ----------------------------------
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ +----and here the quote ends----+
<HR> <UL> <LI>text/plain attachment: diald.conf </UL> <HR> <UL> <LI>text/plain attachment: ptions_ </UL> <HR> <UL> <LI>text/plain attachment: ppscript_ </UL> -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
At 19:22 13-04-00, you wrote:
* On 13-04-00 at 19:17 Graham Smith (gqs@zip.com.au) wrote: +----Here quoted text begins----+
I'm not that hot on diald but it might help to turn on debug in /etc/ppp/options so that we can get some more information on where ppp is failing. I think the debug messages end up in /var/log/messages not sure if they are also placed in the diald log file. I tried wvdial, and the error is attached
Does your ISP use PAP or CHAP for authorisation? PAP (/etc/pap-secrets has everything set up properly)
I noticed that there is a username/password at the end of the chat-script or whatever it was (the first of the files.) Many ISPs get confused if you first give it a script login, and will then not be able to let you login using PAP. Try removing the username and password from the end of that file. Regards Ole Kofoed Hansen okh@post.cybercity.dk ICQ# 25773325 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
gqs@zip.com.au
-
k01164@ko.sdu.dk
-
neonatus@gimp.thz.net