Jump to content

Xaero

Members
  • Content Count

    216
  • Joined

  • Last visited

  • Days Won

    2

Xaero last won the day on July 19

Xaero had the most liked content!

Community Reputation

62 Good

About Xaero

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. See my (old, outdated, don't use it anymore plex has been updated) Plex wrapper script here: https://github.com/Xaero252/unraid-plex-nvdec This script can be added to CA User Scripts to run after your automatic docker updates to reinstall the modifications after the docker has updated. Similarly, you could do this with the pihole docker. I would also suggest pinging the pihole docker maintainer and see if they might be willing to add a layer for your modification. Since its a direct extension of pihole rather than a hack like my plex script, it is more reasonable to include it in the actual docker image as an optional flag.
  2. I only do the overlay as I like persistent settings and bash history. 4GB is massive overkill for that. I also know adding just a couple of lines to the "go" file works but then I have to add lines every time I customize something new. Overlay "just works" I do wholely agree though - for a handful of scripts being added to the 'go' file calling them with their interpreter is sufficient.
  3. You would want to use the remote tunnel option so that 0.0.0.0/24 is the AllowedIPs for the tunnel. This should capture all traffic from the remote device and send it through the DNS (your local router) You would want the DNS set to PiHole to get PiHole to filter it.
  4. Even so; Make sure the unraid IP is in AllowedIPs on the client conf file under the [peer] section. If it's not it won't be routed through the tunnel.
  5. Unraid itself is a collection of Linux programs and utilities. It's probably possible to get it running under the Linux subsystem for windows - but would be completely unsupported, and probably more trouble than just setting it up in a VM - which itself is a fair amount of work.
  6. it would also help if I didn't make as many typos as I do when writing things haha
  7. Apparently it doesn't like me that much; instead: In the particular usage case for this thread: Remove the scripts folder from /boot/config Remove the copy from /boot/config/go Create the overlay Add the overlay to /boot/config/go Copy the scripts to the root directory and set permissions Call the scripts from /boot/config/go or however you normally do.
  8. Needs to go on the client side peer config Add to the list with AllowedIPs=1.2.3.4/32, 5.6.7.8/32 Once set in the client config you do have to stop/start the wireguard server. Make sure the config on the client is updated as well (changing it on the server doesn't change it on the device(s) that have that peer config loaded, so you'd have to reload it onto those devices. Once it's loaded onto the devices, the server has been restarted and you connect, try pinging the IP you are trying to access. It should at least ping if it's routable.
  9. You can circumvent that with the SETUID bit. I've been using an overlayfs for my /root/ folder so that any changes I make are automatically on the flash drive, and support full *nix permissions. The go file is only used to mount that overlay and kick off any scripts if needed. I can share the steps here to recreate the overlayfs. It also enables things like preference persistence for htop, tmux, etc.
  10. In the [Peer] section for the PEER configuration file that you want to have access to 10.0.2.3 make sure that 10.0.2.3/32 is in the list of AllowedIPs. If it's not, the tunnel won't send traffic to it.
  11. The DNS server on my local lan, in this case my ISP provided cable modem gateway. Though eventually that will be replaced with OPNSense, now that I've tested everything works that way. Also, do note that you need to edit the peer configuration files manually in /etc/wireguard/peers Afterwards you can regenerate the QR code using my instructions above, so that you can provide users with a QR code or the ZIP.
  12. FYI, I was able to get this working properly manually with only the following data for all profile types: DNS=<Local-IP> in the [Interface] section of the peer config. <Local-IP>/32 included in the AllowedIPs= of the [Peer] section of the peer config. A single DNS field and some rudimentary logic should sort whether or not the DNS is already included in the range. From there I manually regenerated the QR codes and moved on. Of course I can't touch those peers in the GUI now without ruining everything, but it works as is.
  13. Not my feature request; but this covers the same issue.
  14. Would it be possible to add this as an option in the GUI? I'll do it manually for now; but that doesn't help much for QR code users. A slider in the advanced for "Force DNS" with an input field for the DNS IP would be sufficient, I think. EDIT: For people who do set the DNS manually in the client configs and want the QR code updated as well: cd /etc/wireguard/peers qrencode -o peer-<hostname>-wg#-*.png < peer-<hostname>-wg#-*.conf (where # is the wg profile and * is the peer number) This will update the png manually.