Search results

Idea....? :rolleyes: could be that creating a vswitch and assigning (in some way) the proxmox bridges to the vlan , can limit the layer 2 traffic within the datacenter vswitch? https://docs.hetzner.com/robot/dedicated-server/network/vswitch/...

any news Hi Mr. Thommie. do you have good news?

Please let me know. https://forum.proxmox.com/threads/proxmox-generate-2-mac-address-visibile-on-the-switch-not-allowed-by-the-data-center.95946/post-419866 I scheduled to install proxmox 7 today. If doesn't work I will choose another strategy.

You have installed and configured the beta patch? https://forum.proxmox.com/threads/proxmox-generate-2-mac-address-visibile-on-the-switch-not-allowed-by-the-data-center.95946/post-419866

Really thank you for your work. I will migrate to 7.

This settings?

Doesn't works. After the main server reboot... There is the usual abuse notification email. This problem is fixed on proxmox 7? No LAN traffic is sent on the main Ethernet interface to the switch? I have migrated all to Amazon aws, my options are, try proxmox7 or change data center

What I understand it's that last possibilities to try is to switch to routed mode instead of bridged

at the server reboot .. new abuse message this not solve the problem.

Please let me know if this solution is still working for you! Thank you!

Hi. thank you for sharing. Only incoming rules? outgoing are not necessary? This solution is still working over days and weeks? Thank you.

I have moved critical vps to amazon aws. you confirm me that all this problems are solved on proxmox 7? thank you.-

automatic vps shutdown and start. I apply the same GROUP mac_address_deny After the GROUP mac_address_deny rules, after one week uptime I have received new abuse messages... (without any changes on the server and vps). But every time I restart the node after 5 minutes ..new abuse email...

thank you for the support. I mean proxmox Server reboot. [OPTIONS] log_level_in: info enable: 1 [RULES] GROUP mac_address_deny IN ACCEPT -source xxx.xxx.xxx.xxx -p tcp -dport 10000:30000 -log nolog IN SSH(ACCEPT) -source xxx.xxx.xxx.xxx -log info IN FTP(ACCEPT) -source xxx.xxx.xxx.xxx -log...

Hi "spirit" , I have a global rules added in every VPS and main host and the proxmox firewall is enabled on all VPS. Today after a serve restart: Allowed MACs: > 00:50:56:01:02:62 > d4:3d:7e:d8:bd:c5 > 00:50:56:00:eb:57 > 00:50:56:00:b1:05 > 00:50:56:00:84:12 > 00:50:56:00:b8:95 >...

There is no end to this problem. Allowed MACs: > 00:50:56:01:02:62 > d4:3d:7e:d8:bd:c5 > 00:50:56:00:eb:57 > 00:50:56:00:b1:05 > 00:50:56:00:84:12 > 00:50:56:00:b8:95 > 00:50:56:00:b8:8c > Unallowed MACs: > 00:50:56:00:05:2e >...

Hello. Do you have any news about this issue on proxmox 6.x? Really thank you.

hi thank you. why when are running? What I see is that the mac's are visibile on the switch only when the server is starting , after the complete boot there no mac visibile on the switch.

doesn't work. Restarted the server two times and at the second reboot , new abuse mail received.

nothing...also blocking the 43 port. New MAC address abuse message. how you have applied the rule? as global or replicated the rule for each device in the firewall? > Unallowed MACs: > 26:03:a1:a1:00:6c > 76:9f:bd:f1:bc:de > 9e:f7:09:95:e1:ab > d2:b2:a0:1d:1e:4a