Linked by Howard Fosdick on Mon 21st Nov 2011 07:48 UTC
Google Last June, CNET disclosed that Google collects and publishes the estimated locations of millions of phones, laptops, and other Wi-Fi devices. All without their owner's knowledge or permission. Google has finally announced how to exclude your home network from this database. Simply append "_nomap" to its name. Details over at CNET. Left unsaid is why the burden is placed on millions of individuals to opt-out, instead of on perpetrator Google.
Permalink for comment 497868
To read all comments associated with this story, please click here.
RE[4]: Comment by clhodapp
by Soulbender on Mon 21st Nov 2011 23:14 UTC in reply to "RE[3]: Comment by clhodapp"
Member since:

I really would like to know what you mean here, because in practice having duplicate MAC addresses will break things like DHCP and switching hubs which rely on a MAC address's uniqueness.

Sure, it causes problem..on the local segment. It wont matter one bit if a company in Stockholm and one in Manila have devices with the same MAC address. A MAC does not need to, and in practice sometimes isn't, globally unique. I know some folks who have managed to end up with two different network cards (from the same manufacturer, of course) with the same MAC address.

(Didn't you just say it doesn't need to be unique?)

Yes, it has to be locally unique but not globally.

I'm not here to re-engineer it, but the unique id doesn't need to be static between sessions

You have a point there, it doesn't have to be the same forever. Of course, the problem is how you define a session. Is it the time between reboots of the AP? Individual TCP/IP sessions? As I said, it might be possible but not practically feasible for various reasons. Plus there's also some, very limited, security in knowing what MAC address your AP and workstations has. That said, MAC address security is an administrative burden for anything but tiny home networks and easy to circumvent.

Reply Parent Score: 2