When I ran jetpack, I set it to use the USB network option (“Connect to Jetson device via USB cable”). The jetpack process completed smoothly.
My problem began when I restarted the Xavier (normal shutdown/restart in Linux). At that point the network bridge between the Xavier and the internet was lost. The network between the Xavier and PC was still there–no access to the internet. Which makes me think it’s a routing issue.
This is made worse by the behavior when the USB cable is unplugged. Each time that occurs the host PC picks up a new IP address. I was up to 192.168.55.120 at one point.
We actually had NVIDIA on-site yesterday and I brought this up with them. The network bridge device on the Xavier needs to be setup again. I was unable to figure out how to do this by hand. I ended up re-flashing my board and running jetpack again. The bridge setup commands are visible in the text window during the software load process–there’s a route default command and several nmcli commands. I was unable to capture those from the text window. Is that text logged anywhere?
I’ve just now restarted my Xavier for the first time (since re-flashing with Jetpack yesterday). I have two l4tbr0 devices listed in the “Network Connections” gui. One has the gateway listed at 192.168.55.100 with proper DNS server addresses, and one has the gateway and DNS server fields blank. However, ifconfig on my host PC says that the network addresses are 192.168.55.102 and 192.168.55.103. So, I’m back into the busted configuration. (I didn’t unplug the USB cable, so the IP address change occurred due to the Xavier restart.)
It looks to me that there are two factors here:
- the host PC address isn’t stable. The l4tbr0 bridge assumes the gateway address is 192.168.55.100 and that’s not always true.
- why do I have two l4tbr0 devices after restart? The new blank one isn’t doing any good and the other has stale IP address info.