How to set manual IP address on the TX2

Hi All,

I’d like to know How to set manual IP address on the TX2.

Current status of TX2 network is DHCP.

I have set to /etc/network/interfaces. but, this set is failed.

Could you let me know yours info?

Thanks & BR,

Here’s what I’ve done on the TK1 (should be the same as TX2 unless NetworkManager sticks its fingers in when WiFi changes…this is for wired):
This is my “/etc/network/interfaces” file (the “source” of an entire directory seems to fail…assumes udev doesn’t name this something other than eth0):

# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
source interfaces.d/eth0

This is my “/etc/network/interfaces.d/eth0” file (adjust for your IP addresses, netmask, and gateway):

auto eth0
iface eth0 inet static

Note that my host is on the same subnet and has the “.2” address. My host is set up to allow this and to forward.

I haven’t either tried this on TX2, but on a host with Ubuntu16-04, I had to add some settings in dhcpcd.conf. That would depend on your network.
On L4T, I just see /etc/dhcp/dhclient.conf. If the config as advised by @linuxdev doesn’t work, you may have a look at it (check for ‘fixed-address’).

Incidentally, I do have my host set up as a DHCP server and it supplies exactly one fixed address for each of many devices (versus picking from a pool). However, I have had occasions when I needed the device to have an address to talk to other devices even when my host was not on…which is when I added static address without DHCP for those cases.


Thank you for your support.

I think that it is need netmask, network, broadcast, dns-nameservers for connect to external network.

Also, I think this set is caused with ntp date. Because, ntp date was not sync.

Is it right?

Thanks & BR,

Typically DNS must work for NTP to work…I suppose it is possible to configure NTP with a dotted-decimal format and get around that. In the past I’ve had time not set up correctly when DNS was not being forwarded by my host (this can be the case regardless of using static or DHCP addresses…but DHCP does automate parts of this).

If this is the case, and if your Jetson is not set up to do this correctly, then you can do this to manually get around the issue…but don’t do it unless you have to because it has some holes in it and can fail. Copy the “/etc/resolv.conf” file from your host which acts as a router to the “/etc/resolv.conf” on your Jetson which is failing DNS (verify works/fails with something like “host” to see if it finds a dotted-decimal address). You might save a copy of your Jetson’s previous “/etc/resolv.conf” before doing this…and examine it to see if it is basically empty. Also be sure your host acting as a router is set up to forward DNS.

FYI, the “/etc/resolv.conf” tends to get overwritten each boot. You could temporarily add an alternate name to the file used for your workaround and put a command to copy the file over to resolv.conf name in “/etc/rc.local”.