I have flashed the board many times and always encounter the same problem.
TX2 cannot connect the internet with ethernet, but it can work with wifi.
I’m sure that the ip address is correct, because I can ping TX2 from host computer.
This problem makes the installation easily failed, so I come here for help.
I have tried JetPack 3.2, 3.1 and 3.0.
Try JetPack3.2.1 instead of 3.2…there may be some issues with 3.2 since it was deprecated in favor of 3.2.1 (don’t know if the repository.json download has been fixed yet or not).
Normally only wired ethernet is supported between Jetson and host. Typically only wired can be set up automatically after a flash. The mechanism for the freshly flash Jetson reporting its IP only works for one boot, then you have to manually enter an IP after that (such as if you ran JetPack only to add extra packages).
On your host what do you see from these commands:
route
ifconfig
traceroute <whatever the IP address is of the Jetson>
On your host can you “ssh nvidia@”? Sometimes if you’ve used ssh before and in some way the keys change, then ssh itself might reject a login thinking it is a “man in the middle” attack. At other times, when WiFi and NetworkManger get their fingers into the pie, the route might be incorrect.
chinessgo55,
Please describe more about your problem. Could you ssh to your device?
Hi, linuxdev
I successfully use ssh nvidia@Jetson IP to enter TX2 board, but it has error when I use “apt-get update”. The error is “Temporary failure resolving ‘ports.ubuntu.com’” and “W: Failed to fetch http://ports.ubuntu.com/ubunut-ports/dists/xenial/InRelease”.
The failed update can be done, if I use through wifi.
By the way, I use JetPack 3.2.1 instead of 3.2, sorry for the mistake.
Hi, WayneWWW
As I reply to linuxdev, I got error when I use “apt-get update” through ethernet, but it can be done by wifi.
The error is “Temporary failure resolving ‘ports.ubuntu.com’” and “W: Failed to fetch http://ports.ubuntu.com/ubunut-ports/dists/xenial/InRelease”.
Also, I cannot go to any website with ethernet but wifi.
“Temporary failure resolving ‘ports.ubuntu.com’” tends to imply DNS setup is an issue (though it could be an actual failure of the ubuntu.com server…not likely).
When I run the command “host ports.ubuntu.com” the IPv4 address I see is:
91.189.88.150
On your Jetson try both of these…if the named address fails but the dotted-decimal address works, then DNS setup is your issue:
ping 91.189.88.150
ping ports.ubuntu.com
Try ping with both ethernet and with WiFi up/down. NetworkManager tends to mess things up because of bad assumptions about what should be set up with/without WiFi. Do report this information for the configuration which fails:
route
ifconfig
Hi, linuxdev
The instruction “ping 91.189.88.150” and “ping ports.ubuntu.com” cannot connect through ethernet whether WiFi is up or down.
When I type “route”, the information is below:
"
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 140.118.206.254 0.0.0.0 UG 100 0 0 eth0
140.118.206.0 * 255.255.255.0 U 100 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 l4tbr0
172.17.0.0 * 255.255.0.0 U 0 0 0 docker0
192.168.55.0 * 255.255.255.0 U 0 0 0 l4tbr0
".
It seems normal as I type the same instruction on host computer.
Here is the information of “ifconfig”:
"
docker0 Link encap:Ethernet HWaddr 02:42:2a:28:99:3e
inet addr:172.17.0.1 Bcast:0.0.0.0 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr 00:04:4b:a5:67:38
inet addr:Here is TX2’s Ip Bcast:140.118.206.255 Mask:255.255.255.0
inet6 addr: fe80::b0aa:1bc9:8311:3b28/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8018885 errors:0 dropped:203303 overruns:0 frame:0
TX packets:90140 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1696388123 (1.6 GB) TX bytes:39421302 (39.4 MB)
Interrupt:42
l4tbr0 Link encap:Ethernet HWaddr 32:92:24:d4:02:f9
inet addr:192.168.55.1 Bcast:192.168.55.255 Mask:255.255.255.0
inet6 addr: fe80::9c8c:8ff:fe5d:7e03/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:21353 errors:0 dropped:0 overruns:0 frame:0
TX packets:177 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3872253 (3.8 MB) TX bytes:18863 (18.8 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:13827 errors:0 dropped:0 overruns:0 frame:0
TX packets:13827 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:1061194 (1.0 MB) TX bytes:1061194 (1.0 MB)
usb0 Link encap:Ethernet HWaddr 32:92:24:d4:02:f9
inet6 addr: fe80::3092:24ff:fed4:2f9/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:10653 errors:10653 dropped:0 overruns:0 frame:10653
TX packets:8948 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1929865 (1.9 MB) TX bytes:1831046 (1.8 MB)
usb1 Link encap:Ethernet HWaddr fa:94:f0:81:8e:3d
inet6 addr: fe80::f894:f0ff:fe81:8e3d/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:10700 errors:0 dropped:0 overruns:0 frame:0
TX packets:8901 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1942388 (1.9 MB) TX bytes:1424405 (1.4 MB)
"
Some of the networking in China differs, I’m not sure whether this is related or not. My DNS would refer me to servers near me, yours probably wants a different server. How this relates I’m not sure, but keep in mind there may be issues with the ISP or DNS even if you do everything correctly.
eth0 is wired, and I see this as a problem:
RX packets:8018885 errors:0 <i><b>dropped:203303</b></i>
Default route is through “140.118.206.254”, which is the wired ethernet. An enormous number of packets are simply being dropped, but some do work. I’m thinking this may be some sort of firewall or router issue since not all packets are dropped.
I do not see WiFi in the ifconfig, so it is hard to say anything about it. If you run the command “host ports.ubuntu.com” does it give you any address at all? I don’t know what popular servers are available where you are at, but if “host” works with any of those it means DNS is up (e.g., here I might do “host nvidia.com” or “host google.com” since I know they are always up)…and if it then fails with “host ports.ubuntu.com”, then it is somewhere in your internet outside of the Jetson which is failing.
I have encounted with this same problem. And I solved it by changing the ip address which assigned by tx2 by default. Because the ip address has conflicted with other computer. The default ip address is 192.168.1.67, and I change it to 192.168.1.11 which has not occupied by others.