The lag is not at the local end. Say you move from Module C to Module B, and I have my UrCall=WY0X. The lag is in how long it takes your gateway to tell mine where you have moved to. I / we have not tested this lately, but several months ago, between Temple and Bruceville the lag measured 8 to 12 minutes. Last week and KR7ST C was calling K5CTX B. KB5B using KR7ST C with UrCall=/K5CTX B. Folks on K5CTX B heard KB5B just fine because KR7ST knew the IP for K5CTX B. I am pretty sure (but not certain) that KR7ST is not using a fixed IP. Anyhow folks on K5CTX B with UR=/KR7ST C and also UR=KB5B could not be heard on the KR7ST C repeater. KB5B is a valid user on KR7ST. To me this is a pretty sure (but not certain) sign of lag in the update telling K5CTX the IP for KR7ST C. (Thought being KR7ST had acquired a different IP address that had not propagated thru the system).
73, Steve NU5D Nate Duehr wrote: > Steve S. Bosshard (NU5D) wrote: > > >> One touch can really lag when the called station changes bands or >> repeaters. > Does it still lag after the recent patch to keep a local routing table? > I was under the impression that the patch would not only help local > routing as people switched bands, but was also used to route inbound > gateway streams as well. > > Nate WY0X >
