[SOLVED] MAC Address Blocked, How to Unblock?

[Nollimox]

A few nights ago, a Mac pro that I used to access Proxmox's computer suddenly lost the ability to access. I discovered that it may have been blocked because I used another laptop that was successful...that's when I realized somehow, despite I had not have firewall enabled, Proxmox is blocking by mac address.

The reason for that conclusion is I had installed Openmediavault on a VM and had the wrong user name as well as password on its webgui (had an old user/password set with that IP assigned saved in the browser). So, when the Openmediavault webgui loaded, I had selected enter only to realize it was the wrong user/password combo. After that, I lost access from the Mac pro...timeout. I did not enabled firewall on Openmediavault and the only VM on the Proxmox virtual environment I am able to access from the Mac pro is pfSense...I cannot access Proxmox nor Openmediavault. I am on Proxmox 8.1 with 6.5 kernel.

 

[taurolyon]

I'm not familiar with OMV, but some distros have Fail2Ban installed which monitor for failed login attempts and will jail them for a period of time. I would start by checking your container's /var/log files.

 

[Nollimox]

I'm not familiar with OMV, but some distros have Fail2Ban installed which monitor for failed login attempts and will jail them for a period of time. I would start by checking your container's /var/log files.

Okay...however, why that would cause me to also lose access to Proxmox itself? I can understand OMV...

 

[leesteken]

Okay...however, why that would cause me to also lose access to Proxmox itself? I can understand OMV...

Proxmox does not block MAC addresses (because of wrong passwords or otherwise) unless you added that yourself. Or it's a different kind of network issue.

 

[Nollimox]

Proxmox does not block MAC addresses (because of wrong passwords or otherwise) unless you added that yourself. Or it's a different kind of network issue.

No, didn't add anything and what kind of other network issue...for instance, if I ping the Mac pro from Proxmon, I'll get two packets received and the rest lost, while if I ping Proxmox from the Mac pro, I'll get timeout. I didn't set firewall on any VM or Proxmox because I have pfSense firewall VM, which is the only VM I can connect to from the Mac pro...baffling, indeed.

 

[Nollimox]

Well, it turned out that it wasn't a Proxmox problem or if it was a problem. The Mac pro was set to using DHCP with a manual address. So, I tried setting it as manual address...it's working that way now and it worked as manual using DHCP before...still baffling.

 

[leesteken]

Well, it turned out that it wasn't a Proxmox problem or if it was a problem. The Mac pro was set to using DHCP with a manual address. So, I tried setting it as manual address...it's working that way now and it worked as manual using DHCP before...still baffling.

I've seen more reports recently that routers are blocking traffic from static addresses that are inside the DHCP range. It used to be that people installed Proxmox unwittingly with a DHCP address and it just worked until the duplicate IP appeared on the network. Nowadays, people just can't connect to their new installation. Maybe it's related. Anyway, I'm glad you solved it and thanks for reporting back.

EDIT: Apologies for wasting more of your time.

 

[Nollimox]

I've seen more reports recently that routers are blocking traffic from static addresses that are inside the DHCP range. It used to be that people installed Proxmox unwittingly with a DHCP address and it just worked until the duplicate IP appeared on the network. Nowadays, people just can't connect to their new installation. Maybe it's related. Anyway, I'm glad you solved it and thanks for reporting back.

I had purposely set DHCP lease range from 105 - 254 and all addresses that were set manually are from 1 - 99 just to be careful to not have any conflicts...I may reverse to what the Mac pro had before just to see what happen later after I complete my Proxmox virtual environment for what I want to accomplish. It took lots of time figuring out this...time that I really didn't have to spare...