Gregg Phillips..."Patriot Games"
(media.greatawakening.win)
You're viewing a single comment thread. View all comments, or full comment thread.
Comments (35)
sorted by:
Your MAC address isn't transmitted over the Internet
It doesn't have to be "transmitted over the Internet" for it to be a privacy concern.
A mobile phone broadcasts its MAC Address anytime it's in Wi-Fi range if the user doesn't disable it, which means the local businesses you frequent have a record of your MAC Address and its activity unless you disable Wi-Fi.
And, nowadays, those local businesses often outsource Wi-Fi management to an MSP, which can then combine records of your "check-ins" to different places and sell it to government agencies, advertisers, and even private investigators.
No, this isn’t a scene from Minority Report. This trash can is stalking you
Smartphone-monitoring bins in London track places of work, past behavior, and more.
Dan Goodin - 8/9/2013, 2:15 PM
https://arstechnica.com/information-technology/2013/08/no-this-isnt-a-scene-from-minority-report-this-trash-can-is-stalking-you/
Archived link- https://archive.ph/yf1nY
grapheneOS randomizes those scans and adds a very minimal level of security through obscurity.
That's a good point. Wish I had a Pixel phone to try it on.
But it is collected by hotspots, even if you don't connect to them.
Every packet is encapsulated in a frame, which has both a source and destination MAC address. Both the source and the destination MAC addresses are removed once it crosses out of the local broadcast domain (moves across a router), and are replaced with the appropriate addresses in the next broadcast domain
Truth
There is no such thing as a TCP/IP packet. Ethernet is only for the LAN, hence the MAC/Ethernet address (and the Ethernet header that contains it) doesn't get routed. Routers only route IP addresses, and see you can see that the IP packet header doesn't have a MAC address field. When a router receives an IP packet (which will contain other data from higher OSI layers relevant to other aspects of the interaction), it inspects the Destination Address header. It then inspects its routing table. If the address in that header is "known" (because it is on a local segment) then it will unwrap the message from the IP packet and wrap it in an Ethernet frame with the destination MAC address, then forward it onto the LAN via the relevant local port to be received by the target host. If not it will forward it to the appropriate IP address/router according to the data in its routing table. This "appropriate" address might just be the default route.