Linked by Howard Fosdick on Mon 21st Nov 2011 07:48 UTC
Permalink for comment 497862
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2011-01-28
Soulbender,
"In practice MAC addresses are not unique (and don't actually have to be)."
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.
Sometime adapters make it possible to spoof MAC addresses and do ARP spoofing - which can even have legitimate uses like automatic failover, but then original host will stop receiving packets.
"Probably not because it would have been impossible or at least not practically feasible. How would your devices locate each other without a unique, visible address?"
(Didn't you just say it doesn't need to be unique?)
I'm not here to re-engineer it, but the unique id doesn't need to be static between sessions, it just needs to be unique per AP at any given time.