It turns out that I had the wrong Ethernet connection set up on my laptop.
To fix the problem, I enabled Internet Connection Sharing over my laptop’s Ethernet connection. Under Ubuntu (on the laptop, not the Jetson) you would go to the IPv4 section of your connection properties and set the type to “Shared to other computers.”
Once you install JetPack release with SDKMagager, it’ll also store the image to your local host, then you could perform script file to flash the board again.
you may also check the documentation, Flashing and Booting the Target Device for reference.
Is there any other solution except re-flashing the Jetson Nano?
I encounter the same problem and in case I need to reflash it, it will through away weeks of works I’ve done on the device so far (plenty of complex installations).
Adding to my previous comment (failing to connect to Jetson with SSH due to timeout):
In order to fine tune where the problem comes from I used Wireshark on the client’s computer and ‘tcpdump’ on the Jetson.
The conclusion was that the client get to the server but the server doesn’t answer.
The following thread helped to understand that the problem probably comes from the firewall: https://unix.stackexchange.com/questions/207141/ssh-server-not-answering-connection-requests
So I tried another thing that worked:
Login to the Jetson
Install ‘ufw’ and ‘sshserver’:
sudo apt-get install ufw openssh-server
Add ‘ssh-server’ to the allow list:
sudo ufw allow openssh
Disable the firewall by running:
sudo ufw disable
sudo ufw enable
Make sure that ufw is up with the updated configuration
ssh: connect to host 192.168.65.73 port 22: Connection refused
I have tried many things including the suggestions and experiences in this topic with no avail.
Note that: There is another thing I noticed with my nano. When I am using “Chrome web browser”, most of the time it stuck and and nothing return from web. This issue can be an indication of a faulty hardware or something relevant?!?!
The file was not there. But, normally, if I am not mistaken, it should have been automatically created when it’s been used for the first time.
Anyway, I played around and now we have the “known_hosts” file. But, the problem persists.
I have maybe 10 times re-flashed the image and started over.
Those same strange issues every time;
The “nano ~/.bashrc” returned “bash: nano: command not found”. (during some Computer Vision related installations)
Unstable internet connection, one minute works and another minute unresponsive although it shows connected.
Perhaps it is the time to suspect from the image and/or hardware!?!?!
You are correct. This indicates nobody has successfully run ssh to that account. Also, if permissions in that directory are incorrect, then ssh will be refused. Are other files present? If so, what is the output from “ls -l ~/.ssh/*”?
If you do not have “nano”, then command would not be found. Try “sudo apt-get install nano”.
From login to the local host as that account (I will assume you are logged in locally to “sener”), can you do this:
If this fails, then what do you see from the verbose version? I’ll add some logging:
ssh -vvv sener@localhost 2>&1 | tee log.txt
If you hover your mouse over the quote icon in the upper right of one of your existing posts, then a paper clip icon will show up. You can use this to attach “log.txt”.
you were right about “sudo apt install nano”. Once I run that “nano ~/.bashrc” , it took me to the edit screen this time. A progress!
And I have only Ethernet connection. I have already tried two different places where a working PC connected to it. But, it was still unstable connection.
I am wondering, since I didn’t know if I have to install nano as you suggested what if there will be maybe more to install.
On the other hand, what is the benefit of having ready to use image file from Nvidia if there are even some elementary setup missing in the OS ?!
I want to verify one detail first: This log was from the Jetson using ssh to itself (which is what I’m going by).
I see this part of the log showing success by password:
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
debug3: send packet: type 50
debug2: we sent a password packet, wait for reply
debug3: receive packet: type 52
debug1: Authentication succeeded (password).
Authenticated to localhost ([127.0.0.1]:22).
So we know that when no outside network is involved that your Nano correctly accepts logins by password. The Nano itself is working.
I am unsure how to debug ssh from Windows, but if you use an application such as PuTTY, are you able to get a verbose log of some sort? Or can you check if ssh from another PC running Linux is possible? If you can try login from another Linux PC, and if that login fails, then the same verbose ssh log from that PC remote connecting to the Nano would help.
One detail which may or may not be related is that I noticed some IPv6 addressing in there. It is possible there may be configuration issues related IPv6 support. IPv4 is always supported, but there may be cases when IPv6 may need additional configuration. If you are able to ssh from a Linux PC, then be sure to include the “ifconfig” from that PC to see if it uses IPv4 or IPv6.
The windows subsystem for linux works is probably easiest. Same commands. Openssh can also be installed or you can use a virtual machine.
Fwiw ssh works out of the box, which isn’t even the case for vanilla ubuntu because it’s disabled by default. For better or worse, on Nano, by default, sshd accepts password authentication on all interfaces at port 22 with no restrictions I’m aware of.
I’m unsure of why it’s not working for you, but I don’t believe the software to be the issue here. The problem is likely configuration or your network (or possibly hardware). If you’ve ruled out configuration by flashing a new image, it should work. I can confirm ssh works with the latest image for me.
Can you run these three commands on your nano and post the output?
When you first boot after installing the Nano’s software you have to set up a user name and password. There is no default. You’d use whatever you created on that first boot setup. If you did not set that up, then there won’t be anyone you can log in as.