Re: diald problems. argh.
On Mon, 20 Jan 1997 09:04:55 PST Kevin Traas ([EMAIL PROTECTED]) wrote: You're starting pppd yourself in the connect script while diald expects to start pppd itself. The connect script should just execute the `chat' command. Re-read the diald manpage and look in the mail archives, I've already explained that one week ago. Yes, Phil - that explanation was to me. Thanks very much. I've got everything working successfully now - and it's great! However, I just didn't find this obviously stated in the manpages I haven't gone back to actually see if I could find this point mentioned, but if others are having this same problem, I don't feel so bad grin Should we (or I) talk to someone and get the docs edited slightly and add a , let me repeat, *** YOU DON'T NEED TO START pppd FROM YOUR DIALD CHAT SCRIPT BECAUSE DIALD STARTS pppd AUTOMATICALLY ONCE THE CHAT SCRIPT COMPLETES. *** This or something similar would make things a little more obvious When I installed diald some six months ago, this wasn't a problem for me :-) Maybe because I used the examples provided in /usr/doc/diald... You should contact the diald maintainer and/or open a bug requesting that this advice is placed proeminently for next diald release. Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: diald problems. argh.
On Mon, 20 Jan 1997 09:04:55 PST Kevin Traas ([EMAIL PROTECTED]) wrote: Should we (or I) talk to someone and get the docs edited slightly and add a , let me repeat, *** YOU DON'T NEED TO START pppd FROM YOUR DIALD CHAT SCRIPT BECAUSE DIALD STARTS pppd AUTOMATICALLY ONCE THE CHAT SCRIPT COMPLETES. *** This or something similar would make things a little more obvious When I installed diald some six months ago, this wasn't a problem for me :-) Maybe because I used the examples provided in /usr/doc/diald... Sarcasm attitude aside, I'd love to follow this advice. However, /usr/doc/diald/examples/diald.options[.gz] says connect /etc/ppp/ppp-connect-with-diald but this script is not provided. Hence my stuffing it up. Also, I thought all examples lived in /usr/doc/examples; diald's live in /usr/doc/diald/examples, and there's no sym link in /usr/doc/examples. diald from buzz had even less documentation provided, especially useful versions. rex is much better in this regard, but clearly has some way to go. As I said, I knew diald was going to be horrendous to set up when I started, and I wasn't far wrong. For example, I just added some rules to ignore certain protocols to the bottom of my /etc/diald/diald.conf; bad move, because the default accept any ... lines get you before then. Took quite some hair before I figured this out. The warnings about named were also nearly enough to scare me off. Since non-computer people will be using this setup, in the end I set up apache on the gateway machine, with a quick script to say whether the link is up or not, and if not, provide a button they can press which runs another script which tells diald to go up via the fifo. Seems to work quite well, rather than waiting for a connection to timeout. I have named forwarding requests here. Hamish -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: diald problems. argh.
On Tue, 21 Jan 1997 18:24:33 +1100 Hamish Moffatt ([EMAIL PROTECTED] rmit.edu.au) wrote: On Mon, 20 Jan 1997 09:04:55 PST Kevin Traas ([EMAIL PROTECTED]) wrote: Should we (or I) talk to someone and get the docs edited slightly and add a , let me repeat, *** YOU DON'T NEED TO START pppd FROM YOUR DIALD CHAT SCRIPT BECAUSE DIALD STARTS pppd AUTOMATICALLY ONCE THE CHAT SCRIPT COMPLETES. *** This or something similar would make things a little more obvious When I installed diald some six months ago, this wasn't a problem for me :-) Maybe because I used the examples provided in /usr/doc/diald... Sarcasm attitude aside, I'd love to follow this advice. However, /usr/doc/diald/examples/diald.options[.gz] says connect /etc/ppp/ppp-connect-with-diald but this script is not provided. Hence my stuffing it up. Sarcasm was intended. Indeed, I never saw a modem nor ppp, nor diald in my whole life and I configured it in less than two hours. Maybe am I a geek ? In the diald examples directory lives: /usr/doc/diald/examples/bin/connect.gz which is a very good example of chatscript. Also, I thought all examples lived in /usr/doc/examples; diald's live in /usr/doc/diald/examples, and there's no sym link in /usr/doc/examples. The new package format states that examples should be in /usr/doc/package/examples. The old format used /usr/doc/examples/pa ckage. We still have old packages to be converted... But I admit the manpage is quite confusing on the `connect' command. Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: diald problems. argh.
My /etc/diald/diald.options file says connect /etc/ppp/startppp-diald, and that file says pppd connect chat -f /etc/ppp/chatscript which contains my chatscript, and works fine. (I've been dialing for the past few months by running pppd manually.) You're starting pppd yourself in the connect script while diald expects to start pppd itself. The connect script should just execute the `chat' command. Re-read the diald manpage and look in the mail archives, I've already explained that one week ago. Yes, Phil - that explanation was to me. Thanks very much. I've got everything working successfully now - and it's great! However, I just didn't find this obviously stated in the manpages I haven't gone back to actually see if I could find this point mentioned, but if others are having this same problem, I don't feel so bad grin Should we (or I) talk to someone and get the docs edited slightly and add a , let me repeat, *** YOU DON'T NEED TO START pppd FROM YOUR DIALD CHAT SCRIPT BECAUSE DIALD STARTS pppd AUTOMATICALLY ONCE THE CHAT SCRIPT COMPLETES. *** This or something similar would make things a little more obvious I know the reason I ran into the problem (and probably why Hamish did too) was that the FAQ, HOWTO, doc, or whatever, had a step-by-step procedure on getting the dialup connection going. The first stage was to get a working ppp connection which takes you through getting a chat script going, etc. Then, once that's done, it moves into discussing how to configure Diald. It wasn't clearly stated that you couldn't use the same scripts for Diald that you could for pppd which was the natural assumption I made My $0.02 Kevin Traas Systems Analyst Edmondson Roper Chartered Accountants http://users.uniserve.com/~erca Chilliwack, B.C. Pager: (604) 918-2054 Office: (604) 792-1915 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
diald problems. argh.
I've been avoiding configuring diald for a while because it's always looked (from a distance) like hell. Seems to be confirmed by actually trying it. I'm running named on diald system, and wish to keep doing so. My named is configured to forward to other systems, and appears to do this from non-domain ports, so the link will come up correctly. eg I can go to another machine on the network and look up a web site, and it will try to connect. For added hair loss, I'm using IP masquerading too. However a couple of problems. After connecting, diald says Connect script timed out. Killing script. and this is followed some time later by child process 544 terminated with signal 9 and SIGHUP: modem got hung up on. My /etc/diald/diald.options file says connect /etc/ppp/startppp-diald, and that file says pppd connect chat -f /etc/ppp/chatscript which contains my chatscript, and works fine. (I've been dialing for the past few months by running pppd manually.) Any suggestions as to why I get the kill problem? Other problem. I am using dynamic IPs. In diald.options, I put my IP as 203.12.22.253 (eg a dummy on my ISP's network), and the remote IP as 203.12.22.254. When the link comes up, diald establishes a default route but uses the dummy remote address as the gateway, not the real gateway from pppd. If I remove the dud default and add the correct one, it works fine. (Until I get hung up). Your thoughts appreciated! thanks, Hamish -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: diald problems. argh.
On Sun, 19 Jan 1997 18:44:32 +1100 Hamish Moffatt ([EMAIL PROTECTED] rmit.edu.au) wrote: My /etc/diald/diald.options file says connect /etc/ppp/startppp-diald, and that file says pppd connect chat -f /etc/ppp/chatscript which contains my chatscript, and works fine. (I've been dialing for the past few months by running pppd manually.) You're starting pppd yourself in the connect script while diald expects to start pppd itself. The connect script should just execute the `chat' command. Re-read the diald manpage and look in the mail archives, I've already explained that one week ago. Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: diald problems. argh.
On Sun, 19 Jan 1997 18:44:32 +1100 Hamish Moffatt ([EMAIL PROTECTED] rmit.edu.au) wrote: My /etc/diald/diald.options file says connect /etc/ppp/startppp-diald, and that file says pppd connect chat -f /etc/ppp/chatscript which contains my chatscript, and works fine. (I've been dialing for the past few months by running pppd manually.) You're starting pppd yourself in the connect script while diald expects to start pppd itself. The connect script should just execute the `chat' command. Re-read the diald manpage and look in the mail archives, I've already explained that one week ago. Thanks. Now, is there a way I can have diald ignore ping packets destined for a particular host? I want to run ping to keep the ISP from timing out, but I don't want the packets to stop the link from being taken down by this end. I put ignore icmp ip.daddr=203.12.22.10 in /etc/diald/diald.conf but this does not seem to be having the effect; the link has been idle long enough to be hung up, and the only traffic (according to tcpdump) is some inter-named stuff and the icmp traffic. thanks, Hamish -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: diald problems. argh.
On Sun, 19 Jan 1997, Hamish Moffatt wrote: My /etc/diald/diald.options file says connect /etc/ppp/startppp-diald, and that file says pppd connect chat -f /etc/ppp/chatscript This is becoming an FAQ. As stated in the doumentation, your chat script should not start pppd. diald starts pppd when it is ready. your chat script is only for chatting -- that is getting the connection up. Change your /etc/ppp/startppp-diald to: chat -f /etc/ppp/chatscript Erv ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ ==-- _ / / \ ---==---(_)__ __ __/ / /\ \ - [EMAIL PROTECTED] --==---/ / _ \/ // /\ \/ / / /_/\ \ \ - [EMAIL PROTECTED] -=/_/_//_/\_,_/ /_/\_\ /__\ \ \ - [EMAIL PROTECTED] http://www.linux.org \_\/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
