Jetson Nano Micro USB pip internet connection

I have my jetson nano running with edimax wifi

When I have it connected to a screen then it runs fine.
When I run it with a microusb to ssh in from my ubuntu 18.04 desktop, it seems pip3 can’t get to the internet?

I am guessing pip3 is trying to reach the internet via the micro-usb connection to my desktop rather than the edimax and hence fails.

How can I change this behaviour?

I ran route and it gave me:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default _gateway 0.0.0.0 UG 20600 0 0 wlan0
default _gateway 0.0.0.0 UG 32766 0 0 l4tbr0
link-local 0.0.0.0 255.255.0.0 U 1000 0 0 l4tbr0
192.168.1.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0
192.168.55.0 0.0.0.0 255.255.255.0 U 0 0 0 l4tbr0

what should I do to make sure all services route through wlan0 the wifi adapter rather than l4tbr0 to connection that I am using to ssh in.

Not sure why there is something like pip3 error. pip3 sounds like python package installer to me and should have nothing to do with wifi.

It looks like the ip address are duplicated here.
What is your interface IP of wlan0? Could you share the ifconfig -a? Also, what are the exact peripheral IO when you see the error?

When I run it with a microusb to ssh in from my ubuntu 18.04 desktop

What is “it” in this description? The jetson Nano? If you unplug the micro usb cable, should it go to wlan0?

this is my ifconfig -a

dummy0: flags=130<BROADCAST,NOARP>  mtu 1500
        ether a6:9b:55:7c:93:45  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

eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:e0:4c:68:04:db  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 148  base 0xe000  

l4tbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.55.1  netmask 255.255.255.0  broadcast 192.168.55.255
        inet6 fe80::1  prefixlen 128  scopeid 0x20<link>
        inet6 fe80::a092:3ff:fed8:3510  prefixlen 64  scopeid 0x20<link>
        ether 4e:17:de:ae:70:49  txqueuelen 1000  (Ethernet)
        RX packets 49048  bytes 8307142 (8.3 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 23238  bytes 4914533 (4.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

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 3004  bytes 265965 (265.9 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3004  bytes 265965 (265.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

rndis0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::4c17:deff:feae:7049  prefixlen 64  scopeid 0x20<link>
        ether 4e:17:de:ae:70:49  txqueuelen 1000  (Ethernet)
        RX packets 34057  bytes 5682200 (5.6 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 38276  bytes 9762913 (9.7 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::4c17:deff:feae:704b  prefixlen 64  scopeid 0x20<link>
        ether 4e:17:de:ae:70:4b  txqueuelen 1000  (Ethernet)
        RX packets 14991  bytes 2624942 (2.6 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 13275  bytes 1805803 (1.8 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.60  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::111c:b87d:3d46:7be1  prefixlen 64  scopeid 0x20<link>
        ether 74:da:38:f2:b0:2c  txqueuelen 1000  (Ethernet)
        RX packets 191429  bytes 118711199 (118.7 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 30635  bytes 2913441 (2.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

when I powered off of the Microusb and controlled the nano with keyboard / mouse / HDMI cable it worked fine.
After I switched to using the barrel jack for power and connected the microusb from my desktop to the nano it started having these networking issues.

ok I went through and toggled the “only use this connection for local resources” setting:

sudo nmcli connection modify l4tbr0 ipv4.never-default true

and

sudo nmcli connection modify l4tbr0 ipv6.never-default true

and that seemed to do the trick

bpl.law,

Yes, this method is kind of disabling the internet through micro usb port.
We don’t have such issue report before. Could you help confirm if my understand is correct or not:

  1. You have a edimax wifi connected, what is the interface here?
  2. l4tbr0 exists and seems affect the edimax wifi. Do you connect a micro usb cable between nano and your host?
  3. Would edimax wifi get worked if you unplug the cable in (2)?

Actually I think your method is basically same as removing the micro usb cable here.

the "never-default" option: you can prevent connections (and thus
their interface when that connection is active) from ever getting the
default route by setting this option.

The only purpose for l4tbr0 is to create a interface between host and device.

  1. wlan0
  2. yes
  3. yes