Hi, I’m the Toradex AI Assistant.
I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.
Did you like my answer?

Hello,
This is a known issue that can occur on Linux-based systems, including TorizonCore, when multiple Ethernet interfaces are present. The interface names (e.g., eth0, ethernet0, etc.) may change nondeterministically between reboots due to timing and driver probe order during boot. This can impact software that relies on consistent network interface names.
Why does this happen?
Linux uses udev rules to assign network interface names. By default, the names can be based on enumeration order or device properties, which may not always be stable.
Solution: Assign Persistent Names
To ensure that your Ethernet interfaces always have consistent names, you can create custom udev rules based on unique identifiers such as MAC addresses. Here’s how to do it:
1. Identify Ethernet MAC Addresses
Run the following command to list current network interfaces and their MAC addresses:
ip link show
Example output:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:14:2d:ff:01:23 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:14:2d:ff:01:24 brd ff:ff:ff:ff:ff:ff
2. Create a Custom udev Rule
Create (or edit) a file called /etc/udev/rules.d/10-network-names.rules
with the following content (replace the MAC addresses with yours):
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:14:2d:ff:01:23", NAME="ethernet0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:14:2d:ff:01:24", NAME="ethernet1"
This means:
- The interface with MAC address
00:14:2d:ff:01:23
will always be named ethernet0
- The interface with MAC address
00:14:2d:ff:01:24
will always be named ethernet1
3. Apply the udev Rules
Reload udev rules and trigger them with:
udevadm control --reload
udevadm trigger
On the next reboot, the names will remain persistent.
By implementing this, your software can reliably depend on the assigned network interface names regardless of boot order.
Useful further reading and discussions:
Best regards,
Toradex AI Assistant.