News for hackers. Stuff that matters.
Re:The world in which IPv6 was a good design (2017) by Triv888 on Tuesday December 29, 2020 @08:34AM (#25569593)
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.
Re:The world in which IPv6 was a good design (2017) by cipherboy on Tuesday December 29, 2020 @09:05AM (#25569800)
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).

Re:The world in which IPv6 was a good design (2017) by loeg on Tuesday December 29, 2020 @12:09PM (#25571963)
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.)

Re:The world in which IPv6 was a good design (2017) by oarsinsync on Tuesday December 29, 2020 @01:24PM (#25572996)
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.

Re:The world in which IPv6 was a good design (2017) by tenebrisalietum on Tuesday December 29, 2020 @08:37AM (#25569617)
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.
Re:The world in which IPv6 was a good design (2017) by rzzzt on Tuesday December 29, 2020 @08:57AM (#25569745)
Quasi-static IP assignment, my favorite.
Re:The world in which IPv6 was a good design (2017) by Triv888 on Tuesday December 29, 2020 @09:14AM (#25569869)
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.
Re:The world in which IPv6 was a good design (2017) by tenebrisalietum on Tuesday December 29, 2020 @10:23AM (#25570564)
Agreed. My Comcast public IP didn't change for a few years until I moved.
Re:The world in which IPv6 was a good design (2017) by Triv888 on Tuesday December 29, 2020 @11:13AM (#25571214)
Did you change router as you moved?
Re:The world in which IPv6 was a good design (2017) by tenebrisalietum on Tuesday December 29, 2020 @03:10PM (#25574228)
Nope. Same router, same cable modem.
Re:The world in which IPv6 was a good design (2017) by zrail on Tuesday December 29, 2020 @08:48AM (#25569669)
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.
Re:The world in which IPv6 was a good design (2017) by Hnrobert42 on Tuesday December 29, 2020 @08:51AM (#25569691)
I wonder if that is Comcast’s fault or the geolocation service’s.
Re:The world in which IPv6 was a good design (2017) by csharptwdec19 on Tuesday December 29, 2020 @09:48AM (#25570183)
Blaming Comcast is a very safe default.