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.
Almost. IPv6 privacy extensions are subtly broken.
https://social.technet.microsoft.com/Forums/windows/en-US/57...
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.
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.
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!)
PA can only be held for further assignment in their networks by a LIR that is a member of the RIPE NCC, received in two ways: maximum of one IPv4 allocation /22 with proper justification, or acquisition through merger with another LIR. The membership fees are as you mentioned.
PI resources are assigned to end-users in the region, that do not need to be members of the NCC. They do however need a valid end-user agreement with a LIR, and each(unless they are allocated on the same date) object entails a 50€/yr fee, billed to the LIR. PI IPv4 is no longer being assigned from RIPE, but existing ones are openly traded.
My guess would be that the nets you were looking at were PI networks, so no, you do not need to pay the membership fee.
The document ripe-680 covers basically everything you need to know: https://www.ripe.net/publications/docs/ripe-680
For reference, the list of currently leading and trailing countries by IPv6 adoption (from Akamai's August 2017 numbers):
Belgium 46%, US 40%, India 36%, Greece 32%, Germany 25%, Switzerland 20%, Finland 20%, Brazil 19%, Canada 18%, Norway 16%, Japan 15%
Portugal 13%, UK 12%, France 12%, Australia 8%, New Zealand 8%, Sweden 8%, Netherlands 7%, Mexico 5%
Israel 3%, South Korea 2%, Ireland 1%, Denmark 1%, Russia 1%, Spain 0.7%, Italy 0.5%, China 0.3%, Colombia 0.1%
The way some of these nations are lagging is bizarre.
Once they go live, expect to see the UK climb significantly.
Yet Italy was home to Tinet, part of Tiscali and the largest IPv6 network of the world until 2009.
More saddening than bizarre.
Not quite true - EE (so one of the 'big four' providers rather than a small MNVO) has IPv6 support. Right now, my phone has an IP address assigned out of EE's 2a01:4c8::/29 netblock and I can connect to IPv6 only websites.
My phone isn't super modern either - a 2016 era OnePlus 3 running Android 8.0.
Though thanks to HE/tunnelbroker.net I deployed a /48 on my network and all is good now (and easier).
Was looking at whether it was more economical to buy a small address block vs rent it from a datacentre. A /24 address block seems to cost around $4,000 upfront but then you need to pay €2,000 signup + €1,400 per yr RIPE membership fee. On the other side IPv4 is not going away and the price is only going to go up given the failure of IPv6 to deploy. Is there any way around the RIPE membership? Like owning an IPv4 address block through a proxy / broker?
[edit: RIPE fee]