RPORT(4)

💅 RPORT(4) — the rport manual, bestie edition 🎀

okay so real talk, this is from the Kernel Interfaces Manual, and it's literally all about rport — the rdomain port interface pseudo-device. yes that's a mouthful, we'll get through it together 🫶

---

✨ NAME ✨

rport — the rdomain port interface pseudo-device. it's giving "networking but make it modular" 💜

---

🌸 SYNOPSIS 🌸

pseudo-device rport

that's it. that's the whole vibe check. one line. iconic 👑

---

🦋 DESCRIPTION 🦋

okay so the rport driver hands you point-to-point interfaces for layer 3 connectivity between rdomain(4) instances. lowkey genius ✨

you wanna get two rdomains talking at layer 3? the move is: create an rport interface in each rdomain, then link them together by configuring one of these interfaces as the parent of the other. that's the whole connecting-scheme, no cap 🔥

and here's the fun part — you can make rport interfaces at runtime with the ifconfig rportN create command, or by setting up a hostname.if(5) configuration file for netstart(8). either way slays 💅

the interface itself gets configured with ifconfig(8) — go read its manual page for the deets, iykyk 📖

---

💖 EXAMPLES 💖

okay bestie here's the actual recipe 🍓 — create two rport interfaces in separate rdomain(4) instances and connect them together:

# ifconfig rport0 create rdomain 0 up
# ifconfig rport1 create rdomain 1 parent rport0 up
# ifconfig rport0 inet 192.168.0.0/32 192.168.0.1
# ifconfig rport1 inet 192.168.0.1/32 192.168.0.0

see how rport1 gets parent rport0? that's the glue, bestie 🧚✨ and then the inet lines are literally just the two ends of the link. ate. 💀

---

🌈 SEE ALSO 🌈

• netintro(4)
• veb(4)
• hostname.if(5)
• pf.conf(5)
• ifconfig(8)
• netstart(8)

the whole friend group, honestly 💜

---

⭐ HISTORY ⭐

the rport driver first appeared in OpenBSD 7.6. a recent king 👑 periodt.

---

🎀 AUTHORS 🎀

David Gwynne <dlg@openbsd.org>. that's the main character energy right there, we stan 🙈💖

---

💀 CAVEATS 💀

okay before you go wild, read this part, fr fr:

a pair of rport interfaces must be created for each connection between a pair of rdomains. like, every single connection. no shortcuts 😭

alternatively — and this is the big-brain move — if you need peering between multiple rdomain(4) instances, you can use a single veb(4) interface with a vport(4) interface for each rdomain instead. so basically: two rdomains = rport pair, many rdomains = veb + vports. pick your fighter 🦋🔥

---

so yeah, that's rport. go forth and connect your rdomains, bestie 🌸🫶

this page came to you via the Debian source, dated August 31, 2024, and it's filed under RPORT(4) — mwah, love that for us 💜✨