summaryrefslogtreecommitdiff
path: root/content/site/fixing-ipv6-and-securing-the-domain.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/site/fixing-ipv6-and-securing-the-domain.md')
-rw-r--r--content/site/fixing-ipv6-and-securing-the-domain.md8
1 files changed, 2 insertions, 6 deletions
diff --git a/content/site/fixing-ipv6-and-securing-the-domain.md b/content/site/fixing-ipv6-and-securing-the-domain.md
index 6893274..fc1ea14 100644
--- a/content/site/fixing-ipv6-and-securing-the-domain.md
+++ b/content/site/fixing-ipv6-and-securing-the-domain.md
@@ -1,15 +1,11 @@
---
title: Fixing IPv6 and securing the domain
-category: engineering
+category:
+- site-info
abstract: Mistakes were made
date: 2023-05-05T13:55:14+02:00
year: 2023
draft: false
-tags:
-- meta
-- IPv6
-- DNSSEC
-- Ok
---
Ok, so [recent IPv6 enablement](/2023/now-served-from-ipv6/) didn't went smooth. Even though I've added the AAAA record and I was able to `ping6(8)` from my FreeBSD machine, I forgot about configuring the firewall. Sadly, I know very little about `pf.conf(5)`, so I used a [ready config](https://forums.FreeBSD.org/threads/ipv6-not-working-with-pf.66772/post-395165), changed the network interface, and added ssh. Voila, IPv6 works! Thanks for letting me know about this bug on my side, [Marco](https://twitter.com/marcodavids/status/1653862517309882369).