Wilson Fletcher wrote:
> From: Lourdes Jones[SMTP:[EMAIL PROTECTED]]
>>Take a good at the diald man page and investigating the
Sheesh, what happened to that line? :)
Take a good look at the diald man page and investigate the
>>impulse option.
>> impulse 600,0,0
>>might be a good option if you want to keep the connection up
>>for a minimum
>>of 10 minutes before checking any idle timers.
>
> hmmm, good idea. Might be better than creating a range of
> rules when my
> needs are pretty simple. ie. if the link is being used keep it up and
> provide a buffer of say 10 minutes idle time before disconnecting.
That's why I mentioned it. :)
impulse is typically used inside a restrict block (though I know no reason
why it can't be used outside of one). worse case you stick it after the
default restrict line
'restrict * * * * *'
> Can't you just put a sleep in the script or something similar
> ? ie. Maybe
> your S98Diald could start a diald wrapper as a background
> process that
> would sleep for x seconds and then start diald like you
> previously would
> have done in your S98diald script ? .... just a thought since
> that way it
> wouldn't really matter how fast the machine was ...
I could but an extra connection every 4 to 12 weeks is not worth my time
making the additional changes. I wouldn't reboot that often but I'm
addicted to installing new kernels once they are proven to work on my
workstation.
Besides it makes the initial login ugly since the messages are now out of
sync. :)
>>Note: bind starts querying the root servers immediately in order to
>>determine response times and which server it should poll
>>first in future.
>>The bind users list claims bad things can happen if you don't
>>allow this to
>>happen. I never had any problems but your experience may vary.
>
> I'm willing to give it a go if it breaks my system I can
> always reverse the
> changes.
>
> > BUT !!!!! Why did it go out on port 1024 ? I thought it
> > should be 53 to 53 or is that only for Xfers ?
>
>>Most likely because you are using bind 8 (instead of bind 4
>>which always
>>used port 53). You can setup bind 8 to always use port 53 if
>>you prefer.
>
>>--
>>options {
>> query-source address * port 53;
>>// ... your existing options
>>};
> Yes I might give this a go and see what the implications are
> to my network.
What it means is that named can't ever bring up the link. Folks who use
this and like it are playing resolver games. The second or third
resolv.conf nameserver entry is the one that brings up the link. You must
also have the additional entries on every machine on the network.
In effect, the client app times out waiting on named to resolve (timeout
generally happens before named gives the non-existent reply), it then tries
the secondary nameserver (which is a machine out on the internet) and that
connection brings up the link.
Joke (Atsawin Chowanakritsanakul) mentioned using the following rule:
ignore udp udp.dest=udp.domain,ip.tot_len=45
Try using it in addition to the existing named transfer rules.
Lourdes
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
