How do MAC addresses get burned into devices during manufacturing?Shorthand MAC addressesWhat is this...

A curious equality of integrals involving the prime counting function?

Cat is tipping over bed-side lamps during the night

Which communication protocol is used in AdLib sound card?

Is the child responsible for the Parent PLUS Loan when the parent has passed away?

How does Leonard in "Memento" remember reading and writing?

How do you funnel food off a cutting board?

I have trouble understanding this fallacy: "If A, then B. Therefore if not-B, then not-A."

A starship is travelling at 0.9c and collides with a small rock. Will it leave a clean hole through, or will more happen?

What is a good reason for every spaceship to carry a weapon on board?

Why don't key signatures indicate the tonic?

Why was Lupin comfortable with saying Voldemort's name?

Is a new boolean field better than null reference when a value can be meaningfully absent?

Bash script to truncate subject line of incoming email

What happens when I Twin Life Transference?

Why did Democrats in the Senate oppose the Born-Alive Abortion Survivors Protection Act (2019 S.130)?

After checking in online, how do I know whether I need to go show my passport at airport check-in?

Why is it that Bernie Sanders is always called a "socialist"?

Building an exterior wall within an exterior wall for insulation

Macro expansion inside href

What happens when the wearer of a Shield of Missile Attraction is behind total cover?

In Linux what happens if 1000 files in a directory are moved to another location while another 300 files were added to the source directory?

Separate environment for personal and development use under macOS

Citing paywalled articles accessed via illegal web sharing

Can you tell from a blurry photo if focus was too close or too far?



How do MAC addresses get burned into devices during manufacturing?


Shorthand MAC addressesWhat is this device?Devices with user re-writable MAC addressesWhy are not all MAC addresses randomly assigned?Why are Ethernet/MAC addresses needed?How is uniqueness of MAC addresses enforced?Finding MAC addresses of devices previously plugged into a computerMultiple Devices, One Ethernet Jack, MAC FilteringWorking around IP Conflicts with ARP meddling or custom TCP/IP stackEthernet connection - device does not exist













2















I'm interested in the steps necessary to manufacture an IP-capable device - say an Ethernet card. Manufacturing the hardware is pretty straight forward since all of the devices are exactly the same and there are well-established ways to do this. Next you load up any firmware the device needs - again pretty straight forward as all of the devices can be treated identically.



But now you have an issue: each card needs to have its unique MAC address burned into it. I'm interested in whether the cost of doing this custom process relative to the other things (such as simply loading in firmware) is higher because it's "custom"? I'd imagine that you could simply do this by having a "burner" simply burn the next number in the sequence (for that vendor's unique prefix) to the card.



Are things as simple as that and am I just overthinking things here? Is assigning a MAC address a very very low cost process? Are there any other customizations that your typical device will need done to it?










share|improve this question























  • There's no "burn" operation. That's a chemical reaction induced by lasers on writable optical media. One common method I'm aware of is storing board specifc data such as MAC address and serial number in a serial EEPROM, which are low-pin count, low-capacity (<128 Kbits), low-cost storage devices. These chips are often programmed in bulk (using a chip "progammer" device) and then installed on the boards.

    – sawdust
    Oct 18 '14 at 5:15













  • Yeah, I understand that there's a difference between writing optical media and burning a PROM. So I guess that means that large numbers of chips can be programmed at low cost and then simply placed on a board as just another component. 128 Kbits seems like an awful lot of space for a MAC address and serial number. Is anything else typically written to these devices?

    – Sander Smith
    Oct 18 '14 at 23:19













  • The less than 128 Kbit number was just a number for typical serial EEPROM size. This semi-custom chip has 1.5Kbit capacity.

    – sawdust
    Oct 20 '14 at 1:03













  • I did notice the "less than", but even so, 1.5K is wayyyyyy more space than really necessary. Is there anything else typically written to these chips, or do they end up empty except for a 48 (or sometimes 64) bit address?

    – Sander Smith
    Oct 20 '14 at 14:04











  • I had a client whose board had a 1 Kbit serial EEPROM for storing the MAC address. That's all that they wanted stored there. Not even a CRC32 or checksum to validate the data. Another client's board stored the MAC address in the U-Boot environment in NAND Flash.

    – sawdust
    Oct 22 '14 at 0:36
















2















I'm interested in the steps necessary to manufacture an IP-capable device - say an Ethernet card. Manufacturing the hardware is pretty straight forward since all of the devices are exactly the same and there are well-established ways to do this. Next you load up any firmware the device needs - again pretty straight forward as all of the devices can be treated identically.



But now you have an issue: each card needs to have its unique MAC address burned into it. I'm interested in whether the cost of doing this custom process relative to the other things (such as simply loading in firmware) is higher because it's "custom"? I'd imagine that you could simply do this by having a "burner" simply burn the next number in the sequence (for that vendor's unique prefix) to the card.



Are things as simple as that and am I just overthinking things here? Is assigning a MAC address a very very low cost process? Are there any other customizations that your typical device will need done to it?










share|improve this question























  • There's no "burn" operation. That's a chemical reaction induced by lasers on writable optical media. One common method I'm aware of is storing board specifc data such as MAC address and serial number in a serial EEPROM, which are low-pin count, low-capacity (<128 Kbits), low-cost storage devices. These chips are often programmed in bulk (using a chip "progammer" device) and then installed on the boards.

    – sawdust
    Oct 18 '14 at 5:15













  • Yeah, I understand that there's a difference between writing optical media and burning a PROM. So I guess that means that large numbers of chips can be programmed at low cost and then simply placed on a board as just another component. 128 Kbits seems like an awful lot of space for a MAC address and serial number. Is anything else typically written to these devices?

    – Sander Smith
    Oct 18 '14 at 23:19













  • The less than 128 Kbit number was just a number for typical serial EEPROM size. This semi-custom chip has 1.5Kbit capacity.

    – sawdust
    Oct 20 '14 at 1:03













  • I did notice the "less than", but even so, 1.5K is wayyyyyy more space than really necessary. Is there anything else typically written to these chips, or do they end up empty except for a 48 (or sometimes 64) bit address?

    – Sander Smith
    Oct 20 '14 at 14:04











  • I had a client whose board had a 1 Kbit serial EEPROM for storing the MAC address. That's all that they wanted stored there. Not even a CRC32 or checksum to validate the data. Another client's board stored the MAC address in the U-Boot environment in NAND Flash.

    – sawdust
    Oct 22 '14 at 0:36














2












2








2


1






I'm interested in the steps necessary to manufacture an IP-capable device - say an Ethernet card. Manufacturing the hardware is pretty straight forward since all of the devices are exactly the same and there are well-established ways to do this. Next you load up any firmware the device needs - again pretty straight forward as all of the devices can be treated identically.



But now you have an issue: each card needs to have its unique MAC address burned into it. I'm interested in whether the cost of doing this custom process relative to the other things (such as simply loading in firmware) is higher because it's "custom"? I'd imagine that you could simply do this by having a "burner" simply burn the next number in the sequence (for that vendor's unique prefix) to the card.



Are things as simple as that and am I just overthinking things here? Is assigning a MAC address a very very low cost process? Are there any other customizations that your typical device will need done to it?










share|improve this question














I'm interested in the steps necessary to manufacture an IP-capable device - say an Ethernet card. Manufacturing the hardware is pretty straight forward since all of the devices are exactly the same and there are well-established ways to do this. Next you load up any firmware the device needs - again pretty straight forward as all of the devices can be treated identically.



But now you have an issue: each card needs to have its unique MAC address burned into it. I'm interested in whether the cost of doing this custom process relative to the other things (such as simply loading in firmware) is higher because it's "custom"? I'd imagine that you could simply do this by having a "burner" simply burn the next number in the sequence (for that vendor's unique prefix) to the card.



Are things as simple as that and am I just overthinking things here? Is assigning a MAC address a very very low cost process? Are there any other customizations that your typical device will need done to it?







ethernet burning mac-address






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Oct 18 '14 at 2:46









Sander SmithSander Smith

1163




1163













  • There's no "burn" operation. That's a chemical reaction induced by lasers on writable optical media. One common method I'm aware of is storing board specifc data such as MAC address and serial number in a serial EEPROM, which are low-pin count, low-capacity (<128 Kbits), low-cost storage devices. These chips are often programmed in bulk (using a chip "progammer" device) and then installed on the boards.

    – sawdust
    Oct 18 '14 at 5:15













  • Yeah, I understand that there's a difference between writing optical media and burning a PROM. So I guess that means that large numbers of chips can be programmed at low cost and then simply placed on a board as just another component. 128 Kbits seems like an awful lot of space for a MAC address and serial number. Is anything else typically written to these devices?

    – Sander Smith
    Oct 18 '14 at 23:19













  • The less than 128 Kbit number was just a number for typical serial EEPROM size. This semi-custom chip has 1.5Kbit capacity.

    – sawdust
    Oct 20 '14 at 1:03













  • I did notice the "less than", but even so, 1.5K is wayyyyyy more space than really necessary. Is there anything else typically written to these chips, or do they end up empty except for a 48 (or sometimes 64) bit address?

    – Sander Smith
    Oct 20 '14 at 14:04











  • I had a client whose board had a 1 Kbit serial EEPROM for storing the MAC address. That's all that they wanted stored there. Not even a CRC32 or checksum to validate the data. Another client's board stored the MAC address in the U-Boot environment in NAND Flash.

    – sawdust
    Oct 22 '14 at 0:36



















  • There's no "burn" operation. That's a chemical reaction induced by lasers on writable optical media. One common method I'm aware of is storing board specifc data such as MAC address and serial number in a serial EEPROM, which are low-pin count, low-capacity (<128 Kbits), low-cost storage devices. These chips are often programmed in bulk (using a chip "progammer" device) and then installed on the boards.

    – sawdust
    Oct 18 '14 at 5:15













  • Yeah, I understand that there's a difference between writing optical media and burning a PROM. So I guess that means that large numbers of chips can be programmed at low cost and then simply placed on a board as just another component. 128 Kbits seems like an awful lot of space for a MAC address and serial number. Is anything else typically written to these devices?

    – Sander Smith
    Oct 18 '14 at 23:19













  • The less than 128 Kbit number was just a number for typical serial EEPROM size. This semi-custom chip has 1.5Kbit capacity.

    – sawdust
    Oct 20 '14 at 1:03













  • I did notice the "less than", but even so, 1.5K is wayyyyyy more space than really necessary. Is there anything else typically written to these chips, or do they end up empty except for a 48 (or sometimes 64) bit address?

    – Sander Smith
    Oct 20 '14 at 14:04











  • I had a client whose board had a 1 Kbit serial EEPROM for storing the MAC address. That's all that they wanted stored there. Not even a CRC32 or checksum to validate the data. Another client's board stored the MAC address in the U-Boot environment in NAND Flash.

    – sawdust
    Oct 22 '14 at 0:36

















There's no "burn" operation. That's a chemical reaction induced by lasers on writable optical media. One common method I'm aware of is storing board specifc data such as MAC address and serial number in a serial EEPROM, which are low-pin count, low-capacity (<128 Kbits), low-cost storage devices. These chips are often programmed in bulk (using a chip "progammer" device) and then installed on the boards.

– sawdust
Oct 18 '14 at 5:15







There's no "burn" operation. That's a chemical reaction induced by lasers on writable optical media. One common method I'm aware of is storing board specifc data such as MAC address and serial number in a serial EEPROM, which are low-pin count, low-capacity (<128 Kbits), low-cost storage devices. These chips are often programmed in bulk (using a chip "progammer" device) and then installed on the boards.

– sawdust
Oct 18 '14 at 5:15















Yeah, I understand that there's a difference between writing optical media and burning a PROM. So I guess that means that large numbers of chips can be programmed at low cost and then simply placed on a board as just another component. 128 Kbits seems like an awful lot of space for a MAC address and serial number. Is anything else typically written to these devices?

– Sander Smith
Oct 18 '14 at 23:19







Yeah, I understand that there's a difference between writing optical media and burning a PROM. So I guess that means that large numbers of chips can be programmed at low cost and then simply placed on a board as just another component. 128 Kbits seems like an awful lot of space for a MAC address and serial number. Is anything else typically written to these devices?

– Sander Smith
Oct 18 '14 at 23:19















The less than 128 Kbit number was just a number for typical serial EEPROM size. This semi-custom chip has 1.5Kbit capacity.

– sawdust
Oct 20 '14 at 1:03







The less than 128 Kbit number was just a number for typical serial EEPROM size. This semi-custom chip has 1.5Kbit capacity.

– sawdust
Oct 20 '14 at 1:03















I did notice the "less than", but even so, 1.5K is wayyyyyy more space than really necessary. Is there anything else typically written to these chips, or do they end up empty except for a 48 (or sometimes 64) bit address?

– Sander Smith
Oct 20 '14 at 14:04





I did notice the "less than", but even so, 1.5K is wayyyyyy more space than really necessary. Is there anything else typically written to these chips, or do they end up empty except for a 48 (or sometimes 64) bit address?

– Sander Smith
Oct 20 '14 at 14:04













I had a client whose board had a 1 Kbit serial EEPROM for storing the MAC address. That's all that they wanted stored there. Not even a CRC32 or checksum to validate the data. Another client's board stored the MAC address in the U-Boot environment in NAND Flash.

– sawdust
Oct 22 '14 at 0:36





I had a client whose board had a 1 Kbit serial EEPROM for storing the MAC address. That's all that they wanted stored there. Not even a CRC32 or checksum to validate the data. Another client's board stored the MAC address in the U-Boot environment in NAND Flash.

– sawdust
Oct 22 '14 at 0:36










1 Answer
1






active

oldest

votes


















-1














There are these useful but flawed usb to rj45 dongles that have the same MAC addresses and if you need more then one for your, say Rapsberry pi Cluster, you are in trouble. These are USB devices, there must be a way to reflash the EEPROM memory to issue new MAC addresses?






share|improve this answer








New contributor




Denis Kay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f828032%2fhow-do-mac-addresses-get-burned-into-devices-during-manufacturing%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    -1














    There are these useful but flawed usb to rj45 dongles that have the same MAC addresses and if you need more then one for your, say Rapsberry pi Cluster, you are in trouble. These are USB devices, there must be a way to reflash the EEPROM memory to issue new MAC addresses?






    share|improve this answer








    New contributor




    Denis Kay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.

























      -1














      There are these useful but flawed usb to rj45 dongles that have the same MAC addresses and if you need more then one for your, say Rapsberry pi Cluster, you are in trouble. These are USB devices, there must be a way to reflash the EEPROM memory to issue new MAC addresses?






      share|improve this answer








      New contributor




      Denis Kay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.























        -1












        -1








        -1







        There are these useful but flawed usb to rj45 dongles that have the same MAC addresses and if you need more then one for your, say Rapsberry pi Cluster, you are in trouble. These are USB devices, there must be a way to reflash the EEPROM memory to issue new MAC addresses?






        share|improve this answer








        New contributor




        Denis Kay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.










        There are these useful but flawed usb to rj45 dongles that have the same MAC addresses and if you need more then one for your, say Rapsberry pi Cluster, you are in trouble. These are USB devices, there must be a way to reflash the EEPROM memory to issue new MAC addresses?







        share|improve this answer








        New contributor




        Denis Kay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer






        New contributor




        Denis Kay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 13 mins ago









        Denis KayDenis Kay

        1




        1




        New contributor




        Denis Kay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        Denis Kay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        Denis Kay is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f828032%2fhow-do-mac-addresses-get-burned-into-devices-during-manufacturing%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Couldn't open a raw socket. Error: Permission denied (13) (nmap)Is it possible to run networking commands...

            VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

            Why not use the yoke to control yaw, as well as pitch and roll? Announcing the arrival of...