As a quick solution I rent a hosted virtual server with a static IPv4 address to provide my most important services.
If you have services, which need to be accessible to people other than yourself, you'll probably have to keep that server for years to come.
Out of curiosity, which provider did you choose? I just got myself a virtual server at Hetzner.
My first question now is, if it is common practice by ISPs to assign dynamic IPv6 addresses?
In Denmark it is common practice among ISPs to pretend IPv4 shortage isn't a problem and that NAT is such a great solution that more layers of NAT is a much better solution than IPv6.
What is the sense, actually there is no IPv6 address shortage. Why they do not give me a static IPv6 subnet, which I could use in my LAN at home?
They are supposed to route a static subnet to you. And it certainly would be easier to manage, if they give a static IPv6 prefix to each customer. The easiest way to get you IPv6 probably is to just provide you with a static /64 on the link and no routed prefix. That is what I got on my virtual server, which is the only place I have native IPv6 access.
How could I have a persistent network configuration with this connection? How could I write firewall rules with every host in my LAN has changing IPs? Also my ISP is such a genius that they give me a router (Cisco EPC3208G) that autoconfigures my hosts with IPv6 addresses, routing and DNS resolvers. The DNS resolvers of the ISP of cource, which do not know my network printer and I wonder why I cannot print anymore.
If you have your own domain and setup the proper records to point to IPv6 addresses on your LAN, then you can also resolve those names through the resolvers of your ISP.
Also I do not have access to the configuration options of the router to use stateless DHCPv6 with my own DHCPv6 server. The short form, my provider gives me a nearly unusable native IPv6 and very limited IPv4.
I am not convinced your IPv6 connectivity is unusable. Given the information provided so far, I find it more likely that it is just a matter of configuring devices on your LAN appropriately, than your ISP really giving you addresses from varying subnets.
If you'd be prepared to experiment a little bit, could you try the following:
1. Find out which IPv6 addresses are visible on your network (ping6 -n ff02::1%eth0 if you are using Linux).
2. Go to my test page
http://test-ipv6.netiter.dk/3. Take note of your IPv6 address mentioned on that page
4. Restart the EPC3208G
5. Once you have a received a new IPv6 address repeat step 1 and 2.
6. Find out which parts of the IPv6 address changed, and which parts remained the same.
I had the idea, to use my IPv4 only VPS as my own gateway to the IPv4 world.
Is it possible to set up a IPv6 tunnel between my VPS and my home server, using Tunnelbroker on the IPv4-only VPS?
Then route my IPv4 traffic from my home LAN through the IPv6 tunnel to my VPS and from there to the IPv4 internet.
Yes, that is possible. But I would recommend a VPS with native dual stack. Ideally the tunnel between your home and the VPS can use different redundant sorts of connectivity.
With the right software on a device you have at home and matching software on your VPS, you have many different ways to get packets between your home and the VPS.
- IPv4 through DS-lite from the device at home to the static IPv4 address of your VPS
- IPv6 using native IPv6 address of the VPS
- IPv6 using tunnelbroker.net address of the VPS
- IPv6 using 6to4 address of the VPS
- IPv6 using Teredo address of the VPS
You'll only see all of those fail simultaneously if one of the endpoints is really disconnected from the network.
Perhaps this works better than the DS-Lite of my ISP.
Perhaps. But the way to get reliability is by having redundant connectivity. I think before deciding on any solution, it would be better to understand what sort of IPv6 connectivity you have.
You should also consider, that there may be simpler solutions.
http://en.wikipedia.org/wiki/List_of_IPv6_tunnel_brokers mentions three different 4in6 providers.