Hi all,
We have a Jetson Orin dev kit running Ubuntu 22.04 here. The Jetpack version should be R36 according to the output from $ cat /etc/nv_tegra_release. We are having some problems with the ethernet port (which I assume is the eth0 in ifconfig).
The problem might be the same as this post, where the wifi works but the cabled connection fails, but it is not clear to me how they solved their problem. Our Orin was flashed by the SDK manager.
For our ethernet port, there is no flashing light when we plug in a cable, and it shows cable unplugged in Orin. And not suprisingly we cannot ping any addresses that supposed to be connected to the port.
The output of $ ifconfig -a is in the attachment.
Jetson_Orin_eth0.txt (3.2 KB)
Please let us know if you need further information. Thanks for the help!
J
I see eth0 is listed, so the port is actually functional. What I don’t see is (A) an assigned address, nor do I see (B) bytes of traffic. This means there was no router DHCP activity, and it isn’t directly the port which failed.
Incidentally, I don’t see any bytes of traffic on any interface except for loopback (loopback would always have traffic) and the wireless, but apparently there are also some USB network devices.
Is there anything special about your router? For example, company routers are often secured and won’t provide a DHCP address to MAC addresses it doesn’t know about, although typically you would see some bytes of traffic.
Is your wired ethernet going to a switch, and then the switch to the router? A description of the wiring might help, along with whether or not you might have tried to configure a static address or made other network configuration changes.
Right now we know the driver has loaded, and the network interface is available for traffic, so finding out why the other end did not respond is the next step.
Thanks for your reply. Here are some more details.
The Orin was connected to a KUKA robot controller (basically a static IP address). My ubuntu laptop can ping the KUKA robot controller via the same cable (if I set the correct IP address on my laptop).
Could you please let us know if there are any differences on setting up the ethernet connection between a common ubuntu computer and Jetson? (or what is the proper way to setup a static IP address for Jetson Orin)
Thanks a lot!
Whatever your method of static assignment, that assignment is now gone. It isn’t a case of wired ethernet not working, it is a case of either (A) using a router with DHCP, or else (B) manually setting that static address again. This is entirely a network setup issue and won’t differ between desktop Linux, Windows, or Jetsons.
I can say that your system never tried a DHCP request from any router. There were no bytes sent or received. This means that past configuration changes are causing the ethernet to not attempt automatic assignment.
If you connected the correct USB port from Jetson to a Linux host PC, then that USB will cause the Jetson itself to appear as a router. If the PC accepts this as a router (security might not allow it), then there would be an automatic DHCP assignment by the virtual router on the Jetson such that the host PC has address 192.168.55.100, and the Jetson would have address 192.168.55.1. The host could then ping or communicate with 192.168.55.1. The Jetson could ping or communicate (depending on security) with the host PC at 192.168.55.100. This is 100% over the virtual wired ethernet of USB though, and does not touch the regular ethernet port. However, if you used one of those addresses, and it worked, you can conclude it was due to USB and not wired ethernet.
What IP address did you use? Is there a router involved currently for the wired ethernet? If there is, then you can set it to use DHCP. If not, then you can set a static address, but you need to set it to a subnet of what the host PC ethernet works with. This assumes the host PC’s ethernet is static assignment. If the host PC is itself getting its address via DHCP, then you need to let the same router assign for the Jetson (and skip static assignment as it would probably conflict with the router’s address assignment).