Your ISP (or my ISP) having an address on file and providing a mapping of IP Address (IPv4 or IPv6) to a physical geographic address is an entirely separate problem I _think_ 🤔 -- At least in Australia any entity that provides consumers goods or services has to "know their customer" -- However I argue that tracking (an ISP) an IPv4/IPv6 address on the Internet to a geographic address under a few kms (sorry, I work in metric 🤪) should be illegal -- Much like Targeting Advertising to groups of "people" less than 5,000 is against the law (at least it was in the US when I last worked at Facebook™).
Your ISP (or my ISP) having an address on file and providing a mapping of IP Address (IPv4 or IPv6) to a physical geographic address is an entirely separate problem I _think_ 🤔 -- At least in Australia any entity that provides consumers goods or services has to "know their customer" -- However I argue that tracking (an ISP) an IPv4/IPv6 address on the Internet to a geographic address under a few kms (sorry, I work in metric 🤪) should be illegal -- Much like Targeting Advertising to groups of "people" less than 5,000 is against the law (at least it was in the US when I last worked at Facebook™).
> the Internet kind of requires IP Addresses to even function in the first place
True, but a VPN can be used to mask your real IP address because all of your network traffic is relayed through another computer with a different IP address.
> p2p protocols like WebRTC require peer addresses to be able to communicate with one another
In principle, yes, but they don't need to be able to communicate directly as long as both clients can communicate with a TURN server. At least, that's how I understand it.
> True, but a VPN can be used to mask your real IP address because all of your network traffic is relayed through another computer with a different IP address.
This is true, however you still leak your IP address to _that_ VPN provider anyway. So it comes down to who you trust, your ISP or your VPN provider(s)? 😅
> In principle, yes, but they don’t need to be able to communicate directly as long as both clients can communicate with a TURN server. At least, that’s how I understand it.
Actually I _think_ you're right, STUN/ICE are specifications for services that allow two or more peers to figure out what their direct IP addresses are so they can _communicate_ in a p2p fashion, whilst I _think_ TURN is a specification/service for peers to communicate and exchange (generally) media through a central server.
You still leak your IP address with _that_ TURN server however.
> True, but a VPN can be used to mask your real IP address because all of your network traffic is relayed through another computer with a different IP address.
This is true, however you still leak your IP address to _that_ VPN provider anyway. So it comes down to who you trust, your ISP or your VPN provider(s)? 😅
> In principle, yes, but they don’t need to be able to communicate directly as long as both clients can communicate with a TURN server. At least, that’s how I understand it.
Actually I _think_ you're right, STUN/ICE are specifications for services that allow two or more peers to figure out what their direct IP addresses are so they can _communicate_ in a p2p fashion, whilst I _think_ TURN is a specification/service for peers to communicate and exchange (generally) media through a central server.
You still leak your IP address with _that_ TURN server however.
> So it comes down to who you trust \n\n\n\n\n\n\n\n, your ISP or your VPN provider(s)?
My VPN provider, 100%. I've talked about my ISP in the past.
Besides, I don't *need* to trust them as much as my ISP. Under normal circumstances, this is the important information that your ISP can know about you:
* All of your personal information, down to a home address
* The IP addresses to which you're connecting
* Information leaked by unencrypted traffic (DNS queries, etc.)
As long as the VPN provider doesn't require any personal information, and mine doesn't, you're making it so no single party has all of that information. The IP address cloaking is an added benefit for me.
> You still leak your IP address with that TURN server however.
If your WebRTC implementation isn't broken, the TURN server sees your traffic as coming from the VPN server, just like any thing else you connect to through that tunnel. It's the same story if I open a port and make a direct p2p connection.*
> So it comes down to who you trust [more]\n[more]\n[more]\n[more]\n, your ISP or your VPN provider(s)?
My VPN provider, 100%. I've talked about my ISP in the past.
Besides, I don't *need* to trust them as much as my ISP. Under normal circumstances, this is the important information that your ISP can know about you:
* All of your personal information, down to a home address
* The IP addresses to which you're connecting
* Information leaked by unencrypted traffic (DNS queries, etc.)
As long as the VPN provider doesn't require any personal information, and mine doesn't, you're making it so no single party has all of that information. The IP address cloaking is an added benefit for me.
> You still leak your IP address with that TURN server however.
If your WebRTC implementation isn't broken, the TURN server sees your traffic as coming from the VPN server, just like any thing else you connect to through that tunnel. It's the same story if I open a port and make a direct p2p connection.*
> So it comes down to who you trust [more], your ISP or your VPN provider(s)?
My VPN provider, 100%. I've talked about my ISP in the past.
Besides, I don't *need* to trust them as much as my ISP. Under normal circumstances, this is the important information that your ISP can know about you:
* All of your personal information, down to a home address
* The IP addresses to which you're connecting
* Information leaked by unencrypted traffic (DNS queries, etc.)
As long as the VPN provider doesn't require any personal information, and mine doesn't, you're making it so no single party has all of that information. The IP address cloaking is an added benefit for me.
> You still leak your IP address with that TURN server however.
If your WebRTC implementation isn't broken, the TURN server sees your traffic as coming from the VPN server, just like any thing else you connect to through that tunnel. It's the same story if I have a port opened and make a direct p2p connection.*
> So it comes down to who you trust \n\n, your ISP or your VPN provider(s)?
My VPN provider, 100%. I've talked about my ISP in the past.
Besides, I don't *need* to trust them as much as my ISP. Under normal circumstances, this is the important information that your ISP can know about you:
* All of your personal information, down to a home address
* The IP addresses to which you're connecting
* Information leaked by unencrypted traffic (DNS queries, etc.)
As long as the VPN provider doesn't require any personal information, and mine doesn't, you're making it so no single party has all of that information. The IP address cloaking is an added benefit for me.
> You still leak your IP address with that TURN server however.
If your WebRTC implementation isn't broken, the TURN server sees your traffic as coming from the VPN server, just like any thing else you connect to through that tunnel. It's the same story if I open a port and make a direct p2p connection.*
> So it comes down to who you trust \n\n\n\n, your ISP or your VPN provider(s)?
My VPN provider, 100%. I've talked about my ISP in the past.
Besides, I don't *need* to trust them as much as my ISP. Under normal circumstances, this is the important information that your ISP can know about you:
* All of your personal information, down to a home address
* The IP addresses to which you're connecting
* Information leaked by unencrypted traffic (DNS queries, etc.)
As long as the VPN provider doesn't require any personal information, and mine doesn't, you're making it so no single party has all of that information. The IP address cloaking is an added benefit for me.
> You still leak your IP address with that TURN server however.
If your WebRTC implementation isn't broken, the TURN server sees your traffic as coming from the VPN server, just like any thing else you connect to through that tunnel. It's the same story if I open a port and make a direct p2p connection.*
> So it comes down to who you trust [more][more=][more][more=][more][more=][more][more=], your ISP or your VPN provider(s)?
My VPN provider, 100%. I've talked about my ISP in the past.
Besides, I don't *need* to trust them as much as my ISP. Under normal circumstances, this is the important information that your ISP can know about you:
* All of your personal information, down to a home address
* The IP addresses to which you're connecting
* Information leaked by unencrypted traffic (DNS queries, etc.)
As long as the VPN provider doesn't require any personal information, and mine doesn't, you're making it so no single party has all of that information. The IP address cloaking is an added benefit for me.
> You still leak your IP address with that TURN server however.
If your WebRTC implementation isn't broken, the TURN server sees your traffic as coming from the VPN server, just like any thing else you connect to through that tunnel. It's the same story if I open a port and make a direct p2p connection.*
> So it comes down to who you trust [more][more=], your ISP or your VPN provider(s)?
My VPN provider, 100%. I've talked about my ISP in the past.
Besides, I don't *need* to trust them as much as my ISP. Under normal circumstances, this is the important information that your ISP can know about you:
* All of your personal information, down to a home address
* The IP addresses to which you're connecting
* Information leaked by unencrypted traffic (DNS queries, etc.)
As long as the VPN provider doesn't require any personal information, and mine doesn't, you're making it so no single party has all of that information. The IP address cloaking is an added benefit for me.
> You still leak your IP address with that TURN server however.
If your WebRTC implementation isn't broken, the TURN server sees your traffic as coming from the VPN server, just like any thing else you connect to through that tunnel. It's the same story if I open a port and make a direct p2p connection.=*
> So it comes down to who you trust [more][more][more][more][more][more][more][more], your ISP or your VPN provider(s)?
My VPN provider, 100%. I've talked about my ISP in the past.
Besides, I don't *need* to trust them as much as my ISP. Under normal circumstances, this is the important information that your ISP can know about you:
* All of your personal information, down to a home address
* The IP addresses to which you're connecting
* Information leaked by unencrypted traffic (DNS queries, etc.)
As long as the VPN provider doesn't require any personal information, and mine doesn't, you're making it so no single party has all of that information. The IP address cloaking is an added benefit for me.
> You still leak your IP address with that TURN server however.
If your WebRTC implementation isn't broken, the TURN server sees your traffic as coming from the VPN server, just like any thing else you connect to through that tunnel. It's the same story if I open a port and make a direct p2p connection.*
> So it comes down to who you trust [more], your ISP or your VPN provider(s)?
My VPN provider, 100%. I've talked about my ISP in the past.
Besides, I don't *need* to trust them as much as my ISP. Under normal circumstances, this is the important information that your ISP can know about you:
* All of your personal information, down to a home address
* The IP addresses to which you're connecting
* Information leaked by unencrypted traffic (DNS queries, etc.)
As long as the VPN provider doesn't require any personal information, and mine doesn't, you're making it so no single party has all of that information. The IP address cloaking is an added benefit for me.
> You still leak your IP address with that TURN server however.
If your WebRTC implementation isn't broken, the TURN server sees your traffic as coming from the VPN server, just like any thing else you connect to through that tunnel. It's the same story if I open a port and make a direct p2p connection.*
> If your WebRTC implementation isn’t broken, the TURN server sees your traffic as coming from the VPN server, just like any thing else you connect to through that tunnel. It’s the same story if I open a port and make a direct p2p connection.
Sorry I meant in the case of standard Internet connectivity (without a VPN).
> If your WebRTC implementation isn’t broken, the TURN server sees your traffic as coming from the VPN server, just like any thing else you connect to through that tunnel. It’s the same story if I open a port and make a direct p2p connection.
Sorry I meant in the case of standard Internet connectivity (without a VPN).