• Posts

  • Joined

  • Last visited

  • Days Won


Skitals last won the day on January 21 2020

Skitals had the most liked content!


Recent Profile Visitors

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

Skitals's Achievements


Apprentice (3/14)



  1. How to reproduce: Have docker container using a wireguard network interface, in my case wg1. Stop all docker containers using wg1. Delete wg1 from VPN settings. Create/import new wg1. Attempt to restart docker container. It gives an error that the container doesn't exist. You can fix this broken state by editing the container template (any superficial change such as name) and hitting save. My VPN provider requires generating a new wireguard config every few weeks. IMO, recreating wg1 should not break containers. How to fix them is not obvious, and I had gone through the pain of deleting and recreating all my containers from scratch before figuring it out. I would hate to see others get frustrated by this.
  2. Thanks, I tested the latest update.wireguard.php from github and it is importing my file properly, including the PersistentKeepalive value.
  3. Okay, so analyzing the above I see the error is how it imports "PersistentKeepalive = 25" from my wg config file. It gets cleaned up when you make a change and hit Apply. If I import and remove the "=25" line it works without having to apply any changes.
  4. I see multiple changes are made to both /boot/config/wireguard/wg2.cfg and /boot/config/wireguard/wg2.conf after setting a name, hitting apply, removing the name, hitting apply. Here is wg2.cfg after importing: Endpoint:0="" PROT:0="" Network:0="" PublicKey:0="" UPNP:0="no" NAT:0="no" Address:1="" TYPE:1="8" Here is wg2.cfg after making/reverting a change and clicking Apply: PublicKey:0="" PROT:0="" Network:0="" Endpoint:0="" UPNP:0="no" DROP:0="" RULE:0="" TYPE:1="8" Address:1="" Here is wg2.conf after importing: [Interface] PrivateKey= Address= PostUp=ip -4 route flush table 202 PostUp=ip -4 route add default via table 202 PostUp=ip -4 route add via table 202 PostDown=ip -4 route flush table 202 PostDown=ip -4 route add unreachable default table 202 PostDown=ip -4 route add via table 202 [Peer] AllowedIPs= Endpoint= =25 PublicKey= Here is wg2.conf after making/reverting a change and clicking Apply: [Interface] PrivateKey= Address= PostUp=logger -t wireguard 'Tunnel WireGuard-wg2 started' PostDown=logger -t wireguard 'Tunnel WireGuard-wg2 stopped' PostUp=ip -4 route flush table 202 PostUp=ip -4 route add default via table 202 PostUp=ip -4 route add via table 202 PostDown=ip -4 route flush table 202 PostDown=ip -4 route add unreachable default table 202 PostDown=ip -4 route add via table 202 [Peer] PublicKey= Endpoint= AllowedIPs=
  5. [Interface] Address = PrivateKey = DNS =, [Peer] PublicKey = Endpoint = AllowedIPs = PersistentKeepalive = 25 I was able to reproduce this bug multiple times, tunnel would not work until making any change and hitting apply.
  6. Getting PIA working is as simple as using this utility to generate a config file. It took me a few attempts trying different endpoints before finding one that worked (or perhaps there is some failure rate), but it is possible to create a standard wg config file with PIA.
  7. Using the "import tunnel" feature, I was following the instructions for Configuring “VPN tunneled access for docker” which states "There are no settings to change, except perhaps to give it a local name. Click Apply." However, the Apply button is greyed out unless you make a change. If you import a config and make no changes the tunnel WILL NOT WORK. If you click the activate slider, it immediately deactivates. If you give it a local name and click apply, activate now works. In fact, you can import a config, create a name, apply, remove the name, apply, it will also work. So the local name is indeed optional, but you must make some change any change for the tunnel to work when importing a config file.
  8. Nasty patches? It's a few prebuilt binaries and prebuilt ovmf file. If someone can't edit their own xml file I wouldn't suggest they use a test verion of unraid.
  9. You need to add the tpm to your xml and start the vm for the first time for the files to be created. If you get "Could not run '/usr/bin/swtpm_setup'" error starting the vm, for fix is in this post above (chmod to fix permissions):
  10. The swtpm module is not installed. You need to download the .txz files, put them in /boot/extra, and reboot. The tzx files in /boot/extra get installed at boot time so the binaries aren't installed until reboot.
  11. TYVM. Retail ISO is out, just updated my win10 vm to win11 final no problem after getting TPM emulation working per the guide. I'm on Unraid 6.9.1.
  12. I was avoiding upgrading because I run a custom kernel and I didn't want to be bothered getting everything working again until there was a worthy stable update. I just made the plunge to 6.9.1, took most of the day to get everything working again. This is running a 5700 XT as my gaming gpu which also has the reset bug. The navi reset kernel patch worked great for me. Just upgraded to 6.9.1 and trying out gnif/vendor-reset via ich777's kernel helper container. So far so good and much easier than building the kernel "by hand"!
  13. Any other members? I haven't been active much because I haven't had to tinker. It just... works. Used as my file server, Plex server, and primary Win10 Gaming VM.
  14. As an aside, 6.8.0 rc5 with this kernel has been rock solid. I'm at 84 days uptime as I type, I use this machine as my daily driver (win10 gaming vm w/ 5700xt) with 10+ docker containers running (plex server and more). I'm still holding off updating until there is a 6.9 release candidate.