An great thorough reply! If I cared enough to undertake all this, I'd do exactly what you suggested. Fortunately I have more curiosity than concern 😜 & PLUG has adequately appeased my curiosity.
On Wed, Apr 10, 2024, 17:45 Russell Senior <russ...@personaltelco.net> wrote: > On Wed, Apr 10, 2024 at 5:18 PM mo <mowgli...@gmail.com> wrote: > > > How do I gather more data? > > > > Get between your phone and whatsapp servers and run tcpdump -s0 -w > /tmp/capture.pcap -i $LANIFACE ether host $PHONEMACADDR, where $LANIFACE is > your router's interface closer to the phone and $PHONEMACADDR is the MAC > address that the phone is using on your network. Note that modern phone > operating systems randomize the MAC address they use on each wifi network > for the sake of privacy. You'll have to figure out what it is using either > by looking in the phone or by looking at the DHCP lease your router > provided. Then, let it run for as long as it takes to send your whatsapp > message, but minimize other traffic on the phone, because the tcpdump will > need to copy/store everything to and from the device. Then copy the > /tmp/capture.pcap to a real computer and run wireshark on it, e.g.: > wireshark capture.pcap > > And then stare at wireshare until it makes sense. The payloads of the > messages will be encrypted, but the envelopes/headers and their timing > should provide information. > > That's how I would do approach the problem. > > > > > > > On Wed, Apr 10, 2024, 16:09 Russell Senior <russ...@personaltelco.net> > > wrote: > > > > > It could be some weird DNS or maybe even ipv6 related timeout problem. > > Wild > > > added guessing. More data means less guessing. > > > > > > -- > > > Russell Senior > > > russ...@personaltelco.net > > > > > > On Wed, Apr 10, 2024, 14:13 Tomas Kuchta <tomas.kuchta.li...@gmail.com > > > > > wrote: > > > > > > > On Wed, Apr 10, 2024, 06:02 Russell Senior < > russ...@personaltelco.net> > > > > wrote: > > > > > > > > > If you manage your own gateway, using OpenWrt for example, you > could > > > put > > > > > your own diagnostic tools (like tcpdump) on that gateway and, for > > > > example, > > > > > capture the transactions from your phone to whatsapp servers. If > you > > > > don't > > > > > manage your own gateway, then you might be stuck asking > > > > CenturyLink/Quantum > > > > > what's going on. > > > > > > > > > > I'm not a whatsapp user, so I don't have any personal insight. > > > > > > > > > > -- > > > > > Russell Senior > > > > > russ...@personaltelco.net > > > > > > > > > > On Tue, Apr 9, 2024 at 10:43 PM mo <mowgli...@gmail.com> wrote: > > > > > > > > > > > Hi. I've Quantum fiber. It has latency issues with WhatsApp. Any > > idea > > > > > why & > > > > > > how to resolve this? > > > > > > > > > > > > I've no other issues with them. Using the WiFi. All other sites > > apps > > > > etc > > > > > > have no noticeable latency. WhatsApp takes minutes to send a > > message > > > & > > > > > > receives messages minutes after someone sends. However if I turn > of > > > > WiFi > > > > > & > > > > > > switch to cellular data (TMO) it immediately sends & receives the > > > > > > backlogged messages. The latency can be up to 10 min sometimes. > > > > > > > > > > > > Thoughts? > > > > > > > > > > > > > > > > > > > Minutes difference is unlikely to be network related. Unless, of > > course, > > > a > > > > three letter agency? > > > > > > > > It may be that the cell phone app update events are more timely when > it > > > can > > > > see the celular network than with WiFi. > > > > > > > > Just my 2¢, > > > > T > > > > > > > > > > > > > > > > > > >
