Hi,
As the title states, I tried installing virtio drivers from versions virtio-win-0.1.137 to virtio-win-0.1.185, each time on fresh install. They all report the same thing, "windows cannot verify digital signature"...
Which leads me to believe that the virtio drivers were signed with a newer...
Hayia.... I never thought of adding this permission because I trust and follow the documentation. Once again I was wrong to do so.
Next time when I see someone adding links and insisting on docs I will get frustrated....
Thanks for the solution.
I use the correct permissions as specified here: https://pve.proxmox.com/pve-docs/api-viewer/#/nodes/{node}/storage/{storage}/content
Pretty sure I know what I'm doing...
Hi, why would I create another separate thread for the same issue? I won't even mention the fact that most of them are not replied to.
Nevertheless, to answer your question:
proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pve)
pve-manager: 7.3-4 (running version: 7.3-4/d69b70d4)
pve-kernel-5.15...
Because using a single VM with pfSense for many VM's is not ideal, it cannot handle that much PPS when under attack. If it was a separate dedicated server only for pfSense, sure.
Well, considering nobody gave a crap to even try and reply... I will leave my answer here.
Looking at https://github.com/proxmox/pve-firewall/blob/master/src/pvefw-logger.c and following the log format will indeed put your custom logs into the VM firewall log.
Hello,
I'm trying to leverage Notes to fit my needs, however I'm unable to save a small JSON snippet; I get the following message via UI:
The maximum length for this field is 8192
Is there a workaround?
Many thanks
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.