dibbler-relay(8)

✨ dibbler-relay(8) ✨

okay bestie, buckle up, we're reading the dibbler-relay manual page together 💖 it's giving portable DHCPv6 relay and honestly? iconic.

---

🎀 NAME 🎀

dibbler-relay — a portable DHCPv6 relay, no cap 💅

---

🌸 DESCRIPTION 🌸

dibbler-relay is a portable implementation of the DHCPv6 relay. so what even is a DHCPv6 relay, you ask? it's a proxy, babes 🫶 — it lets one single server support links that the server isn't directly connected to. main character energy, honestly.

there are ports available for Linux 2.4/2.6 systems as well as MS Windows XP and 2003 ✨ and they're freely available under the GNU GPL version 2 (or later) license. slay.

---

🦋 SYNOPSIS 🦋

dibbler-relay [ run | start | stop | status ]

---

💅 OPTIONS 💅

• run — starts the relay in the console. you can close the relay using ctrl-c 🛑
• start — starts the relay in daemon mode 🌙
• stop — stops the running relay 🙈
• status — shows the status of the relay 👑

---

🌈 EXAMPLES 🌈

the relay forwards DHCPv6 messages between interfaces, periodt. messages from a client are encapsulated and forwarded as RELAY_FORW messages. replies from the server come back as RELAY_REPL messages. after decapsulation, they get sent back to the clients 💌

it is vital to inform the server where this relayed message was received. DHCPv6 does this using the interface-id option. this identifier must be unique — otherwise relays will get confused when they receive a reply from the server 😭 no cap. and note that this id does not need to be aligned with the system interface id (ifindex). think about it as an "ethernet segment identifier" if you're on an Ethernet network, or as a "bss identifier" if you're on an 802.11 network 🧚

okay so let's assume this case: the relay has 2 interfaces: eth0 and eth1. clients are located on the eth1 network. the relay should receive data on that interface using the well-known ALL_DHCP_RELAYS_AND_SERVER multicast address (ff02::1:2). the relay also listens on its global address 2000::123. packets received on eth1 should be forwarded on the eth0 interface, also using the multicast address:

log-level 8
log-mode short

iface eth0 {
  server multicast yes
}

iface eth1 {
  client multicast yes
  client unicast 2000::123
  interface-id 1000
}

here's another example 🌸 this time messages should be forwarded from eth1 and eth3 to the eth0 interface (using multicast) and to the eth2 interface (using the server's global address 2000::546). also clients must use multicasts — that's the default approach, bestie:

iface eth0 {
  server multicast yes
}

iface eth2 {
  server unicast 2000::456
}

iface eth1 {
  client multicast yes
  interface-id 1000
}

iface eth3 {
  client multicast yes
  interface-id 1001
}

---

🍓 FILES 🍓

all files are created in the /var/lib/dibbler directory ✨ during operation, Dibbler saves various files in that directory. the Dibbler relay reads the /etc/dibbler/relay.conf file. the log file is named client.log 📝

---

⭐ STANDARDS ⭐

this implementation aims at conformance to the following standards:

• RFC 3315 — DHCP for IPv6
• RFC 3736 — Stateless DHCPv6

---

💀 BUGS 💀

bugs are tracked with bugzilla, available at http://klub.com.pl/bugzilla/ 🌈 if you believe you have found a bug, don't hesitate to report it — do it for the girls 🫶

---

👑 AUTHOR 👑

Dibbler was developed as a master thesis on the Technical University of Gdansk by Tomasz Mrugalski and Marek Senderski. currently Marek doesn't have enough free time, so this project is being developed by Tomasz Mrugalski. the author can be reached at thomson@klub.com.pl 💌

---

🌟 SEE ALSO 🌟

there are dibbler-server(8) and dibbler-client(8) manual pages available 👀 you're also advised to take a look at the project website located at http://klub.com.pl/dhcpv6/ ✨

as far as the authors know, this is the only Windows DHCPv6 stateful implementation available and the only one with relay support 🏆 it's also one of two freely available under Linux. the other Linux implementation is available at http://dhcpv6.sourceforge.net, but it's rather outdated and seems not to be actively developed 💀 rip.

---

💖 and that's the whole vibe, bestie — go forth and relay some DHCPv6. iykyk.

this has been the Dibbler relay page, dated 2004-12-11 — GNU, dibbler-relay(8) 💅✨