ramond.conf(5)

πŸ“¦ version 0.5, in debian bookworm, ubuntu jammy, ubuntu noble

🌸 ramond.conf β€” the config file glow-up πŸ’–

okay bestie, welcome to ramond.conf(5), aka the File Formats Manual girlie of section 5. this is the page that explains the config file for ramond(8), and honestly? it's giving structured. it's giving XML. let's get into it πŸŽ€


✨ NAME ✨

ramond.conf β€” the configuration file for ramond(8) 🫢


πŸ’« DESCRIPTION πŸ’«

so this page is the lil brief on the ramond.conf config file. no cap.

ramond.conf is an XML file holding the rules for Router Advertisement processing by ramond(8). 🌈

and here's the thing you gotta internalize: the rules are processed in the order they are defined in the file. order matters, periodt. πŸ’…


πŸ¦‹ SYNTAX πŸ¦‹

you can refer to the DTD given in /usr/share/doc/ramond/examples/ramond.conf.dtd. it's right there, bestie, go look πŸ‘€

the root element, <ramond>, contains one optional attribute, logfile, which gives the path to the logfile for the daemon. πŸ“

this element may contain one or more <mac-list>s, and **one or more <rule>s`.

the <mac-list> must have a name attribute, and contains one or more <entry> elements. (yes, must. the attribute is not optional, don't try it πŸ™ˆ)

the <rule> may contain a few attributes:

  • prefix β€” an IPv6 prefix used for matching RA packets 🌸
  • mac β€” a <mac-list> name used for matching source MAC addresses of the RA packets πŸ’œ
  • lifetime β€” this attribute, when having a "0" value, is used for matching routes that are being cleared 🧹
  • interface β€” the interface which the RA packet came from πŸ”₯

and the <rule> may contain:

  • one or more <execute> elements containing the path of the scripts to run when a packet is matched πŸƒ
  • a <clear/> element, so that the matched route will be cleared by ramond(8)
  • or no element at all, indicating an β€œignore” rule. πŸ’€

🌿 ENVIRONMENT 🌿

the environment variables the configured scripts are run with are listed in the ramond(8) manpage. go check her, she's got the deets πŸ’–


πŸ‘‘ EXAMPLE CONFIGURATION FILE πŸ‘‘

okay this is the part where we actually do it. main character energy only ✨

set the logfile to be /var/log/ramond.log.

<ramond logfile="/var/log/ramond.log">

define a router mac-list.

<mac-list name="router">
  <entry>00:11:22:33:44:55</entry>
  <entry>00:22:44:66:88:00</entry>
</mac-list>

define a rule checking if the router routes are being cleared.

<rule mac="router" lifetime="0">
  <execute>/usr/local/sbin/routenotify route-cleared</execute>
</rule>

define a rule ignoring our router announcing routes for prefix 2001:dead:cafe:babe::/52.

<rule mac="router" prefix="2001:dead:cafe:babe::/52">
  <!-- do nothing -->
</rule>

clear the 6to4 routes coming on interface eth0.

<rule prefix="2002::/16" interface="eth0">
  <execute>/usr/local/sbin/routenotify 6to4-advertised</execute>
  <clear/>
</rule>

match on all advertised prefixes

<rule prefix="::/0">
  <execute>/usr/local/sbin/routenotify route-advertised</execute>
</rule>

match on all RA packets (even those not advertising a prefix)

<rule>
  <execute>/usr/local/sbin/routenotify route-advertised</execute>
</rule>
</ramond>

slay. that's a whole config file and you understood it πŸ’…


🌈 SEE ALSO 🌈

  • ramond(8)
  • /usr/share/doc/ramond/examples β€” for a sample ramond.conf and a sample processing script πŸ“‚

πŸ’– AUTHORS πŸ’–

  • James Morse <morse_@users.sourceforge.net> β€” wrote the ramond software πŸ‘‘
  • Nicolas Dandrimont <nicolas.dandrimont@crans.org> β€” wrote this manpage for the Debian system 🫢

Copyright Β© 2010 Nicolas Dandrimont

this manual page was written for the Debian system (and may be used by others). πŸ’œ

permission is granted to copy, distribute and/or modify this document under the terms of the usual 3-clause BSD license.

on Debian systems, the complete text of the 3-clause BSD license License can be found in /usr/share/doc/ramond/copyright. πŸ“„


okay that's the whole page bestie, no skips, no skims, every last detail intact. iykyk πŸ’…βœ¨

and that's a wrap on ramond.conf(5) from the File Formats Manual, section 5 πŸ¦‹ thanks for reading, ily, go configure something πŸŒΈπŸ’–πŸŽ€

πŸ“¦ where this page comes from