BoarAnt
Members
-
Joined
-
Last visited
-
Memtest reboots my server the second I select it in grub, but I'm assuming it's because I'm running a new EPYC 7002 build. I am able to run windows memory diagnostic and passmark's memtest86 fine, so I've used those instead to test my memory.
-
Hi, I'm have a Chelsio T6225-OCP nic that is currently experiencing errors when I try to bring it up: Nov 14 02:37:13 kernel: cxgb4 0000:81:00.4: Can't allocate queues, err=6 Nov 14 02:37:46 kernel: cxgb4 0000:81:00.4: Can't allocate queues, err=6 Nov 14 02:38:02 kernel: cxgb4 0000:81:00.4: Can't allocate queues, err=6 Nov 14 02:39:58 kernel: cxgb4 0000:81:00.4: Can't allocate queues, err=6 Nov 14 02:40:10 kernel: cxgb4 0000:81:00.4: Can't allocate queues, err=6 The boot log mentions that the drivers are failing to load: cxgb4 0000:81:00.4: Direct firmware load for cxgb4/t6fw.bin failed with error -2 cxgb4 0000:81:00.4: unable to load firmware image cxgb4/t6fw.bin, error -2 And upon further digging, there are no T5 & T6 drivers present in /lib/firmware/cxgb4 (/lib/firmware/cxgb3 drivers are present though). Hopefully it can be added soon (RC6 maybe?) Thanks.
-
Awesome. I just tried it with the original version and it imports fine. Thanks for the quick turnaround!
-
Following Mantene's suggestion, I also got it to work tonight by removing the comment at the top and removing any empty lines between the [Interface] and [Peer] entries. Importing the original config untouched ---------------------------------------------------------------------------------- # TorGuard WireGuard Config [Interface] PrivateKey = yyyyyyyyyyyyyyyyyyyyyy ListenPort = 51820 DNS = 1.1.1.1 Address = 10.29.1.55/24 [Peer] PublicKey = xxxxxxxxxxxxxxxxxxxxx AllowedIPs = 0.0.0.0/0 Endpoint = 111.111.111.111:443 PersistentKeepalive = 25 ---------------------------------------------------------------------------------- would give me 4 sections total: whereas the more compact version ---------------------------------------------------------------------------------- [Interface] PrivateKey = yyyyyyyyyyyyyyyyyyyyyy ListenPort = 51820 DNS = 1.1.1.1 Address = 10.29.1.55/24 [Peer] PublicKey = xxxxxxxxxxxxxxxxxxxxx AllowedIPs = 0.0.0.0/0 Endpoint = 111.111.111.111:443 PersistentKeepalive = 25 ---------------------------------------------------------------------------------- would give me 2 sections: The 2nd version was connecting fine, so I think it's just the import config parser that's messing up the setup. Thanks.
-
To answer your question, no, those fields are not populated during the config file import.
-
I disabled UPnP globally under Settings > Management Access, switched back to VPN Manager, got the popup message saying "UPnP stated changed to OFF", verified that the Tunnel's "Local gateway uses UPnP" setting is No, and tried to activate the tunnel... It's still alternating between active/inactive quickly. Any other ideas?
-
TorGuard VPN also supports WireGuard: https://torguard.net/blog/what-is-wireguard-vpn/ Now if I could only figure out how to configure unraid to work with it, then I'd be golden. The steps above doesn't seem to work with TorGuard's import config by default unfortunately.
