Ethernet MAC Corruption on MTCDT-LAT1-247L

[joe@jtdc.ca]

Has anyone experienced a situation where the Ethernet MAC becomes corrupted? I noticed this recently on my MTCDT-LAT1-247L. The Ethernet MAC is 00:80:00:10:00:00 which is not what it’s supposed to be per the sticker. Most likely, this occurred several years ago when my gateway was upgraded from the AEP 1.x firmware.

Not a huge problem usually but Orbiwise forwarder seems to construct the Gateway EUI from the the Ethernet MAC address rather than use the actual Gateway EUI.
Obviously, the NS can be configured to accept the fake Ethernet MAC address-based EUI but seems wrong.

I’m guessing this is stored on in the EEPROM somewhere. Is there a way to re-write it?

[Jeff Hatch]

Hello Joe,

First, can you confirm that the EEPROM has the incorrect value? Is the 00:80:00:10:00:00 the address reported in the /var/log/messages when the device is booted? There are log messages from the mts-io kernel module that report the EEPROM contents.

Thank You,

Jeff

[joe@jtdc.ca]

option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[INFO] mts-io:mts_id_eeprom_load:635: Platform EEPROM contents loaded
[INFO] mts-io:mts_id_eeprom_load:756: Adding WiFi/BT to mts-io driver
[INFO] mts-io:mts_id_eeprom_load:761: Adding GPS to mts-io driver
[INFO] mts-io:mts_id_eeprom_load:773: detected board MTCDT-0.1
[INFO] mts-io:mts_id_eeprom_load:844: sizeof: 512
[INFO] mts-io:mts_id_eeprom_load:845: vendor-id: Multi-Tech Systems
[INFO] mts-io:mts_id_eeprom_load:846: product-id: MTCDT-LAT1-247L
[INFO] mts-io:mts_id_eeprom_load:847: device-id: 12345678
[INFO] mts-io:mts_id_eeprom_load:848: hw-version: MTCDT-0.1
[INFO] mts-io:mts_id_eeprom_load:855: mac-addr: 00:08:00:10:00:00
[INFO] mts-io:mts_id_eeprom_load:857: imei: 123456789123456789
[INFO] mts-io:mts_id_eeprom_load:858: capa-gps: yes
[INFO] mts-io:mts_id_eeprom_load:859: capa-din: no
[INFO] mts-io:mts_id_eeprom_load:860: capa-dout: no
[INFO] mts-io:mts_id_eeprom_load:861: capa-adc: no
[INFO] mts-io:mts_id_eeprom_load:862: capa-wifi: yes
[INFO] mts-io:mts_id_eeprom_load:863: capa-bluetooth: yes
[INFO] mts-io:mts_id_eeprom_load:864: capa-lora: no
[INFO] mts-io:mts_id_eeprom_load:865: capa-battery: no
[INFO] mts-io:mts_id_eeprom_load:874: mac-bluetooth: 00:00:00:00:00:00
[INFO] mts-io:mts_id_eeprom_load:883: mac-wifi: 00:00:00:00:00:00
[INFO] mts-io:mts_id_eeprom_load:890: uuid: AAA00000000000000000000000000021
option 1-2.3:1.4: device disconnected

[joe@jtdc.ca]

Hmmm… seems like there are a few parameters that may have been corrupted.

[Jeff Hatch]

Hello Joe,

The device-id, imei, mac-addr, and uuid do not look correct. The mac-bluetooth and mac-wifi are not set for some reason even though the capa values for those are set to “yes”. Do you know where this device came from? This looks like someone set dummy values for some reason. Without the device-id it is going to be hard to figure out where this device came from.

Jeff

[joe@jtdc.ca]

I bought it from Arrow on January 20, 2019.
If by device-id, you mean the serial number then that’s on the sticker along with every other identifier except for the Bluetooth MAC address.

Serial #:19755128
NODE ID: 00:80:00:4A:58:B4 (This is probably the real Ethernet MAC)
NODE LORA: 00:80:00:00:A0:00:2E:1E (LoRa Gateway EUI)
WiFi NODE ID: 00:23:A7:Da:81:4C (Guessing this is the Wi-Fi MAC)
IMEI: 358942053808482
UUID: 314d4732-c0cb-0a07-1226-7d575dc1683a

[Jeff Hatch]

Hello Joe,

Updating the EEPROM will require opening the chassis/case to put a jumper on the MTCDT board. Unfortunately, I think that would void the warranty. I suggest that you contact Multitech support at https://support.multitech.com. I can’t promise anything, but they may be able to do an exchange or something.

Someone definitely reprogrammed those fields in the EEPROM. The numbers in the device-id and IMEI would not end up that way due to corruption.

Jeff

[Author]

Posts