Search results

Very nice, it also runs on VenusOS.

You can also enable the Hetzner Robot Firewall: https://forum.proxmox.com/threads/proxmox-claiming-mac-address.52601/post-419029

No, I have reproduced it on 2 hosts, other 2 (after setting echo 0 > /proc/sys/net/ipv4/igmp_link_local_mcast_reports) hosts looks good, no abuse message. We use hetzner (over 10 Years) and proxmox (since pve 5) lots of years, and we hand never a big trouble.

@spirit for me net.ipv4.igmp_link_local_mcast_reports = 0 in combination of the Hetzner Robot Firewall it looks good, I tried to restart CTs (and also update from 10.5 to 10.10 ;)) on different hosts. No new Abuse Message.

Thanks, I will try it soon. At the moment: # cat /proc/sys/net/ipv4/igmp_link_local_mcast_reports 1 I also have IPv6 enabled, here the /etc/network/interfaces (xxx.xxx -> Public IPs) (yyy.yyy -> Internal (local) IPv4) # interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet...

Now, the problem is back after i upgraded a LXC with Debian 10.5 to 10.10 (and reboot the lxc, reboots on 10.5 makes no problems), I can find the problematic MAC with "ip add" on the fwln100i0@fwpr100p0 bridge. But it's strange with enabled Hetzner Robot Firewall there is no traffic to find with...

For us it is working for 8 days, the abuse messages before without the rules cams every 2 days. - Do you now that no of your VM has a wrong MAC ? - Yes, only a in comming rule, because its redirected traffic for other hosts... Read the posts of this thread to understand it. Edit: - Have you...

It's very simple, I created a screenshot replace <Your IP 1 - 5> with your public IP that you can find at the first tab "IPs". The name filed is irrelevant choose everything that describe your rule.

Hello, we have the same trouble, I tried a lot to drop the traffic with iptables and ebtabels every times the solve check from hetzner results in ok, but after some days the problem war’s back with new MACs. Now, I fixed it by activating the hetzner firewall (in robot) and replaced the default...

I put the arc_max to 24GB the host has 64GB RAM, the disks are 4 x ST10000NM0568 - Seagate Exos x14 10TB.

Hello, we have a PBS datastore on a ZFS encrypted volume. When the garbage collection is running, the kernel is crashing after 31% of the marking process. PBS Log: 2021-09-17T07:22:50+02:00: starting garbage collection on store synflow 2021-09-17T07:22:50+02:00: Start GC phase1 (mark used...

I think you mean we should run rsync manual? vzdump does not support the Aruments -v --progress Edit: I get the right log while the backup job was running, I passed a bash file with the arguments and a log output to the original rsync location: 2021/08/31 09:00:54 [3886663] Number of files...

Here I found a new thread: https://forum.proxmox.com/threads/error-backup-container-lxc-code-error-23.94899/#post-413937 Sorry, I would not reopen a thread, when the problem still exists.

Hello, same problem here also on an upgrade to PVE 7. () INFO: starting new backup job: vzdump 199 --mode snapshot --remove 0 --storage pvebackup --node host03 INFO: Starting Backup of VM 199 (lxc) INFO: Backup started at 2021-08-31 07:38:44 INFO: status = running INFO: CT Name: M*********...

Hello, I have the same problem after upgrading to PVE 7 and PBS 2. Two LXCs there wont backup, ACL enable/disable dosn't fix it.

Hello, I have the same Problem after an upgrade to PVE 7 and PBS 2. Have any one fix this problem?

Hallo, die MergeIDE funktioniert für alle gängigen Microsoft Systeme: https://pve.proxmox.com/wiki/File:Mergeide.zip?? Einfach ausführen und VM Herrunterfahren (nicht noch einmal booten). Anschließend die virtuelle HDD ins Proxmox migrieren. (IDE für den ersten Start nutzen) Viele Grüße, Marvin

On a Intel S5520UR with two Intel Xeon E5620 the Kernel 5.11.22-6 (and also 5.11.22-7) fixes the problem. (Without the aio=native) Thanks!

Vielen Dank, es scheint das gleiche zu sein. Leider war es mir nicht möglich die Kernel Panic auszugeben.

Thanks, it seams to fix it. Unfortunately, I was unable to create a kernel panic dump, because I use some nic bonding.