logoalt Hacker News

matja • last Thursday at 2:25 PM • 5 replies • view on HN

s/IP/IPv4/g

Configuring my OS to prefer IPv6 addresses of DNS responses significantly reduced the number of web captchas I see (on NAT444 with native IPv6).

IPv4 is old and broken, use IPv6.


Replies

malfist • last Thursday at 2:54 PM

I'd love to do that, if my ISP would provide me an IPv6 address. Windstream doesn't provide IPv6s. They did a trial a few years ago rolling it out and then undid it.

It's crazy I can get fiber to my house in the US, but not IPv6.

➕ show 4 replies
thayne • yesterday at 3:29 AM

My ISP is only a few years old, but they don't support IPv6 at all. And when I complain about it to support, their response is basically "we don't see the point".

➕ show 1 reply
sandeepkd • last Thursday at 5:51 PM

This is an interesting take, however from what I seen its other way around. Most security conscious operators would only allow IPv4 instead of IPv6. Your ACL rules and tools are still better at handling/managing IPv4 compared to IPv6

➕ show 3 replies
TacticalCoder • last Thursday at 5:22 PM

> IPv4 is old and broken

IPv4 is old, very old. But how is it broken? It's literally been working just fine since it came out.

That there are limited addresses is something else: it doesn't mean it's broken.

I don't care that spying/surveillance devices have more trouble spying on me with IPv4 than with IPv6 and I don't care that some apps have a harder time establishing connection.

IPv4 works. SSH over IPv4 works. Browsing the Web over IPv4 works.

➕ show 2 replies
w3ll_w3ll_w3ll • last Thursday at 2:42 PM

There is no need for that, every modern OS prefer IPv6 over IPv4

➕ show 1 reply