Ok, I understand what you're saying. The end user only cares whether their thing works or doesn't work. If it doesn't work due to NAT or doesn't work due to a default "drop all" rule in a firewall they don't know difference and don't care. I concede that 100%.
But still: 1) I may or may not have a reasonable fix for a NAT issue. I can definitely fix a firewall rule. 2) I definitely don't have enough IPv4 public IP's, whereas IPv6 is plentiful. 3) IPv6 exists now and is widely adopted. I can't get the IETF to design me an IPv8 that I like better, and even if they did I'd have to wait another 20 years for it to proliferate. At this company we have a full dual stack implementation, but the CG-NAT appliances are taking most of the load (hundreds of gbps). All the major content networks are also dual stack, as are the transit providers. If the consumer routers consistently implemented IPv6 then we ought to have >80% of our traffic going end to end from customer to content provider and our CG-NAT would be a secondary function. That's the root of my looking -Adam -----Original Message----- From: Matt Hoppes <[email protected]> Sent: Wednesday, December 15, 2021 11:22 AM To: [email protected]; 'AnimalFarm Microwave Users Group' <[email protected]> Subject: Re: [AFMUG] IPv6 in home routers Let me try again... IPv6 is suppose to give every device it's own public IP address. End users have devices on their network that are just waiting to be compromised and most users are not smart enough nor do they care enough to play with the firewall. Therefore, we block inbound traffic on the IPv6 firewall. So what benefit does IPv6 have to the end user? None... Zilch... Absolutely none. If we block inbound traffic by default, it's no different (for the average home user) than just opening some ports on IPv4 in the NAT translation table. On 12/15/21 11:20 AM, [email protected] wrote: > I'm not sure what you're talking about tbh. > You can use SLACC or DHCP to get an IP address on the WAN side, but you must > do prefix delegation to push IP's to the LAN side. It's different, but it's > not more difficult. > > What I'm observing is routers that don't have IPv6 at all, or haven't > bothered to do the prefix delegation. That's not a flaw in the protocol, > they just haven't implemented it. > > > > -----Original Message----- > From: Matt Hoppes <[email protected]> > Sent: Wednesday, December 15, 2021 11:15 AM > To: Adam Moffett <[email protected]>; AnimalFarm Microwave Users > Group <[email protected]> > Subject: Re: [AFMUG] IPv6 in home routers > > Because it's not straight forward to deploy. > > On 12/15/21 11:11 AM, Adam Moffett wrote: >> I don't think we're talking about flaws in the protocol. I think >> we're talking about it being a secondary concern for manufacturers so >> they're not putting enough attention into it. >> >> >> On 12/15/2021 11:06 AM, Matt Hoppes wrote: >>> Correct. We still don't know how to properly hand out IPv6 to end >>> users, and routers have issues doing it. >>> >>> The protocol stack is a flawed implementation. >>> >>> On 12/13/21 4:51 PM, [email protected] wrote: >>>> I was doing some testing on our dual stack FTTX network. >>>> >>>> I grabbed a CnPilot R201P off the shelf. IPv6 was disabled by >>>> default. You had to enable it in 3 different places and even after >>>> following the guides on Cambium’s site the prefix delegation seems >>>> to not really work. >>>> >>>> I grabbed an AirCube…..no IPv6 support at all. It’s supported in >>>> the underlying OS, but not in the GUI. Ubiquiti support says it’s >>>> coming, but they’ve been saying that for 2 years +. >>>> >>>> I grabbed a Mikrotik…..works perfectly fine, but setup is beyond >>>> what any consumer is going to do. If I’m quibbling, it doesn’t >>>> support stateful dhcp assignments from a delegated prefix. That’s >>>> not too big of a deal. >>>> >>>> Out of 3 routers I have close at hand, 1 is a faulty >>>> implementation, >>>> 1 is not implemented at all, and one is too hard for normal people. >>>> >>>> So when people run out to the store and get a Netgear, Asus, or >>>> whatever router off the shelf is it hit-or-miss with those too? I >>>> guess I naively assumed that 25 years after IPv6 was created that >>>> we’d have working implementations by now. >>>> >>>> > -- AF mailing list [email protected] http://af.afmug.com/mailman/listinfo/af_af.afmug.com
