fserb

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

fserb's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. That doesn't seem to work. The go file gets executed way after the bluetooth module gets loaded. What I end up doing is: on go file I copy the patch and rmmod/modprobe all BT modules. That seems to work fine.
  2. I know that since 6.9.1 there's a overlayfs on /lib/firmware and /lib/modules to "make it possible to install 3rd party modules at boot time" I need to add some bluetooth driver file to /lib/firmware to be installed during boot. The overlayfs allows me to write on /lib/firmware (that ends up on /var/local/overlay/lib/firmware) but the files I add there disappear after a reboot (obviously). I don't understand how I'm supposed to use it to install 3rd party modules (or in my case a patch) at boot time. I understand how I could is this for modprobe, is this the only use case supported? Do I need to regenerate bzfirmware? If so, is there a tutorial for that? My actual problem: [ 16.149827] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [ 16.150209] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-21e8.hcd' I have the hcd file, but not sure how to have it available at that point. Thanks for the help.
  3. Just had this exact problem twice (happening now again). I lose internet and access to all local network until I unplug my unraid.
  4. Go on the container Edit page, on the top right, press on "basic view" (to switch to advanced). Find the "Extra Parameters" field. Either add or edit the `--hostname` to use the hostname you want.
  5. I figured out the problem (after pinging Tailscale folks)! The Tailscale unstable is broken for docker bridge mode. v0.98 is working fine. It took us a while to figure, because there's another problem on this Dockerfile. `RUN git checkout -b v0.98` doesn't do what you think it does, either do `RUN git checkout v0.98` (for detached head mode) or `RUN git checkout -b v0.98 v0.98` . The way it is you are just creating a new branch called v0.98 on top of master.
  6. I'm pretty sure there's an issue with Tailscale's iptables rules and Unraid's docker iptables. I've also tried using tailscale tip of tree, but no success there either. Someone who understands Unraid iptables better would have an easier time with this. dsmith, I have a suggestion for your docker-entrypoint.sh. Replace the bottom lines with: (sleep 10; tailscape up) & exec tailscaled --state=/state/tailscaled.state it's much nicer than your current while loop.
  7. Just setting the docker to bridge didn't work for me. I can ping the host, but not even access other services on the unraid (even the ones that did work with "host", like ssh). I'm guess yours works as a side-effect of the ip forwarding you set up?
  8. Hey. I can also confirm that 0.98.1 works. (as in, it connects and is part of the mesh, etc). But I'm still having some unraid specific issues... Right now, with this docker running, I'm able to, for example, ssh to unraid using the Tailscale IP. I'm also able to access ports that are being served from other docker containers that have network set to "host". My problem right now is: all the other dockers that I have that are using "bridge" network, those ports are not currently available over the tailscale IP. I'm not sure if this is Working As Intended (i.e., I need to move all my containers out of "bridge" and into "host"), if I messed up some "docker bridge" configuration (to not bind to a particular IP?), or if I need to do anything extra on the Tailscale docker. Help?
  9. I tried what you said: fetch my repro locally, "docker build -t xxxx ." from the Unraid, and started a new container with "xxxx". The "apply update" is still there and clicking doesn't update anything and doesn't remove it.
  10. So, I have a docker container that I created by doing "docker save" on my local machine and "docker load" on Unraid. From there, I create a normal instance using WebGUI. It works great, but the container is marked as "apply update". When I do that, nothing gets updated, but the request to update doesn't disappear. Is there any suggestions on how to deal with this? Also, if I want to have private dockers, what's the proper way to do so (apart form paying dockerhub, I guess)?