Search results

That's brute forced in less then 10 minutes. Bad idea. You can check gui logins with: zcat /var/log/syslog*gz | grep "successful auth" But they probably purged logs, so it doesn't help much.

How strong was your password ? Was portainer exposed as well ? Wipe it completely, be careful with backups they are likely compromised as well. CPU usage comes from kvm which is your running pfsense. The theme doesn't even change much, where did you get it from ?

ZFS falsch konfiguriert, cache und slog auf gleicher platte ist performance killer. Der slog macht bei raidz1 auf ssd wenig sinn und cache braucht nicht redundant sein. Teste mal die pool performance, hat nichts mit dem netzwerk zu tun. Würde slog und cache raus nehmen und erneut testen. apt...

Looks good to me. Sadly I have no documentation for the ha part of opnsense and it's been over a year since. I would make sure the multicast traffic works. Install tcpdump on both pve nodes and run "tcpdump -i <interface> -s0 -vv net 224.0.0.0/4" Make sure multicast traffic from firewall1...

You can override mac in interface settings, maybe that helps. Since both firewalls are master there must be a issue with the carp multicast traffic. Can you login to the opnsense shell (setup serial console or ssh) And post the output of "ifconfig vtnet0" (remove public ipv6 if needed)

Depends on the storage, only possible with zfs. But you can always full disk encrypt your whole proxmox.

Yeah the second firewall should show "BACKUP" on the dashboard. Can you double check with the official documentation https://docs.opnsense.org/manual/how-tos/carp.html Did you create firewall rules to allow carp on all interfaces ? You can use floating to make it simpler. Maybe post...

For l2arc it doesn't really make sense, there is no data loss. For slog always use a mirror.

There is none, but it is really easy to setup, takes 1 minute. Create container, change container options -> features -> enable keyctl and nesting. Start the container, run "pct enter <id>" or select container shell and login. Run the docker bootstrap script to install it automatically: apt...

Use vlans, you need a managed switch e.g. netgear gs308e or tplink sg108e

You can't create containers from iso files. In your pve gui select storage "local" -> ct templates -> templates -> search for ubuntu -> download VM's and container have different pros and cons. For speed container win in every aspect since they have raw host performance.

Das ist nicht möglich, bis auf regelmäßige cache drops, sollte man aber möglichst vermeiden. Einfach der VM nicht mehr Arbeitsspeicher geben als sie benötigt.

Replacing / recursively on a live system calls for trouble. Just restore the files that you changed if possible. Otherwise live boot debian/ubuntu, install pbs-client, mount pve and restore that way.

Dafür sql via grafana, kannst dir Tabellen generieren und als csv exportieren.

Config is correct, supposed your switch supports lacp. Just to be sure, you have a gateway with dhcp in the other vlans ? Post vm config, switch config and nic details. Some nic have trouble with vlan over bond, you can try without the bond to verify.

Dir ist aber schon bewust, dass du die range oben rechts einstellen kannst ? Stunde/Tag/Woche/Monat/Jahr Ansonsten grafana benutzen, damit kannst du dann per sql genaue reports erstellen. https://pve.proxmox.com/wiki/External_Metric_Server Ich hoffe du weißt was du machst...

For RA set container network to "SLAAC" Otherwise setup a DHCPv6 server.

Afaik sata doesn't support trim. You have to use virtio for trim to work. Download virtio drivers here: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso Install the vioscsi driver, after that power down the vm and change the config from "sata0" to...

In case you use autosnapshot or other tools to do periodic zfs snapshots and thus can't use the roolback feature of pve. This patch enforces the rollback, execute as root in terminal: cat << 'EOF' > /etc/cron.hourly/proxmox-zfs-rollback-force #!/bin/bash...

The features are the same, but community is bleeding edge. Enterprise is stable and lacks multiple weeks behind.