From: Thomas Peroutka (Thomas@xxxxxxxxxxx)
Date: Wed May 09 2001 - 04:42:11 GMT-3
Hello Andrew,
I4d say this is an excellent idea for a workaround! But than I get
another problem:
the only way to realize it would be an access-list for interesting
traffic on the dial-up link like this:
dialer-list 1 protocol ip list 110
And in this case, another problem occurs: if I specify just ip in this
access-list with
access-list 110 permit ip any any
and I start a download over this bri interface, the download is _not_
interesting traffic, that means during the download, the idle timer
increases and after the idle timeout, the line is disconnected :-( and
I absolutely don4t know why.
If I do it with
dialer-list 1 protocol ip permit
I don4t have any problems. I am running 12.1(3), but I also tried it
with 12.0(7) and 11.3(14), all the same behaviour.
Any idea with this?
-- Viele Gr|sse/ Best regards, Thomas mailto:Thomas@Peroutka.deTuesday, May 08, 2001, 10:13:40 PM, you wrote:
AL> I wonder what the effect of using a time based access list on udp123 once a AL> week would be on the NTP algorithm?
AL> Andy
AL> -----Original Message----- AL> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of AL> Thomas Peroutka AL> Sent: 08 May 2001 08:36 AL> To: Julie Stewart AL> Cc: ccielab@groupstudy.com AL> Subject: Re[2]: ntp poll interval
AL> Hello Julie,
AL> yeah, that4s what it sounds like - but it would be quite a pitty if AL> you have to poll ntp servers over an ISDN dialup line which would be AL> almost a leased line then. I wonder why it should not be possible to AL> change the interval like you can do it in several unix and windows AL> apps :-(
AL> -- AL> Viele Gr|sse/ Best regards, AL> Thomas mailto:Thomas@Peroutka.de
AL> Friday, May 04, 2001, 5:56:05 PM, you wrote:
JS>> Thomas,
JS>> At http://www.cisco.com/warp/customer/620/ntpassoc.html I found the JS>> following:
JS>> "The poll field [in the output of 'show ntp associations'] represents AL> the JS>> polling interval (in seconds) between NTP poll packets. As the NTP AL> server JS>> and client are better synced and there aren't dropped packets, this AL> number JS>> increases to a maximum of 1024. The offset field is the calculated AL> offset JS>> (in milliseconds) between the client and server time. The client slows AL> down JS>> or speeds up its clock to match the server's time value. The offset JS>> decreases toward zero over time. It probably will never reach zero since AL> the JS>> packet delay between the client and server is never exactly the same, so AL> the JS>> client NTP can't ever exactly match its clock with the server's."
JS>> That leads me to think that the polling interval and offset are dynamic JS>> internals of ntp that change with the state of the connection between AL> the JS>> server and client and cannot be changed manually.
JS>> Julie
JS>> ----- Original Message ----- JS>> From: "Thomas Peroutka" <Thomas@Peroutka.de> JS>> To: <ccielab@groupstudy.com> JS>> Sent: Friday, May 04, 2001 7:31 AM JS>> Subject: ntp poll interval
>>> Hi there, >>> >>> does anybody know a possibility to change the ntp polling interval >>> (which is 64 s per default and RFC) on a cisco router? >>> >>> >>> -- >>> Best regards, >>> Thomas mailto:Thomas@Peroutka.de >>> **Please read:http://www.groupstudy.com/list/posting.html JS>> **Please read:http://www.groupstudy.com/list/posting.html AL> **Please read:http://www.groupstudy.com/list/posting.html **Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:36 GMT-3