In message <b2e27b9f4e.druck@xxxxxxxxxxxxxxxx> David J. Ruck <druck@xxxxxxxxxxxx> wrote: > On 3 Jan 2007 Tom Hughes <tom@xxxxxxxxxx> wrote: >> It's more likely that it is related to the routing cache (assuming >> that the RISC OS stack is based on a recent enough BSD stack to have >> that) which will implicitly create a host route for each host you >> connect to and then (after you haven't talked to it for a while) timeout >> that host route and delete it. That is functionality that is entirely >> internal to the stack. > > That would certainly explain why it hasn't been possible to narrow it down to > a specific application in Harriet's case, and seems to have after any period > of internet activity regardless of the application in use. > >> The point of creating the implicit host routes is to use them to cache >> things like round trip times and MTU values so that if you connect to >> the same host again it has a better idea what values to start with. > > The question then being how come this is going wronng for Harriet almost > constantly on two different machines and has only occured once for me. > Could there be some issue with the values returned when talking to a > particular ISP or remote site causing an overflow? It shouldn't do - those are just numbers stored in the routing table entry and have nothing to do with managing it's lifetime. Tom -- Tom Hughes (tom@xxxxxxxxxx) http://www.compton.nu/ --- To alter your preferences or leave the group, visit //www.freelists.org/list/iyonix-support Other info via //www.freelists.org/webpage/iyonix-support