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.
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.