Live data from Hacker News

New patches allow building Linux IPv6-only

phoronix.com

121–130 of 198 posts

Re: New patches allow building Linux IPv6-only

#121

Earlier quoted context omitted.

Why not just type in "mates-pc" and have functional mDNS and not have to memorize a bunch of numbers? Why not just expect your OS's DNS setup to actually just work?

Because mDNS usually doesn't work and just expecting it to work doesn't change that?

> Why not just expect your OS's DNS setup to actually just work?

Maybe use an OS or DNS stack that isn't terrible?

Incredible asking for a not-broken DNS and IP stack is just too far out there when it seems most of the closed source OS platforms seem to manage just fine.

Or let me guess, you've specifically configured it to not "leak" such useful information?

Re: New patches allow building Linux IPv6-only

#122
post #48
post #24

Earlier quoted context omitted.

You already have a public IP address the only difference is if you have a rotating IP address which is orthogonal to IPv6. The only difference is most ISPs rotate IPv4 but not IPv6. Heck IPv6 allows more rotation of IPs since it has larger address spaces.

IPv6 can "leak" MAC addresses of connected devices "behind the firewall" if you don't have the privacy extensions / random addresses in use. There are a number of footguns for privacy with IPv6 that you need to know enough to avoid.

All desktop/mobile OSes today use "Stable privacy addresses" for inbound traffic (only if you are hosting something long-term) and "Temporary addresses" for outbound traffic and P2P (video/voice calls, muliplayer games...) that change quickly (old ones are still assigned to not break long-lived connections but are not used for new ones).

Re: New patches allow building Linux IPv6-only

#123

Earlier quoted context omitted.

Why not just type in "mates-pc" and have functional mDNS and not have to memorize a bunch of numbers? Why not just expect your OS's DNS setup to actually just work?

Because mDNS usually doesn't work and just expecting it to work doesn't change that?

Skill issue. Works fine for me in a mixed Linux/Apple environment.

Re: New patches allow building Linux IPv6-only

#124
post #54

Earlier quoted context omitted.

[flagged]

You can't correlate the number of addresses with the number of devices because IPv6 temporary addresses exist. If you enable temporary addresses, your computer will periodically randomly generate a new address and switch to it. https://www.rfc-editor.org/rfc/rfc8981.html

[deleted]

Re: New patches allow building Linux IPv6-only

#125

Earlier quoted context omitted.

You can't correlate the number of addresses with the number of devices because IPv6 temporary addresses exist. If you enable temporary addresses, your computer will periodically randomly generate a new address and switch to it. https://www.rfc-editor.org/rfc/rfc8981.html

I feel like this is a silly narrowing of the problem for normal, retail users. My priority isn't masking "the number of addresses" or devices. My desire is to not have a persistent identifier to correlate all my traffic. The whole idea of temporary addresses fails at this because the network prefix becomes the correlation ID. I'm not an IPv4 apologist though. Clearly the NAT/DHCP assignments from the ISP are essentia…

> The whole idea of temporary addresses fails at this because the network prefix becomes the correlation ID.

So the same as the public IPv4 on a traditional home NAT setup?

Re: New patches allow building Linux IPv6-only

#126
post #49

As it should. Date notwithstanding, I would actually enjoy if there was a manually induced latency penalty for "legacy IP" that needs to be manually turned off on Linux. I know some people don't care at all, but the internet was made to be addressable. IPv6 is the only shot we have to go back to that.

As sad as it makes me to admit, I don't think IPv6 is ever going to happen without government intervention. Adoption is flat at under 50% over the past year. IPv6 doesn't benefit big tech. SNI routing and NAT work pretty well for centralized platforms. AWS will gladly rent us IPv4 addresses until the end of time.

SNI routing is such a bad way to do what should be L3 problem that people implemented PROXY protocol to send information about user's endpoint address without doing MITM.

Re: New patches allow building Linux IPv6-only

#127
post #125

Earlier quoted context omitted.

I feel like this is a silly narrowing of the problem for normal, retail users. My priority isn't masking "the number of addresses" or devices. My desire is to not have a persistent identifier to correlate all my traffic. The whole idea of temporary addresses fails at this because the network prefix becomes the correlation ID. I'm not an IPv4 apologist though. Clearly the NAT/DHCP assignments from the ISP are essentia…

> The whole idea of temporary addresses fails at this because the network prefix becomes the correlation ID. So the same as the public IPv4 on a traditional home NAT setup?

Most home users do not have a static public IPv4 address - they have a single address that changes over time.

Re: New patches allow building Linux IPv6-only

#128
post #22

Earlier quoted context omitted.

- I don't want my interfaces to have multiple IP addresses - I don't want my devices to have public, discoverable IPs - I like NAT and it works fine - I don't want to use dynamic DNS just so I have set up a single home server without my ISP rotating my /64 for no reason (and no SLAAC is not an answer because I don't want multiple addresses per interface) - I don't need an entire /48 for my home network IPv6 won't hel…

IPv4 is not holding back home setups, nobody cares about NAT at home. The place where it hurts is small VPSs, from AWS to mom and pop hosters, the cost of addresses is becoming significant compared to low cost VPSs.

Plenty of people care about CGNAT making it impossible to connect to them.

Re: New patches allow building Linux IPv6-only

#129

Earlier quoted context omitted.

Because mDNS usually doesn't work and just expecting it to work doesn't change that?

Skill issue. Works fine for me in a mixed Linux/Apple environment.

I didn't write any mDNS software. Blame those guys.
Post reply on HN