At Jetson Orin Nano, Hardware ID changes every time it reboots. It invalidates a license.
Answered
Hello support,
I have a Jetson Orin Nano 4GB device. I installed Nx Witness and a license. It ran everything OK. I rebooted the device and found the license was gone.
I noticed that hardware ID changed every time it rebooted. This is a capture of hardware ID. The first is the hardware ID when I first booted the device. The second one is when I rebooted. The last one is when I rebooted again. They are all different.
In
/opt/networkoptix/mediaserver/etc/mediaserver.conf, I changed from 'useEmbeddedLinuxHardwareId=true' field to 'useEmbeddedLinuxHardwareId='. After the changing of the field, the hardware ID was changed at the very next reboot. But it did not change any more, no matter how many I rebooted the device. This solved but I doubt I could use this workaround.
This is the inetface list of another device with the same Orin Nano one.
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:4a:72:e0:4f txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.9 netmask 255.255.0.0 broadcast 192.168.255.255
ether 48:b0:2d:d9:4c:b4 txqueuelen 1000 (Ethernet)
RX packets 6386192 bytes 1936447093 (1.9 GB)
RX errors 0 dropped 484478 overruns 0 frame 0
TX packets 5502 bytes 565571 (565.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lan1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 48:b0:2d:d9:4c:b5 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 348856 bytes 54163007 (54.1 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 348856 bytes 54163007 (54.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
rndis0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether ea:57:19:9b:86:89 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
usb0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether ea:57:19:9b:86:8b txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Thanks.
-
Hello Jason,
Long time not seen. :)
Thanks for reporting the issue.
This solved but I doubt I could use this workaround.
Could you please give more details what restricts you of using the solution you've found?
0 -
Hi Andrey,
I hope you are well. ;)
I have not tested whether the mediaserver.conf is intact or not when Nx Witness is uninstalled or is upgraded by in-client update. What is your policy? Do you keep it or rewrite all of files?
If some of key files were kept, I think we can use the workaround. Otherwise, we have to tell customers instructions.
Cheers.
0 -
Following for same issue.
0
Please sign in to leave a comment.
Comments
3 comments