This is the first post in a planned multi-post series on deploying a TACACS+ server using open-source components. I hope to create a complete guide for such a solution, while also delving reasonably deep into TACACS+ itself, LDAP set-up and various vendor-specific configuration needed for this to work. In this post, I will describe my solution and what I was aiming to achieve. I will also give a brief overview of TACACS+ protocol that will hopefully make future posts easier to follow. I deployed this on Rocky Linux 9 (a bug-for-bug clone of Red Hat 9), because that’s what I had to work with, but any modern Linux distro should…
-
-
Raspberry Pi/Debian A2DP Sink or How to Make Your Own Bluetooth Speaker
Requirements: An up-to-date Debian or Raspberry Pi Buster installation. Equivalent Ubuntu Server version should also work, but hasn’t been tested. Might work with other distributions, mutatis mutandis. Bluetooth dongle/card that supports A2DP (anything even remotely modern will do) Rationale: Streaming audio over LAN is a mess, an even bigger mess if WiFi is involved. Sure, many apps do that for their own output, Pulseaudio allows streaming audio over RTP, but there is no universal, application-independent solution that works on all platforms. Audio over Bluetooth, using the Advanced Audio Distribution Profile, is, however, universally supported and requires next to zero configuration on the client beyond pairing. Configuring a host to receive…