Quote from: RamSense on February 24, 2024, 12:53:42 PMThe only action behind ... is 'Reset certificate'. There is no such an item like "Delete".
click on the ... at the end and hit yes for delete
Resetting does not remove it.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: RamSense on February 24, 2024, 12:53:42 PMThe only action behind ... is 'Reset certificate'. There is no such an item like "Delete".
click on the ... at the end and hit yes for delete
Quote from: axel2078 on September 02, 2021, 05:28:17 AMI have the same issue but I do not use Unbound DNS but instead I employed AdGuard to lookup for internal hosts by their dns names. I was unable to find anything like DNS in AdGuard so I am not sure how to let the WireGuard clients access the names. Any clue how to achieve that?
Update: I found the fix. I had to go in my Unbound DNS settings and add an ACL to allow the Wireguard network to access DNS. Now, I can point the client to my OPNsense system for DNS and it works.
Quote from: marcquark on May 11, 2023, 07:30:03 PMNot really. I installed the agent on other Linux VMs but have not tried with OPNsense yet.
Do you have the QEMU Guest Agent installed? It's available as a plugin. That should enable Proxmox to communicate with the guest, iirc it will also help display correct memory usage stats.
Quote from: netnut on May 11, 2023, 07:05:21 PMFrankly, this is my first two weeks of my OPNsense journey, same for Proxmox, so I am still on the learning curve ;)systat -vmstat
https://wiki.freebsd.org/Memory
https://papers.freebsd.org/2017/bsdtw/johnston-memory_management_in_freebsd_12.0/