Hacker News Reader

Comment by cptskippy | Hacker News Reader

Support for IPv6 is weird.

Comcast's IPv6 implementation is rock solid and faster than IPv4 most of the time. I've been running publicly accessible IPv6 HTTP hosts over it for several years now.

The last two Motorola Modems I've had came with IPv6 support and were provisioned by Comcast out of the box.

Access Points from D-Link will autoconfigure via SLAAC but DNS has to be hardcoded.

It's 2018 and yet Ubiquiti's UniFi enterprise networking gear only has alpha support.

IPv6 on Tomato just works and has for years, IPv6 on Raspbian not so much.

Windows just works seems to fuck with nonWindows clients so Enterprises disable it via Group Policy.

Android devices seem to forget IPv4 if they catch a wiff of IPv6 on the network.

View on HN

> Windows just works

Almost. IPv6 privacy extensions are subtly broken.

https://social.technet.microsoft.com/Forums/windows/en-US/57...

Does your Comcast IPv6 address ever change on you? If yes, do you have any tricks to keep your HTTP servers accessible?

It does but I can't say how frequently. My IPv4 address has only changed 7 times since 2012. My IPv6 record has changed once this year when I shut down my modem for an extended period of time.

I use http://freedns.afraid.org/ to manage my DNS. They support IPv4 and IPv6 with domain linking so you can update all your DNS records with 2 calls (one for IPv4 and one for IPv6). This can be done with wget via a cronjob on your web server or in most routers these days. If you use their premium tier you can use stealth records and wildcard DNS.

Just remember to set your TTLs on your A records to something low like 60 seconds. And don't host anything mission critical.

Thanks. I am very much interested in making a similar setup of my own on a Raspberry Pi. Do you recall what were the IPv6 issues with Rasbian? Also, do you have any concerns about potentially going against Comcast policies which appear to prohibit running servers?

I guess I should rescind my comment about Raspbian because I haven't had any major issues since the Jesse release and I doubt anyone is even going to use that with the Stretch release out.

I had a lot of issues with Raspbian prior to Jesse just failing completely to get an IPv6 address from the Gateway and not being able to resolve anything.

I've been running Pi.Hole and OctoPi on Jesse for at least 6 months with only minor issues that aren't the distro's fault but the applications. OctoPi doesn't even configure the HTTP Server so IPv6. Pi.Hole listens for HTTP requests and responds with errors.

I installed Stretch on a Pi and setup a Ubiquiti Controller a few weeks ago and IPv6 works flawlessly with it.

\* Regarding Comcast's policies, I have never run into an issue with them and I've been running servers for over a decade. That being said, mine are personal use, low traffic, and not business related.

> Windows just works seems to fuck with nonWindows clients so Enterprises disable it via Group Policy.

well I've seen most enterprise networks with no IPv6 support. (mostly admins thing that this beast is hard to work with) Also Kubernetes has limited IPv6 support (mostly on the documentation site) (of course it's easier to support a IPv6 only cluster, because heck you wouldn't really need BGP or some wierd overlay networks (sadly it still is not there yet)).

In Germany IPv6 within "Deutsche Telekom" is just good. But sadly on the consumer side you still won't get any fixed IPv6 (due to privacy concerns!)

privacy is not the issue. Selling business plans is the real reason.

You won't believe the number of crazy people in Germany who believe that static IP addresses are the root of all evil because of all the magucal tracking and surveillance possibilities they famtasize about.

IPv6 would allow for both.

The only reason I can still post here is that I don't have a static IP address. So yes, they are the root of all evil.

Other big German providers just fail at this. O2 for example only hands out IPv6 addresses very selectively based on whose lines they are renting in the area. I have no chance in hell of getting an IPv6 prefix from them.

telekom has some IPv6 routing issues every now and then that I did not encounter with other ISPs. I believe it is because they peer more selectively at de-cix instead of having open peering.

They finally peer on DE-CIX?

In Belgium, my provider's (Telenet) IPv6 connection is better than IPv4. Every now and then some network applications and websites will stop working, and invariably they're the ones that depend on IPv4. Meanwhile the IPv6 internet just keeps working without a hitch. Takes a good 5 minutes for the IPv4 to come back on then. Luckily I've got a static /64 subnet from the ISP so most of the services I run for personal use are basically IPv6-only at this point.

I'd wager your v4 goes through a CGN (carrier grade nat) which is very high grade until it breaks.

My ISP supports IPv6, but I have to open up a second PPPoE connection to an IPv6-only endpoint. I've never gotten it to work.

Reply on news.ycombinator.com