## connecting to 172.20.5.79 as fireman ...
## connected


===== [uname] =====
$ uname -a; sysctl kern.version
OpenBSD mickopenbsd1.onecontact.local 7.8 GENERIC.MP#8 amd64
kern.version=OpenBSD 7.8 (GENERIC.MP) #8: Wed May  6 11:23:25 MDT 2026
    root@syspatch-78-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
[rc=0]

===== [rcd_files] =====
$ ls -la /etc/rc.d/ 2>&1 | grep -iE 'dhcp6|rad|slaac' || echo NONE
-r-xr-xr-x   1 root  wheel    285 Oct 12  2025 dhcp6leased
-r-xr-xr-x   1 root  wheel    254 Oct 12  2025 rad
-r-xr-xr-x   1 root  wheel    143 Oct 12  2025 radiusd
-r-xr-xr-x   1 root  wheel    137 Oct 12  2025 slaacd
[rc=0]

===== [rcctl_all] =====
$ rcctl ls all 2>/dev/null | grep -iE 'dhcp6|^rad$|rad|slaac' || echo NONE
dhcp6leased
rad
radiusd
slaacd
[rc=0]

===== [rcctl_on] =====
$ rcctl ls on 2>/dev/null | grep -iE 'dhcp6|rad|slaac' || echo NONE_ON
slaacd
[rc=0]

===== [rcctl_started] =====
$ rcctl ls started 2>/dev/null | grep -iE 'dhcp6|rad|slaac' || echo NONE_STARTED
NONE_STARTED
[rc=0]

===== [bins] =====
$ ls -la /sbin/dhcp6leased /usr/sbin/dhcp6leasectl /usr/sbin/rad /sbin/slaacd 2>&1
-r-xr-xr-x  1 root  bin  87432 Oct 12  2025 /sbin/dhcp6leased
-r-xr-xr-x  1 root  bin  77512 Apr 18 13:17 /sbin/slaacd
-r-xr-xr-x  1 root  bin  10576 Oct 12  2025 /usr/sbin/dhcp6leasectl
-r-xr-xr-x  1 root  bin  78616 Apr 14 10:57 /usr/sbin/rad
[rc=0]

===== [dhcp6leased_n] =====
$ dhcp6leased -n 2>&1; echo EXIT=$?
/etc/dhcp6leased.conf: No such file or directory
EXIT=1
[rc=0]

===== [rad_n] =====
$ rad -n 2>&1; echo EXIT=$?
/etc/rad.conf: No such file or directory
EXIT=1
[rc=0]

===== [example_dhcp6] =====
$ cat /etc/examples/dhcp6leased.conf 2>&1
cat: /etc/examples/dhcp6leased.conf: No such file or directory
[rc=1]

===== [example_rad] =====
$ cat /etc/examples/rad.conf 2>&1
# $OpenBSD: rad.conf,v 1.2 2018/07/25 05:11:49 jasper Exp $

# The most simple configuration is a single interface section which uses the
# interface IPv6 address to discover the prefix to announce.
#interface em0

# A slightly more complex case sets a prefix and basic DNS options.
interface em1 {
	prefix 2001:db8::/32
	dns {
		nameserver 2001:db8::53
		search example.org
	}
}
[rc=0]

===== [live_dhcp6_conf] =====
$ ls -la /etc/dhcp6leased.conf 2>&1; echo '---BODY---'; cat /etc/dhcp6leased.conf 2>&1 | head -40
ls: /etc/dhcp6leased.conf: No such file or directory
---BODY---
cat: /etc/dhcp6leased.conf: No such file or directory
[rc=0]

===== [live_rad_conf] =====
$ ls -la /etc/rad.conf 2>&1; echo '---BODY---'; cat /etc/rad.conf 2>&1 | head -40
ls: /etc/rad.conf: No such file or directory
---BODY---
cat: /etc/rad.conf: No such file or directory
[rc=0]

===== [man_dhcp6_conf] =====
$ man dhcp6leased.conf 2>&1 | col -bx
DHCP6LEASED.CONF(5)           File Formats Manual          DHCP6LEASED.CONF(5)

NAME
     dhcp6leased.conf - DHCPv6 client configuration file

DESCRIPTION
     The dhcp6leased(8) daemon is a dynamic host configuration protocol client
     daemon for IPv6 prefix delegation.

     The dhcp6leased.conf config file is divided into the following main
     sections:

     Macros
           Definitions of variables that can be used later, simplifying the
           configuration file.

     Global configuration
           Global settings for dhcp6leased(8).

     Prefix delegation
           dhcp6leased(8) requests prefix delegation from a DHCPv6 server and
           assigns prefixes to interfaces.  This section defines on which
           interfaces prefix delegation should be requested and to which
           interfaces prefixes should be assigned.

   Macros
     A macro is defined with a command of the form name=value.  The macro name
     can contain letters, digits, and underscores and cannot be a reserved
     word (for example, interface).  Within unquoted arguments, the string
     $name is later expanded to value.

   Global configuration
     These settings affect the operation of the dhcp6leased(8) daemon as a
     whole.

     request rapid commit
             Send the rapid commit DHCPv6 option, requesting a two-message
             exchange from the server instead of the normal four-message
             exchange.

   Prefix delegation
     A list of interfaces on which to request prefix delegation:

     request prefix delegation on name for {name[/prefix] ...}

     This requests a prefix delegation on the upstream network interface name
     for the list of name[/prefix] network interfaces.  If prefix is omitted a
     default of /64 is used.

     dhcp6leased(8) will calculate the prefix length needed to cover all
     interfaces in the list.  When a prefix is delegated by a DHCPv6 server,
     dhcp6leased(8) splits the prefix into smaller prefixes and assigns them
     to the interfaces in the order they are listed.  This might create
     unassigned gaps in the delegated prefix.

     For example if a /64 and /60 prefix are to be assigned to network
     interfaces, dhcp6leased(8) requests a /59 prefix.  The prefix is then
     split into two /60 prefixes and the first /64 out of the first /60 prefix
     is assigned to the first interface.  The second /60 prefix from the
     delegated /59 is assigned to the second interface.  This leaves 15 unused
     /64 prefixes in the first /60.

     Care should be taken to avoid renumbering of existing interfaces when new
     interfaces are added or existing interfaces are removed.  New interfaces
     can be added to the end of the list or in places where unassigned gaps
     were present.

     The special name reserve can be used to reserve space in the delegated
     prefix for later use or when an interface is removed.

     Running dhcp6leased(8) in configtest mode with a verbosity of two or more
     will print the configuration file with comments indicated how prefixes
     would be assigned to network interfaces.  This can be used to check that
     existing interface are not renumbered.

     More than one prefix can be requested from a DHCPv6 server, however most
     ISP DHCPv6 servers will only delegate a single prefix.  Therefore it is
     better to let dhcp6leased(8) request a single larger prefix and split it
     up.  dhcp6leased(8) has a compile time limit on how many prefix requests
     per interface it can handle.

FILES
     /etc/dhcp6leased.conf  dhcp6leased(8) configuration file.

SEE ALSO
     dhcp6leasectl(8), dhcp6leased(8)

OpenBSD 7.8                      July 8, 2025              DHCP6LEASED.CONF(5)
[rc=0]

===== [man_rad_conf] =====
$ man rad.conf 2>&1 | col -bx
RAD.CONF(5)                   File Formats Manual                  RAD.CONF(5)

NAME
     rad.conf - router advertisement daemon configuration file

DESCRIPTION
     The rad(8) daemon is an IPv6 router advertisement daemon.

     The rad.conf config file is divided into the following main sections:

     Macros
           Definitions of variables that can be used later, simplifying the
           configuration file.

     Global configuration
           Global settings for rad(8).  These are used as default values for
           interface definitions and can be overwritten in an interface block.

     Interfaces
           rad(8) sends IPv6 router advertisement messages.  This section
           defines on which interfaces to advertise prefix information and
           their associated parameters.

     Additional configuration files can be included with the include keyword.

   Macros
     A macro is defined with a command of the form name=value.  The macro name
     can contain letters, digits, and underscores and cannot be a reserved
     word (for example, interface).  Within unquoted arguments, the string
     $name is later expanded to value.

   Global configuration
     The global configuration section sets defaults for router advertisement
     messages.  These can be overwritten in interface blocks.

     default router (yes|no)
             Act as a default router or not.  The default is yes.

     dns {option ...}
             Add a DNS router advertisement option to communicate network
             provided nameservers.  In a dns block, a search option or at
             least one nameserver option is required, whereas specifying the
             lifetime is optional:

             lifetime seconds
                     The number of seconds the dns options are valid after
                     receiving a router advertisement message.  The default is
                     1800 seconds.

             nameserver (address|{address ...})
                     IPv6 address or list of IPv6 addresses of DNS name
                     servers.

             search (domain|{domain ...})
                     Domain or list of domains for the resolv.conf(5) search
                     list.

     hop limit hops
             Specify the diameter of the internet.  The default is 0, meaning
             unspecified by this router.

     managed address configuration (yes|no)
             If set to yes, indicate that stateless address configuration
             prefixes are not available and hosts should consult DHCPv6.  The
             default is no.

     mtu bytes
             The MTU option is used in Router Advertisement messages to ensure
             that all nodes on a link use the same MTU value in those cases
             where the link MTU is not well known.  The default is 0, meaning
             unspecified by this router.

     nat64 prefix prefix [{option ...}]
             Add a PREF64 router advertisement option to communicate prefixes
             used for Network Address and Protocol Translation from IPv6 to
             IPv4 (NAT64).  If prefix is specified without a prefix length,
             its default is 64.

             nat64 prefix options are as follows:

             lifetime seconds
                     The number of seconds the nat64 prefix option is valid
                     after receiving a router advertisement message.  A value
                     of zero indicates to not use the prefix anymore.  The
                     maximum is 65528 seconds.  The default is 1800 seconds.

     other configuration (yes|no)
             If set to yes, hosts should consult DHCPv6 for additional
             configuration like NTP servers or DNS name servers.  The default
             is no.

     router lifetime seconds
             The number of seconds this router is a valid default router after
             receiving a router advertisement message.  The default is 1800
             seconds.

     router preference (high|medium|low)
             Indicate whether to prefer this router over other default
             routers.  The default is medium.

     reachable time number
             The time, in milliseconds, that a node assumes a neighbor is
             reachable.  The default is 0, meaning unspecified by this router.
             This option is ignored by slaacd(8) and cannot be set on OpenBSD
             IPv6 hosts.

     retrans timer number
             The time, in milliseconds, between retransmitted Neighbor
             Solicitation messages.  The default is 0, meaning unspecified by
             this router.  This option is ignored by slaacd(8) and cannot be
             set on OpenBSD IPv6 hosts.

     source link-layer address (yes|no)
             Add a source link-layer address option to router advertisement
             messages, to communicate the link-layer address of the sending
             interface.  The default is yes.

   Interfaces
     This section contains a list of interfaces or interface groups to send
     advertisements on.  At least one interface is required.

     interface name [{prefix ...}]
             Options set in the global section can be overwritten inside an
             interface block.  In addition an interface block can contain a
             list of prefixes:

             [no] auto prefix [{option ...}]
             prefix prefix [{option ...}]
                     The default is to discover prefixes to announce by
                     inspecting the IPv6 addresses configured on an interface.
                     This can be disabled with no auto prefix.  If prefix is
                     specified without a prefix length, its default is 64.

                     prefix options are as follows:

                     autonomous address-configuration (yes|no)
                             This prefix can be used to generate IPv6
                             addresses.  The default is yes.

                     on-link (yes|no)
                             This prefix is considered on-link.  The default
                             is yes.

                     preferred lifetime seconds
                             The preferred lifetime (pltime) in seconds for
                             addresses generated from this prefix.  The
                             default is 2700.  This option is ignored if the
                             prefix is discovered from a network interface and
                             it has a lower preferred lifetime.

                     valid lifetime seconds
                             The valid lifetime (vltime) in seconds for
                             addresses generated from this prefix.  The
                             default is 5400.  This option is ignored if the
                             prefix is discovered from a network interface and
                             it has a lower valid lifetime.

FILES
     /etc/rad.conf           rad(8) configuration file.
     /etc/examples/rad.conf  Example configuration file.

EXAMPLES
     With the following example configuration, rad(8) will pick a prefix from
     the ix1 interface and send router advertisements on it:

           interface ix1

SEE ALSO
     ractl(8), rad(8), rc.conf.local(8)

HISTORY
     The rad.conf file format first appeared in OpenBSD 6.4.

OpenBSD 7.8                   September 15, 2025                   RAD.CONF(5)
[rc=0]

===== [man_dhcp6leased] =====
$ man dhcp6leased 2>&1 | col -bx | sed -n '1,90p'
DHCP6LEASED(8)              System Manager's Manual             DHCP6LEASED(8)

NAME
     dhcp6leased - Dynamic Host Configuration Protocol (DHCPv6) client daemon
     for IPv6 prefix delegation

SYNOPSIS
     dhcp6leased [-dnv] [-f file] [-s socket]

DESCRIPTION
     dhcp6leased is an IPv6 dynamic host configuration protocol (DHCPv6)
     daemon for clients.  It requests IPv6 prefix delegations from DHCPv6
     servers for assignment to downstream interfaces.

     DHCPv6 clients are identified by DHCPv6 Unique Identifiers (DUID).
     dhcp6leased uses a DUID based on a random Universally Unique Identifier
     (UUID).  The DUID is stored in /var/db/dhcp6leased/uuid.  If the file
     does not exist or the UUID is not readable a new UUID is generated.

     A running dhcp6leased can be controlled with the dhcp6leasectl(8)
     utility.

     The options are as follows:

     -d      Do not daemonize.  If this option is specified, dhcp6leased will
             run in the foreground and log to stderr.

     -f file
             Specify an alternative configuration file.

     -n      Configtest mode.  Only check the configuration file for validity.

     -s socket
             Use an alternate location for the default control socket.

     -v      Produce more verbose output.  Multiple -v options increase the
             verbosity.

FILES
     /dev/dhcp6leased.sock     Unix-domain socket used for communication with
                               dhcp6leasectl(8).
     /etc/dhcp6leased.conf     Default dhcp6leased configuration file.
     /var/db/dhcp6leased/<if>  Interface specific lease files.
     /var/db/dhcp6leased/uuid  DUID to identify this client.

SEE ALSO
     dhcp6leased.conf(5), dhcp6leasectl(8), ifconfig(8)

STANDARDS
     T. Mrugalski, M. Siodelski, B. Volz, A. Yourtchenko, M. Richardson, S.
     Jiang, T. Lemon, and T. Winters, Dynamic Host Configuration Protocol for
     IPv6 (DHCPv6), RFC 8415, November 2018.

HISTORY
     The dhcp6leased program first appeared in OpenBSD 7.6.

AUTHORS
     The dhcp6leased program was written by Florian Obser
     <florian@openbsd.org>.

OpenBSD 7.8                    October 29, 2024                 DHCP6LEASED(8)
[rc=0]

===== [man_dhcp6ctl] =====
$ man dhcp6leasectl 2>&1 | col -bx
DHCP6LEASECTL(8)            System Manager's Manual           DHCP6LEASECTL(8)

NAME
     dhcp6leasectl - control the dhcp6leased client

SYNOPSIS
     dhcp6leasectl [-l] [-s socket] [-w maxwait] interface

DESCRIPTION
     The dhcp6leasectl program instructs the dhcp6leased(8) daemon to request
     a new lease.

     The following options are available:

     -l      List the configured lease on interface instead of requesting a
             new lease.

     -s socket
             Use socket instead of the default /dev/dhcp6leased.sock to
             communicate with dhcp6leased(8).

     -w maxwait
             Specify the maximum number of seconds to wait for interface to be
             configured.  The default is 10 seconds.

FILES
     /dev/dhcp6leased.sock    Unix-domain socket used for communication with
                              dhcp6leased(8).

SEE ALSO
     dhcp6leased.conf(5), dhcp6leased(8)

HISTORY
     The dhcp6leasectl program first appeared in OpenBSD 7.6.

OpenBSD 7.8                      June 7, 2024                 DHCP6LEASECTL(8)
[rc=0]

===== [man_rad] =====
$ man rad 2>&1 | col -bx | sed -n '1,90p'
RAD(8)                      System Manager's Manual                     RAD(8)

NAME
     rad - router advertisement daemon

SYNOPSIS
     rad [-dnv] [-f file] [-s socket]

DESCRIPTION
     rad is an IPv6 router advertisement daemon.  It periodically sends IPv6
     router advertisement messages with prefix and default router information.
     Clients like slaacd(8) use these to configure IPv6 addresses on network
     interfaces and set default routes.  Additionally it listens for IPv6
     router solicitation messages and responds with router advertisements.

     To have rad enabled at boot time, use "rcctl enable rad", which sets

           rad_flags=""

     in rc.conf.local(8).

     A running rad can be controlled with the ractl(8) utility.

     The options are as follows:

     -d      Do not daemonize.  If this option is specified, rad will run in
             the foreground and log to stderr.

     -f file
             Specify an alternative configuration file.

     -n      Configtest mode.  Only check the configuration file for validity.

     -s socket
             Use an alternate location for the default control socket.

     -v      Produce more verbose output.

FILES
     /etc/rad.conf        Default rad configuration file.
     /var/run/rad.sock    Unix-domain socket used for communication with
                          ractl(8).

SEE ALSO
     rad.conf(5), ractl(8), slaacd(8)

STANDARDS
     R. Draves and D. Thaler, Default Router Preferences and More-Specific
     Routes, RFC 4191, November 2005.

     R. Hinden and S. Deering, IP Version 6 Addressing Architecture, RFC 4291,
     February 2006.

     T. Narten, E. Nordmark, W. Simpson, and H. Soliman, Neighbor Discovery
     for IP version 6 (IPv6), RFC 4861, September 2007.

     A. Yourtchenko and L. Colitti, Reducing Energy Consumption of Router
     Advertisements, RFC 7772, February 2016.

     J. Jeong, S. Park, L. Beloeil, and S. Madanapalli, IPv6 Router
     Advertisement Options for DNS Configuration, RFC 8106, March 2017.

     L. Colitti and J. Linkova, Discovering PREF64 in Router Advertisements,
     RFC 8781, April 2020.

HISTORY
     The rad program first appeared in OpenBSD 6.4.

AUTHORS
     The rad program was written by Florian Obser <florian@openbsd.org>.

OpenBSD 7.8                    October 15, 2022                         RAD(8)
[rc=0]

===== [man_slaacd] =====
$ man slaacd 2>&1 | col -bx | sed -n '1,110p'
SLAACD(8)                   System Manager's Manual                  SLAACD(8)

NAME
     slaacd - Stateless Address Autoconfiguration (SLAAC) daemon

SYNOPSIS
     slaacd [-dv] [-s socket]

DESCRIPTION
     slaacd is a stateless address autoconfiguration (SLAAC) daemon for
     clients.  If an interface has the AUTOCONF6 flag set (auto configuration
     is enabled), slaacd regularly sends out requests for IPv6 router
     advertisement messages, such as those sent by rad(8), and uses those
     messages to configure the relevant interface.

     See hostname.if(5) and ifconfig(8) on how to enable auto configuration on
     an interface.

     slaacd monitors network interface states (interface going up or down,
     auto configuration enabled or disabled, etc.) and sends router
     solicitations when necessary.  A running slaacd can be controlled with
     the slaacctl(8) utility.

     The options are as follows:

     -d      Do not daemonize.  If this option is specified, slaacd will run
             in the foreground and log to stderr.

     -s socket
             Use an alternate location for the default control socket.

     -v      Produce more verbose output.  Multiple -v options increase the
             verbosity.

FILES
     /dev/slaacd.sock    Unix-domain socket used for communication with
                         slaacctl(8).

SEE ALSO
     hostname.if(5), ifconfig(8), rad(8), slaacctl(8)

STANDARDS
     R. Draves and D. Thaler, Default Router Preferences and More-Specific
     Routes, RFC 4191, November 2005.

     R. Hinden and S. Deering, IP Version 6 Addressing Architecture, RFC 4291,
     February 2006.

     T. Narten, E. Nordmark, W. Simpson, and H. Soliman, Neighbor Discovery
     for IP version 6 (IPv6), RFC 4861, September 2007.

     F. Gont, A Method for Generating Semantically Opaque Interface
     Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC), RFC
     7217, April 2014.

     A. Yourtchenko and L. Colitti, Reducing Energy Consumption of Router
     Advertisements, RFC 7772, February 2016.

     F. Gont, A. Cooper, D. Thaler, and W. Liu, Recommendation on Stable IPv6
     Interface Identifiers, RFC 8064, February 2017.

     J. Jeong, S. Park, L. Beloeil, and S. Madanapalli, IPv6 Router
     Advertisement Options for DNS Configuration, RFC 8106, March 2017.

     F. Gont, S. Krishnan, T. Narten, and R. Draves, Temporary Address
     Extensions for Stateless Address Autoconfiguration in IPv6, RFC 8981,
     February 2021.

HISTORY
     The slaacd program first appeared in OpenBSD 6.2.

AUTHORS
     The slaacd program was written by Florian Obser <florian@openbsd.org>.

OpenBSD 7.8                     August 11, 2024                      SLAACD(8)
[rc=0]

===== [leasedb] =====
$ ls -la /var/db/dhcp6leased 2>&1; echo '---'; ls -la /var/db/dhcpleased 2>&1
total 8
drwxr-xr-x   2 root  wheel  512 Oct 12  2025 .
drwxr-xr-x  12 root  wheel  512 Jun 27 10:43 ..
---
total 12
drwxr-xr-x   2 root  wheel  512 May 27 00:14 .
drwxr-xr-x  12 root  wheel  512 Jun 27 10:43 ..
-rw-r--r--   1 root  wheel  105 May 27 10:32 vio0
[rc=0]

===== [sysctl_ip6] =====
$ sysctl net.inet6.ip6 2>&1 | grep -iE 'forward|tempaddr|accept|soii|mtudisc|auto'
net.inet6.ip6.forwarding=1
net.inet6.ip6.mforwarding=0
net.inet6.ip6.multicast_mtudisc=0
net.inet6.ip6.mtudisctimeout=600
[rc=0]

===== [ifconfig_brief] =====
$ ifconfig -a 2>&1 | grep -E '^[a-z]|inet6 |inet ' | head -100
lo0: flags=2008049<UP,LOOPBACK,RUNNING,MULTICAST,LRO> mtu 32768
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
	inet6 ::1 prefixlen 128
	inet 127.0.0.1 netmask 0xff000000
vio0: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST> mtu 1500
	inet 172.20.5.79 netmask 0xffffff00 broadcast 172.20.5.255
vio1: flags=2008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LRO> mtu 1500
enc0: flags=0<>
bridge0: flags=41<UP,RUNNING> mtu 1500
bridge1: flags=41<UP,RUNNING> mtu 1500
gre0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1476
	tunnel: inet 172.20.5.79 --> 5.0.0.1 ttl 64 nodf ecn
vether0: flags=808943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,AUTOCONF4> mtu 1500
vlan0: flags=808943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,AUTOCONF4> mtu 1500
vlan1: flags=808943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,AUTOCONF4> mtu 1500
	inet 5.5.5.5 netmask 0xffffff00 broadcast 5.5.5.255
vlan5: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	inet 1.2.3.4 netmask 0xffffff00 broadcast 1.2.3.255
vxlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1520
	tunnel: inet 172.20.5.79:4789 --> 5.0.0.1 ttl 1 nodf
vxlan1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	tunnel: inet 1.2.3.4:4789 --> 2.2.2.2 ttl 1 nodf
vxlan2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	tunnel: inet 5.5.5.5:4789 --> 224.0.0.1 ttl 1 nodf
wg0: flags=8043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1420
	inet 10.1.2.1 netmask 0xffffff00 broadcast 10.1.2.255
wg1: flags=8043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1420
	inet 10.92.0.21 netmask 0xffffff00 broadcast 10.92.0.255
[rc=0]

===== [unbound_v6] =====
$ man unbound.conf 2>&1 | col -bx | grep -B1 -A3 -iE 'interface:|access-control:|do-ip6|interface-automatic|ip-transparent' | head -80

     interface: <IP address or interface name[@port]>
            Interface to use to connect to the network.  This interface is
            listened to for queries from clients, and answers to clients are
            given from it.  Can be given multiple times to work on several
--

     interface-automatic: <yes or no>
            Listen on all addresses on all (current and future) interfaces,
            detect the source interface on UDP queries and copy them to
            replies.  This is a lot like ip-transparent, but this option
            services all interfaces whilst with ip-transparent you can select
            which (future) interfaces Unbound provides service on.  This
            feature is experimental, and needs support in your OS for
            particular socket options.
--

     interface-automatic-ports: "<string>"
            List the port numbers that interface-automatic listens on.  If
            empty, the default port is listened on.  The port numbers are
            separated by spaces in the string.

--

     outgoing-interface: <IPv4/IPv6 address or IPv6 netblock>
            Interface to use to connect to the network.  This interface is
            used to send queries to authoritative servers and receive their
            replies.  Can be given multiple times to work on several
--

     ip-transparent: <yes or no>
            If yes, then use IP_TRANSPARENT socket option on sockets where
            Unbound is listening for incoming traffic.  Allows you to bind to
            non-local interfaces.  For example for non-existent IP addresses
--

            This is a lot like interface-automatic, but that one services all
            interfaces and with this option you can select which (future)
            interfaces Unbound provides service on.

--

            Exists only on Linux, where the similar ip-transparent option is
            also available.

            Default: no
--

     do-ip6: <yes or no>
            Enable or disable whether IPv6 queries are answered or issued.  If
            disabled, queries are not answered on IPv6, and queries are not
            sent on IPv6 to the internet nameservers.  With this option you
--

     access-control: <IP netblock> <action>
            Specify treatment of incoming queries from their originating IP
            address.  Queries can be allowed to have access to this server
            that gives DNS answers, or refused, with other actions possible.
--
            as they will be overridden by the implicit default
            "access-control: 127.0.0.0/8 allow" option.

            NOTE:
               The interface needs to be already specified with interface and
--

     control-interface: <IP address or interface name or path>
            Give IPv4 or IPv6 addresses or local socket path to listen on for
            control commands.  If an interface name is used instead of an IP
            address, the list of IP addresses on that interface are used.
[rc=0]

===== [ifconfig_v6_man] =====
$ man ifconfig 2>&1 | col -bx | grep -B1 -A3 -iE 'autoconf|temporary|eui64|AUTOCONF|soii' | head -70

     autoconf        Set the AUTOCONF4 or AUTOCONF6 flag on the interface,
                     depending on address_family.  slaacd(8) automatically
                     configures IPv6 addresses for interfaces with AUTOCONF6
                     set.  dhcpleased(8) automatically configures IPv4
                     addresses (using DHCP protocol) for interfaces with
                     AUTOCONF4 set.

                     Automatically mark the interface as "up".

--
     -autoconf       Unset the AUTOCONF4 or AUTOCONF6 flag on the interface,
                     depending on address_family.

     broadcast addr  (inet only) Specify the address to use to represent
--
                     configured inet6(4) addresses, including the link-local
                     ones.  This is the default.  To turn inet6 on, use eui64
                     or autoconf, or assign any inet6 address.

     instance minst  Set the media instance to minst.  This is useful for
                     devices which have multiple physical layer interfaces
--
INET6
     ifconfig interface inet6 [[-]anycast] [[-]temporary] [eui64] [pltime n]
              [[-]soii] [[-]tentative] [vltime n]

     The following options are available for an ip6(4) interface:

--

     temporary
             Enable temporary address extensions for stateless IPv6 address
             autoconfiguration (RFC 8981) on the interface.  These extensions
             are enabled by default.  The purpose of these extensions is to
             prevent tracking of individual devices which connect to the IPv6
             internet from different networks using stateless
--
             autoconfiguration.  The interface identifier often remains
             constant and provides the lower 64 bits of an autoconfigured IPv6
             address, facilitating tracking of individual devices (and hence,
             potentially, users of these devices) over long periods of time
             (weeks to months to years).  When these extensions are active,
--
             random interface identifiers are used for autoconfigured
             addresses.

             Autoconfigured addresses are also made temporary, which means
             that they will automatically be replaced regularly.  Temporary
             addresses are deprecated after 24 hours.  Once a temporary
             address has been deprecated, a new temporary address will be
             configured upon reception of a router advertisement indicating
             that the prefix is still valid.  Deprecated addresses will not be
             used for new connections as long as a non-deprecated address
--
             remains available.  Temporary addresses become invalid after
             another 24 hours, at which time they will be removed from the
             interface.

--
     -temporary
             Disable IPv6 autoconf temporary address extensions on the
             interface.  Currently configured addresses will not be removed
             until they become invalid.

--
     eui64   Fill the interface index (the lowermost 64 bits of an IPv6
             address) automatically.

     pltime n
[rc=0]

===== [hostname_if_man] =====
$ man hostname.if 2>&1 | col -bx | grep -B1 -A3 -iE 'inet6|autoconf|rtsol|eui64|slaac' | head -60
     each network interface.  Interfaces are referenced by name and unit, such
     as "hostname.fxp0".  For some machines, autoconfiguration makes this
     system inconsistent, so interfaces can alternatively be referenced by
     their link layer address (lladdr), such as "hostname.00:00:5e:00:53:af".
     Priority is given to configuration by interface lladdr over name/unit.  A
--
           join mynwid wpakey mywpakey
           inet6 autoconf
           inet autoconf

     would run ifconfig three times to add a wireless network using WPA to the
     join list and enable dynamic address configuration for IPv6 and IPv4.
--

           inet6 [alias] addr prefixlen options
           dest dest_addr

     Other network setup:
--
      # This is an example comment line.
      inet6 alias fec0::1 64
      inet6 alias fec0::2 64 anycast
      !route add 65.65.65.65 10.0.1.13
      up

--
                   The address family of the interface, generally "inet" or
                   "inet6".

           alias   The literal string "alias" if this is an additional network
                   address for the interface.
--
                         inet 192.0.2.1/32
                         inet6 2001:db8::1/128
                         up
                         !route sourceaddr -ifp \$if

--
DYNAMIC ADDRESS CONFIGURATION
     IPv4 dynamic addressing via DHCP is requested using "inet autoconf"
     followed by any options to be passed to ifconfig(8).

           inet autoconf [ifconfig_options]

     The token "dhcp" on its own line without any options is short for "inet
     autoconf".

     IPv6 stateless address autoconfiguration is requested using the literal
     string "inet6 autoconf" followed by any options to be passed to
     ifconfig(8).

           inet6 autoconf [ifconfig_options]

     The autoconf configurations will communicate learned DNS information to
     resolvd(8).

FILES
--
SEE ALSO
     hosts(5), ifconfig(8), netstart(8), rc(8), slaacd(8)
[rc=0]

## done
