Recent content by olegburca

I checked previously and it was not really set on any interface. Cannot check right now as already disabled IPv6 at kernel level. I have a feeling like it was set occasionally for some purpose (unknown for me). Tonight it logged about 20 records, but without any evident periodicity. There were...

I added the rules with DROP, however looks like it was not blocking the packets with wrong MAC address. I inspected the traffic using tcpdump and found the following packages: 08:21:56.823350 00:25:90:d8:38:96 (oui Unknown) > 00:31:46:0d:24:02 (oui Unknown), ethertype IPv6 (0x86dd), length 78...

Yes, it is: # sysctl -a |grep net.ipv4.igmp_link_local_mcast_reports net.ipv4.igmp_link_local_mcast_reports = 0 I did this and restarted the server when you recommended this previously.

Hi, We got a new warning from Hetzner, despite we already set the configurations above. net.ipv4.igmp_link_local_mcast_reports is disabled, pve-cluster and pve-firewall packages are updated, No rules for port 43 in the firewall configuration, port 43 is not accessible (Connection timed out...

Hi @spirit, Everything was done excepting the net.ipv4.igmp_link_local_mcast_reports configuration. Just applied it. In case we use IPv6 - is there an equivalent igmp_link_local_mcast_reports directive for it? Should it be also disabled? Thank you!

Yes, I use firewall functionality, configured from Proxmox web interface. I set the Input policy to DROP (at Datacenter, Proxmox server and VM level) and only allowed the required ports. Proxmox was installed using Hetzner image for Proxmox 7 two months ago. In CLI these are the existing REJECT...

Hi, Here we go again :) We are using Proxmox 7.1-8 and got an abuse message from Hetzner today: Anyone else got the abuse message for Proxmox 7? Any ideas how to fix it?