You can't really fix it because your medium (the atmosphere) is really awful for transmitting data. Wireless is unreliable and you're seeing proof of that. WISP? Meaning Wireless ISP? If so, there's your likely answer. In other words, while having troubles with my application, if I run a trace at the same time I get the above result while simultaneously pinging the suspect host shows a normal ping. Why does this latency only show up during a trace-route and not with a normal ping? The lack of performance I see in my application coincides with this. The high latency can persist for only a few seconds up to a few minutes at a time.ĮDIT Yes this is a bad example of a trace showing a definite problem, but after repeated tests there is never latency >100ms before hop 9, that's why I thought it could be a problem.Ī pathping during the event produces the following: Source to Here This Node/Link Pinging subsequent hops after the suspected node gives reasonable round-trip times as well. However, if I directly ping the host everything seems fine (~10ms round-trip). Which seems to indicate that the problem is the host at 10.250.200.1. If I do a trace route you can see the path though the back-haul network: Tracing route to The latency is detectable in online games and other streaming applications. I have been working with my ISP (which is a WISP, actually Fixed Broadband Wireless) trying to figure out why I intermittently get high latency.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |