Merge pull request #924 from booxter/ipv6-lab-resolved-conf

document how to configure resolved on rhel

Author: openshift-merge-bot[bot]

devsetup/scripts/ipv6-nat64/README.md

@@ -1,6 +1,22 @@
 Development environment - IPv6 NAT64 lab
 ========================================
 
+Prerequisites
+-------------
+
+Network setup relies on `systemd-resolved` service enabled and used for DNS
+resolution. If it's not installed on your machine (for example, if you use
+RHEL), then:
+
+#. Install the package: `dnf install -y systemd-resolved`
+#. Enable and start the service: `systemctl enable --now systemd-resolved`
+#. Configure it as the default resolver for the system: `ln -sf ../run/systemd/resolve/stub-resolv.conf /etc/resolv.conf`
+
+Further DNS requests initiated by the hypervisor should now go through the stub `systemd-resolved` resolver.
+
+Overview
+--------
+
 These scripts can be used to set up an IPv6 lab utilizing [NAT64](https://en.wikipedia.org/wiki/IPv6_transition_mechanism#NAT64) and [DNS64](https://en.wikipedia.org/wiki/IPv6_transition_mechanism#DNS64) (4 to 6 translation).
 
 To set up the lab run the scripts in order:
@@ -60,8 +76,6 @@ options:
 * nftables - Firewall for IPv4 NAT (Masqurade NAT64 pool behind a single ip
   address)
 
-Note: you will have to detach from the VM console by pressing `Ctrl+]`.
-
 
 sno.sh
 ------

devsetup/scripts/ipv6-nat64/sno.sh

@@ -328,6 +328,7 @@ EOF
 }
 
 function print_cluster_info {
+    set +x
     API_URL="https://api.sno.lab.example.com:6443"
     echo
     echo "Source ${WORK_DIR}/sno_env to set up PATH and KUBECONFIG:"
@@ -342,6 +343,7 @@ function print_cluster_info {
     echo "      to be ready ... if you see an authentication error with"
     echo "      the admin user, wait moments and try again."
     echo
+    set -x
 }
 
 function create {