Re: diald problem
I had a somewhat similar problem some time ago, I don't remember the exact details now so I'm not sure I'm talking about the same issue. When you upgrade your 2.2.x kernel to a 2.4.x one, you must upgrade many packages in order to keep them all working OK, this is documented in /Docs in the kernel source, CHANGES or README, IIRC. For example, pppd must be 2.4. Be sure to upgrade all that packages as documented and try again. Good luck !!! I installed Debian 2.2r6, installed a ppp-dialup link. This works fine with 'pon provider' I automated it with diald so it responds when there is an ISP-request an brings the link down after som idle time. So far, so good. I recently installed a new kernel 2.4.18. This look OK, but diald is dead (process is running thou). It won't respond to commands such as 'lynx', 'route' etc. Everything look the same as with 2.2r6. Same scripts are there, diald-process is running. Reinstalled diald while 2.4.18 is active, no change. ppp is working fine (pon provider establishes the link). Running 2.2r6 (2.2.20 kernel) everything works fine, including diald. What could be the problem here? Any clues? Anybody could help a little??? Thanx in advance, Frank. -- Daniel Toffetti --- 'There is no spoon...' - The Matrix Running Debian Sid version 3.0 with Linux 2.4.13 i686 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
diald problem
Dear all, I installed Debian 2.2r6, installed a ppp-dialup link. This works fine with 'pon provider' I automated it with diald so it responds when there is an ISP-request an brings the link down after som idle time. So far, so good. I recently installed a new kernel 2.4.18. This look OK, but diald is dead (process is running thou). It won't respond to commands such as 'lynx', 'route' etc. Everything look the same as with 2.2r6. Same scripts are there, diald-process is running. Reinstalled diald while 2.4.18 is active, no change. ppp is working fine (pon provider establishes the link). Running 2.2r6 (2.2.20 kernel) everything works fine, including diald. What could be the problem here? Any clues? Anybody could help a little??? Thanx in advance, Frank. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
diald problem
Hello, I have diald 0.99.1-1 and I think I have set things up properly put it is still not working. I have replaces the contents of /etc/diald/connect with pppd call name which is what I use to bring up my ppp link. I have set things up for modem use, and dynamic IP. When I start diald from /etc/init.d it dumps a whole load of modprobe errors Ex: modprobe: Can't locate module tap15 and many others. Then it says: diald[30416]: SLIP not supported by kernel, can't build proxy. followed by: diald[30416]: Unable to get a proxy interface. Manual control only. Nevertheless diald starts but doesn't seem to dial a connection. Any ideas? David.
Diald Problem
Hi, Looking for help with diald. Trying to set an old 486 up as a dial on demand router for my home network. Using official slink with 2.0.36 kernel. Problem. diald will not automatically connect. dctrl up-request or up in diald.options works fine. But telnet/ftp/ping to an IP address or via name will not trigger an auto dial up. Even tried telnet to other ports. Using tcpdump, netwatch. doesn't seem to be anything going to sl0. Have debug on in diald.options and nothing written to any logs (unless of course I force up the connection). I'm not trying to do anything tricky. Have used other's working /etc/diald, but they don't work for me. After booting netstat -nr command shows: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.0.2 0.0.0.0 255.255.255.255 UH 552 65536 0 sl0 192.168.1.0 0.0.0.0 255.255.255.0 U 1500 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 3584 0 0 lo 0.0.0.0 0.0.0.0 0.0.0.0 U 552 65536 0 sl0 Please reply directly. Not sure my mail-list registration is working. Thanks. -CURT
Re: diald problem
On Mon, 17 May 1999, Pollywog wrote: I had to reinstall Linux, and I did not have everything I needed on my backup floppies. I thought I had backed up all my config files, so I believe I accidentally deleted stuff. Anyhow, when my ISP drops me during long downloads, I am allowed to come right back, and diald took care of this for me until now, because I lost the diald.options file I was using. There is an option (I have checked the man pages but cannot find it) that I had set to four seconds so that if I get disconnected, I come back in 4 seconds, not 30. Anyone know what that option is? I have redial-timeout, but that does not seem to be it. I am doing lots of this stuff by trial and error. Pollywog Did you get an answer to this? I do not use diald, but there are option under ppp that may help you, so on the off chance that this will do you some good, I'm sending it on. My system reconnects if the line is dropped for a couple of minutes. I looked in my /etc/ppp/peers/provider and found the last command is persist. Here are items from the pppd man page, and from /etc/ppp/options. Can these be used to detect disconnect and after 4 seconds effect reconnect? From the man 8 pppd page: lcp-echo-failure n If this option is given, pppd will presume the peer to be dead if n LCP echo-requests are sent without receiving a valid LCP echo-reply. If this happens, pppd will terminate the connection. Use of this option requires a non-zero value for the lcp-echo- interval parameter. This option can be used to enable pppd to terminate after the physical connec- tion has been broken (e.g., the modem has hung up) in situations where no hardware modem control lines are available. lcp-echo-interval n If this option is given, pppd will send an LCP echo-request frame to the peer every n seconds. Normally the peer should respond to the echo- request by sending an echo-reply. This option can be used with the lcp-echo-failure option to detect that the peer is no longer connected. I find these settings in the /etc/ppp/options file: # If this option is given, pppd will send an LCP echo-request frame to # the peer every n seconds. Under Linux, the echo-request is sent when # no packets have been received from the peer for n seconds. # Normally the peer should respond to the echo-request by sending an # echo-reply. This option can be used with the lcp-echo-failure # option to detect that the peer is no longer connected. lcp-echo-interval 30 # If this option is given, pppd will presume the peer to be dead if n # LCP echo-requests are sent without receiving a valid LCP echo-reply. # If this happens, pppd will terminate the connection. Use of this # option requires a non-zero value for the lcp-echo-interval parameter. # This option can be used to enable pppd to terminate after the physical # connection has been broken (e.g., the modem has hung up) in # situations where no hardware modem control lines are available. lcp-echo-failure 4 --David David Teague, [EMAIL PROTECTED] Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. (Hoping this is useful!)
Re: diald problem
On 21-May-99 David B.Teague wrote: On Mon, 17 May 1999, Pollywog wrote: I had to reinstall Linux, and I did not have everything I needed on my backup floppies. I thought I had backed up all my config files, so I believe I accidentally deleted stuff. Anyhow, when my ISP drops me during long downloads, I am allowed to come right back, and diald took care of this for me until now, because I lost the diald.options file I was using. There is an option (I have checked the man pages but cannot find it) that I had set to four seconds so that if I get disconnected, I come back in 4 seconds, not 30. Anyone know what that option is? I have redial-timeout, but that does not seem to be it. I am doing lots of this stuff by trial and error. Pollywog Did you get an answer to this? Diald is working now. I was looking for redial-timeout :) thanks -- Andrew
Re: diald problem
On 21-May-99 David B.Teague wrote: On Mon, 17 May 1999, Pollywog wrote: I had to reinstall Linux, and I did not have everything I needed on my backup floppies. I thought I had backed up all my config files, so I believe I accidentally deleted stuff. Anyhow, when my ISP drops me during long downloads, I am allowed to come right back, and diald took care of this for me until now, because I lost the diald.options file I was using. There is an option (I have checked the man pages but cannot find it) that I had set to four seconds so that if I get disconnected, I come back in 4 seconds, not 30. Anyone know what that option is? I have redial-timeout, but that does not seem to be it. I am doing lots of this stuff by trial and error. Pollywog Did you get an answer to this? I do not use diald, but there are option under ppp that may help you, so on the off chance that this will do you some good, I'm sending it on. My system reconnects if the line is dropped for a couple of minutes. I looked in my /etc/ppp/peers/provider and found the last command is persist. Here are items from the pppd man page, and from /etc/ppp/options. Can these be used to detect disconnect and after 4 seconds effect reconnect? From the man 8 pppd page: lcp-echo-failure n If this option is given, pppd will presume the peer to be dead if n LCP echo-requests are sent without receiving a valid LCP echo-reply. If this happens, pppd will terminate the connection. Use of this option requires a non-zero value for the lcp-echo- interval parameter. This option can be used to enable pppd to terminate after the physical connec- tion has been broken (e.g., the modem has hung up) in situations where no hardware modem control lines are available. lcp-echo-interval n If this option is given, pppd will send an LCP echo-request frame to the peer every n seconds. Normally the peer should respond to the echo- request by sending an echo-reply. This option can be used with the lcp-echo-failure option to detect that the peer is no longer connected. I find these settings in the /etc/ppp/options file: # If this option is given, pppd will send an LCP echo-request frame to # the peer every n seconds. Under Linux, the echo-request is sent when # no packets have been received from the peer for n seconds. # Normally the peer should respond to the echo-request by sending an # echo-reply. This option can be used with the lcp-echo-failure # option to detect that the peer is no longer connected. lcp-echo-interval 30 # If this option is given, pppd will presume the peer to be dead if n # LCP echo-requests are sent without receiving a valid LCP echo-reply. # If this happens, pppd will terminate the connection. Use of this # option requires a non-zero value for the lcp-echo-interval parameter. # This option can be used to enable pppd to terminate after the physical # connection has been broken (e.g., the modem has hung up) in # situations where no hardware modem control lines are available. lcp-echo-failure 4 --David David Teague, [EMAIL PROTECTED] Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. (Hoping this is useful!)
diald problem
I had to reinstall Linux, and I did not have everything I needed on my backup floppies. I thought I had backed up all my config files, so I believe I accidentally deleted stuff. Anyhow, when my ISP drops me during long downloads, I am allowed to come right back, and diald took care of this for me until now, because I lost the diald.options file I was using. There is an option (I have checked the man pages but cannot find it) that I had set to four seconds so that if I get disconnected, I come back in 4 seconds, not 30. Anyone know what that option is? I have redial-timeout, but that does not seem to be it. I am doing lots of this stuff by trial and error. thanks -- Andrew
Diald problem
I am having some problem with diald. Iam using it with ppp and ip masquerade. I have an internal network which I assign the standard 192.168.0.x This is working fine. The modem is connected to the linux box. If I don't use diald, pppd works fine and I am able to go out using ip masquerade, no problem. Now, the problem start when I add diald. When it dial out, it some how does not change the default route from pointing at sl0 to ppp0 so the network can't go out. So what I do is at the ip-up and ip-down scripts I manually delete the default sl0 before ppp is up and add default sl0 when ppp is down. This makes it work. But am I doing it correctly? I thought diald is supposed to handle all this rerouting?? TIA -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Diald problem
Hi, On Sun, Jul 26, 1998 at 10:43:56AM +0800, Jieyao wrote: I am having some problem with diald. Iam using it with ppp and ip masquerade. I have an internal network which I assign the standard 192.168.0.x This is working fine. The modem is connected to the linux box. If I don't use diald, pppd works fine and I am able to go out using ip masquerade, no problem. Now, the problem start when I add diald. When it dial out, it some how does not change the default route from pointing at sl0 to ppp0 so the network can't go out. So what I do is at the ip-up and ip-down scripts I manually delete the default sl0 before ppp is up and add default sl0 when ppp is down. This makes it work. But am I doing it correctly? I thought diald is supposed to handle all this rerouting?? Yes, it is. Do you have defaultroute in your diald.options file? Below is my diald.options. connect-timeout 200 fifo /etc/diald/diald.ctl redial-timeout 5 ip-down /etc/diald/ip-down ip-up /etc/diald/ip-up accounting-log /var/log/diald.log mode ppp crtscts modem lock device /dev/ttyS2 speed 115200 local 194.222.63.202 remote 158.152.1.222 pppd-options 194.222.63.202:158.152.1.222 defaultroute connect /etc/diald/connect include /etc/diald/standard.filter TIA Regards -- Robbie Murray -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Diald problem
Michael Legart wrote: Well, I just use the things scripts in /etc/diald. Not long ago, it worket fine but it looks like my isp has changest something... Before, the first question was : Annex username:, then Annex password:, and then at last: annex. The last one is now removed, but have have removed the part in the script, with the annex stuff. Allso, my modem hangs up, just 1-2 secs. after carrier detect. A quick look at the /etc/diald/connect script yielded the following: # When debugging a connection, set DEBUG to -v to increase chat's # verbosity and to report on this script's progress. WARNING: # THIS MIGHT CAUSE YOUR PASSWORD TO SHOW UP IN THE SYSTEM LOGS # DEBUG=-v I would suggest uncommenting the DEBUG=-v line and then looking in your system logs to see exactly what is going on. It should be a breeze to solve from there. Paul Serice -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Diald problem
At 11:07 28-09-97 -0500, Paul Serice wrote: Sep 28 11:19:57 badpixel connect: Connected Sep 28 11:19:57 badpixel connect: Loggin in Sep 28 11:19:57 badpixel diald[674]: Connect script failed. Sep 28 11:19:58 badpixel diald[674]: Delaying 30 seconds before clear to dial. Looks like your Connect script failed. :-) Yep! If you're using chat ... Well, I just use the things scripts in /etc/diald. Not long ago, it worket fine but it looks like my isp has changest something... Before, the first question was : Annex username:, then Annex password:, and then at last: annex. The last one is now removed, but have have removed the part in the script, with the annex stuff. Allso, my modem hangs up, just 1-2 secs. after carrier detect. -- Regards, [EMAIL PROTECTED] icq uin: 2565176 - pgpN4QZJsgjYz.pgp Description: PGP signature
Diald problem
Hi! I have some problems with diald: Sep 28 11:19:37 badpixel diald[674]: Running connect (pid = 681). Sep 28 11:19:37 badpixel connect: Initializing Modem Sep 28 11:19:37 badpixel connect: Dialing system Sep 28 11:19:57 badpixel connect: Connected Sep 28 11:19:57 badpixel connect: Loggin in Sep 28 11:19:57 badpixel diald[674]: Connect script failed. Sep 28 11:19:58 badpixel diald[674]: Delaying 30 seconds before clear to dial. I can't seem to figure out what's wrong... could someone send me a example of the connect file? Or ideas about what else could me wrong. Thanks! -- Regards, [EMAIL PROTECTED] icq uin: 2565176 - pgphZftoLPiVx.pgp Description: PGP signature
Re: Diald problem
Michael Legart wrote: Hi! I have some problems with diald: Sep 28 11:19:37 badpixel diald[674]: Running connect (pid = 681). Sep 28 11:19:37 badpixel connect: Initializing Modem Sep 28 11:19:37 badpixel connect: Dialing system Sep 28 11:19:57 badpixel connect: Connected Sep 28 11:19:57 badpixel connect: Loggin in Sep 28 11:19:57 badpixel diald[674]: Connect script failed. Sep 28 11:19:58 badpixel diald[674]: Delaying 30 seconds before clear to dial. I can't seem to figure out what's wrong... could someone send me a example of the connect file? Or ideas about what else could me wrong. Thanks! Looks like your Connect script failed. :-) If you're using chat as your connect script, when you execute diald from the command line, add the -v command line parameter to the chat portion of your command line. For example, connect chat -v -f login.script where the rest of the command line has been omitted. Then go look in /var/log/messages to see exactly what is causing your connect script to fail. man chat for exactly what -v or -V will do for you. Oh yeah, your password will more than likely show up in your logs. You'll want to delete all those occurrences. Paul Serice -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: diald problem
Reply-to: [EMAIL PROTECTED] To:debian-user@lists.debian.org Subject: diald problem Date: Mon, 02 Jun 1997 22:01:00 +0200 From: Giuseppe Vacanti [EMAIL PROTECTED] Howdy, On my system at fairly regular intervals (every couple of days) diald dies without reason. When that happens the routing table shows no sign of sl0. The pid file is left in place (which suggests that diald didn't exit cleanly). No traces are left in any of the logs. Has anybody else experienced something like this? Thanks, Giuseppe Yes, it does that sometimes. Try starting it from /etc/inittab with the respawn option, that way every time it dies it reappears. Stephen. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
diald problem
Howdy, On my system at fairly regular intervals (every couple of days) diald dies without reason. When that happens the routing table shows no sign of sl0. The pid file is left in place (which suggests that diald didn't exit cleanly). No traces are left in any of the logs. Has anybody else experienced something like this? Thanks, Giuseppe -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
ppp diald problem
hi i have a problem vith diald daemon..it start correctly, set up slip line ant others, but..if i try connect to site out of my internal network, nothing happend...diald NOT START ppp daemon and second problem: i try solve this problem to running pon/poff script . i need to allow to run this by 5 others users i set +s to scripts zand related programs (pppd, chat...) but if pon is started by one users, it can't be stoped by others any hints? peter
Re: ppp diald problem
On Tue, 08 Apr 1997 09:54:48 +0200 Peter Bodnar ([EMAIL PROTECTED]) wrote: i have a problem vith diald daemon..it start correctly, set up slip line ant others, but..if i try connect to site out of my internal network, nothing happend...diald NOT START ppp daemon Which version of diald are you running ? What are your conffiles ? Phil.
diald problem half fixed
well, it occurs to me that my connect option should just run chat, not pppd connect chat ..., so I've fixed this (although not tested yet). Still unsure about the gateway problem; I guess it might be fixed (since nobody was setting a default route last time, since diald didn't think we'd connected) but I'm not sure. hamish -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
