News for hackers. Stuff that matters.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by hitpointdrew on Monday March 06, 2023 @04:37PM (#35048008)
Who the hell is giving their Roku a public IP? How is this remotely a problem? This is 100% not the fault of Roku, and 100% the fault of the ISP. The ISP should have an IPv6 to IPv4 gateway built into their modem/router. You have a WAN port that is IPv6 and an LAN port that IPv4.

IPv6 for local networks, makes no sense is completely unnecessary, and is a hill I will die on. IPv4 is here to stay.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by ArchOversight on Monday March 06, 2023 @04:47PM (#35048132)
The ISP said they got only a limited set of IPv4 addresses, those are assigned to their CGNAT gateways. Which are expensive, especially for an Indian Reservation, not the deep pockets of some MSP.

The users are behind CG-NAT.

But instead of using IPv6 which is cheaper (no need to maintain CG-NAT, translation devices, or deal with traffic that is being routed way more expensively) the Roku devices are only streaming over IPv4.

Each new user that adds an IPv4 only device adds additional load the CG-NAT and additional capacity will need to be provisioned. That is an additional expense and burden.

Most of my traffic at my house (on Comcast) is over IPv6, because most if not all streaming services now support IPv6 for content delivery, so the small amount of data that may need to go over IPv4 when the majority can go over IPv6 reduces the load on IPv4.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by brokencode on Monday March 06, 2023 @05:02PM (#35048334)
Why does the IPv4 address need to be publicly exposed outside of a customer’s LAN? I thought you could set up NAT on a router to translate local IPv4 addresses to something IPv6 that is exposed publicly.

Is this simply bad planning from the ISP where they didn’t handle it correctly? Or is there something I’m not understanding about NAT?

I think in an ideal world all devices would be using IPv6. But I thought it would be common knowledge among network engineers that many devices still use IPv4, so you have to either handle it somehow or tell your customers that some of their devices simply won’t work.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by ArchOversight on Monday March 06, 2023 @05:12PM (#35048478)
Because the IP address the Roku is trying to reach is an IPv4 address. You can't just translate that to IPv6 and say "good luck little packet".

If you translate at the customers router that's fine and all, but now you have an IPv4 packet in an IPv6 packet, that IPv6 packet needs to get routed to a device that knows how to then turn it back into an IPv4 packet so that it can then go travel on the open internet like the electrons intended...

Once that IPv4 response come back, it needs to get translated back to IPv6, sent to the customers edge, which translates it back from IPv6 to IPv4 to send to the Roku device.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by brokencode on Monday March 06, 2023 @05:22PM (#35048598)
Oh, what a mess. I don’t like that at all.

I was assuming that there was some way to translate the IPv4 address of the server to an IPv6 one and process it that way, putting the burden of supporting IPv6 on the server side. I had no idea that Roku would actually need to be exposing an IPv4 server to handle these requests.

That makes sense then that the ISP would need some number of IPv4 addresses that it could use to communicate with IPv4 servers then on behalf of IPv4 client devices.

Shame on Roku for perpetuating this problem.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by makomk on Monday March 06, 2023 @06:30PM (#35049364)
The more usual reason why devices would be making an IPv4 request despite having an IPv6-supporting connection is precisely because the server doesn't support IPv6 - either the network it's on doesn't support it, or it's not configured for it, or more rarely the software on the other end doesn't have IPv6 support. The request can't just be translated into an IPv6 one because there's no way of knowing that the server even understands that, let alone what its associated IPv6 address is.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by zamadatix on Monday March 06, 2023 @05:04PM (#35048376)
CG-NAT (NATing centrally at the ISP's internet edge) is cheaper/simpler than something like 464xlat (NATing v4 locally over v6) since you can do the former on 2 boxes instead of 20,000. That said the 2nd option is much cooler :).
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by ArchOversight on Monday March 06, 2023 @05:10PM (#35048443)
464XLAT still requires IPv4 boxes on the edge to translate IPv6 traffic back to IPv4. Whether that is two boxes or 20,000, the same is true for other CG-NAT solutions. Someone somewhere is bearing the cost of translating.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by zamadatix on Monday March 06, 2023 @05:17PM (#35048526)
Usually you need a special box at the consumer side to do 464XLAT, it's not something you can just ask your customer's Netgear to do and it's usually more expensive if you want to provide it as the customer's rented router. CG-NAT however looks completely normal to all gear (other than the particular numbers assigned) except the 2 edge boxes. It's the ultimate cost saving kludge.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by cmeacham98 on Monday March 06, 2023 @05:22PM (#35048592)
Most modern OSes (I know for a fact Android, iOS, and Windows) support automatically doing the 4->6 translation on their side (as a matter of fact, some cellular networks in the US are ipv6 only).

I'm unsure if consumer routers would pass on the appropriate RA flag to tell the OS they need to do this in their default configuration however.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by zamadatix on Monday March 06, 2023 @05:29PM (#35048668)
Well the devices that support 464xlat already support IPv6 by definition. CG-NAT/464XLAT+Client NAT at the gateway is for the devices like the Rokus that don't support IPv6 at all.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by cmeacham98 on Monday March 06, 2023 @05:30PM (#35048684)
NAT64 doesn't work if the connection is made to a hardcoded IP(v4) address rather than DNS entry, and that's way more common than you'd think! Thus why 464XLAT and similar exist.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by zamadatix on Monday March 06, 2023 @06:03PM (#35049074)
Absolutely but CG-NAT would be NAT444 (i.e. double NAT to dual stack) not NAT64. I mean they probably did try NAT64 based on the description of the botched 1st attempt but CG-NAT would have negated the need for NAT64 in the first place. Putting a x464 CLAT that can gateway/NAT the local network everywhere would definitely achieve the same functional goal though, just more ISP devices.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by zamadatix on Monday March 06, 2023 @05:00PM (#35048311)
Realistically they are already running a large scale NAT device anyways, otherwise the v6 only clients wouldn't be able to reach v4 only internet services (hello HN server), and if they had planned to CG-NAT from the start it probably could have all been done on the same pair of internet edge routers for much less than 300k additional expense.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by Symbiote on Monday March 06, 2023 @05:12PM (#35048473)
As the article says, the Roku traffic is the overwhelming majority of that ipv4 traffic.

HN and similar mostly-text websites would barely show up on the statistics.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by zamadatix on Monday March 06, 2023 @06:59PM (#35049661)
NAT scales in both dimensions, you're just as likely to need a larger box for a larger connection table as you are a larger bandwidth.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by noAnswer on Monday March 06, 2023 @07:30PM (#35049905)
At some point you also need more IPv4-addresses. There are only 65535 ports to be mapped.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by zamadatix on Monday March 06, 2023 @07:54PM (#35050066)
At some point but remember it's not "after 65535 connections per IP" it's "after 65535 connections of the same type to the same IP per IP". That is to saythese NATs where 156.78.92.154 is a single public address on the NATing box:

  156.78.92.154:6781<->8.8.8.8:53 UDP
  156.78.92.154:6781<->8.8.8.8:53 TCP
  156.78.92.154:6781<->8.8.4.4:53 TCP
  156.78.92.154:6781<->8.8.4.4:53 UDP
Can all exist simultaneously even though only 1 port is in use and we haven't even started changing the destination IP or ports yet (e.g. 80 and 443 as the destination won't double count and thousands of web servers on different addresses can be accessed via the same source port).

With CG-NAT you can usually support somewhere around 30k customers on the free /24 you get from ARIN for having only IPv6 and needing space to translate in (for new orgs like new ISPs this is assigned immediately out of a reserved block, bypassing the waitlist for existing orgs trying to get free reclaimed space).

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by ArchOversight on Tuesday March 07, 2023 @10:01AM (#35056067)
It's also about ports. If I have 10 Gbps of IPv4 flow but my devices are licensed for and operate on 1 Gbps, I need to license 10 1 Gbps ports.

When I was last working at an ISP, various CG-NAT solutions charged not just based on the connection table, but also there was various licensing for various slide-in cards.

If the ISP is having to buy additional hardware/additional ports on upstream providers just to power their CG-NAT that is an additional cost.

If the POP where you have your CG-NAT doesn't have more bandwidth available you end up running your ports hot... so now you either need to rent a new location, get your connectivity up there and start figuring out how to route the traffic.

It's not as simple, and it all costs copious amounts of money. Especially if your IPv6 can more easily be distributed across multiple POP's with multiple forms of connectivity and traffic shaped using BGP or other solutions thereby reducing the load on a single upstream port.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by lmm on Monday March 06, 2023 @04:48PM (#35048146)
> IPv6 for local networks, makes no sense is completely unnecessary, and is a hill I will die on. IPv4 is here to stay.

Why would you make everything gratuitously complicated by having two separate forms of addressing? All that IPv4 gains you is new and exciting ways to mess up your networking. Just give every device a normal public address (of course you probably want to firewall off inbound traffic from the WAN to the LAN, but that's got nothing to do with addresses) and have a normal network rather than some bizzare frankenstein mashup.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by hitpointdrew on Monday March 06, 2023 @04:56PM (#35048250)
Why would I want any of my devices on my network to have a publicly route-able address?

> Why would you make everything gratuitously complicated by having two separate forms of addressing?

How is IPv6 itself not "gratuitously complicated". You think I am going to remember the IP of my firewall, my network switch, if it is that mess of characters that is an IPv6 address? I can easily recall 10.10.10.1 is my gateway, or that 192.168.1.1 is my gateway. You think instead setting up local DNS server and domain so I can do myrouter.lan is somehow "less complicated"?

Hard pass.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by zamadatix on Monday March 06, 2023 @05:03PM (#35048351)
fe80::1 is your gateway, fe80::2 can be your switch, fe80::blah can be your server. Let the device automatically get it's temporary public address it uses when talking through fe80::1, you shouldn't really need to know it or use it. If you really do feel free to use DHCPv6 or a static SLAAC offset of mDNS but you're just making more work for yourself if it's a home environment.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by tristanbvk on Monday March 06, 2023 @05:29PM (#35048666)
>Why would I want publically routable addresses

Hate to break it to you but that is how the internet was intended to work for end-users. Firewalls are cheap and easy to install :)

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by ownagefool on Monday March 06, 2023 @05:06PM (#35048389)
The main reason would be to do p2p without hacks / servers.

Why are you so militant against the idea?

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by dijit on Tuesday March 07, 2023 @05:10AM (#35053638)
Sunk cost fallacy.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by xxpor on Monday March 06, 2023 @05:00PM (#35048314)
Why would you need a DNS server? That's what mDNS is for.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by vetinari on Monday March 06, 2023 @05:18PM (#35048540)
Some people might have more than one subnet. Or road-warrior VPN and VPN-ing in. It is nice when your networks name resolution works, even if you are outside your network.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by xxpor on Monday March 06, 2023 @05:29PM (#35048670)
If you have multiple subnets, you almost certainly have an advanced enough router that it supports mDNS forwarding. There's no reason why it can't work across a VPN either.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by maherbeg on Monday March 06, 2023 @06:39PM (#35049474)
mDNS forwarding doesn't work on Tailscale :(
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by JohnFen on Monday March 06, 2023 @07:22PM (#35049849)
mDNS has some downsides that can be important for some. For instance, the fact that you can more easily set the same host name on multiple machines, or the fact that it uses a lot of bandwidth.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by anotherhue on Monday March 06, 2023 @07:27PM (#35049889)
I felt this way until I learned that the RFC1918s we all love (10. 192.168. etc.) have a nice v6 equivalent: fd80::1 fd80::2 ... etc.

https://www.ripe.net/participate/member-support/lir-basics/i...

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by cassianoleal on Monday March 06, 2023 @07:41PM (#35049984)
My internal v6 addressing is as such:

fd65:<16-bit-mnemonic>:<vlan-id>::/56

The 16-bit-mnemonic is something memorable to me (e.g. b37a:7357 would be addressable l33tsp34k for "beta test" - that's not the one I use :P). In this case, VLAN 10 would be in the fd65:b37a:7357:10::/56. Gateway for it is fd65:b37a:7357:10::1.

It's really not harder than IPv4 for these cases.

Servers and services are assigned static IPs either via DHCPv6 or directly on the boxes (or both as I kinda use the DHCP table as a poor man's IPAM). Other devices internal IPs and globally routable IPs are assigned through SLAAC with privacy extensions where available.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by lmm on Monday March 06, 2023 @11:03PM (#35051403)
> Why would I want any of my devices on my network to have a publicly route-able address?

So that your addressing works normally, and you don't have to deal with the same machine having two different addresses depending where you are (e.g. my photo server's address is the same whether I'm travelling or at home). Even if you only ever access your home network from outside via a VPN (which may well be a good idea), having globally unique addresses eliminates a whole bunch of possible issues - no more weirdness because the coffee shop you're in picked the same private subnet as you did.

> How is IPv6 itself not "gratuitously complicated".

IPv6 is needed for the public internet, there are just too many hosts for anything else. So you either learn IPv6 or IPv6 + another similar, but somewhat different thing.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by tristanbvk on Monday March 06, 2023 @05:28PM (#35048657)
Finally some sense. There are so many senseless IPv4 shills here. IPv6 always works, never had a problem with it.

Just switch to it alrready.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by slackdog on Monday March 06, 2023 @05:59PM (#35049020)
I'll switch when IPv4 stops working. Until then, I have no reason to switch.

> It's costing ISPs

I hate my ISP so this is actually a feature. If they add an IPv4 surcharge to my bill then I'll reconsider.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by throw0101c on Monday March 06, 2023 @10:46PM (#35051291)
> I'll switch when IPv4 stops working. Until then, I have no reason to switch.

IPv4 has stopped working for a lot of people already, especially if they're not with a fancy-pants ISP with lots of legacy IPv4 addresses already 'in the bank'. From another discussion:

> I've actually run into this [CG NAT] helping a friend host a game server on their residential internet in a more rural part of Texas. They had to call their ISP and request a static IP address at an extra cost of something like $5/mo.

* https://news.ycombinator.com/item?id=35046929

IPv4 is also not working for the Indian reservation mentioned in the article: they had to spend >$200K to support these Roku devices.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by slackdog on Tuesday March 07, 2023 @12:37PM (#35058332)
Sure, I get that. But it's their problem, not my problem. I'll only switch when it becomes my problem.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by garbagecoder on Monday March 06, 2023 @06:30PM (#35049370)
So, because I don't want to change something that works and whose predictions of demise have been grossly overstated by decades I'm a shill?

"Just switch to it." Sure, pal, You pay all of the transition costs for everyone and you got a deal.

Not everything needs or should have a public IP address much less a bunch of IOT garbage. I suspect you, like everyone else who just says, whY aReNt We On IpV6 yEt??!11 imagine that most people's security practices are like yours and most people's ability to maintain software and security practices are like yours.

They are not.

I'm holding out for a modern address space extension conceived this century that doesn't suck, or at least a naming convention that doesn't suck. But no one will change until it's really needed and "hack" that improve the Internet, even if by accident, like NAT, can't fix it.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by kalleboo on Monday March 06, 2023 @08:30PM (#35050322)
> Sure, pal, You pay all of the transition costs for everyone and you got a deal

Except at this point the costs are reversed - IPv4 costs more than IPv6. Just look at the article we're commenting on - supporting IPv4 clients is costing them a lot more. At the same time more and more cloud hosts are charging more for IPv4. In 2023 it's supporting IPv4 that costs more, not IPv6.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by JohnFen on Monday March 06, 2023 @04:58PM (#35048282)
> Why would you make everything gratuitously complicated by having two separate forms of addressing?

If it ain't broke, don't fix it? If IPv6 brings no benefit to my LAN, why should I spend all the effort needed to shift it to IPv6? I can just make the connection to the internet IPv6 and leave everything else alone.

Although I have additional friction in my case, in that I have numerous devices that are IPv4-only. So no matter what, I'd have to at least have one LAN segment that is IPv4.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by pixl97 on Monday March 06, 2023 @06:21PM (#35049280)
Because that's not the way TCP was designed in the first place. Instead you're used to hack on top of hack to make IPv4 not explode in a ball of flame there are far more billions of end points than IP addresses.

The thing is you really don't realize how shit your network experiences are because of this. Everyone is just attempting to tunnel more services via HTTP/HTTPS and the particular fun problems that entails rather than having byzantine hacks built in to their NAT routers. IPv4 is no longer fit for purpose.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by JohnFen on Monday March 06, 2023 @06:42PM (#35049499)
> to make IPv4 not explode in a ball of flame there are far more billions of end points than IP addresses.

But in my LAN, there is no IP address exhaustion. I have orders of magnitude more IP addresses than I'll ever use. IP address exhaustion applies to the internet at large. I'm not talking about that.

In the internet at large, IPv6 has to happen. In my LAN, I don't see a need for it. I can route between the IPv4 endpoints in my LAN and the IPv6 endpoints on the internet.

And because I have IPv4-only hardware on my LAN, I need an IPv4 segment to support it at the very least. So why not keep the entire LAN IPv4?

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by lmm on Tuesday March 07, 2023 @06:04PM (#35062608)
> But in my LAN, there is no IP address exhaustion. I have orders of magnitude more IP addresses than I'll ever use. IP address exhaustion applies to the internet at large. I'm not talking about that.

As long as you never VPN into or out of another network whose administrator thought the same thing. But yes.

> And because I have IPv4-only hardware on my LAN, I need an IPv4 segment to support it at the very least. So why not keep the entire LAN IPv4?

v6 uplink is going to increasingly be cheaper and/or faster than v4 uplink (as with the issue in the article), so presumably you'll want to run v6 on your LAN at least for the devices you game/stream from (and sooner or later there will be v6-only services that you want to connect to). I would think that any device not supporting IPv6 is so obsolete/unsupported as to be dangerous to connect to the internet, so you already need to deal with having two distinct segments on your LAN. But sure, if you've got good v4 uplink at a reasonable cost then no need to migrate yet.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by garbagecoder on Monday March 06, 2023 @06:32PM (#35049390)
If I don't realize how shit it is, I don't think it's a shit experience. I don't care how it was designed and what you call a "byzantine hack" I call a feature that saved the Internet about 20-25 years ago. Having everyone on a public addressable host is not good. (Yes, I know you can do this on IPv6, but then it's like you're just applying Byzantine hacks to get the security feature you already had on IPv4.)
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by lamontcg on Monday March 06, 2023 @07:09PM (#35049746)
> Having everyone on a public addressable host is not good.

We had every host on an IPv4 address at the University of Washington back before 1998 and NAT was actually banned by the CAC Department since they billed by number of nodes on the network, so NAT was a way to cheat their billing system.

I learned quite a lot of internet security from having 1998-era Unix servers hanging directly off onto the internet with no firewall or NAT.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by znpy on Monday March 06, 2023 @04:53PM (#35048214)
> you probably want to firewall off inbound traffic from the WAN to the LAN

But all modem/routers are doing it anyway, they might as well do that on ipv6.

Effectively all router appliances (at home and soho level) are linux appliances, and the firewall is built into the kernel (and in use anyway).

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by phpisthebest on Monday March 06, 2023 @05:00PM (#35048315)
Sorry I do not trust the likes of home router vendors to implement a linux firewall correctly

While people may say "NAT is Not security", it is in fact a layer (ahd huge one) in the security onion, that ipV6 is likely going to increase drastically the amount of ransomware and other malware on the public internet simply because that NAT layer is gone

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by blibble on Monday March 06, 2023 @05:36PM (#35048757)
> that ipV6 is likely going to increase drastically the amount of ransomware and other malware on the public internet simply because that NAT layer is gone

malware has connected outwards to c&c servers for more than 20 years

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by yamtaddle on Monday March 06, 2023 @05:07PM (#35048401)
I remember what it was like when lots more home computers were routable from the public Internet, because having a NAT router between them and there wasn't a nearly-100%-adoption thing yet. In fact, I worked at an ISP (dial-up and DSL) in that era.

It was indeed a shit-show. Adding a NATting router to those set-ups instantly increased their security tremendously. Sure you could use a proper firewall, but the router w/NAT Just Works.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by phpisthebest on Monday March 06, 2023 @05:10PM (#35048444)
I cant wait until all the printers, and webcams all showup on the public internet again....
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by yamtaddle on Monday March 06, 2023 @05:12PM (#35048479)
Portscanning for smb shares and webcams, LOL. Good times. Found entire offices routing their whole network publicly, back then, shared network drives and printers right there for use by anyone who stumbled on them. It was nuts. Worms spread like crazy. It was a real mess, and that's with the Internet being way the fuck friendlier than it is now.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by garbagecoder on Monday March 06, 2023 @06:35PM (#35049420)
What's ironic is that the IPv6 people will tell you you can do all of that with IPv6. Which is true, but if we NEED TO CHANGE because we're out of addresses then why go to something that doesn't use the address space?

The problem IPv6 seeks to address has mostly been engineered around for now.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by JohnFen on Monday March 06, 2023 @07:31PM (#35049910)
> The problem IPv6 seeks to address has mostly been engineered around for now.

For now is the operative phrase. These are band-aids to keep IPv4 running, but they won't be effective forever.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by JohnFen on Monday March 06, 2023 @05:14PM (#35048502)
> Sorry I do not trust the likes of home router vendors to implement a linux firewall correctly

Neither do I, but that's a fixable situation. Get an appliance router that lets you put DD-WRT (or similar) on it. Or use a computer instead of an appliance and set it up any way you like.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by phpisthebest on Monday March 06, 2023 @05:17PM (#35048534)
I am by trade a network administrator, and I run enterprise gear in my home.

I am not running a home router or dd-wrt. But I am not a typlical user going down to best buy to pick up the latest Belkin or Asus wireless AP / router combo they have on sale for $99 and hooking it up to my internet using default "wizard" settings from the mobile app...

Nor I am I trusting Comcast, or ATT to configure their residental rented equipment properly with proper firewall rules

My comment is not about me, I have enterprise grade nextgen firewalls that are $$

My comment is about Grandma that calls up comcast to have them set it all up, or Sally that is going into best buy for the "Geek Squad" so hook her up...

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by Symbiote on Monday March 06, 2023 @06:38PM (#35049464)
Large ISPs like Comcast already have enormous IPv6 networks, and have appropriate, default-deny firewall configurations for them.

I'm only familiar with the largest ISPs in Britain, but they also have default-deny configurations on the IPv6 routers they supply. Obviously.

> Grandma / Sally

Try avoiding the casual ageism and sexism.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by phpisthebest on Monday March 06, 2023 @07:52PM (#35050049)
>Try avoiding the casual ageism and sexism.

Try not to find offense in all things, feel free to refer to my comment thread from the other day about offense being a you problem not a me problem ;)

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by KerrAvon on Monday March 06, 2023 @06:38PM (#35049470)
If I’m following your logic, you’re saying you trust tplink etc to keep Grandma safe, but only for IPv4, and not IPv6? Why?
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by phpisthebest on Monday March 06, 2023 @07:51PM (#35050042)
I am not trusting them, behind a ipv4 nat inbound connections are by default inaccessible

ipv6 most configuration end up with all devices publically routable and must have a firewall deny policy inplace to block inbound connection

Shodan is filled with people with misconfigured ipv4 routers that end up with all kinds of device that should not be on the public internet (webcams, printers etc) out there for anyone to connect to. This requires a user to actively do something on the device (most likely following a bad online tutorial) in order to port something though the NAT.

with IPv6 this problem will get FAR FAR FAR FAR worse.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by lmm on Monday March 06, 2023 @11:07PM (#35051424)
> I am not trusting them, behind a ipv4 nat inbound connections are by default inaccessible

No they're not. They're by default obscured, but anyone can guess your internal IP and send a packet for it, and the router will happily forward it on unless its firewalling tells it not to. And that's without even even getting into all the extra attack surface opened up by legitimate and not-so-legitimate workarounds for the issues NAT causes.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by pixl97 on Monday March 06, 2023 @06:24PM (#35049315)
This is one of the worst takes I've seen in this thread.

NAT is only kind of a firewall and there have been plenty of terrible router firmwares out there that have lead people to subvert it (UPNP being one of the most problematic).

If you in your other thread don't trust the ISP device, then don't trust NAT on your ISP device either. Quite often the ISP can have their modem route traffic from their internal 10 net to your internal network if they so choose to.

Instead IPv4, or IPv6 setup to drop NEW/SYN connections to your devices via a router that you provide.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by phpisthebest on Monday March 06, 2023 @07:55PM (#35050074)
>If you in your other thread don't trust the ISP device, then don't trust NAT on your ISP device either

There is no logic there. firewall configuration is much harder to secure than NAT configuration.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by lmm on Monday March 06, 2023 @11:04PM (#35051410)
> There is no logic there. firewall configuration is much harder to secure than NAT configuration.

Disagree. Just the XML parsing logic required for uPnP alone is more complex than a basic firewall implementation.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by JohnFen on Tuesday March 07, 2023 @02:33PM (#35060039)
uPnP seems a distraction from the topic. It's not necessary for networking to network -- my LAN intentionally does not support it at all. It is necessary for certain use cases, of course, but it's not mandatory in a network in the general case.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by lmm on Tuesday March 07, 2023 @06:10PM (#35062660)
It's necessary for feature parity with IPv6 (or, equivalently, with the 2000s-era Internet). Even if you don't use uPnP, the amount of complex protocol parsing necessary to support/work around NAT (e.g. SIP is particularly tricky) is a larger attack surface than a full IPv6 stack.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by acedTrex on Monday March 06, 2023 @04:50PM (#35048178)
A pipe dream, but the best case seems to be a total standardization on v6
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by dijit on Monday March 06, 2023 @04:55PM (#35048239)
link local ipv6 can be deterministic (no more shuffling IPs around!) and no more silly dhcp services running on anaemic hardware.

Ditto for NAT, where devices can reach v6 endpoints (though stateful firewalls should stick around!).

Honestly, I really hate change. but ipv6 does have some upsides and rather than complicate things, embracing actually simplifies things.

The issue is that we have a lot of sunk cost on how we bolt on shit to ipv4 to make it passable in the modern day, and we begrudge having to relearn what we think is solved.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by bonsaibilly on Monday March 06, 2023 @04:59PM (#35048294)
Congratulations on completely failing to understand how CGNAT loads work & their costs, and jumping to a wildly incorrect understanding of the situation
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by outworlder on Monday March 06, 2023 @05:13PM (#35048490)
Yeah, and that's currently the top comment.

Which leads me to believe that the main barrier to IPV6 is just that people don't want to re-learn anything.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by dpkirchner on Monday March 06, 2023 @05:40PM (#35048805)
I think the main barrier is that for most people IPv4 works just fine and they've never experienced a problem that IPv6 would solve. Maybe they will, some day, like if Facebook and Google shut down their IPv4 IPs.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by JohnFen on Monday March 06, 2023 @05:19PM (#35048554)
> the main barrier to IPV6 is just that people don't want to re-learn anything.

I disagree, actually. I think the main barrier is that networking folks have been pretty bad at explaining this to non-networking folks. IPv6 isn't exactly simple to understand.

I'm a reasonably network-savvy guy, and I'm sure that I understand less about IPv6 than I think I do. I just don't know what parts I'm not understanding properly, and what parts I just don't know about.

It's pretty hard to find good explanations of this stuff that aren't aimed at networking experts.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by harry8 on Monday March 06, 2023 @07:02PM (#35049693)
It's terrible isn't it. I'm not a network specialist yet have a reasonable enough understanding of ipv4, nat etc that I think my home network is, at least ok. Can look at ip addresses in logs and know what machines most of them are etc.

I get tired of this "I'm an expert you're an idiot" trope that comes up about it. Here on this damn website you have people who hack kernel, people who manage massive databases, people who hack front end stuff that scares me, experts in functional programming, language designers, fpga designers... In short it's very, verry flipping technically adept crowd. You didn't reach them.

Networking "experts" who want to blame everyone else for a lack of understanding need to look in the damn mirror and ask themselves "How did we fail so very, very hard at explaining this stuff?" "Why are we not able to provide a link to an article with an estimate of time taken for everything you need to know about ipv6 to use it exclusively?" "Why don't we want to make this easy for everyone?" "Why can't we be minimally polite?"

I'm an expert in being a jerk on occasion and this occasion the "Everybody else is stupid and lazy because they don't understand it's not us at all" trope is definitely being a jerk. And I'm jerk enough to point it out.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by lamontcg on Monday March 06, 2023 @07:23PM (#35049862)
Yeah as an old former-system admin its kind of amusing to be on the receiving end...
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by JohnFen on Tuesday March 07, 2023 @02:20PM (#35059869)
The hostility is what I think is more damaging than anything else. When people have an objection to something that is resulting from them misunderstanding the thing, telling them they're stupid, lazy, or even malicious just makes them disengage (and correctly so).

The end result is that they will continue to object to the thing, but won't raise their objections to the experts anymore. And why would they? Nothing good came from it the first time.

It turns what should be a cooperative relationship into a combative one. I see this happen in pretty much every discussion of IPv6 around, including this one.

The other issue is that the subject matter experts rarely actually explain anything. They just toss out acronyms and buzzwords and consider the matter corrected. But it's not -- they're talking as if their audience is another subject matter expert, when it's usually not. Acronyms and buzzwords mean little to them.

And telling them to "google it" likewise does little good. The audience isn't a subject matter expert, doesn't want to be, and shouldn't have to be. If IPv6 really is so complex that you have to be an expert in order to use and configure it properly, then isn't that a problem with IPv6?

My assumption is that's not the case (but I'm not sure on this point), but instead, the experts are failing to actually teach people about this stuff.

In the end, I blame the rollout of IPv6 itself. Exactly zero attention and effort was paid to evangelizing and educating people about it. There was no gradual rollout plan put into place and encouraged.

The IPv6 rollout effort failed to do the things that are necessary to facilitate a shift of this magnitude. This makes the whole thing very confusing and leads people who aren't elbows deep in the topic to lean toward "I don't feel that I can do this safely, so it's better than I don't do it at all".

The tragedy is that it all could have gone so much better than it has. It could have been a thing everyone unified about rather than a thing that is rapidly becoming a kind of holy war.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by harry8 on Tuesday March 07, 2023 @11:45PM (#35065368)
yeah or just what about an article or even a whole book on the subject of:

"You're gonna move your home network to ipv6, here's what you need to know to not f&^k up hard and get pwned" At the level like we know for ipv4.

Right now, I actively disable ipv6 in devices on my network because I don't have a clue about how it all works. Am I making something addressable from the public internet? Am leaking every mac address I have? So much more I'm sure I havent even considered.

Then when you look at ipv6 tutorials you see nuts things like each octet containing a zero value can be shortened to just a single zero :00000000: becomes :0: ok fine, but consecutive octets of zero are removed so :00000000:00000000: becomes :: swallowing a delimiter so programming this stuff you can't even just split on the delim and /know/ what octet is where. Now maybe theres a good reason for that but where is the explanation? Not in any of the tutorials that have to explain how this stuff works rather than something, you know, useful. As presented it's pure additional, utterly meaningless, learning overhead.

So yeah. I'm too stupid to run ipv6 and I know it. But I'm not nearly as stupid as those who claim it's ready for prime time because it damn well isn't.

Anyone thinks it is. Link the document with a time estimate on running a home network with ipv6 knowing what you need to know (and know already for ipv4) to not do something idiotic.

In this crowd, we'll learn stuff just because it looks cool and you can't reach us? Get outta here.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by DaiPlusPlus on Monday March 06, 2023 @05:31PM (#35048685)
Speaking for myself, but my main barrier to IPv6 adoption is my ISP (Wave/Astound, Seattle eastside) still being IPv4-only, despite having DOCSIS3.1 service.

I didn’t think it was even possible to have DOCSUS3.1 without IPv6 :S

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by commandersaki on Monday March 06, 2023 @08:10PM (#35050189)
Main barrier for me is there’s no interoperability with ipv4, and no official transition plan (just a bunch of rfcs suggesting different transition plans).
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by tpmx on Monday March 06, 2023 @05:11PM (#35048467)
Prediction: CGNAT processing costs for gigabit subscribers will become neglible in the medium term (3-5 years). Not that it's wildly expensive today...
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by bonsaibilly on Monday March 06, 2023 @06:21PM (#35049277)
You are literally posting this comment on a story about CGNAT processing costs being wildly more expensive than a small ISP cares to deal with.

Even if that price decreases in real terms, washing a whole bunch of traffic through a big-ass NAT is always going to cost more than just not doing that.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by tpmx on Wednesday March 08, 2023 @03:34PM (#35074372)
The cost of an IPv4 address is around $50. Annualized it's a few dollars. So, that's the baseline for where CGNAT makes financial sense.

That's a lot less than the cost of an Apple TV.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by merbanan on Monday March 06, 2023 @05:56PM (#35048992)
MAP-T/MAP-E moves the CG-NAT functionality to the CPE. 60x users per IPv4 address should be doable.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by bastardoperator on Monday March 06, 2023 @05:03PM (#35048358)
Not going to lie, I just turn IPv6 off on my router because I don't fully understand it and because I pay a little extra for a block of 3 IPv4 addresses.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by ehPReth on Monday March 06, 2023 @05:13PM (#35048480)
who cares if it's "public" if it's firewalled; likely by default
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by blibble on Monday March 06, 2023 @05:33PM (#35048714)
> IPv6 for local networks, makes no sense is completely unnecessary, and is a hill I will die on. IPv4 is here to stay.

my mobile phone in the UK on one of the big 4 carriers only has IPv6 addresses

and only has IPv6 connectivity

(using 464XLAT)

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by carlhjerpe on Monday March 06, 2023 @05:37PM (#35048770)
How do you reach all 2^128 ips when you only have 2^32 destinations?

IPv6 makes sense everywhere.

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by Narkov on Monday March 06, 2023 @06:09PM (#35049138)
> IPv6 for local networks, makes no sense is completely unnecessary, and is a hill I will die on. IPv4 is here to stay.

This is a position of privilege. The developing world would like access to the Internet and lack access to the (mostly) exhausted IPv4 space. Should we not work to make Internet access ubiquitous?

Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by JohnFen on Monday March 06, 2023 @07:39PM (#35049964)
He's talking about running IPv4 on his LAN, not the internet. That wouldn't use up any of the internet's IPv4 space and wouldn't affect other internet users.
Re:Roku devices don't support IPv6 in 2023 and its costing ISPs by 1ncorrect on Monday March 06, 2023 @06:16PM (#35049235)
Hills sparsely populated with corpses are equally fascinating and comical.