tbtadm(1)

πŸ“¦
version 0.9.3 Β· 5 versions
, in nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ tbtadm β€” Thunderbolt(tm) management tool ✨

okay bestie, so this is tbtadm(1), a whole General Commands Manual page, and it's literally your little bestie for talking to the Thunderbolt(tm) kernel module πŸ’–


🌈 SYNOPSIS 🌈

tbtadm

tbtadm devices

tbtadm peers

tbtadm topology

tbtadm approve [--once] <route-string>

tbtadm approve-all [--once]

tbtadm acl

tbtadm add <route-string>

tbtadm remove <uuid | route-string>

tbtadm remove-all

πŸ’… DESCRIPTION πŸ’…

tbtadm is the convenient way to interact with the Thunderbolt kernel module β€” approving the connection of Thunderbolt devices, handling the ACL for auto-connecting devices, and more πŸ¦‹

And the cutest part? If you run it with no argument at all, it just prints out all the available commands for you. main character energy, honestly πŸ‘‘


πŸŽ€ OPTIONS πŸŽ€

  • devices β€” prints a list of all the currently connected Thunderbolt devices, in exactly this format:
Route-string    Vendor    Device name    Authorized?    In ACL?
  • peers β€” prints a list of all the currently connected hosts, in exactly this format:
Route-string    Vendor    Device name
  • topology β€” prints all the currently connected Thunderbolt devices as a tree, starting with the controller itself, so it resembles the actual device connection topology 🌸 (it's giving family tree but make it hardware)
  • approve [--once] <route-string> β€” if the Thunderbolt device you picked isn't authorized, this approves it, and (if --once wasn't specified) adds it to the ACL πŸ’–
  • approve-all [--once] β€” approves all currently connected Thunderbolt devices that aren't authorized yet, and (if --once wasn't specified) adds them to the ACL. the group-chat mass-approval, if you will ✨
  • acl β€” prints the ACL content, in exactly this format:
UUID    Vendor    Device name    Currently connected?
  • add <route-string> β€” adds a device to the ACL. The argument picks the device to be added by its route-string 🫢
ngl bestie, this one doesn't work in SL2 (secure; key-based), because adding to the ACL must be done together with the device authorization β€” that means with approve or approve-all without the --once flag. no cap 😭
  • remove <uuid | route-string> β€” removes an ACL entry. The argument picks the device to be removed by its UUID, or (if it's currently connected) by its route-string πŸ’…
  • remove-all β€” clears the ACL, removing all the entries. it's giving spring cleaning 🧹✨

πŸ¦‹ SEE ALSO πŸ¦‹

no SEE ALSO refs on this page, bestie β€” it's a short and sweet one πŸ’œ


and that's the whole page, periodt πŸ‘‘

cute sign-off time πŸŽ€ β€” this little masterpiece was written by Yehezkel Bernat, and the footer was serving 2mtime(2m/2d/2Y) with tbtadm(1) at the bottom. obsessed πŸ’–