![]() ![]() ![]() To counter this, you just need to update the udev rules. If it has an entry for eth1 with a known MAC address and a card appears with a different MAC address it will allocate a different ethX device name to the interface. So udev uses persistence rules based on the MAC address of the network card. The OS cannot rely on them just being physically in the same spot each time - you may move them around for example, or some systems do not report their physical connections in the same sequence each boot. This is because when you have multiple nics, you want them to always have the same ethX name, so that your /etc/network/interfaces configuration targets the right nic each boot. One of the things it does by default is to try to maintain persistent names for network interface cards. This is the process that looks at hardware and sets that hardware up in /dev (or whatever else might need to be done). However, a temporary change as in the other answer by Zuul may be best for your purposes, as it will change the MAC without causing too many additional problems - however it will not survive a reboot.Ĭhanging it in VirtualBox will of course survive a reboot, but the issue you are facing is with udev. Public static string ErrorMessage ) and change string retorno = Bash(arp) to string retorno = CMD(arp) or use the method mentioned in question.You are very likely using the "correct" method to change the MAC address, if you are doing this in the advanced network settings in VirtualBox. I already have tools that can identify the Mac-Address of the devices in my network, as long as the 'server' or the application is running in Windows and. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |