Search results

Update: the proxmox-firewall service fails if there are aliases not referenced by the new "dc/" or "guest/" notation. After replacing all of them and restarting the firewall, nftables rules are created.

Enabled, all rules in iptables are removed, but no new rules added to nftables -> ending up without any firewall -> revert.

I know, but that's nothing official and may be discontinued at any time.

+1. Please make it possible. ARM <3

Upgraded and now the server sends backup e-mails, even if the backup is perfectly successful (we use on error only). Why?

I've reinstalled the node to which push didn't work. SSH was working good to the nodename, but not to the IP (still had the old host key). After removing the host key for the IP from known_hosts, SDN seems to be working again.

Same here.

Looks like firewall is broken in v8, might be related to https://forum.proxmox.com/threads/pve-8-pve-firewall-status-no-such-alias.130202/ https://forum.proxmox.com/threads/ipset-not-working-for-accepting-cluster-traffic.129599/

are you seeing value does not look like a valid IP address or CIDR network no such alias 'xxx' if you run pve-firewall status? I've inserted a "die $cidr" on /usr/share/perl5/PVE/Firewall.pm:3008 and executed a "pve-firewall status" again, and it throws aliases to me. So somehow the alias...

Since the last update, acme does not work anymore: Loading ACME account details Placing ACME order Order URL: https://acme-v02.api.letsencrypt.org/acme/order/yyyy Getting authorization details from 'https://acme-v02.api.letsencrypt.org/acme/authz-v3/yyy' The validation for xxxxx is pending...

Thanks for fixing! Btw, are there any plans to support trunks in the webgui? (e.g. under advanced, a simple text field where we can enter all vlan id's)

sure (zrh2)root@vms1:~# pveversion -v proxmox-ve: 6.1-2 (running kernel: 5.3.18-3-pve) pve-manager: 6.1-11 (running version: 6.1-11/f2f18736) pve-kernel-helper: 6.1-9 pve-kernel-5.3: 6.1-6 pve-kernel-5.3.18-3-pve: 5.3.18-3 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.3-pve1 criu: 3.11-3...

Since the last update, trunks= is ignored, instead, all 4096 vlans are added.

ACPI is not installed :S

Yes, but it won't go over 500 Mhz after it was throttled down. Any Ideas how I could find out the reason & how to turn it back?

Update: It seems not to be disk related. After some time, the system changes its CPU frequency to around 400 MHz. I have no idea why.

Hey @aaron Thanks for your feedback, I updated the initial post with the results. Best regards Patrick

Hi there On my SSD servers, the SSD performance is really bad. I test the performance with dd if=/dev/zero of=test.img bs=4k count=262133 conv=fdatasync (I'm aware that dd is not the best tool to test performance) System 1 (SSD + ZFS & RAID1) SuperMicro E300-8D 32 GB RAM 1x Samsung SSD 860...

Ah, found out there's "trunks=" in the vm config. An implementation in the webinterface would be nice :-)

A feature to tag only selected vlans on the vm's interface would be very useful (at the moment it's either one untagged or all tagged). Is such thing planned?