@9to5linux i guess that is good. But until ipfire 3 is out, with #IPv6 support, this project is unfortunatly not a realistic firewall alternative
Oops! The MXP01 (Italy) peer had some fuck ups, followed by some insane traffic f*ckups at 3AM & 6AM on the other instances.
Rule Nr. 1: Even changing a single character can result in f*ckups. Always test!
Thank you @nlnetlabs for this great software.
new freebsd PR: merge traceroute6 into traceroute
Yggdrasil is a new experimental compact routing scheme. It is designed to be a future-proof and decentralised alternative to the structured routing protocols commonly used today on the Internet, as well as an enabling technology for future large-scale mesh networks.
#ipv6
https://yggdrasil-network.github.io/
Bummer. fosstodon.org's host doesn't support #IPv6
#MyVirtualServer wirft das Handtuch. Hat jemand eine Idee, wo ich mit dem #IPv6Droid Backend hinziehen könnte? Es braucht eine öffentliche statische IPv4-Adresse und ein ordentliches öffentliches #IPv6-Subnetz.
Plan for April: I'll spend two hours per day (average) on each of the following projects:
* A paid project related to IPv6
* https://github.com/becarpenter/book6
* my blog and (IPv6) YouTube content
And I'll also work on my Python Skills.
And if you had any problems sending mails to me, accessing
https://techlog.jenslink.net or https://www.flarp.de
You are only using IPv4 and the problems are related. ;-)
As I mentioned, IPv6 tutorial videos here:
https://mastodon.social/@quux/114280081895734757
I do have a rather large list of topics, but feel free to add a suggestion in the comments, and I'll see what I can do (and in which order).
And I promise, that I will have some first results in the next couple of days.
for the authoritative side:
When you put AAAA and A records into DNS, IPv6 enabled clients will try IPv6 first and then fall back to IPv4. So Configure and test your systems first, then configure the DNS records.
HTTP / HTTPS are an exception here, they are using something called HappyEyeballs.
For the resolver side:
When you only have an IPv4 resolver configured, your clients will only use this one. When your clients get an IPv6 resolver, either via Router Advertisement or DHCPv6, they will try that one. They should fall back.
As with any service: Configure the service first, check the connection, then configure your clients to use the service.
@ryan Yes, you should learn IPv6.
You can find a collection of training material here:
https://gitlab.com/jenslink/ipv6-resources/-/blob/main/resources.md?ref_type=heads
BTW, In many cases you don't need DHCPv6, you can just use router advertisements to configure your clients. And if you are running Android, DHCPv6 does not work at all.
I really should start working on the IPv6 tutorial YouTube videos...
For those that run a homelab with DNS and DHCP, are you using IPv6? I'm running BIND and debating if I need to configure IPv6 just to future-proof myself. I'm not seeing any issues, at least any that I notice.
Also, I know little about IPv6, so I admit I need to do some learning.