![]() ![]() One thing this doesn't do is avoid using your actual mac address. a much more comprehensive list is the file 'manuf' in the root directory of the wireshark source, but it needs some editing before it will work with the code snippet. I know of two sources for a list of valid manufacturer mac address triples. # Returns a random MAC address with first three octets from last three random. # Loads vendor mac prefix file into load_vendors = () I do have better ideas, but, before I set up to reinvent the wheel, I would like to ask if there's some well-established practice to deal with the problem.My = ( "00:00:0C:", "00:00:CE:", "00:00:EF:" ) dtb just to change MAC address (and find the right place to dump it) does not look better. ![]() This, beside being inelegant, means a different address will appear on-line for a short time. Are there:) Netbook (Acer Aspire One 110 160gb SATA HD 1.5gb ram): archlinux i686 / KDE mod 4. My current strategy id to retrieve it in the startup phase and modify the (random generated) MAC address (together with other data) using something like macchanger. In my case this serialized data is loaded in a very small MTD partition. Normal procedure is to have a "programming station" at the end of the production line to load Flash (SPI NOR, in my case) with all needed data most of it is static, but a small part will need to be "serialized". What is the "best practice" for serialization in production? This is testified by several drovers calling const void *of_get_mac_address(struct device_node *np)Īddr = of_get_mac_addr(np, "mac-address") Īddr = of_get_mac_addr(np, "local-mac-address") Your networking equipment needs to be able to handle promiscuous mode, where. Apparently the current trend in kernel (correct me if I got that wrong) is to embed it in Device Tree. have an inappropriately large number of unique MAC addresses in your network. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |