Hi, everyone. I have several xaviers and have flashed three xaviers with jetpack successfully, but there is something wrong with one xavier while installing CUDA on target using jetpack.
Jetpack installer on the host reports:
Err: http://ports.ubuntu.com/ubuntu-ports bionic InRelease
Cannot initialte the connection to ports.ubuntu.com:80 (2001:67c:1360:8001::22)
- connect (101: Network is unreachable) Could not connect to ports.ubuntu.com:80 (91.189.88.150), connection timed out.
My network is fine both on host and xavier:
ping ports.ubuntu.com
PING ports.ubuntu.com (91.189.88.150) 56(84) bytes of data.
64 bytes from astomi.canonical.com (91.189.88.150): icmp_seq=1 ttl=49 time=227 ms
64 bytes from astomi.canonical.com (91.189.88.150): icmp_seq=2 ttl=49 time=227 ms
64 bytes from astomi.canonical.com (91.189.88.150): icmp_seq=3 ttl=49 time=227 ms
64 bytes from astomi.canonical.com (91.189.88.150): icmp_seq=4 ttl=49 time=227 ms
64 bytes from astomi.canonical.com (91.189.88.150): icmp_seq=5 ttl=49 time=227 ms
64 bytes from astomi.canonical.com (91.189.88.150): icmp_seq=6 ttl=49 time=228 ms
64 bytes from astomi.canonical.com (91.189.88.150): icmp_seq=7 ttl=49 time=227 ms
64 bytes from astomi.canonical.com (91.189.88.150): icmp_seq=8 ttl=49 time=227 ms
64 bytes from astomi.canonical.com (91.189.88.150): icmp_seq=9 ttl=49 time=227 ms
64 bytes from astomi.canonical.com (91.189.88.150): icmp_seq=10 ttl=49 time=227 ms
64 bytes from astomi.canonical.com (91.189.88.150): icmp_seq=11 ttl=49 time=227 ms
64 bytes from astomi.canonical.com (91.189.88.150): icmp_seq=12 ttl=49 time=227 ms
And ‘apt-get update’ doesn’t work on xavier as following:
nvidia@jetson-0423718017049:~$ sudo apt-get update
[sudo] password for nvidia:
Err:1 http://ports.ubuntu.com/ubuntu-ports bionic InRelease
Cannot initiate the connection to ports.ubuntu.com:80 (2001:67c:1360:8001::22). - connect (101: Network is unreachable) Could not connect to ports.ubuntu.com:80 (91.189.88.150), connection timed out
Err:2 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease
Cannot initiate the connection to ports.ubuntu.com:80 (2001:67c:1360:8001::22). - connect (101: Network is unreachable)
Err:3 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease
Cannot initiate the connection to ports.ubuntu.com:80 (2001:67c:1360:8001::22). - connect (101: Network is unreachable)
Err:4 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease
Cannot initiate the connection to ports.ubuntu.com:80 (2001:67c:1360:8001::22). - connect (101: Network is unreachable)
Reading package lists... Done
W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic/InRelease Cannot initiate the connection to ports.ubuntu.com:80 (2001:67c:1360:8001::22). - connect (101: Network is unreachable) Could not connect to ports.ubuntu.com:80 (91.189.88.150), connection timed out
W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-updates/InRelease Cannot initiate the connection to ports.ubuntu.com:80 (2001:67c:1360:8001::22). - connect (101: Network is unreachable)
W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-backports/InRelease Cannot initiate the connection to ports.ubuntu.com:80 (2001:67c:1360:8001::22). - connect (101: Network is unreachable)
W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-security/InRelease Cannot initiate the connection to ports.ubuntu.com:80 (2001:67c:1360:8001::22). - connect (101: Network is unreachable)
W: Some index files failed to download. They have been ignored, or old ones used instead.
If “Network is unreachable”, then perhaps there is another firewall or proxy. Some parts of the world may also block this content.
Are you using wired or WiFi? If wired, then it becomes much easier to figure out. Generally speaking though, can you ping the outside world, e.g., “ping google.com”?
I am using a wired network, and i also question the firewall or proxy, but the same network and Jetpack installer worked on the other xaviers and “apt-get update” succeeded on the host when it failed on my “problem” xavier.
You have two gateway routes through wired eth0…other than metric they are the same:
default _gateway 0.0.0.0 UG 0 0 0 eth0
default _gateway 0.0.0.0 UG 20100 0 0 eth0
I don’t know what will happen with this…perhaps nothing will happen…but it is quite odd. How this would happen I don’t know.
I don’t see the full addresses, I assume you just masked those, which should be ok (if this is the literal output though, then there is a problem).
I also see DNS works:
ports.ubuntu.com has address 91.189.88.150
Since 91.189.88.150 is not in the 172.30.**.0/255.255.255.0 subnet it does mean that the gateway must provide the final connection. What is your gateway? Is this from a router appliance?
For particular testing, does this work?
ping 91.189.88.150
If not, then where does it fail? Keep in mind that ping and traceroute are ICMP and not all gateways will support ICMP, so some hops might not show results, but see if there is an obvious cut off point…I am thinking it will be your router. Use this command to find out:
The problem disappeared this morning, “apt-get update” worked fine and Jetpack installer succeeded to install CUDA on the “problem” xavier.
It seems a problem with the route table which is automatically generated by the system or our network. There were two default gateway routes yesterday, but one default gateway route today.
Whenever dns is changed, it takes a while for dns servers across the internet to sync up. Some ISPs are horrendous at this. If you use google dns on your router, or cloudflare, you will never run into this problem.
