View Single Post
Old 02-05-2012, 10:48 AM   #17
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,695
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by knc1
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.
You're assuming that I haven't already (but I prefer Ethereal... I'm old-fashioned).
I already know the answers to my own questions: I've never caught my Kindle transmitting anything large enough to represent the log file it collects. I'm not making fun... I'd be sincerely interested if someone caught their Kindle doing so red-handed. I'm just not interested in assumptions that packets being sent to a particular net-range contain log data. I want someone to show me that data. Because frankly... I'm tired of pouring through log files that time and time again reveal tiny transmissions not capable of carrying data of any "log-file" substance.

Perhaps your data will eventually prove me wrong—and I'll certainly be willing change my stance if/when it does. Good luck!
DiapDealer is offline   Reply With Quote