Using l4tbr0 ethernet

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
1

Hello

I want to use Ethernet through the l4tbr0(Micro usb) interface without using an ethernet cable . Is there any way?

HOST PC : UBUNTU 18.04
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:08:04:2a:df txqueuelen 0 (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

enp0s20f0u2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 42:36:81:66:9f:d9 txqueuelen 1000 (Ethernet)
RX packets 87 bytes 9446 (9.4 KB)
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

enp0s20f0u2i5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.55.100 netmask 255.255.255.0 broadcast 192.168.55.255
ether 2a:69:33:4f:4e:4e txqueuelen 1000 (Ethernet)
RX packets 1826 bytes 456537 (456.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1949 bytes 182228 (182.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.196 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::f7e8:eb85:2d6a:273b prefixlen 64 scopeid 0x20
ether d4:5d:64:b7:b4:0c txqueuelen 1000 (Ethernet)
RX packets 222451 bytes 286842579 (286.8 MB)
RX errors 0 dropped 733 overruns 0 frame 0
TX packets 56553 bytes 8304276 (8.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xa4100000-a41fffff

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 11317 bytes 1081827 (1.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 11317 bytes 1081827 (1.0 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Xavier NX
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:93:89:64:52 txqueuelen 0 (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 48:b0:2d:07:67:a5 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 36

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::2869:33ff:fe4f:4e4d prefixlen 64 scopeid 0x20
inet6 fe80::1 prefixlen 128 scopeid 0x20
ether 2a:69:33:4f:4e:4d txqueuelen 1000 (Ethernet)
RX packets 2716 bytes 237185 (237.1 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2339 bytes 511837 (511.8 KB)
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
loop txqueuelen 1 (Local Loopback)
RX packets 467 bytes 34778 (34.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 467 bytes 34778 (34.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

rndis0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::2869:33ff:fe4f:4e4d prefixlen 64 scopeid 0x20
ether 2a:69:33:4f:4e:4d txqueuelen 1000 (Ethernet)
RX packets 53 bytes 9401 (9.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 423 bytes 63349 (63.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::2869:33ff:fe4f:4e4f prefixlen 64 scopeid 0x20
ether 2a:69:33:4f:4e:4f txqueuelen 1000 (Ethernet)
RX packets 2663 bytes 227784 (227.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1671 bytes 604860 (604.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

3

The device mode micro-OTG USB connector makes this available by default. If you use a micro-B USB cable at the Jetson, and then the type-A connector on the host, then the host should see this and configure with DHCP. The Jetson side has address 192.168.55.1, and the host has address 192.168.55.100. If this does not occur, then it is usually because the host has security requiring you to ok this. Sometimes though it is due to using a cheap charger cable (about 2 out of 3 charger cables have such extraordinarily low quality data design that they fail; typically it is two strands of 32 or 34 gauge copper).

5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.