I haven't read the entire thread, but this may be relevant. If not, you
know where to find the delete key.
I live in a life care community - one of 450 people in 300 apartments on
3 floors. When I moved in a year ago, I could get Internet from the
house cable, and they provided the modem. I boug
Yes, it will be interesting to see how well wifi rtt/tof does indoors with
plenty of multipath. But for sure sub microsecond.
On Sat, Jan 14, 2017 at 6:32 PM Bob Camp wrote:
> Hi
>
>
>
>
>
> > On Jan 14, 2017, at 5:29 PM, Scott Stobbe
> wrote:
>
> >
>
> > I don't think wifi is ever going to be
On 1/14/17 4:25 PM, Bob Camp wrote:
Hi
Maybe the magic stamping has been hiding in the chips all along.
What’s pretty clear is that if it’s there, it’s well hidden ….
or totally unstandardized - it might be one of those "we put it in for
manufacturing test" features, and everyone does it diffe
Hi
Maybe the magic stamping has been hiding in the chips all along.
What’s pretty clear is that if it’s there, it’s well hidden ….
Bob
> On Jan 14, 2017, at 7:04 PM, jimlux wrote:
>
> On 1/14/17 3:32 PM, Bob Camp wrote:
>> Hi
>>
>>
>>> On Jan 14, 2017, at 5:29 PM, Scott Stobbe wrote:
>>>
On 1/14/17 3:32 PM, Bob Camp wrote:
Hi
On Jan 14, 2017, at 5:29 PM, Scott Stobbe wrote:
I don't think wifi is ever going to be a real-time system, as it shares the
ether with all other ISM devices. That said even 1 ms of variation is still
4 orders of magnitude greater than the actual time o
Hi
> On Jan 14, 2017, at 5:29 PM, Scott Stobbe wrote:
>
> I don't think wifi is ever going to be a real-time system, as it shares the
> ether with all other ISM devices. That said even 1 ms of variation is still
> 4 orders of magnitude greater than the actual time of flight.
>
> The precision
I don't think wifi is ever going to be a real-time system, as it shares the
ether with all other ISM devices. That said even 1 ms of variation is still
4 orders of magnitude greater than the actual time of flight.
The precision time aspect will most certainly be done in hardware, even if
it's just
May I suggest to turn the 24 hours reset period into a parameter?
On Fri, Jan 13, 2017 at 8:45 PM, Tom Van Baak wrote:
> Mark, Ole,
>
> Yes, averaging can both enhance precision but also destroy information. In
> many cases too much data is a bad thing. The solution is to add another
> dimensio
Hi
Here’s what I am seeing:
64 bytes from 192.168.2.2: icmp_seq=3700 ttl=64 time=5.025 ms
64 bytes from 192.168.2.2: icmp_seq=3701 ttl=64 time=4.579 ms
64 bytes from 192.168.2.2: icmp_seq=3702 ttl=64 time=1.511 ms
64 bytes from 192.168.2.2: icmp_seq=3703 ttl=64 time=1.601 ms
64 bytes from 192.168
kb...@n1k.org said:
> Ok, what I see is that every few hours, I get a ârogue delayâ on a single
> ping. How would NTP help me spot a single transit with a 250 ms round trip
> and identify the time it occured? Keep in mind that NTP is going to
> throttle back to a very low level of âchatâ
Sorry as this is perhaps a bit off topic but I've tried to make this somewhat
time nuts relevant.
Over the years I found ping tests have worked quite well (at least on WAN
links) to roughly measure network bandwidth. When I used to visit remote sites
with WAN links I would often perform severa
I merely used the ping to demonstrate Wireshark's packet time stamping
(though in this case, it seems that the router responds immediately).
FWIW, a couple of NTP packets got captured too with a 34 ms round trip. I
was actually looking for an ARP request/response in consecutive packets on
the grou
Hi
> On Jan 14, 2017, at 1:38 PM, Chris Albertson
> wrote:
>
> On Sat, Jan 14, 2017 at 7:46 AM, Bob Camp wrote:
>
>> Hi
>>
>> Ok, what I see is that every few hours, I get a “rogue delay” on a single
>> ping. How
>> would NTP help me spot a single transit with a 250 ms round trip and
>> ide
Hi
The issue with using Wireshark is that it still is looking at a ping. It may
tag the
event to one more digit, but all of the earlier mentioned issues with pings are
still there. Simply put, they aren’t the greatest thing for testing timing.
Bob
> On Jan 14, 2017, at 1:51 PM, Orin Eman wrot
You could run a network monitor, Wireshark for example...
https://wiki.wireshark.org/CaptureSetup/WLAN
There are specialized WIFI capture programs, but they tend to be designed
to break into networks rather than monitor performance - kismet/kismac. I
run them every so often to check for malfeasa
On Sat, Jan 14, 2017 at 7:46 AM, Bob Camp wrote:
> Hi
>
> Ok, what I see is that every few hours, I get a “rogue delay” on a single
> ping. How
> would NTP help me spot a single transit with a 250 ms round trip and
> identify the
> time it occured? Keep in mind that NTP is going to throttle back
Hi
> On Jan 14, 2017, at 12:44 PM, jimlux wrote:
>
> On 1/14/17 8:35 AM, Bob Camp wrote:
>> Hi
>>
>
>>
>> I also believe that ping data is one way to come up with an upper bound on
>> just how awful WiFi timing can be. If others have a similar single shot
>> measure
>> of WiFi round trip th
On 1/14/17 8:35 AM, Bob Camp wrote:
Hi
I also believe that ping data is one way to come up with an upper bound on
just how awful WiFi timing can be. If others have a similar single shot measure
of WiFi round trip that can be run on a wide range of devices, I’d certainly be
just
as interest
Hi
We have a double issue here:
1) It’s a problem because “not enough information was given"
2) It’s a problem because “we are talking about it to much”
Sorry, but there is absolutely no way at all both of those criteria can
be met by me.
I do believe that WiFi time protocols are an on topic
On 1/14/17 7:53 AM, John Hawkinson wrote:
I tried to engage with you off-list and give you some pointers on this, but
that does not seem to be working. Consumer wifi driver problems are manifestly
inappropriate for this list, and trying to do both at once leads to gross
confusion :( I know this
On 1/14/17 7:46 AM, Bob Camp wrote:
Hi
Ok, what I see is that every few hours, I get a “rogue delay” on a single ping.
How
would NTP help me spot a single transit with a 250 ms round trip and identify
the
time it occured? Keep in mind that NTP is going to throttle back to a very low
level
of
This has nothing to do with time-nuts, can it stop please?
[ I don't know what forum to send you to for "weird wifi problems"; there
is probably no good one, because it is a very common consumer problem :( ]
NTP was mentioned because you (Bob Camp) had not defined the problem
very well, and asked
Hi
This is very much a one laptop to one router issue. The other couple dozen
laptops
and tablets do not see an issue. The whole thing started when a series of
firmware
updates rolled through a few weeks ago. The laptop is *maybe* 12 feet from the
router.
It’s running at 5 GHz so microwaves (a
Hi
Ok, what I see is that every few hours, I get a “rogue delay” on a single ping.
How
would NTP help me spot a single transit with a 250 ms round trip and identify
the
time it occured? Keep in mind that NTP is going to throttle back to a very low
level
of “chat” quite quickly…..
While this *
24 matches
Mail list logo
