![]() ![]() Process: 4571 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)ġ0월 26 17:40:13 kobuksun systemd: Reloading OpenBSD Secure Shell server.ġ0월 26 17:40:13 kobuksun sshd: Received SIGHUP restarting.ġ0월 26 17:40:13 kobuksun systemd: Reloaded OpenBSD Secure Shell server.ġ0월 26 17:40:13 kobuksun sshd: Server listening on 0.0.0.0 port 22.ġ0월 26 17:40:13 kobuksun sshd: Server listening on :: port 22.ġ0월 26 17:40:14 kobuksun sshd: Received SIGHUP restarting.ġ0월 26 17:40:14 kobuksun systemd: Reloaded OpenBSD Secure Shell server.ġ0월 26 17:40:14 kobuksun sshd: Server listening on 0.0.0.0 port 22.ġ0월 26 17:40:14 kobuksun sshd: Server listening on :: port 22. Process: 6304 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 6309 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCES Process: 1430 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1434 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCES Loaded: loaded (/lib/systemd/system/ssh.service enabled vendor preset: enabĪctive: active (running) since Fri 07:08:49 KST 8h left ssh.service - OpenBSD Secure Shell server. ![]() TX errors 0 dropped 0 overruns 0 carrier 0 collisions routeĭestination Gateway Genmask Flags Metric Ref Use Ifaceĭefault _gateway 0.0.0.0 UG 100 0 0 enp3s0ġ17.17.251.0 0.0.0.0 255.255.255.0 U 100 0 0 enp3s0 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 It might indicate a forwarding issue or a simple “forwarding works, but ssh is not reacting” ifconfig If it turns out that your forwarding is correct, then it implies sshd is not running or configured to not accept incoming connections if it turns out that forwarding is wrong, then the ssh connection is failing because it isn’t the computer you expected to be the host.įor one thing, try a traceroute to the host from the Jetson, and try a traceroute from the Jetson to the PC. A connection timeout indicates that there was a route to host, and the network was not rejected, but the host did not provide a service on that port (or the service is denied). The sshd daemon might also be set to not accept certain connections. Keep in mind that the ufw might control not only forwarding, but also the particular port (port 22 TCP). Many PC Linux installations default to this. Perhaps your PC is not set to allow outside ssh access. But reversely i can’t access to my desktop (ubuntu18.04) on my jetson nano both of them don’t work well saying “connection timeout”
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |