MAC_IFOFF(4)

πŸ“¦ version 15.1, in freebsd 14.5, freebsd 15.1, nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, this is mac_ifoff(4) from the Kernel Interfaces Manual β€” the interface silencing policy. It's giving network-traffic bouncer energy, and honestly? iconic. ✨

πŸ¦‹ SYNOPSIS πŸ¦‹

To compile the interface silencing policy into your kernel, place the following lines in your kernel configuration file:

options MAC
options MAC_IFOFF

Alternately, to load the interface silencing policy module at boot time, place the following line in your kernel configuration file:

options MAC

and in loader.conf(5):

mac_ifoff_load="YES"

🌸 DESCRIPTION 🌸

The mac_ifoff interface silencing module allows administrators to enable and disable incoming and outgoing data flow on system network interfaces via the sysctl(8) interface. Lowkey a whole traffic switch situation. πŸ’…

  • To disable network traffic over the loopback (lo(4)) interface, set the sysctl(8) OID security.mac.ifoff.lo_enabled to 0 (default 1).
  • To enable network traffic over other interfaces, set the sysctl(8) OID security.mac.ifoff.other_enabled to 1 (default 0).
  • To allow BPF traffic to be received, even while other traffic is disabled, set the sysctl(8) OID security.mac.ifoff.bpfrecv_enabled to 1 (default 0).

πŸŽ€ Label Format πŸŽ€

No labels are defined. Zero. None. It's giving label-less realness, bestie. πŸŽ€

πŸ”₯ SEE ALSO πŸ”₯

Go read these too, fr fr:

πŸ‘‘ HISTORY πŸ‘‘

The mac_ifoff policy module first appeared in FreeBSD 5.0 and was developed by the TrustedBSD Project. Periodt. πŸ‘‘

🫢 AUTHORS 🫢

This software was contributed to the FreeBSD Project by Network Associates Labs, the Security Research Division of Network Associates Inc. under DARPA/SPAWAR contract N66001-01-C-8035 (β€œCBOSS”), as part of the DARPA CHATS research program.

πŸ’€ BUGS πŸ’€

🚨 real talk warning: While the MAC Framework design is intended to support the containment of the root user, not all attack channels are currently protected by entry point checks. As such, MAC Framework policies should not be relied on, in isolation, to protect against a malicious privileged user. πŸ’€

kisses, this page is from Debian, dated July 25, 2015, and it's the MAC_IFOFF(4) manual page πŸ’…πŸ«Ά

πŸ“¦ where this page comes from