Ethernet do not work on TX2

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

Dear community，

Ethernet do not work on TX2.
BSP version:r 32.5.1

Is there a solution，Thanks.

~$ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 48:b0:2d:3b:5e:04  txqueuelen 1000  (Ethernet)
        RX packets 5169  bytes 846249 (846.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 181  bytes 32606 (32.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 37

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 1  (Local Loopback)
        RX packets 953  bytes 60249 (60.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 953  bytes 60249 (60.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

rndis0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether ae:30:b6:1d:0f:75  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 ae:30:b6:1d:0f:77  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

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.5.5.1  netmask 255.255.255.224  broadcast 10.5.5.31
        ether c8:02:8f:a3:d1:52  txqueuelen 1000  (Ethernet)
        RX packets 4964  bytes 640103 (640.1 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1704  bytes 224741 (224.7 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wwan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::5c35:43ff:fee5:47a8  prefixlen 64  scopeid 0x20<link>
        ether 5e:35:43:e5:47:a8  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 28  bytes 3062 (3.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
~$ ping www.baidu.com
ping: www.baidu.com: Name or service not know
2

Ethernet interface is up but looks like no IP assigned.

How is your network environment?

3

network environment is good, Tried on other devices work ok .

4

Ah… I didn’t mean something bad or good. I mean does it connect to a router or something else?

Any dmesg to share here? Do you have other jetson devices to validate?

5

Network environment is good.I try NANO ,network is good and ping www.baidu.com.

IMG_5748.HEIC
IMG_5748.HEIC1920×2560 685 KB

dmesg.log (116.0 KB)

6

Is it possible to move your test to TX2 devkit instead of your custom board?

7

I donot has TX2 devkit.

8

Ok then could you run below command and see if any new log coming out to dmesg and syslog?

sudo dhclient eth0

9

Ethernet code donot modify,I try NANO or NX Xavier eth0 do work.

10

Do you have other TX2 to validate?

11

other TX2 eht0 no ip.

12

$ sudo dhclient eth0

No result, stuck here

13

Please connect TX2 directly to a PC and assign the IP manually to each side and see if you can ping each other with this setup.

14

It looks like ipv6

~$ ping 192.168.1.86
connect: Network is unreachable

~$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::95b4:5a12:a1d3:b540  prefixlen 64  scopeid 0x20<link>
        ether 48:b0:2d:3b:5e:04  txqueuelen 1000  (Ethernet)
        RX packets 2138  bytes 168203 (168.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 156  bytes 27293 (27.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 3
15

If the jetson nano and NX you just validated are with IPv4, then it is not related to the IPv6.

Do you also get failure if you manually assign a IP to it?

16

According to the data the network is operating correctly, but DHCP was never attempted…thus the ethernet never asked for an address. If the router requires any kind of security, e.g., only allowing devices with a known MAC address, then the router would never assign an address when asked. Just to emphasize though, the log looks like the interface never asked for any address.

You might want to include the output of “ifconfig” and “route” from both the Jetson and the PC you are working with. Also, describe any switch and router connection between the Jetson and PC.

Note: You can use “nm-connection-editor” to assign an address for testing, or to switch to DHCP. If you don’t have “nm-connection-editor”, then “sudo apt-get install network-manager-gnome”. There are also other standard tools for doing this, but I personally prefer nm-connection-editor.

17

I manually assign a IP to it：
$ sudo ifconfig eth0 192.168.1.171

$ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.1.171 netmask 255.255.255.0 broadcast 192.168.1.255
ether 48:b0:2d:3b:5e:04 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
device interrupt 37

$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.171 icmp_seq=1 Destination Host Unreachable
From 192.168.1.171 icmp_seq=2 Destination Host Unreachable
From 192.168.1.171 icmp_seq=3 Destination Host Unreachable
^C
— 192.168.1.1 ping statistics —
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4073ms

18

IMG_5751.HEIC
IMG_5751.HEIC1920×1440 527 KB

IMG_5750.HEIC
IMG_5750.HEIC1920×1440 403 KB

I try it，but eth0 donot have ip.

19

Host side is 192.168.1.1?

20

yes,Our company server address.