Hacker News Reader

Comment by odc | Hacker News Reader

So what? Just because IPv6 does does not solve all the problems in networking it's trash and we should abandon it? No thanks. Where I live, ISPs are starting to share IPv4 addresses between several customers, which creates many problems.

And QUIC over IPv6 is still a lot better than QUIC over IPv4.

View on HN

Where did this abandonment strawman come from? The article was just lamenting the mess.

Here Comcast started giving out "static" IPv4 addresses to dynamic IP customers, which is the opposite of sharing IPs... I can change it by spoofing my router's MAC address though.

What do you mean? Just because Comcast leases you the same IP for years doesn't mean they're obligated to give you the same IP on your router's next DHCP request.

Quasi-static IP assignment, my favorite.

Sure, they aren't obligated but they must not be short on IP addresses if they are doing that. I added quotes around "static" to make it more clear.

Agreed. My Comcast public IP didn't change for a few years until I moved.

Did you change router as you moved?

Nope. Same router, same cable modem.

When we moved recently Comcast rotated our IP to one that geolocates to two states away. Which is fine until every single big box store geolocates us to the wrong store.

I wonder if that is Comcast’s fault or the geolocation service’s.

Blaming Comcast is a very safe default.

Comcast is the reason I disabled IPv6. They'd frequently route traffic over IPv6 to... Nowhere. Websites of major tech companies such as Google and GitHub would occasionally get routed wrong and just... Hang. It's like they black holed outbound IPv6 traffic. The traceroute6 output would quit displaying new routes.

Never had that problem on IPv4. So I ended up disabling it.

(I do have an unrelated issue that sometimes they can't route traffic between two customers in the same general area. Traffic tends to go out to the west coast Comcast DCs and get stuck, never comes back. We're midwest).

Github is IPv4-only to this day. So you should not be getting AAAA records for it, nor any v6 routing issues to a v4 address.

(Also, my experience with IPv6 on Comcast was relatively solid; just hated their billing department. Now my ISP doesn't offer IPv6 at all, which isn't great.)

Used to run the network for a large hosting company. Can confirm, I disabled all peering and transit on one set of border routers for maintenance, restored, and then did the same on the other set.

In both cases, I disabled everything, and then only restored IPv4. Took me a week to notice and restore IPv6. Not a single support request was received relating to the week long IPv6 outage.

This was when I gave up and removed IPv6 from my home network. I’m now behind IPv4 CGN, and don’t care. It works.

Reply on news.ycombinator.com