diald question
Hi all, I have a small network with a debian gnu/linux box with modem sharing connection with windows clients (using masquerade). I want to install and configure diald to automagically dials when some windows client try to acess the Internet. I installed diald and I'm lost. I dont know how to configure it. and how to test it. any help will be great. Thanks, Paulo Henrique
Re: diald question
John Hasler wrote: Pollywog writes: Do I need *both* a diald.conf and a diald.options? diald.conf? I don't have one, nor does the diald man page mention it. But it's included in /usr/doc/diald/examples which seems to be misleading. But apparently you're not the maintainer. Why do I always think you are? Hope we can work on pppconfig together. Regards, Joey -- Never trust an operating system you don't have source for! Please always Cc to me when replying to me on the lists.
diald question
Do I need *both* a diald.conf and a diald.options? I am using only diald.options and cannot seem to get disconnect-timeout 0 to work when I put in in diald.options. When I get disconnected, diald waits 30s to reconnect. thanks -- Andrew [PGP5.0 Key ID 0x5EE61C37]
Re: diald question
Pollywog writes: Do I need *both* a diald.conf and a diald.options? diald.conf? I don't have one, nor does the diald man page mention it. I am using only diald.options and cannot seem to get disconnect-timeout 0 to work when I put in in diald.options. 'disconnect-timeout' doesn't do what you want. It tells diald how long to wait for the disconnect script to complete before giving up. Most people don't need a disconnect script at all. You want 'redial-timeout'. -- John HaslerThis posting is in the public domain. [EMAIL PROTECTED] Do with it what you will. Dancing Horse Hill Make money from it if you can; I don't mind. Elmwood, Wisconsin Do not send email advertisements to this address.
Re: diald question
On 14-Mar-99 John Hasler wrote: Pollywog writes: Do I need *both* a diald.conf and a diald.options? diald.conf? I don't have one, nor does the diald man page mention it. I am using only diald.options and cannot seem to get disconnect-timeout 0 to work when I put in in diald.options. 'disconnect-timeout' doesn't do what you want. It tells diald how long to wait for the disconnect script to complete before giving up. Most people don't need a disconnect script at all. You want 'redial-timeout'. Thanks, I probably misunderstood the diald man page. I had a diald.conf when I used Caldera OpenLinux, but it does not seem necessary in Debian. The two files have the same content, just different names, I believe. -- Andrew [PGP5.0 KeyID 0x5EE61C37]
Diald question
I just replaced my hard drive with a larger one and reinstalled hamm. I copied over my ppp and diald configuration files and ppp works fine with 'pon', but diald connects and then disconnects with the message: peer refused to authenticate All the /etc/diald files are identical to what I worked before. Does anyone have a clue as to why this is happening? Bob Bob Nielsen Internet: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] DM42nh http://www.primenet.com/~nielsen
Re: Diald question
I just replaced my hard drive with a larger one and reinstalled hamm. I copied over my ppp and diald configuration files and ppp works fine with 'pon', but diald connects and then disconnects with the message: peer refused to authenticate All the /etc/diald files are identical to what I worked before. Does anyone have a clue as to why this is happening? Check to make sure your ppp configuration files are the same. If so, pon probably starts ppp differently from the way diald does it, and you'll need to track down the differences. My guess is that you installed a newer version of pppd and that your /etc/ppp/options file is now different. Specifically, the auth option is now set. If you read the man page, you'll see that you probably shouldn't mess with this file to fix the problem. (See man diald for more details, and search for pppd-options.) Instead, append -- noauth to the end of the command you use to start diald. Paul Serice
diald question
Hello, I have been messing with my diald/ppp setup and I have a strange problem. Basically everything works fine, that is, when I try to use some command that needs the net, my modem dials in and off I go. diald will then hang up after a specified time of inactivity. This I believe is controlled by the file /etc/diald/standard.filters. I have been using dctrl to look at timeouts and noticed that although my general tcp timeout is set to 10 minutes, fetchmail generates tcp packets that start as though they'd keep the link up for 10 minutes, but after about 1 second it changes to keeping the link up for only 5 seconds. If the host that fetchmail is trying to connect is not in my /etc/hosts, then everything still works since the host query udp packets have 30 second timeouts. (My modem takes about 20 seconds to connect.) I am using partially upgraded Debian 1.2. In particular, diald is in version 0.16.4-7, and ppp is 2.2.0f-23. I included a copy of my /etc/diald/standard.filters in case it's relevant. I'd be glad to hear your insights, Janos. # This is a pretty complicated set of filter rules. # (These are the rules I use myself.) # # I've divided the rules up into four sections. # TCP packets, UDP packets, ICMP packets and a general catch all rule # at the end. #-- # Rules for TCP packets. #-- # General comments on the rule set: # # In general we would like to treat only data on a TCP link as signficant # for timeouts. Therefore, we try to ignore packets with no data. # Since the shortest possible set of headers in a TCP/IP packet is 40 bytes. # Any packet with length 40 must have no data riding in it. # We may miss some empty packets this way (optional routing information # and other extras may be present in the IP header), but we should get # most of them. Note that we don't want to filter out packets with # tcp.live clear, since we use them later to speedup disconnects # on some TCP links. # # We also want to make sure WWW packets live even if the TCP socket # is shut down. We do this because WWW doesn't keep connections open # once the data has been transfered, and it would be annoying to have the link # keep bouncing up and down every time you get a document. # # Outside of WWW the most common use of TCP is for long lived connections, # that once they are gone mean we no longer need the network connection. # We don't neccessarily want to wait 10 minutes for the connection # to go down when we don't have any telnet's or rlogin's running, # so we want to speed up the timeout on TCP connections that have # shutdown. We do this by catching packets that do not have the live flag set. # --- start of rule set proper --- # When initiating a connection we only give the link 15 seconds initially. # The idea here is to deal with possibility that the network on the opposite # end of the connection is unreachable. In this case you don't really # want to give the link 10 minutes up time. With the rule below # we only give the link 15 seconds initially. If the network is reachable # then we will normally get a response that actually contains some # data within 15 seconds. If this causes problems because you have a slow # response time at some site you want to regularly access, you can either # increase the timeout or remove this rule. accept tcp 15 tcp.syn # Keep named xfers from holding the link up ignore tcp tcp.dest=tcp.domain ignore tcp tcp.source=tcp.domain # (Ack! SCO telnet starts by sending empty SYNs and only opens the # connection if it gets a response. Sheesh..) accept tcp 5 ip.tot_len=40,tcp.syn # keep empty packets from holding the link up (other than empty SYN packets) ignore tcp ip.tot_len=40,tcp.live # make sure http transfers hold the link for 2 minutes, even after they end. # NOTE: Your /etc/services may not define the tcp service www, in which # case you should comment out the following two lines or get a more # up to date /etc/services file. See the FAQ for information on obtaining # a new /etc/services file. #accept tcp 120 tcp.dest=tcp.www #accept tcp 120 tcp.source=tcp.www # make it 10 minutes for more sluggish viewers accept tcp 600 tcp.dest=tcp.www accept tcp 600 tcp.source=tcp.www # Once the link is no longer live, we try to shut down the connection # quickly. Note that if the link is already down, a state change # will not bring it back up. keepup tcp 5 !tcp.live ignore tcp !tcp.live # an ftp-data or ftp connection can be expected to show reasonably frequent # traffic. accept tcp 120 tcp.dest=tcp.ftp accept tcp 120 tcp.source=tcp.ftp #NOTE: ftp-data is not defined in the /etc/services file provided with # the latest versions of NETKIT, so I've got this commented out here. # If you want to define it add the following line to your /etc/services: # ftp-data20/tcp # and uncomment the following two rules.
Re: diald question
On Sun, 23 Nov 1997 22:33:11 PST Janos A Csirik ([EMAIL PROTECTED] du) wrote: [snip] I have been using dctrl to look at timeouts and noticed that although my general tcp timeout is set to 10 minutes, fetchmail generates tcp packets that start as though they'd keep the link up for 10 minutes, but after about 1 second it changes to keeping the link up for only 5 seconds. If the host that fetchmail is trying to connect is not in my /etc/hosts, then everything still works since the host query udp packets have 30 second timeouts. (My modem takes about 20 seconds to connect.) [snip] I included a copy of my /etc/diald/standard.filters in case it's relevant. keepup tcp 5 !tcp.live This line says that when a tcp connection is closed, this connection will only hold the link up for 5 secs. That's probably this one you want to change: when the pop3 tcp connection is closed, the link has 5 secs to live unless you have other connections around. Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: diald question
Philippe Troin wrote: On Sat, 18 Jan 1997 11:30:33 +0800 Lu Jimmy Chenji ([EMAIL PROTECTED]) wrote: BTW, I installed Debian-1.2 base system and want to use FTP method to download more files. So I need to use diald. Diald doc tells me that in order to use diald, I must have SLIP devices in my kernel. How can I check if my kernel has SLIP devices? Secondly. is there any simple way to setup diald? Can anybody guied me? You don't have to run diald to use the ftp method. Only pppd. Actually, though that diald is not that hard to configure. You can insmod (or modprobe) slip.o, it should do the trick. To check if it's in the kernel, try a lsmod. Phil. -- In order to know what devices are compiled inside the kernel, try: cat /proc/devices FYI, you can try cat on other files in /proc as well. What they contain are obvious by their file names. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Seak Teng-Fong E-mail: [EMAIL PROTECTED] Bât 507 DRFC / SPPFTel: 33 (0) 4 42256125 CE / Cadarache Fax: 33 (0) 4 42256233 13108 Saint Paul lez Durance Cedex FRANCE -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
diald question
Hi all, First of all, I would like to express my sincere appreciation to this user group to guide me to solve my questions. BTW, I installed Debian-1.2 base system and want to use FTP method to download more files. So I need to use diald. Diald doc tells me that in order to use diald, I must have SLIP devices in my kernel. How can I check if my kernel has SLIP devices? Secondly. is there any simple way to setup diald? Can anybody guied me? Thanks in advance. Jimmy Lu -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: diald question
On Sat, 18 Jan 1997 11:30:33 +0800 Lu Jimmy Chenji ([EMAIL PROTECTED]) wrote: BTW, I installed Debian-1.2 base system and want to use FTP method to download more files. So I need to use diald. Diald doc tells me that in order to use diald, I must have SLIP devices in my kernel. How can I check if my kernel has SLIP devices? Secondly. is there any simple way to setup diald? Can anybody guied me? You don't have to run diald to use the ftp method. Only pppd. Actually, though that diald is not that hard to configure. You can insmod (or modprobe) slip.o, it should do the trick. To check if it's in the kernel, try a lsmod. Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
