YaneonY

Members
  • Posts

    3
  • Joined

  • Last visited

YaneonY's Achievements

Noob

Noob (1/14)

2

Reputation

  1. So, I've found solution: Download package from here on your host (unraid): https://slackware.pkgs.org/15.0/slackware-patches-x86_64/bluez-5.64-x86_64-1_slack15.0.txz.html Then install taht package: upgradepkg --install-new bluez-5.64-x86_64-1_slack15.0.txz Restart service: /etc/rc.d/rc.bluetooth restart Passthru 2 paths to your HomeAssistant container (get your ID of usb device with lsusb) /dev/bus/usb/003/002 /run/dbus Restart your HomeAssistant container... and VOILA, Bluetooth found and working! Have fun!
  2. Okay, for everyone facing same problem: Go to Settings -> Docker and change "Host access to custom networks" to "Enabled".
  3. I've faced the same problem as some people here: I am unable to access any Docker container running on br0 with a static address set. I've tested different commands, such as: tailscale up --advertise-routes=192.168.1.0/24 --accept-routes --accept-dns --advertise-exit-node tailscale up --advertise-routes=192.168.1.0/24 --accept-routes=false --accept-dns=false --advertise-exit-node Basically, I don't want my home server to be an exit node, so I would remove it later. However, regardless of whether it's included or not, I can't access anything from Unraid Docker. I can access Unraid itself and other IPs running on my network, like Unifi, Printer GUI, etc. Is it possible that some routes need to be added to the routing tables?