Activating on Linux without eth0

조회 수: 23(최근 30일)
Daniel Shub
Daniel Shub 2013년 4월 29일
편집: Scott 2016년 6월 6일
I have an activation question. I have asked technical support, but I thought I would ask here. I thought this would be desirable both in terms of speed for me and potentially to share the issue for others ...
I run Arch Linux. Arch Linux has switched to the new standard of Consistent Network Device Naming where network devices are no longer named eth0, eth1, wlan0, wlan1. Both 1-661QJD and 1-EUTG50 are relevant and highlight the problem. For activation on Linux, TMW requires the legacy eth0 naming convention.
For Red Hat, TMW suggests removing the package that implements consistent network device naming. This is not an option on Arch. does anyone know a work around? Does anyone know a work around that does not require disabling consistent network device naming? I thought it used to be possible to activate with the UUID of a harddisk...
  댓글 수: 5
Walter Roberson
Walter Roberson 2013년 4월 29일
Hmmm, apparently device files for ethernet have changed considerably ... I cannot find any on my OS-X system! I guess it must be using system calls to find the ethernet table. If something similar is what is happening on your system, then creating a new file might not help at all :(

댓글을 달려면 로그인하십시오.

채택된 답변

Daniel Shub
Daniel Shub 2013년 4월 29일
편집: Scott 2016년 6월 6일
I asked a related question over at Unix and Linux.SE. Basically, for Linux the dummy kernel module will create a dummy network interface that you can then set the mac address of
modprobe dummy
ip l set dev dummy0 name eth0
ip link set dev eth0 address xx:xx:xx:xx:xx:xx
where xx:xx:xx:xx:xx:xx is the registered mac address/host id of the machine. I don't think that this violates the license agreement, although it is best to check.
I don't know the best way to make this persistent across reboots, but it shouldn't be too hard.
It might also be possible to simply rename one of the consistently named devices to eth0. This would eliminate the need for the dummy device and I believe the naming would still be consistent since you are always renaming the same device.
I have also been told that a udev rule can be used to revert back to ethX type naming. For machines that only have eth0 and/or wlan0 there is no advantage of consistent device naming since there is only one device. This means the udev rule does not hurt anything.
  댓글 수: 1
Scott 2016년 6월 6일
편집: Scott 2016년 6월 6일
Hi Daniel,
I am glad to hear you got MATLAB up and running on Arch using the instructions from Unix & Linux Stack Exchange. Just so you know, R2014a added support for Consistent Network Device Naming so these steps shouldn't be necessary for R2014a and later releases.
If you are unable to activate MATLAB normally using R2014a or later please contact us so we can look into this further:
MathWorks Installation & Licensing Support

댓글을 달려면 로그인하십시오.

추가 답변(1개)

A 2013년 9월 7일
편집: A 2013년 9월 7일
I run Gentoo linux, and consistent NIC naming has been introduced since udev v197 I think. So activation was an issue for me as I had no eth0 device on my system.
My work-around was to create a udev rule to force the name eth0.
I have the following in /etc/udev/rules.d/70-use-eth0-for-matlab-licensing.rules (one line):
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="your:mac:address:here", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth?", NAME="eth0"
You can find the mac address of your device by running 'ifconfig -a'. Keep it in lower-case. I used my ethernet NIC's mac, as I hardly use it, so I'm hoping this won't have unintended consequences for the rest of my system.
You'll need to keep this work-around for as long as you use matlab (not just for activation), as the licensing info is verified at launch, so it needs to find eth0 every time.
You may have to update a /etc/init.d/net.* link and /etc/conf.d/net to use the new name.

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by