Quote:
Originally Posted by DiapDealer
Except that you said:
If you haven't recorded the payloads, why have you made the assertion that that particular net-range is responsible for receiving Kindle log-files? Shouldn't you wait until the evidence is in to make that claim if you're just doing unbiased research?
|
You caught me:
Please replace: "not recorded the payload" with "hit restart rather than stop" button in Wireshark in the single case of the log transmittal discovery. Hitting "restart" deletes the file rather than saving it first.
Wireshark saves on packet boundaries, it is not possible to "not save the payload" when you save a packet with Wireshark.
I should probably go back and edit that sentence now that you have proof-read it for me.
Translation: The evidence was passing in front of my eyes as I edited the first post to include that additional range. I just fat-fingered the saving of it.
Wireshark is an OpenSource tool, available for nearly all operating systems.
I suggest you install it and monitor that specific address range for yourself.
I am not the only person qualified to watch packets, you can do it also.
Important Note:
This is
__not__ "Unbiased Research" - I posted my bias and flagged it as "Off Topic" in a post above.