Concerned about what is being sent to Amazon but not quite ready to take measures such as those in the "Big Brother" threads?
Such as:
https://www.mobileread.com/forums/sho...t=51371&nojs=1
Being a newcomer to the Amazon Kindle I wanted to do some exploring before doing any modifications to my new Keyboard+3g reader.
My new toy is nicknamed: Chatty Kathy for well known reasons.
First step was to disable her 3G connectivity to cell phone services.
The quick and easy way - unplug her 3G modem/radio (its a mini-PCIe card).
Yes, if your careful, the card can be removed without removing the antenna assemble.
Whoot! Now I have a Kindle Keyboard - Wifi only model.
The Wifi access I can control since the only access points in-range are my own.
After a few hours of packet capture from initial power-on, and a bit of study...
I decided to brute force the matter in my gateway/router using source based, policy routing rules.
Your gateway/router does run Linux, doesn't it? If not, adapt the following:
Day 2:
Based on the Day one activity, you want to give these ranges special routing treatment before Chatty Kathy can talk to them:
Code:
CIDR: 23.0.0.0/12
CIDR: 50.16.0.0/14 (the log collector)
CIDR: 72.21.192.0/19
CIDR: 107.20.0.0/14
CIDR: 184.72.0.0/15
CIDR: 204.246.160.0/19
CIDR: 205.251.192.0/18
CIDR: 207.171.160.0/19
Example:
Where
169.254.0.225/27 is the range you assigned to your wireless devices;
Then in your Linux based, gateway router, do:
Code:
$ sudo ip rule add from 169.254.0.225/27 to 23.0.0.0/12 prohibit
$ sudo ip rule add from 169.254.0.225/27 to 50.16.0.0/14 prohibit
$ sudo ip rule add from 169.254.0.225/27 to 72.21.192.0/19 prohibit
$ sudo ip rule add from 169.254.0.225/27 to 107.20.0.0/14 prohibit
$ sudo ip rule add from 169.254.0.225/27 to 184.72.0.0/15 prohibit
$ sudo ip rule add from 169.254.0.225/27 to 204.246.160.0/19 prohibit
$ sudo ip rule add from 169.254.0.225/27 to 205.251.192.0/18 prohibit
$ sudo ip rule add from 169.254.0.225/27 to 207.171.160.0/19 prohibit
Which should result in:
Code:
$ ip rule show
0: from all lookup local
32758: from 169.254.0.225/27 to 205.251.192.0/18 prohibit
32759: from 169.254.0.225/27 to 207.171.160.0/19 prohibit
32760: from 169.254.0.225/27 to 50.16.0.0/14 prohibit
32761: from 169.254.0.225/27 to 204.246.160.0/19 prohibit
32762: from 169.254.0.225/27 to 184.72.0.0/15 prohibit
32763: from 169.254.0.225/27 to 107.20.0.0/14 prohibit
32764: from 169.254.0.225/27 to 72.21.192.0/19 prohibit
32765: from 169.254.0.225/27 to 23.0.0.0/12 prohibit
32766: from all lookup main
32767: from all lookup default
Unless you typo'd something or already have other policy rules.
The above has been tested in a controlled packet capture environment for:
Wifi-On
Wifi-Off
Wakeup-Wifi-On
Wakeup-Wifi-Off
Adding bookmarks and highlights
Doing web searchs
Chatty Kathy asks for domain addresses in those ranges for each of the above cases, but of course can't get out to them.
I will get all of the related reference materials and packet captures up on my homesite RSN, you all know how that goes.