Unable to SSH via direct ethernet into Jetson AGX Xavier


I have two devices: the Jetson AGX Xavier, and a laptop running Debian. I am attempting to establish an SSH connection between the two devices using a direction ethernet connection.

Currently, the laptop has a connection to Wi-Fi, and there is a direct ethernet link from the laptop to the Jetson.

I have the same issue and error messages as this poster: Unable to SSH into Jetson Nano through Ethernet

However, their solution of turning on Internet Connection Sharing did not work for me, and the same errors persist.

Thanks in advance for any help.

Did you set a static IP for you Xavier?
Setting static IP for your Xavier and laptop Ethernet interface in a same subnet (such as 192.168.0.x) should work for your case.

1 Like

What is the exact error message if you try to connect? You can log this on command line, for example:
ssh theaddress 2>&1 | tee log_ssh.txt
(this won’t record hidden keystrokes like passwords, but you can examine the log file anyway)

Hi yingliu,

I tried this, and after typing

ssh jetson@

I get the error

ssh: connect to host port 22: Connection timed out

I am new to networking, so I will show you in the following screenshots how I set static IPs. Let me know if it’s wrong.

The first image is on the laptop, and the second image is on the Jetson.

Hi linuxdev,

The following shows exactly the error and commands I have been using

$ ssh jetson@xx:xx:xx:xx:xx:xx

ssh: Could not resolve hostname xx:xx:xx:xx:xx:xx: Name or service not known

After trying yingliu’s suggestion, the following is the result:

$ ssh jetson@

ssh: connect to host port 22: Connection timed out


For manual set up, it seems like gateway is missing. Please try Automatic(HDCP) and see if you can get valid IP address.

May be Openssh server is not installed or not running.
To verify really Openssh server is installed and running, please try “ssh jetson@localhost” on the jetson terminal and let us know if its successful.

Was “xx:xx:xx:xx:xx:xx” a numeric address? What I’m seeing is a DNS issue, not an ssh issue. The host does not know what the “xx:xx:xx:xx:xx:xx” is, which implies it is a named address. Systems on your local network which are behind the same router would normally need a dotted-decimal format to find each other. Connection timed out might be related, or it might be a lack of the service (but usually not from DNS issues…the timing out is usually something different).

Can you “ping”? Incidentally, in one screenshot, it shows", which is different. From both Jetson and host you should be able to ping that address successfully; assuming the Jetson is really (adjust if it is not), then try pinging that address from both Jetson and host PC. Even Windows should be able to do that on command line. If one computer is the “.1” address, and the other is a “.2” address, then ping both from both and see what happens (each should ping itself, and each should ping the other).

Incidentally, if you manually assign an IP address and have a router, and not a switch, this is likely a problem. The router could behave badly (perhaps by intent of design) when seeing traffic to/from an address it did not assign.

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