Live data from Hacker News

IPv6 is the only way forward

ankshilp.in

261–270 of 350 posts

Re: IPv6 is the only way forward

#262

Earlier quoted context omitted.

Please don't put words in my mouth. I did not say "Because pfSense, does really bad things." How pfSense works is fairly reasonable if every IPv6 deployment had been as the original designers intended, ie you have a static prefix. It's just that the way IPv6 ended up getting deployed in practice was often not aligned with that original vision. And that has been a large source of IPv6 frustration.

There's a few things here that are a bit iffy tbh! I can't see why an ISP is dynamically changing the IPv6 addressing for a client, but if that's what is going on, then v6 NPT is your friend (RFC6296 - https://datatracker.ietf.org/doc/html/rfc6296 ). But pfsense's behaviour is a bit iffy too, unless when you say 'public IP', you mean the IPv6 address being used on the pfsense facing the clients? (I'm assuming it's us…

opnsense can use the delegated prefix for DHCPv6, it then automatically becomes the “LAN net” firewall alias and you can refer to it in a firewall rule I believe. I assume it’s the same for pfsense and I suspect they are not the only ones.

Re: IPv6 is the only way forward

#263
post #111

Earlier quoted context omitted.

Or ... people can use the DoD/Mod and assorted other space to get their IPv4 allocations. There is a ton of unused space in IPv4. Reserved, allocated but entirely unused. Also take back some /8's from greedy companies that don't need all that space. stares at HP When I say take I mean take as in a forceful annex and a timeline.

> Or ... people can use the DoD/Mod and assorted other space to get their IPv4 allocations. Someone did the math on this: > Now, average daily assignment rates have been running at above 10 /8s per year, for 2010, and approached 15 /8s towards the end. This means any reclamation effort has to recover at least 15 /8s per year just to break even on 2010’s growth. That’s 5.9% of the total IPv4 address space, or 6.8% of…

There are 'only four billion IPv4 addresses, and there are eight billion people on the planet. There are just as many smartphones (I have two: personal and work)

Unless all of these devices are running a dedicated full time server that must be reachable inbound by everyone this is not required. At any given time "all the people" are not online. That is why DHCP (per ISP) takes care of this. Maybe some day all the people may become terminally online but I would not count on it.

Yeah some day IPv6 may be required. Maybe in 100 years or so. IPv4 has plenty of unused allocated addresses that can be ripped away from greedy people. There was a time when ARIN would check to see what was in use and would take back anything people were squatting on. I think the reclamation project works if we dont assume everything has to be reachable as a server.

I should add that cell phones (where people are terminally online) were already IPv6 a long time ago for the most part so it's really a non issue. The only risk I see is if someone wanted to start a new massive dedicated server and VPS provider. Most of those are dual stack IPv4+IPv6 now and doing that means clawing some IPv4 space away from those I mentioned earlier.

Re: IPv6 is the only way forward

#264

For everyone getting into the details about how all of this should work please look at RFC7084: Basic Requirements for IPv6 Customer Edge Routers https://www.rfc-editor.org/rfc/rfc7084 It describes in detail what a home router needs to be doing to make all of this work seamlessly. Things work so well that half the world has working IPv6 already. Openwrt pretty much implements all of this out of the box. If you are st…

And I know the homenet WG has concluded but I found RFC 7368 IPv6 Home Networking Architecture Principles[1] interesting as well, including its discussion of reachability and RFC 6092 Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet Service.[2] IPv6 still occasionally seem more flaky than IPv4 with some set ups though.

[1] https://datatracker.ietf.org/doc/html/rfc7368.html#section-3...

[2] https://datatracker.ietf.org/doc/html/rfc6092

Re: IPv6 is the only way forward

#265

Earlier quoted context omitted.

There's a few things here that are a bit iffy tbh! I can't see why an ISP is dynamically changing the IPv6 addressing for a client, but if that's what is going on, then v6 NPT is your friend (RFC6296 - https://datatracker.ietf.org/doc/html/rfc6296 ). But pfsense's behaviour is a bit iffy too, unless when you say 'public IP', you mean the IPv6 address being used on the pfsense facing the clients? (I'm assuming it's us…

It's a legal requirement in Europe for privacy. A long term static address is a personal identifier.

Does the mailman come around and change house numbers and street names every month, too?

Re: IPv6 is the only way forward

#266

Can someone pity me enough to explain how to do DNS on ipv6 while using slaac? All I want to do is give every machine on my network a friendly hostname like storage.lan, timsPhone.lan, etc without having to run BIND (if possible), or dhcpd. I have heard of zeroconf for ipv4, but the catch is I want this to work across several different platforms like Windows , freebsd, Linux, etc. I also don't want to use static addr…

You are looking for mDNS which is the modern name for zeroconf/Bonjour/etc. The URL suffix is .local (storage.local, myphone.local, myprinter.local). Most modern OSes support it out of the box, but also don't advertise their names on mDNS until you ask them nicely (travel through a maze of Settings and Firewall options). mDNS supports IPv6 just fine/works on IPv6 only LANs. https://en.wikipedia.org/wiki/Multicast_DNS

Thank you. I may have tried this previously, but I think my router was blocking traffic between WiFi and wired. I will try this again. Appreciate it

Re: IPv6 is the only way forward

#267

I'm surprised how few people are talking about ULAs. For any home network where you don't have a reserved global address space from your ISP, it makes sense to configure a ULA on your router and use it for all internal hosts, and the ISP assigned address is only used for Internet access. This does not require NAT/Npt and you have the best of both worlds.

Unmentioned in the Wikipedia article is RFC 7368 IPv6 Home Networking Architecture Principles[1] that discusses them as well.

> A home network running IPv6 should deploy ULAs alongside its globally unique prefix(es) to allow stable communication between devices (on different subnets) within the homenet

[1] https://datatracker.ietf.org/doc/html/rfc7368.html#section-2...

Re: IPv6 is the only way forward

#268
post #90

Earlier quoted context omitted.

It's possible for Indian ISPs to buy IPv4 addresses and assign them to customers. Maybe not for $5/month but if you're willing to pay US prices (plus tax) you should be able to get US quality service.

Yes, but they can't do that if every Indian wants one, and they especially can't do that if every Chinese person wants one at the same time. IPv4 is 32 bits. It has a hard cap of ~4 billion addresses. China and India alone have 2.85 billion people. Add in the United States and Europe, and now nobody else gets an IP address. South America, Canada, Mexico, Australia, Africa, the middle east, the rest of Southeast Asia,…

My point in mentioning pricing is that the Indian and Chinese middle class can have IPv4 addresses; the rest can't.

Re: IPv6 is the only way forward

#269

I'm surprised how few people are talking about ULAs. For any home network where you don't have a reserved global address space from your ISP, it makes sense to configure a ULA on your router and use it for all internal hosts, and the ISP assigned address is only used for Internet access. This does not require NAT/Npt and you have the best of both worlds.

If you want to have an airgapped network, sure. For most people it doesn't make sense. You'll just get the worst of of both worlds.

RFC 7368 for home networks recommends the use of ULA locally.

> A home network running IPv6 should deploy ULAs alongside its globally unique prefix(es) to allow stable communication between devices (on different subnets) within the homenet

> When an IPv6 node in a homenet has both a ULA and a globally unique IPv6 address, it should only use its ULA address internally and use its additional globally unique IPv6 address as a source address for external communications.

Re: IPv6 is the only way forward

#270

Earlier quoted context omitted.

> so ipv6 is now a social justice issue? I'll send you the $2 a month for a elastic IP . And the billion people in India? The billion in China? The billion on the continent of Africa? And even in the US: > Our [American Indian] tribal network started out IPv6, but soon learned we had to somehow support IPv4 only traffic. It took almost 11 months in order to get a small amount of IPv4 addresses allocated for this use.…

“Got in early” vs “invented it”?

> “Got in early” vs “invented it”?

PSINet/Cogent got 38/8 in 1994: did they invent it? Ford got 19/8 in 1995: how about them?

How many places and people/companies didn't have the ability to go to a RIR in the 1990s or 2000s and get an allocation because their local infrastructure (power, telecom) wasn't developed at the time? So because they got computers, fibre, smartphones later they're SOL?

Post reply on HN