Problems with MAC addresses on hosting, ESXi 6.5 hypervisor

System & Network Administration — incorrectly specified categories?

13 USD

Client's review of cooperation with Roman L.

Problems with MAC addresses on hosting, ESXi 6.5 hypervisor

13 USD

Very quickly found what the problem, Roman knows his business perfectly, and understands the administration of servers at the highest level, for which, thank him very much, we remained happy.

5.0

Aleksey Oleynik

Reciprocal Feedback

28 June 2022

Freelancer's review of cooperation with Aleksey Oleynik

Problems with MAC addresses on hosting, ESXi 6.5 hypervisor

13 USD

It’s hard to work after r*** colleagues. But everything is accomplished. I recommend the customer.

5.0

Project translated automatically. Log in or register, to view the original There is hosting on www.hetzner.com, the last few months started with their support to send letters that we have MAC addresses that are not in the white list of MAC addresses, according to their recommendation updated the hypervisor version to the latest versions, it should have been to fix the problem, but again send letters about the same problem. We have 4 virtual machines on the host, nothing new has been set up, we can’t understand where these 2 MAC addresses came from, we need help in detecting and correcting this error, as we can block access to the server. I will provide more details in the project. Copy of the last letter: Dear Customer I'm afraid we can't unblock your server until the problem is solved. Unfortunately we still learn MAC addresses which are not allowed: Mostly is: Unallowed MACs: 7b: 87:a4 00:50:56:64:d8:2b

Proposals 4 Withdrawn 1 Rejected 2 Discussions 1

Yevhenii Sirov

1 0

Projects -
Rating -
Rating 397

Budget: 300 UAH Deadline: 1 day

Good day .
This is a well-known wealth of VMware, it is the way to unlock one of the services ready to help.

Serhii Mazurov

0 0

Projects -
Rating -
Rating 102

Budget: 500 UAH Deadline: 1 day

Good day .
Mac addresses generated by Hypervisor (VMware)
Such a problem occurs when the routing and network bridges are wrongly set. In this case, the virtual adapter "see" outside, and for the host these addresses are foreign.