| ▲ | dmitrygr 6 days ago |
| I'll assume you are speaking in good faith, so i'll reply so as well: I do not want to be a "reasonably-skilled admin". Not my job nor desire. I want DHCP to work and NAT to exist which acts as a de-facto firewall and hides my internal network config from the outside world. All with zero or fewer clicks in my home router's config. With IPv4 this works. With IPv6 it does not. Simple choice for me then: find the IPv6 checkbox and turn it off, as usual. |
|
| ▲ | miyuru 6 days ago | parent | next [-] |
| > I do not want to be a "reasonably-skilled admin"
> NAT to exist which acts as a de-facto firewall My option is you should not handle router config at all and leave it to the ISP. |
|
| ▲ | Dylan16807 6 days ago | parent | prev [-] |
| That's the fault of whoever designed the router, not IPv6. |
| |
| ▲ | dmitrygr 6 days ago | parent [-] | | As a consumer, I don’t care if it’s Santa Claus’s fault. IPv4: works, IPv6: doesn’t. I don’t even need to know what IPv6 means. I just need to know: Turn it off to make things work. As a technologist, growing up involves learning not to blame the consumer. They are not holding it wrong, you just designed it in a dumb way. | | |
| ▲ | Dylan16807 6 days ago | parent [-] | | And I'm not blaming the consumer. If you want to come into a topic and say the problem is that IPv6 did too much, you can't fall back on "it doesn't matter who's at fault". Yes it does matter, that's what this thread is about, that and looking at how technological changes would have affected deployment. | | |
| ▲ | dmitrygr 6 days ago | parent [-] | | It is forever tainted and I will put down money on a bet that when IPv4 is replaced (in the 2040s), it will be by something that will not be IPv6. | | |
|
|
|
