Why isn't my forced MAC address change working (Raspberry Pi)?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I'm working with Raspberry Pi Zeros on a subnet. I bought external Ethernet adapters for each one to connect them to one another. Unfortunately, these ethernet adapters all came with the exact same MAC addresses, making communication between the Pis near impossible.



Because of that I've tried forcing a change to the MAC addresses by editing /etc/systemd/network/00-default.link in each Pi Zero in accordance with the steps outlined in this post. Ultimately, I used the following code:



[Match]
MACAddress=00:e0:4c:53:44:58

[Link]
MACAddress=10:00:00:00:00:11


Note that I used a different new MAC address for each Pi



Unfortunately, after restarting all of my Pi Zeros, none of the MAC addresses updated to the new assigned values. When I check with ifconfig they all had remained the same original values. What am I doing wrong?



Additional info:



ip neighbor show yields the following result:



pi@raspberrypi:~ $ ip neighbor show
192.168.2.37 dev wlan0 lladdr ac:bc:32:87:93:39 DELAY
192.168.3.12 dev enxb827eb9c0ecf lladdr 00:e0:4c:53:44:58 STALE
192.168.3.10 dev enxb827eb9c0ecf lladdr 00:e0:4c:53:44:58 STALE
192.168.3.11 dev enxb827eb9c0ecf lladdr 00:e0:4c:53:44:58 STALE
192.168.2.1 dev wlan0 lladdr 40:c7:29:4e:4d:f8 STALE


ifconfig shows:



eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.12 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 fe80::4db4:2630:6df9:2aeb prefixlen 64 scopeid 0x20<link>
ether 00:e0:4c:53:44:58 txqueuelen 1000 (Ethernet)
RX packets 144 bytes 11482 (11.2 KiB)
RX errors 1 dropped 0 overruns 0 frame 0
TX packets 133 bytes 17886 (17.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


I also cannot sudo ifdown eth0 - it yields the error: ifdown: unknown interface eth0 Then when I check cat /run/network/ifstate, eth0 is not listed. The contents is only:



lo=lo


I've also set a static IP in /etc/dhcpcd.conf like so:



interface eth0
static ip_address=192.168.3.12


I'm starting to think that this issue is being caused by the naming difference between the interface name eth0 shown when calling ifconfig and enxb827eb9c0ecf shown when calling ip neighbor show from another computer. I only have 1 network interface so having multiple names doesn't make sense to me.









share







New contributor




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























    up vote
    0
    down vote

    favorite












    I'm working with Raspberry Pi Zeros on a subnet. I bought external Ethernet adapters for each one to connect them to one another. Unfortunately, these ethernet adapters all came with the exact same MAC addresses, making communication between the Pis near impossible.



    Because of that I've tried forcing a change to the MAC addresses by editing /etc/systemd/network/00-default.link in each Pi Zero in accordance with the steps outlined in this post. Ultimately, I used the following code:



    [Match]
    MACAddress=00:e0:4c:53:44:58

    [Link]
    MACAddress=10:00:00:00:00:11


    Note that I used a different new MAC address for each Pi



    Unfortunately, after restarting all of my Pi Zeros, none of the MAC addresses updated to the new assigned values. When I check with ifconfig they all had remained the same original values. What am I doing wrong?



    Additional info:



    ip neighbor show yields the following result:



    pi@raspberrypi:~ $ ip neighbor show
    192.168.2.37 dev wlan0 lladdr ac:bc:32:87:93:39 DELAY
    192.168.3.12 dev enxb827eb9c0ecf lladdr 00:e0:4c:53:44:58 STALE
    192.168.3.10 dev enxb827eb9c0ecf lladdr 00:e0:4c:53:44:58 STALE
    192.168.3.11 dev enxb827eb9c0ecf lladdr 00:e0:4c:53:44:58 STALE
    192.168.2.1 dev wlan0 lladdr 40:c7:29:4e:4d:f8 STALE


    ifconfig shows:



    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.3.12 netmask 255.255.255.0 broadcast 192.168.3.255
    inet6 fe80::4db4:2630:6df9:2aeb prefixlen 64 scopeid 0x20<link>
    ether 00:e0:4c:53:44:58 txqueuelen 1000 (Ethernet)
    RX packets 144 bytes 11482 (11.2 KiB)
    RX errors 1 dropped 0 overruns 0 frame 0
    TX packets 133 bytes 17886 (17.4 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    inet6 ::1 prefixlen 128 scopeid 0x10<host>
    loop txqueuelen 1000 (Local Loopback)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


    I also cannot sudo ifdown eth0 - it yields the error: ifdown: unknown interface eth0 Then when I check cat /run/network/ifstate, eth0 is not listed. The contents is only:



    lo=lo


    I've also set a static IP in /etc/dhcpcd.conf like so:



    interface eth0
    static ip_address=192.168.3.12


    I'm starting to think that this issue is being caused by the naming difference between the interface name eth0 shown when calling ifconfig and enxb827eb9c0ecf shown when calling ip neighbor show from another computer. I only have 1 network interface so having multiple names doesn't make sense to me.









    share







    New contributor




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





















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I'm working with Raspberry Pi Zeros on a subnet. I bought external Ethernet adapters for each one to connect them to one another. Unfortunately, these ethernet adapters all came with the exact same MAC addresses, making communication between the Pis near impossible.



      Because of that I've tried forcing a change to the MAC addresses by editing /etc/systemd/network/00-default.link in each Pi Zero in accordance with the steps outlined in this post. Ultimately, I used the following code:



      [Match]
      MACAddress=00:e0:4c:53:44:58

      [Link]
      MACAddress=10:00:00:00:00:11


      Note that I used a different new MAC address for each Pi



      Unfortunately, after restarting all of my Pi Zeros, none of the MAC addresses updated to the new assigned values. When I check with ifconfig they all had remained the same original values. What am I doing wrong?



      Additional info:



      ip neighbor show yields the following result:



      pi@raspberrypi:~ $ ip neighbor show
      192.168.2.37 dev wlan0 lladdr ac:bc:32:87:93:39 DELAY
      192.168.3.12 dev enxb827eb9c0ecf lladdr 00:e0:4c:53:44:58 STALE
      192.168.3.10 dev enxb827eb9c0ecf lladdr 00:e0:4c:53:44:58 STALE
      192.168.3.11 dev enxb827eb9c0ecf lladdr 00:e0:4c:53:44:58 STALE
      192.168.2.1 dev wlan0 lladdr 40:c7:29:4e:4d:f8 STALE


      ifconfig shows:



      eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
      inet 192.168.3.12 netmask 255.255.255.0 broadcast 192.168.3.255
      inet6 fe80::4db4:2630:6df9:2aeb prefixlen 64 scopeid 0x20<link>
      ether 00:e0:4c:53:44:58 txqueuelen 1000 (Ethernet)
      RX packets 144 bytes 11482 (11.2 KiB)
      RX errors 1 dropped 0 overruns 0 frame 0
      TX packets 133 bytes 17886 (17.4 KiB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
      inet 127.0.0.1 netmask 255.0.0.0
      inet6 ::1 prefixlen 128 scopeid 0x10<host>
      loop txqueuelen 1000 (Local Loopback)
      RX packets 0 bytes 0 (0.0 B)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 0 bytes 0 (0.0 B)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


      I also cannot sudo ifdown eth0 - it yields the error: ifdown: unknown interface eth0 Then when I check cat /run/network/ifstate, eth0 is not listed. The contents is only:



      lo=lo


      I've also set a static IP in /etc/dhcpcd.conf like so:



      interface eth0
      static ip_address=192.168.3.12


      I'm starting to think that this issue is being caused by the naming difference between the interface name eth0 shown when calling ifconfig and enxb827eb9c0ecf shown when calling ip neighbor show from another computer. I only have 1 network interface so having multiple names doesn't make sense to me.









      share







      New contributor




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











      I'm working with Raspberry Pi Zeros on a subnet. I bought external Ethernet adapters for each one to connect them to one another. Unfortunately, these ethernet adapters all came with the exact same MAC addresses, making communication between the Pis near impossible.



      Because of that I've tried forcing a change to the MAC addresses by editing /etc/systemd/network/00-default.link in each Pi Zero in accordance with the steps outlined in this post. Ultimately, I used the following code:



      [Match]
      MACAddress=00:e0:4c:53:44:58

      [Link]
      MACAddress=10:00:00:00:00:11


      Note that I used a different new MAC address for each Pi



      Unfortunately, after restarting all of my Pi Zeros, none of the MAC addresses updated to the new assigned values. When I check with ifconfig they all had remained the same original values. What am I doing wrong?



      Additional info:



      ip neighbor show yields the following result:



      pi@raspberrypi:~ $ ip neighbor show
      192.168.2.37 dev wlan0 lladdr ac:bc:32:87:93:39 DELAY
      192.168.3.12 dev enxb827eb9c0ecf lladdr 00:e0:4c:53:44:58 STALE
      192.168.3.10 dev enxb827eb9c0ecf lladdr 00:e0:4c:53:44:58 STALE
      192.168.3.11 dev enxb827eb9c0ecf lladdr 00:e0:4c:53:44:58 STALE
      192.168.2.1 dev wlan0 lladdr 40:c7:29:4e:4d:f8 STALE


      ifconfig shows:



      eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
      inet 192.168.3.12 netmask 255.255.255.0 broadcast 192.168.3.255
      inet6 fe80::4db4:2630:6df9:2aeb prefixlen 64 scopeid 0x20<link>
      ether 00:e0:4c:53:44:58 txqueuelen 1000 (Ethernet)
      RX packets 144 bytes 11482 (11.2 KiB)
      RX errors 1 dropped 0 overruns 0 frame 0
      TX packets 133 bytes 17886 (17.4 KiB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
      inet 127.0.0.1 netmask 255.0.0.0
      inet6 ::1 prefixlen 128 scopeid 0x10<host>
      loop txqueuelen 1000 (Local Loopback)
      RX packets 0 bytes 0 (0.0 B)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 0 bytes 0 (0.0 B)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


      I also cannot sudo ifdown eth0 - it yields the error: ifdown: unknown interface eth0 Then when I check cat /run/network/ifstate, eth0 is not listed. The contents is only:



      lo=lo


      I've also set a static IP in /etc/dhcpcd.conf like so:



      interface eth0
      static ip_address=192.168.3.12


      I'm starting to think that this issue is being caused by the naming difference between the interface name eth0 shown when calling ifconfig and enxb827eb9c0ecf shown when calling ip neighbor show from another computer. I only have 1 network interface so having multiple names doesn't make sense to me.







      linux networking mac-address





      share







      New contributor




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










      share







      New contributor




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








      share



      share






      New contributor




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









      asked 4 mins ago









      Matt

      1011




      1011




      New contributor




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





      New contributor





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






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

























          active

          oldest

          votes











          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          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',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );






          Matt is a new contributor. Be nice, and check out our Code of Conduct.









           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f475191%2fwhy-isnt-my-forced-mac-address-change-working-raspberry-pi%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          Matt is a new contributor. Be nice, and check out our Code of Conduct.









           

          draft saved


          draft discarded


















          Matt is a new contributor. Be nice, and check out our Code of Conduct.












          Matt is a new contributor. Be nice, and check out our Code of Conduct.











          Matt is a new contributor. Be nice, and check out our Code of Conduct.













           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f475191%2fwhy-isnt-my-forced-mac-address-change-working-raspberry-pi%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Bahrain

          Postfix configuration issue with fips on centos 7; mailgun relay