Quote-O, --dhcp-option=[tag:<tag>,[tag:<tag>,]][encap:<opt>,][vi-encap:<enterprise>,][vendor:[<vendor-class>],][<opt>|option:<opt-name>|option6:<opt>|option6:<opt-name>],[<value>[,<value>]]
...
An option without data is valid, and includes just the option without data. (There is only one option with a zero length data field currently defined for DHCPv4, 80:rapid commit, so this feature is not very useful in practice). Options for which dnsmasq normally provides default values can be omitted by defining the option with no data. These are netmask, broadcast, router, DNS server, domainname and hostname. Thus, for DHCPv4 --dhcp-option = option:router will result in no router option being sent, rather than the default of the host on which dnsmasq is running. For DHCPv6, the same is true of the options DNS server and refresh time.
$ ip a
...
2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 1000
link/ether <redacted> brd ff:ff:ff:ff:ff:ff
inet 172.21.30.100/24 brd 172.21.30.255 scope global dynamic noprefixroute enp6s0
valid_lft 86248sec preferred_lft 86248sec
inet6 fd7b:1236:9970:1003:e717:cc84:66e1:d8f3/64 scope global temporary dynamic
valid_lft 86357sec preferred_lft 85901sec
inet6 fd7b:1236:9970:1003:44df:603e:214c:824f/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 86357sec preferred_lft 86357sec
inet6 26xx:xx:xxxx:3163:a54b:860e:9bf9:3109/64 scope global temporary dynamic
valid_lft 86357sec preferred_lft 85901sec
inet6 26xx:xx:xxxx:3163:xxxx:xxxx:xxxx:xxx/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 86357sec preferred_lft 86357sec
inet6 fe80::xxxx:xxxx:xxx:xxxx/64 scope link noprefixroute
valid_lft forever preferred_lft forever
$ resolvectl status
Current DNS Server: 172.21.30.1
DNS Servers: 172.21.30.1 26xx:xx:xxxx:3163::1
DNS Domain: clear.h1.internal
root@hds-firewall:/tmp/os-amneziawg # sh install.sh
============================================================
os-amneziawg plugin installer
============================================================
Current version : 2.6.0
New version : 2.6.0
Version 2.6.0 is already installed.
Reinstall? [y/N] y
==> Pre-check: Verifying pkg integrity...
[OK] pkg is healthy
==> Step 1: Checking AmneziaWG packages...
Missing packages detected:
- amnezia-tools (awg, awg-quick)
Install from FreeBSD quarterly repo? [Y/n]
[OK] Temporary FreeBSD quarterly repo configured
[OK] pkg locked (preventing self-upgrade from quarterly)
Updating FreeBSD-quarterly repository catalogue...
Fetching meta.conf: 100% 179 B 0.2kB/s 00:01
Fetching packagesite.pkg: 100% 10 MiB 5.5MB/s 00:02
Processing entries: 100%
FreeBSD-quarterly repository update completed. 37061 packages processed.
All repositories are up to date.
Installing amnezia-tools...
Updating FreeBSD-quarterly repository catalogue...
Unable to update repository FreeBSD-quarterly
Error updating repositories!
[WARN] Failed to install amnezia-tools via pkg.
Try manually: pkg add <URL from pkg.freebsd.org>
[OK] Temporary FreeBSD repo config removed
[WARN] One or more binaries/modules are still missing.
[WARN] Plugin will be installed but AmneziaWG will NOT start.
==> Step 2: Checking for existing AmneziaWG configuration...
[OK] No existing configuration found (clean install).
==> Step 3: Installing plugin files...
[OK] Plugin files installed.
==> Step 4: Restarting configd...
Stopping configd...done
Starting configd.
==> Step 5: Clearing cache...
============================================================
os-amneziawg v2.6.0 installed!
============================================================***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 26.1.6 (amd64) at Fri Apr 17 09:29:21 CEST 2026
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 929 packages processed.
Updating SunnyValley repository catalogue...
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
repository SunnyValley has no meta file, using default settings
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
Unable to update repository SunnyValley
Error updating repositories!
***DONE***Quote from: Patrick M. Hausen on Today at 08:36:05 AMSeparating clients of different trust levels into different networks, e.g. via VLANs, is common best practice, yes.