2021-05-19 21:40:06 +0000 | received badge | ● Famous Question (source) |
2021-05-19 21:40:06 +0000 | received badge | ● Notable Question (source) |
2019-09-29 13:44:09 +0000 | received badge | ● Famous Question (source) |
2019-04-29 23:59:57 +0000 | received badge | ● Taxonomist |
2018-10-26 17:51:05 +0000 | received badge | ● Popular Question (source) |
2018-08-13 01:41:46 +0000 | received badge | ● Notable Question (source) |
2018-08-13 01:41:46 +0000 | received badge | ● Popular Question (source) |
2018-03-07 15:07:40 +0000 | marked best answer | why is my NTP client timestamp wrong? This has been puzzling me for several hours now, and I'm pretty out of ideas. I'm modifying an embedded application to use NTP. I can send a request and get a reply (so I guess it's working), but my client timestamps show up in Wireshark incorrectly. They seem to be off by about 66 years, which makes me think it's related to how WS is interpreting my timestamp era, but my online research hasn't found anything. I'd attribute this to a preference setting, except that the timestamps in the response are correct. Thanks for any ideas... I realize that a snapshot would be very useful here, but I can't yet post images (or files). Edit: posting a link to a file (hope I did this right): Edit again: image file. Note the different interpretations of the transmit timestamp data: URL to this image file: |
2018-03-06 22:00:22 +0000 | received badge | ● Rapid Responder |
2018-03-06 22:00:22 +0000 | answered a question | why is my NTP client timestamp wrong? Oops. sigh... It sucks getting old and having your eyes go south (that's my excuse anyway). Thanks, cmaynard. With |
2018-03-06 19:10:17 +0000 | commented question | why is my NTP client timestamp wrong? Jaap - I apologize for the confusion -- I didn't mean to imply that the capture file was associated with the image. In |
2018-03-06 17:20:56 +0000 | edited question | why is my NTP client timestamp wrong? why is my NTP client timestamp wrong? This has been puzzling me for several hours now, and I'm pretty out of ideas. I'm |
2018-03-06 17:20:11 +0000 | edited question | why is my NTP client timestamp wrong? why is my NTP client timestamp wrong? This has been puzzling me for several hours now, and I'm pretty out of ideas. I'm |
2018-03-06 15:26:18 +0000 | received badge | ● Editor (source) |
2018-03-06 15:26:18 +0000 | edited question | why is my NTP client timestamp wrong? why is my NTP client timestamp wrong? This has been puzzling me for several hours now, and I'm pretty out of ideas. I'm |
2018-03-05 22:38:28 +0000 | asked a question | why is my NTP client timestamp wrong? why is my NTP client timestamp wrong? This has been puzzling me for several hours now, and I'm pretty out of ideas. I'm |
2018-01-03 15:02:19 +0000 | commented answer | How to capture UDP traffic and not NBNS traffic? @jaap: done, and thanks. |
2018-01-03 15:01:36 +0000 | marked best answer | How to capture UDP traffic and not NBNS traffic? Hi - I'm sure this question has been asked and answered many times, but I can't find what I'm looking for. I'm trying to apply filters so I only see traffic between two devices, and only when they're of UDP protocol. In the display filter, I use this: (ip.addr == 192.168.70.20 || ip.src == 192.168.70.22) and in Capture->Options, I've selected the (presupplied) udp filter. I'm still seeing traffic of other protocols, though. Can someone tell me what I'm doing wrong? Thanks. |
2018-01-03 15:01:36 +0000 | received badge | ● Scholar (source) |
2018-01-02 18:56:52 +0000 | commented answer | How to capture UDP traffic and not NBNS traffic? Beautiful. That helps a lot. Thanks...I'd upvote you if I could. |
2018-01-02 18:20:12 +0000 | commented answer | How to capture UDP traffic and not NBNS traffic? Thanks for the response. The protocol I'm seeing that I don't wish to is NBNS. The communication between the two devices |
2018-01-02 17:29:22 +0000 | asked a question | How to capture UDP traffic and not NBNS traffic? filtering by protocol Hi - I'm sure this question has been asked and answered many times, but I can't find what I'm loo |