win10 PC,ping 192.168.1.1
You are connecting the TX2 ethernet port directly to the Windows PC’s ethernet port?
Yes
Could you use TX2 and NX to validate?
I mean connect tx2 eth port to nx eth port.
I connect nx eth port， network is ok. but TX2 eth0 donot work.
Even 2x tx2 or 1x tx2 + 1x nx cannot have any ethernet working?
If so, I can only suggest you to find one and move to devkit.
I not has TX2 devkit，it try other methods
I don’t know if it is relevant or not, but I see in one screenshot that link negotiation is “ignore”. If the link is only compatible with link negotiation, then this might cause a problem. In the case of the Jetson and PC talking to a switch instead of direct wiring I’d say odds of success without link negotiation goes up.
I will add that when you set an address by “sudo ifconfig eth0 192.168.1.171”, and then ping, you should run “ifconfig” again (without any argument, this is to examine stats and not to change anything) to see statistics. Also run the command “route” on the Jetson to see routing information.
Also note that the other side of the ping might be be blocked by firewall. If a network switch is used, and if that switch is “managed”, then that too might need to be configured to allow ping (I mention this because you said it is a “company” server, and perhaps it uses a higher end managed switch which includes security).
It try other methods，but eth0 has no IP.
route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.5.5.0 0.0.0.0 255.255.255.224 U 0 0 0 wlan0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
That route does not have a default. However, the combination of netmask and IP address says this would work for “ping 192.168.1.1” since no default route is involved. The information still missing is that after you have run ping 192.168.1.1 for a short time, what shows up from “ifconfig” after the ping? The act of sending or receiving data will change the statistics shown in “ifconfig”, so we need to see statistics with data having been run (this “ifconfig” should be run on the Jetson).
Dear linuxdev,
In the case of the same network cable, eth0 can not work and no ip address， but eth1 do work and ping www.baidu.com.
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 48:b0:2d:3b:5d:ec txqueuelen 1000 (Ethernet)
RX packets 3124 bytes 265434 (265.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 162 bytes 29034 (29.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 37
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.108 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::392c:959e:df8b:21ba prefixlen 64 scopeid 0x20<link>
ether 08:62:66:b6:28:eb txqueuelen 1000 (Ethernet)
RX packets 59 bytes 8869 (8.8 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 67 bytes 7505 (7.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
What interface is eth1?
eht0 is Gigabit Ethernet(GEthernet，1000Mb/s internet interface)， can not work.
eth1 is fei Ethernet（100Mb/s internet interface），do work.
Hi,
We have nothing to share here. If you don’t have devkit to test, then we cannot help.
Testing things on devkit is necessary for debug in this forum.
Hi，
I donot has TX2 NX devkit，TX2 NX devkit support Gigabit Ethernet(GEthernet)？
Hi,
Yes, TX2 NX devkit supports Gigabit Ethernet. We have TX2 NX working with ethernet everyday…
It is just some basic debug logic. If the ethernet can work fine on devkit, it means this is hardware design issue on your custom board.
Hi，
ok.
if My custom board + Xavier_NX or NANO ，Gigabit Ethernet can work. but TX2 can not work，Is it different？
Thanks
Still suggest to move to devkit to test. NX and Nano result may not represent anything for TX2NX.
ok，
I donot has TX2 NX devkit，Can I try the Xavier NX devkit board？