RXECHO.CONF(5)

πŸ’– RXECHO.CONF πŸ’–

okay bestie, gather round, because this is the manual page for rxecho.conf β€” that's the config file living in the Linux Programmer's Manual, section 5 (file formats, iykyk). it's little, it's powerful, and it's literally the vibe check for your AX.25 packet routing. let's get into it πŸ¦‹


✨ NAME ✨

rxecho.conf β€” control rxecho AX.25 packet routing.

like. the whole personality of this file is "which packets get copied where." that's it. that's the job. πŸ‘‘


🌸 DESCRIPTION 🌸

So rxecho.conf is the file that tells the program rxecho how to copy packets between AX.25 ports. that's the entire assignment. no cap.

The format of the configuration file is:

portin    portout        * | callsign...

fr fr, that's the whole shape of it. let's break it down because the way this works is lowkey elegant:

  • Every entry in the file represents a one-way packet flow between ports. one direction, bestie. if you want it both ways you write two entries, periodt.
  • Any packet received on portin gets copied to portout β€” but only if its destination callsign, or the next callsign to digipeat the frame, is in the list of callsigns. so like, it's picky. it's got standards. πŸ’…
  • If the callsign list is replaced by a β€œ*” then all packets are copied. every single one. no filtering, full send, main character energy. 🌈
oh and also β€” the configuration file may contain comments that begin with a #. so go ahead and annotate your entries, you deserve it πŸŽ€

πŸ—‚οΈ FILES πŸ—‚οΈ

  • /etc/ax25/rxecho.conf

that's the one. that's where it lives. go visit it. 🫢


πŸ‘€ SEE ALSO πŸ‘€

read those too, bestie, they're the supporting cast and they ate πŸ’…


and that's the whole page!! this one came from the Linux manual, dated 2 August 1996 β€” yes, 1996, an absolute icon, a vintage queen πŸ‘‘. she's been slaying since before some of us were born and honestly? obsessed. mwah, go configure something πŸ’–βœ¨