usrp-users@lists.ettus.com
Discussion and technical support related to USRP, UHD, RFNoC
View all threadsNon-Unique Device MAC Address's After Mender F.S. Update
Hi,
We had a need for a multiple device - single subnet setup. After updating multiple E320’s to a newer UHD version, me and my colleague, we realized that all of the devices share a common MAC address. This results in unstable connections within the network. As for in this thread is there a non-third party, Ettus supported, homegrown way of restoring/updating the MAC address of a network device, specifically E320?
Thanks.
On 11/03/2024 11:42, edenmclaughlin123@gmail.com wrote:
Hi,
We had a need for a multiple device - single subnet setup. After
updating multiple E320’s to a newer UHD version, me and my colleague,
we realized that all of the devices share a common MAC address. This
results in unstable connections within the network. As for in this
thread
https://lists.ettus.com/empathy/thread/POYUYNB4RH5MFPADPFYTSLLKVAWT64M6?hash=POYUYNB4RH5MFPADPFYTSLLKVAWT64M6#POYUYNB4RH5MFPADPFYTSLLKVAWT64M6
is there a non-third party, Ettus supported, homegrown way of
restoring/updating the MAC address of a network device, specifically E320?
Thanks.
Trying to attract R&D's attention on this. I know we went through this
with E310 years and years ago, but it was resolved.
The MAC address should come from the EEPROM. You can run eeprom-dump on the
device to see what MAC addresses are programmed in it. You can use
eeprom-init to program the EEPROM. Run either with --help to see the syntax.
https://github.com/EttusResearch/uhd/blob/master/mpm/tools/README.md
I'm curious if your devices somehow have the same MAC in the EEPROM or if
it's reverting to some default because it can't read the EEPROM, or the
EEPROM isn't properly programmed.
Wade
On Mon, Mar 11, 2024 at 12:01 PM Marcus D. Leech patchvonbraun@gmail.com
wrote:
On 11/03/2024 11:42, edenmclaughlin123@gmail.com wrote:
Hi,
We had a need for a multiple device - single subnet setup. After updating
multiple E320’s to a newer UHD version, me and my colleague, we realized
that all of the devices share a common MAC address. This results in
unstable connections within the network. As for in this thread
https://lists.ettus.com/empathy/thread/POYUYNB4RH5MFPADPFYTSLLKVAWT64M6?hash=POYUYNB4RH5MFPADPFYTSLLKVAWT64M6#POYUYNB4RH5MFPADPFYTSLLKVAWT64M6
is there a non-third party, Ettus supported, homegrown way of
restoring/updating the MAC address of a network device, specifically E320?
Thanks.
Trying to attract R&D's attention on this. I know we went through this
with E310 years and years ago, but it was resolved.
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com
On 3/12/24 22:22, Wade Fife wrote:
The MAC address should come from the EEPROM. You can run eeprom-dump on
the device to see what MAC addresses are programmed in it. You can use
eeprom-init to program the EEPROM. Run either with --help to see the syntax.
https://github.com/EttusResearch/uhd/blob/master/mpm/tools/README.md
https://github.com/EttusResearch/uhd/blob/master/mpm/tools/README.md
I'm curious if your devices somehow have the same MAC in the EEPROM or
if it's reverting to some default because it can't read the EEPROM, or
the EEPROM isn't properly programmed.
Yeah, bad night and I am bored:
This is ancient, but I am wondering if it got lost for the mender builds.
Philip
Wade
On Mon, Mar 11, 2024 at 12:01 PM Marcus D. Leech
<patchvonbraun@gmail.com mailto:patchvonbraun@gmail.com> wrote:
__
On 11/03/2024 11:42, edenmclaughlin123@gmail.com
<mailto:edenmclaughlin123@gmail.com> wrote:
Hi, We had a need for a multiple device - single subnet setup. After updating multiple E320’s to a newer UHD version, me and my colleague, we realized that all of the devices share a common MAC address. This results in unstable connections within the network. As for in this thread <https://lists.ettus.com/empathy/thread/POYUYNB4RH5MFPADPFYTSLLKVAWT64M6?hash=POYUYNB4RH5MFPADPFYTSLLKVAWT64M6#POYUYNB4RH5MFPADPFYTSLLKVAWT64M6> is there a non-third party, Ettus supported, homegrown way of restoring/updating the MAC address of a network device, specifically E320? Thanks.
Trying to attract R&D's attention on this. I know we went through
this with E310 years and years ago, but it was resolved.
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com>
To unsubscribe send an email to usrp-users-leave@lists.ettus.com
<mailto:usrp-users-leave@lists.ettus.com>
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com
Hi,
On 2024-03-11 15:42 +0000, edenmclaughlin123@gmail.com wrote:
We had a need for a multiple device - single subnet setup. After
updating multiple E320’s to a newer UHD version, me and my colleague,
we realized that all of the devices share a common MAC address. This
results in unstable connections within the network. As for in this
thread is there a non-third party, Ettus
supported, homegrown way of restoring/updating the MAC address of a
network device, specifically E320?
It seems that network is managed by systemd-networkd.
So, I guess in the meantime,
you could change networkd configurations to assign a different MAC address.
From [1], the configuration should be in /data/network/.
You could modify the file handling that network interface
(i.e. if the interface is eth0, then the file should have 'Name=eth0'),
by adding:
[Link]
MACAddress=<uniqueMACAddress>
I guess that if the file does not exist,
copy pasting the one from [1] should be fine (?)
Or you could add/modify a <name>.link with a correct [Match] and a
[Link]
MACAddressPolicy=<persistent|random>
and let systemd-networkd generate a MAC address.
Relevant documentations:
https://man.archlinux.org/man/systemd.network.5.en
https://man.archlinux.org/man/systemd.link.5.en
https://wiki.archlinux.org/title/Systemd-networkd
[1] https://files.ettus.com/manual/page_usrp_e3xx.html#e3xx_getting_started_connectivity
Best regards
Cédric Hannotier