Difference between revisions of "Mesh/Tracking"

Jump to navigation Jump to search
153 bytes removed ,  01:22, 10 October 2013
m
(Created page with "sudomesh does not want to do any tracking or logging, nor do we wish to facilitate any tracking or logging. = MAC address tracking = Since batman-adv operates on layer 2, i...")
 
Line 11: Line 11:
= MAC address logging =
= MAC address logging =


We have to log at least some sort of hash of MAC addresses at the exit nodes in order to ensure that the same device does not see the splash page constantly. This is problematic since a normal hashing algorithm could probably be brute-forced given the effective in-use pool size of MAC addresses, especially if the type of device is known in advance. The solution seems to be to use a hashing algorithm that has some percentage of false positives, such that several MAC addresses would hash to the same value. The only side-effect would be that some devices would not show the splash page when they should. This is ok. It's unclear if not logging MAC addreses is really that important, since anyone listening to network traffic would be able to see which devices connect.
We have to log at least some sort of hash of MAC addresses at the exit nodes in order to ensure that the same device does not see the splash page constantly. This is problematic since a normal hashing algorithm could probably be brute-forced given the effective in-use pool size of MAC addresses, especially if the type of device is known in advance. The solution seems to be to use a hashing algorithm that has some percentage of false positives, such that several MAC addresses would hash to the same value. The only side-effect would be that some devices would not show the splash page when they should. This is ok.

Navigation menu