NG_BRIDGE(4)

📦
version 15.1 · 2 versions
, in freebsd 15.1, nixpkgs unstable

okay bestie, this is NG_BRIDGE(4) from the Kernel Interfaces Manual — literally the page for the ng_bridge netgraph node type, and she is an Ethernet-bridging icon 💅✨

✨ NAME ✨

ng_bridge — Ethernet bridging netgraph node type. That’s the vibe: bridge node, Ethernet bridging, main character energy. Periodt.

🌸 SYNOPSIS 🌸

okay so before you can use her, you gotta include these, no cap:

#include <sys/types.h>
#include <netgraph/ng_bridge.h>

💖 DESCRIPTION 💖

bestie, the bridge node type performs Ethernet bridging over one or more links. Each link (represented by a connected hook) is used to transmit and receive raw Ethernet frames. As packets are received, the node learns which link each host resides on. Packets unicast to a known host are directed out the appropriate link only, and other links are spared the traffic. That is literally the selective-forwarding slay. This behavior is in contrast to a hub, which always forwards every received packet to every other link. Hub found boring, bridge found iconic 🫶

🌀 LOOP DETECTION 🌀

The bridge node incorporates a simple loop detection algorithm. A loop is when two ports are connected to the same physical medium. Loops are important to avoid because of packet storms, which severely degrade performance. A packet storm results when the same packet is sent and received over and over again. If a host is detected on link A, and is then detected on link B within a certain time period after first being detected on link A, then link B is considered to be a looped back link. The time period is called the minimum stable time.

A looped back link will be temporarily muted, i.e., all traffic received on that link is ignored. So yeah, she mutes the messy link for a bit. Not me being dramatic, that’s just the algorithm 💅

🔥 IPFW PROCESSING 🔥

Processing of IP packets via the ipfirewall(4) mechanism on a per-link basis is not yet implemented. So that feature is lowkey not here yet. Don’t come for me, I don’t make the rules 😭

🦋 HOOKS 🦋

This node type supports an unlimited number of hooks. Each connected hook represents a bridged link. The hooks are named link0, link1, etc. Typically these hooks are connected to the lower hooks of one or more ng_ether(4) nodes. To connect the host machine to a bridged network, simply connect the upper hook of an ng_ether(4) node to the bridge node.

Instead of naming a hook linkX the hook might be also named uplinkX. The node does not learn MAC addresses on uplink hooks, which keeps the internal address table small. This way it is desirable to connect the lower hook of an ng_ether(4) node to an uplink hook of the bridge, and ignore the complexity of the outside world. Frames with unknown MACs are always sent out to uplink hooks, so no functionality is lost. The uplink0 hook is not allowed. Ngl, uplink0 is banned from the group chat 💀

The linkX and uplinkX hook numbers can be autoassigned. If a new hook name was specified as link or uplink the node will append lowest available valid number to the name of the new hook.

Frames with unknown destination MAC addresses are replicated to any available hook, unless the first connected hook is an uplink hook. In this case the node assumes, that all unknown MAC addresses are located solely on the uplink hooks and only those hooks will be used to send out frames with unknown destination MACs. If the first connected hook is a link hook, the node will replicate such frames to all types of hooks, even if uplink hooks are connected later. That’s the whole first-impression rule, highkey.

👑 CONTROL MESSAGES 👑

okay bestie, this node type supports the generic control messages, plus the following — get into it 👑

  • NGM_BRIDGE_SET_CONFIG (setconfig) — set the node configuration. This command takes a struct ng_bridge_config as an argument:
/* Node configuration structure */
struct ng_bridge_config {
  u_char      debugLevel;           /* debug level */
  uint32_t    loopTimeout;          /* link loopback mute time */
  uint32_t    maxStaleness;         /* max host age before nuking */
  uint32_t    minStableAge;         /* min time for a stable host */
};

The debugLevel field sets the debug level on the node. At level of 2 or greater, detected loops are logged. The default level is 1.

The loopTimeout determines how long (in seconds) a looped link is muted. The default is 60 seconds. The maxStaleness parameter determines how long a period of inactivity before a host’s entry is forgotten. The default is 15 minutes. The minStableAge determines how quickly a host must jump from one link to another before we declare a loopback condition. The default is one second. So yes, she has timers, and yes, they are serving.

  • NGM_BRIDGE_GET_CONFIG (getconfig) — returns the current configuration as a struct ng_bridge_config. Give her a little vibe check and she’ll report back 💖
  • NGM_BRIDGE_RESET (reset) — causes the node to forget all hosts and unmute all links. The node configuration is not changed. It’s giving fresh start, not factory reset.
  • NGM_BRIDGE_GET_STATS (getstats) — this command takes a four byte link number as an argument and returns a struct ng_bridge_link_stats containing statistics for the corresponding link, which must be currently connected:
/* Statistics structure (one for each link) */
struct ng_bridge_link_stats {
  uint64_t   recvOctets;     /* total octets rec'd on link */
  uint64_t   recvPackets;    /* total pkts rec'd on link */
  uint64_t   recvMulticasts; /* multicast pkts rec'd on link */
  uint64_t   recvBroadcasts; /* broadcast pkts rec'd on link */
  uint64_t   recvUnknown;    /* pkts rec'd with unknown dest addr */
  uint64_t   recvRunts;      /* pkts rec'd less than 14 bytes */
  uint64_t   recvInvalid;    /* pkts rec'd with bogus source addr */
  uint64_t   xmitOctets;     /* total octets xmit'd on link */
  uint64_t   xmitPackets;    /* total pkts xmit'd on link */
  uint64_t   xmitMulticasts; /* multicast pkts xmit'd on link */
  uint64_t   xmitBroadcasts; /* broadcast pkts xmit'd on link */
  uint64_t   loopDrops;      /* pkts dropped due to loopback */
  uint64_t   loopDetects;    /* number of loop detections */
  uint64_t   memoryFailures; /* times couldn't get mem or mbuf */
};

Negative numbers refer to the uplink hooks. So querying for -7 will get the statistics for hook uplink7. Negative link number, positive slay.

  • NGM_BRIDGE_CLR_STATS (clrstats) — this command takes a four byte link number as an argument and clears the statistics for that link. Bye-bye, stats 🧚
  • NGM_BRIDGE_GETCLR_STATS (getclrstats) — same as NGM_BRIDGE_GET_STATS, but also atomically clears the statistics as well. Read and wipe, one atomic moment, obsessed.
  • NGM_BRIDGE_GET_TABLE (gettable) — returns the current host mapping table used to direct packets, in a struct ng_bridge_host_ary. It’s the address-table reveal ✨
  • NGM_BRIDGE_SET_PERSISTENT (setpersistent) — this command sets the persistent flag on the node, and takes no arguments. No args, just vibes.
  • NGM_BRIDGE_MOVE_HOST (movehost) — this command takes a struct ng_bridge_move_host as an argument. It assigns the MAC addr to the hook. If the hook is the empty string, the incoming hook of the control message is used as fallback.

If necessary, the MAC is removed from the currently assigned hook and moved to the new one. If the MAC is moved faster than minStableAge, the hook is considered as a loop and will block traffic for loopTimeout seconds.

struct ng_bridge_move_host {
  u_char  addr[ETHER_ADDR_LEN]; /* ethernet address */
  char    hook[NG_HOOKSIZ];     /* link where addr can be found */
};

💅 SHUTDOWN 💅

This node shuts down upon receipt of a NGM_SHUTDOWN control message, or when all hooks have been disconnected. Setting the persistent flag via a NGM_BRIDGE_SET_PERSISTENT control message disables automatic node shutdown when the last hook gets disconnected. So she can stay on read, basically.

🎀 FILES 🎀

  • /usr/share/examples/netgraph/ether.bridge — example script showing how to set up a bridging network. It’s giving tutorial energy, go look 🫶

🌈 SEE ALSO 🌈

⭐ HISTORY ⭐

The ng_bridge node type was implemented in FreeBSD 4.2. Vintage, but make it fresh.

🍓 AUTHORS 🍓

Archie Cobbs <archie@FreeBSD.org> — the icon behind this page, no cap.

💀 BUGS 💀

The ng_bridge node refuses to create the uplink0 hook to avoid later ambiguity with the NGM_BRIDGE_GET_STATS message. So uplink0 stays uninvited, fr fr.

mwah 💋 this page came from the Debian build, dated April 8, 2024 — love u, bestie, go bridge something iconic 🫶

📦 where this page comes from