From ed31009a8007c0287f615b0d128705d353094de0 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Fri, 8 Aug 2025 18:48:44 +0300 Subject: Update content for html --- ...5-07-14-f3s-kubernetes-with-freebsd-part-6.html | 28 ++++++++++++++++++++ gemfeed/atom.xml | 30 +++++++++++++++++++++- 2 files changed, 57 insertions(+), 1 deletion(-) (limited to 'gemfeed') diff --git a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.html b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.html index dfd1242c..5d59b5cc 100644 --- a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.html +++ b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.html @@ -63,6 +63,7 @@
  • ⇢ ⇢ Automatic Failback After Reboot
  • ⇢ Client Configuration for NFS via Stunnel
  • ⇢ ⇢ Configuring Rocky Linux Clients (r0, r1, r2)
    • +
  • ⇢ ⇢ NFSv4 user mapping config on Rocky
  • ⇢ ⇢ Testing NFS Mount with Stunnel
  • ⇢ ⇢ Testing CARP Failover with mounted clients and stale file handles:
  • ⇢ ⇢ Complete Failover Test
    • @@ -1532,6 +1533,33 @@ EOF
    Note: Each client must use its certificate file (r0-key.pem, r1-key.pem, r2-key.pem, or earth-key.pem - the latter is for my Laptop, which can also mount the NFS shares).

    +

    NFSv4 user mapping config on Rocky


    +
    +Update: This section was added 08.08.2025!
    +
    +For this, we need to set the Domain in /etc/idmapd.conf on all 3 Rocky hosts to lan.buetow.org (remember, earlier in this blog post we set the nfsuserd domain on the NFS server side to lan.buetow.org as well!)
    +
    +
    +[General]
+
+Domain = lan.buetow.org
+.
+.
+.
+
    +
    +And afterwards, we need to run the following on all 3 Rocky hosts::
    +
    + +
    [root@r0 ~]# systemctl enable --now nfs-idmapd
+[root@r0 ~]# systemctl enable --now nfs-client.target
+
    +
    +and then, safest, reboot those.
    +

    Testing NFS Mount with Stunnel



    To mount NFS through the stunnel encrypted tunnel, we run:
    diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 13ceb5a8..e81b032d 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ - 2025-08-08T18:20:01+03:00 + 2025-08-08T18:47:55+03:00 foo.zone feed To be in the .zone! @@ -544,6 +544,7 @@ content = "{CODE}"
  • ⇢ ⇢ Automatic Failback After Reboot
  • ⇢ Client Configuration for NFS via Stunnel
  • ⇢ ⇢ Configuring Rocky Linux Clients (r0, r1, r2)
    • +
  • ⇢ ⇢ NFSv4 user mapping config on Rocky
  • ⇢ ⇢ Testing NFS Mount with Stunnel
  • ⇢ ⇢ Testing CARP Failover with mounted clients and stale file handles:
  • ⇢ ⇢ Complete Failover Test
    • @@ -2013,6 +2014,33 @@ EOF
    Note: Each client must use its certificate file (r0-key.pem, r1-key.pem, r2-key.pem, or earth-key.pem - the latter is for my Laptop, which can also mount the NFS shares).

    +

    NFSv4 user mapping config on Rocky


    +
    +Update: This section was added 08.08.2025!
    +
    +For this, we need to set the Domain in /etc/idmapd.conf on all 3 Rocky hosts to lan.buetow.org (remember, earlier in this blog post we set the nfsuserd domain on the NFS server side to lan.buetow.org as well!)
    +
    +
    +[General]
+
+Domain = lan.buetow.org
+.
+.
+.
+
    +
    +And afterwards, we need to run the following on all 3 Rocky hosts::
    +
    + +
    [root@r0 ~]# systemctl enable --now nfs-idmapd
+[root@r0 ~]# systemctl enable --now nfs-client.target
+
    +
    +and then, safest, reboot those.
    +

    Testing NFS Mount with Stunnel



    To mount NFS through the stunnel encrypted tunnel, we run:
    -- cgit v1.2.3