DHCP no longer works

[igalic]

DHCP no longer works

[igalic]

to quote the jail(8) man page:

devfs_ruleset

The number of the devfs ruleset that is enforced for mounting devfs in this jail. A value of zero (default) means no ruleset is enforced. Descendant jails inherit the parent jail's devfs ruleset enforcement. Mounting devfs inside a jail is possible only if the allow.mount and allow.mount.devfs permissions are effective and enforce_statfs is set to a value lower than 2. Devfs rules and rulesets cannot be viewed or modified from inside a jail.

NOTE: It is important that only appropriate device nodes in devfs be exposed to a jail; access to disk devices in the jail may permit processes in the jail to bypass the jail sandboxing by modifying files outside of the jail. See devfs(8) for information on how to use devfs rules to limit access to entries in the per-jail devfs. A simple devfs ruleset for jails is available as ruleset #4 in /etc/defaults/devfs.rules.

and

enforce_statfs

This determines what information processes in a jail are able to get about mount points. It affects the behaviour of the following syscalls: statfs(2), fstatfs(2), getfsstat(2), and fhstatfs(2) (as well as similar compatibility syscalls). When set to 0, all mount points are available without any restrictions. When set to 1, only mount points below the jail's chroot directory are visible. In addition to that, the path to the jail's chroot directory is removed from the front of their pathnames. When set to 2 (default), above syscalls can operate only on a mount-point where the jail's chroot directory is located.

[igalic]

results from further investigation:

this function

libioc/libioc/Config/Jail/BaseConfig.py

Lines 365 to 376 in 1563cd8

	def _get_enforce_statfs(self) -> int:
	key = "enforce_statfs"
	if key in self.data.keys():
	return int(self.data[key])
	if self.__has_mounts_enabled:
	self.logger.verbose(
	"setting enforce_statfs=1 to support allowed mounts"
	)
	return 1
	raise KeyError(f"{key} unconfigured")

is never called

---

funnily enough, that function was only introduced in #727 — which is believed to be the cause of this issue.

[gronke]

fixed in #734