question

kenrick avatar image

CCGX ethernet MAC address changing (link-local)

I am attempting to use the ethernet MAC address of CCGX to determine it's IP on a DHCP network. The CCGX is running firmware v2.53.


Our device is acting as the DHCP server in this case, and the MAC address we see in the arp table for the CCGX changes back and forth between two addresses. Sometimes the MAC appears correctly, with a prefix of 'c4:f3:12' which matches the value reported on the console display and by ifconfig on the CCGX for the eth0 interface. However, sometimes we are seeing what appears to be a random address (changing on reboot), for example with a prefix of '56:e8:21'.

This second value corresponds with the MAC shown on the link-local (ll-eth0) MAC address shown by ifconfig on the CCGX. Which looks like it was added as part of this issue: https://github.com/victronenergy/venus/issues/361

My guess as to why we're seeing the other MAC is that the CCGX is sending packets out over this link-local interface, even though it has a valid DHCP IP address. Do you have any suggestions? We would ideally like to see only the 'real' eth0 MAC address once it has a DHCP IP so we can easily identify it.
CCGX Color Controlethernet
2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

2 Answers
mvader (Victron Energy) avatar image
mvader (Victron Energy) answered ·

Hi Kenrick, we found an issue with arp, see here for the fix:


https://github.com/victronenergy/meta-victronenergy/commit/0b0880c8db77aa2ade4e49a501b473c0ad4bf877


(Note that link might disappear once we included in the master-branch of that repo. The commit is called sysctl-conf: set arp_ignore .


its scheduled to be included in v2.60.


all the best & thanks for helping to make a better product!

Matthijs

1 comment
2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Daniël Boekel (Victron Energy Staff) avatar image
Daniël Boekel (Victron Energy Staff) answered ·

Hi @Kenrick

Did you check if it does this also when using a 'normal' router that does DHCP?

1 comment
2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Hi Daniël,

We have now tested this with a two new devices (CCGX + client computer). Both devices were connected to a 'normal' office LAN which has a physical router acting as the DHCP server. We see similar behaviour. This new CCGX's mac changed between '3e:3e:bf' and '0c:b2:b7', where the first one is unknown and the second is a Texas Instruments MAC (a 'real' address).

Any other suggestions? It seems like something on the CCGX itself is causing this, because we have seen it on multiple CCGX devices but don't see it on most other network devices. If it helps here is some output that we see when we point arping at the CCGX (with the last few characters of the MAC addresses hidden):

~$ arping -I eth0 192.168.15.133
ARPING 192.168.15.133 from 192.168.15.98 eth0
Unicast reply from 192.168.15.133 [0C:B2:B7:XX:XX:XX]  1.113ms
Unicast reply from 192.168.15.133 [3E:3E:BF:XX:XX:XX]  1.406ms
Unicast reply from 192.168.15.133 [0C:B2:B7:XX:XX:XX]  165.599ms
Unicast reply from 192.168.15.133 [3E:3E:BF:XX:XX:XX]  167.127ms
Unicast reply from 192.168.15.133 [3E:3E:BF:XX:XX:XX]  1.007ms
Unicast reply from 192.168.15.133 [0C:B2:B7:XX:XX:XX]  850.505ms
Unicast reply from 192.168.15.133 [3E:3E:BF:XX:XX:XX]  850.952ms
Unicast reply from 192.168.15.133 [0C:B2:B7:XX:XX:XX]  953.276ms
Unicast reply from 192.168.15.133 [3E:3E:BF:XX:XX:XX]  953.696ms
Unicast reply from 192.168.15.133 [3E:3E:BF:XX:XX:XX]  1.140ms
Unicast reply from 192.168.15.133 [0C:B2:B7:XX:XX:XX]  779.928ms
Unicast reply from 192.168.15.133 [3E:3E:BF:XX:XX:XX]  780.454ms
Unicast reply from 192.168.15.133 [3E:3E:BF:XX:XX:XX]  1.677ms
Unicast reply from 192.168.15.133 [0C:B2:B7:XX:XX:XX]  155.854ms
Unicast reply from 192.168.15.133 [3E:3E:BF:XX:XX:XX]  157.078ms
Unicast reply from 192.168.15.133 [3E:3E:BF:XX:XX:XX]  1.609ms
^CSent 5 probes (1 broadcast(s))
Received 16 response(s)