Multiple clusterHATs on the same LAN have duplicate MAC addresses

[trei...@xs4all.nl]

Trying to get two (or more) clusterHATs working on the same network, as expected I ran into neworking trouble as the Pi Zeroes have the same LAN MAC addresses on both clusters (00:22:82:FF:FF:0X, with X indicating the slotnumber of the Pi Zero).

Of course I could try to put each cluster on a separate VLAN and route these VLANs together somehow, but a better solution would be to get the MAC addresses unique.

How can I achieve that? Each cluster consists of a RPi 3B+ with clusterHAT v2.2 and four RPi Zeroes V1.3.

[David Glaude]

From memory, you are not limited to p1, p2, p3 and p4.

By checking some files, I feel that up to 255 mac could be possible.

I would try use the intermediate level setup instruction and try with customisation to do

     " quiet init=/sbin/reconfig-clusterhat p5"

But you will soon get a more expert answer.

(also, you may want to wait for the new image)

Regards

--
You received this message because you are subscribed to the Google Groups "ClusterHAT" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clusterhat+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/clusterhat/10319504-96c3-4cc1-9c08-8542fbddbe88%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chris Burton]

Hi, 

But you will soon get a more expert answer.

(also, you may want to wait for the new image)

What David said :)

For mine I reconfigure them (following "Intermediate" instructions on https://clusterhat.com/setup-software to reconfigure) as p11-p14 for the first controller, p21-p24 for the second etc. but as David said you can use anything between p1 and p255 (you can still logiin after and change the hostname if you want to use your own naming).

Chris.

[trei...@xs4all.nl]

Hello David and Chris,

thank you for your fast replies. Unfortunately I was away for a few days so I could not test & answer at the same speed.

With your information - sorry I missed that part of the "intermediate" instructions before - I got the second clusterHAT working alongside the first, although some questions remain:

1. Controller 1 has the Zeroes on the original p1-p4 (later to be changed to p11-p14), Controller 2 has them on p21-p24. The p21 and p22 work fine, but p23 and p24 do not show in lsusb or in ifconfig on controller 2. When I put the SDHC cards from p3 and p4 in as they are, they do run (of course as p3 and p4), so it is not a hardware problem on the HAT or the Zeroes. I have rewritten the cards from the image, but that did not help. I saw that Chris just put new images online so the next step is try to use a new SDHC card with the new images.

2. ifconfig on either controller still does not show the IPv4 addresses of the Zeroes, it does however show IPv6 addresses. After a while it will also show APIPA adresses on ethpi21 and ethpi22 on MAC addresses 00:22:82:ff:fe:15 and fe:16. These MAC addresses seem to relate to the controller and not to the Zeroes.

pi@DRCnode20:~ $ ifconfig
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.178.110  netmask 255.255.255.128  broadcast 192.168.178.127
        inet6 fe80::5937:72e:c09b:3b1d  prefixlen 64  scopeid 0x20<link>
        inet6 2001:980:aef1:1:d6e2:8171:bc4b:3d06  prefixlen 64  scopeid 0x0<global>
        ether b8:27:eb:97:fe:42  txqueuelen 1000  (Ethernet)
        RX packets 1494  bytes 203394 (198.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 340  bytes 55271 (53.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether b8:27:eb:97:fe:42  txqueuelen 1000  (Ethernet)
        RX packets 4113  bytes 1394619 (1.3 MiB)
        RX errors 0  dropped 36  overruns 0  frame 0
        TX packets 632  bytes 91110 (88.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ethpi3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::222:82ff:feff:fe03  prefixlen 64  scopeid 0x20<link>
        ether 00:22:82:ff:fe:03  txqueuelen 1000  (Ethernet)
        RX packets 75  bytes 8200 (8.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 692  bytes 82469 (80.5 KiB)
        TX errors 1  dropped 0 overruns 0  carrier 0  collisions 0

ethpi4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::222:82ff:feff:fe04  prefixlen 64  scopeid 0x20<link>
        ether 00:22:82:ff:fe:04  txqueuelen 1000  (Ethernet)
        RX packets 71  bytes 7876 (7.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 597  bytes 67177 (65.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ethpi21: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 169.254.58.166  netmask 255.255.0.0  broadcast 169.254.255.255
        inet6 fe80::b567:de85:ed0a:b312  prefixlen 64  scopeid 0x20<link>
        ether 00:22:82:ff:fe:15  txqueuelen 1000  (Ethernet)
        RX packets 74  bytes 7804 (7.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 760  bytes 95533 (93.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ethpi22: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 169.254.59.150  netmask 255.255.0.0  broadcast 169.254.255.255
        inet6 fe80::18ee:d22c:a7c2:f0a3  prefixlen 64  scopeid 0x20<link>
        ether 00:22:82:ff:fe:16  txqueuelen 1000  (Ethernet)
        RX packets 72  bytes 7871 (7.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 739  bytes 92590 (90.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 8  bytes 312 (312.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8  bytes 312 (312.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:c2:ab:17  txqueuelen 1000  (Ethernet)
        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

pi@DRCnode20:~ $