Please provide the following info (tick the boxes after creating this topic):
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
Target Operating System
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
SDK Manager Version
Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
I had been trying to ssh but it gives the response connection refused.
devgan@ES:/$ ssh email@example.com
ssh: connect to host 192.168.10.186 port 22: Connection refused
sshd_config (3.2 KB)
Orincmd.txt (5.1 KB)
Kindly find the sshd_config file and target system terminal logs attached.
Please check that the SSH service is running on the target machine by running the command “systemctl status sshd” on the target machine.
yes, it is active (running).
kindly find the response of command “systemctl status sshd” attached :
op.txt (922 Bytes)
You can check that the target machine is reachable from your machine. You can do this by running the command “ping 192.168.10.186” on your machine.
I tried to do that, i am getting destination port unreachable.
PING 192.168.10.186 (192.168.10.186) 56(84) bytes of data.
From 192.168.9.1 icmp_seq=1 Destination Port Unreachable
From 192.168.9.1 icmp_seq=2 Destination Port Unreachable
So i even tried to ping to 192.168.9.1 and i received the same response Destination Port Unreachable.
the response of traceroute 192.168.10.186 :
traceroute -n 192.168.10.186
traceroute to 192.168.10.186 (192.168.10.186), 30 hops max, 60 byte packets
1 192.168.9.1 1.025 ms 1.328 ms 1.385 ms
2 192.168.9.1 1.913 ms 1.958 ms 2.332 ms
Does reflashing help with this issue?
It seems like there might be an issue with the network connection or configuration. You could try resetting the network settings or check if the IP address of the device you’re trying to connect to is correct. If the issue persists, you may want to reach out to your network administrator or IT support for further assistance.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.