How do I setup the included 1G ethernet interface box with a static IP address?
I have the interface box connected via this port as shown in the hardware quick start guide
how do I go about setting this up?
Dear @rforsberg ,
Did you connect this port to LAN cable? Do you mean which mgbe interface is used? Can you see IP from ifconfig to see which interface got IP?
See if https://developer.nvidia.com/docs/drive/drive-os/7.0.3/public/drive-os-linux-sdk/getting-started/Host_TargetSetupandConfiguration1.html#configuring-static-ip-to-the-device helps?
Hi yes, I cannot tell which interface is used. Plugging and unplugging the network cable does not give any interface in ifconfig an IP address, the output of ifconfig is always the same (even when unplugging the 1G interface box completely):
oxts@tegra-ubuntu:~$ ifconfig
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:92:ff:e2:3b 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
enx803f5d09ebc6: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 80:3f:5d:09:eb:c6 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
enxe8ea6ab0789b: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.25.45 netmask 255.255.255.0 broadcast 192.168.25.255
inet6 fe80::eaea:6aff:feb0:789b prefixlen 64 scopeid 0x20<link>
ether e8:ea:6a:b0:78:9b txqueuelen 1000 (Ethernet)
RX packets 63629338 bytes 7205709126 (7.2 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7675 bytes 406804 (406.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eqos_0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1466
inet6 fe80::7643:7cdb:8e62:8c70 prefixlen 64 scopeid 0x20<link>
ether 4c:bb:47:5c:88:d3 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1321 bytes 350674 (350.6 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<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 125 bytes 9848 (9.8 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 125 bytes 9848 (9.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
mgbe0_0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1466
ether 4c:bb:47:5c:88:d4 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
mgbe1_0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1466
inet6 fe80::65e9:3b47:b8eb:8ad0 prefixlen 64 scopeid 0x20<link>
ether 4c:bb:47:5c:88:d5 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1015358 bytes 76290579 (76.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
mgbe1_0.200: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1466
inet6 fe80::4ebb:47ff:fe5c:88d5 prefixlen 64 scopeid 0x20<link>
ether 4c:bb:47:5c:88:d5 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 48 bytes 4594 (4.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
mgbe2_0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1466
inet6 fe80::cd47:227c:30ff:dc54 prefixlen 64 scopeid 0x20<link>
ether 4c:bb:47:5c:88:d6 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1015313 bytes 76286967 (76.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
mgbe3_0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1466
inet6 fe80::e523:dcab:efb3:9944 prefixlen 64 scopeid 0x20<link>
ether 4c:bb:47:5c:88:d7 txqueuelen 1000 (Ethernet)
RX packets 1811 bytes 83356 (83.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 137215 bytes 10383721 (10.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
mgbe3_0.200: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1466
inet 10.42.0.28 netmask 255.255.255.0 broadcast 10.42.0.255
inet6 fe80::4ebb:47ff:fe5c:88d7 prefixlen 64 scopeid 0x20<link>
ether 4c:bb:47:5c:88:d7 txqueuelen 1000 (Ethernet)
RX packets 1811 bytes 76112 (76.1 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 64304 bytes 3954534 (3.9 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enxe8ea6ab0789b is my USB dongle and that has been set with a static IP and allows me to ssh.
I have attempted to add a static IP address to each of the interfaces (eqos_0, mgbe0_0, mgbe1_0, mgbe2_0 and mgbe3_0) - using the template netplan file in the link you provided as a starting point - in turn to see if any would respond to having a static IP set, none of them allow me to ping anything else on my network or the internet
Dear @rforsberg ,
Could you check my private message and update your observations.
Dear @rforsberg ,
Could you reset the network file changes and share bootlog(tegra serial console log after restarting) connection pictures. Please share the LED light condition on NIC adapter . Please check Chapter 5 in DRIVE AGX Thor product brief for details.
ok I have disabled every netplan configuration file I have and rebooted
Here are some photos of the connections:
The blue ethernet cable goes into a switch that is connected to my network and pc etc
The USB-C power is coming from my ubuntu host PC
The H-MTD connector with the red arrow is the one that is connected to the 1G interface box as mentioned in the DM (the 6 pin is not connected to anything, it is left over from when I switched to the 4 pin after the DM)
The Lights on the interface box :
The light on the top left of the rj45 is rapidly blinking yellow and the light on the top right is blinking green at a slower rate, I am not certain by the table if the green is meant to be solid or not. The white LED under the USB-C port is solid on.
The switch that the device is connected to is only a 100Mbit switch so yellow would be expected.
here is the serial boot log:
thor_console_log.txt (73.5 KB)
Dear @rforsberg ,
I would expect mgbe3 interface to get IP fromDHCP by default as per the connection.
I tried below config in our network to assign IP using netplan via serial connection and notice IP is detected. Please check the settings on linux machine first before trying on DRIVE platform. You may seek guidance on any linux platform about issue with netplan.
mgbe3_0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1466
inet 10.0.0.10 netmask 255.255.252.0 broadcast 10.0.3.255
inet6 fe80::3e6d:66ff:fe28:b92d prefixlen 64 scopeid 0x20<link>
ether 3c:6d:66:28:b9:2d txqueuelen 1000 (Ethernet)
RX packets 6 bytes 326 (326.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 384 bytes 36209 (36.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
config file
network:
version: 2
renderer: networkd
ethernets:
mgbe3_0: # Use your interface name
dhcp4: no
dhcp6: no
addresses:
- 10.0.0.10/22 # Your IP address
routes:
- to: default
via: 10.0.0.1 # Your gateway
nameservers:
search: [nvidia.com, client.nvidia.com, nvclient.nvidia.com] #Your corp domain names
addresses: [ DNS IPs]
that has given the interface an IP address, but I cannot ping it from my network unless my USB dongle is also plugged in at the same time (from my linux host pc or a windows pc on the same network)
below screenshots are with the USB dongle unplugged:
Hi @rforsberg
We had the same trouble, getting the network running and assigning a static IP.
For us the only Connection that worked was the Eth 1 connector as shown in your image.
This mapped to mgbe2_0:
mgbe2_0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1466
inet 192.168.178.5 netmask 255.255.255.0 broadcast 192.168.178.255
inet6 fe80::4ebb:47ff:fe5c:7586 prefixlen 64 scopeid 0x20<link>
ether 4c:bb:47:5c:75:86 txqueuelen 1000 (Ethernet)
RX packets 7230 bytes 586525 (586.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1173824 bytes 104443441 (104.4 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
This is our netplan config:
network:
version: 2
renderer: networkd
ethernets:
mgbe2_0:
dhcp4: no
addresses:
- 192.168.178.5/24
gateway4: 192.168.178.1
nameservers:
addresses:
- 8.8.8.8
- 8.8.4.4
Hope that helps
Hi @andreas.westhues this setup has successfully worked and I’m now able to connect via the 1G interface box
Thank you both @SivaRamaKrishnaNV and @andreas.westhues for your help
Thanks @andreas.westhues for your sharing