Error : cannot connect the device via SSH

Error_cannot_connect · November 7, 2022, 11:25am

during the flashing of the Jetson AGX Xavier i am getting this error:
Error : cannot connect the device via SSH check the user name and password (both are correct) and make sure that SSH service is running on the device.

linuxdev · November 7, 2022, 4:29pm

Are you seeing this during flash? FYI, this command also requires the network route to be available. If one is depending on the USB virtual ethernet during a flash, then the host PC will try using address 192.168.55., but if using actual ethernet, then you’ll need to put in that address.

In the case of virtual ethernet sometimes the host PC requires the user to allow this connection.

Are you flashing? Or is this another time? On both host PC and Jetson what do you see from:

ip -s addr show
ip route show

Error_cannot_connect · November 8, 2022, 10:21am

i am flashing the jetson
On host PC

**ip -s addr show**

ip -s addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
RX: bytes packets errors dropped overrun mcast
366182 3752 0 0 0 0
TX: bytes packets errors dropped carrier collsns
366182 3752 0 0 0 0
2: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 54:ee:75:1a:2e:de brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
1793030 2965 0 8 0 0
TX: bytes packets errors dropped carrier collsns
509936 2392 0 0 0 0
3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether e8:2a:ea:d2:4d:df brd ff:ff:ff:ff:ff:ff
inet 192.168.10.74/24 brd 192.168.10.255 scope global dynamic noprefixroute wlp4s0
valid_lft 86039sec preferred_lft 86039sec
inet6 fe80::f57a:2209:12bc:5550/64 scope link noprefixroute
valid_lft forever preferred_lft forever
RX: bytes packets errors dropped overrun mcast
35531062 41659 0 16 0 0
TX: bytes packets errors dropped carrier collsns
1428025 10233 0 0 0 0
4: enxea1150cd693a: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether ea:11:50:cd:69:3a brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
11669 111 0 0 0 0
TX: bytes packets errors dropped carrier collsns
146086 904 0 0 0 0
5: usb1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether 22:dc:67:a5:70:eb brd ff:ff:ff:ff:ff:ff
inet 192.168.55.100/24 brd 192.168.55.255 scope global dynamic noprefixroute usb1
valid_lft 13sec preferred_lft 13sec
inet6 fe80::3bde:e1af:6905:83a/64 scope link noprefixroute
valid_lft forever preferred_lft forever
RX: bytes packets errors dropped overrun mcast
366596 2087 0 0 0 0
TX: bytes packets errors dropped carrier collsns
273347 973 0 0 0 0

**ip route show**

ip route show
default via 192.168.10.1 dev wlp4s0 proto dhcp metric 600
169.254.0.0/16 dev usb1 scope link metric 1000
192.168.10.0/24 dev wlp4s0 proto kernel scope link src 192.168.10.74 metric 600
192.168.55.0/24 dev usb1 proto kernel scope link src 192.168.55.100 metric 101

On Jetson

ip route show
default via 192.168.206.158 dev eth1 proto dhcp metric 100
default via 192.168.55.100 dev l4tbr0 metric 32766
169.254.0.0/16 dev l4tbr0 scope link metric 1000
192.168.55.0/24 dev l4tbr0 proto kernel scope link src 192.168.55.1
192.168.206.144/28 dev eth1 proto kernel scope link src 192.168.206.146 metric 100

ip -s addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
RX: bytes packets errors dropped overrun mcast
96925 1124 0 0 0 0
TX: bytes packets errors dropped carrier collsns
96925 1124 0 0 0 0
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 32:c2:2f:30:09:15 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 00:e0:4c:68:03:2f brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 48:b0:2d:4d:9c:05 brd ff:ff:ff:ff:ff:ff
inet 192.168.206.146/28 brd 192.168.206.159 scope global dynamic noprefixroute eth1
valid_lft 3266sec preferred_lft 3266sec
inet6 fe80::8da2:c01f:504c:4868/64 scope link noprefixroute
valid_lft forever preferred_lft forever
RX: bytes packets errors dropped overrun mcast
15218010 15946 0 4 0 0
TX: bytes packets errors dropped carrier collsns
1713937 11221 0 0 0 0
5: l4tbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ea:11:50:cd:69:39 brd ff:ff:ff:ff:ff:ff
inet 192.168.55.1/24 brd 192.168.55.255 scope global l4tbr0
valid_lft forever preferred_lft forever
inet6 fe80::1/128 scope link
valid_lft forever preferred_lft forever
inet6 fe80::e811:50ff:fecd:6939/64 scope link
valid_lft forever preferred_lft forever
RX: bytes packets errors dropped overrun mcast
898917 3073 0 0 0 1004
TX: bytes packets errors dropped carrier collsns
429637 2243 0 0 0 0
6: rndis0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master l4tbr0 state UP group default qlen 1000
link/ether ea:11:50:cd:69:39 brd ff:ff:ff:ff:ff:ff
inet6 fe80::e811:50ff:fecd:6939/64 scope link
valid_lft forever preferred_lft forever
RX: bytes packets errors dropped overrun mcast
723693 1943 0 0 0 0
TX: bytes packets errors dropped carrier collsns
776914 3422 0 0 0 0
7: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master l4tbr0 state UP group default qlen 1000
link/ether ea:11:50:cd:69:3b brd ff:ff:ff:ff:ff:ff
inet6 fe80::e811:50ff:fecd:693b/64 scope link
valid_lft forever preferred_lft forever
RX: bytes packets errors dropped overrun mcast
179557 1162 0 0 0 0
TX: bytes packets errors dropped carrier collsns
38964 208 0 0 0

linuxdev · November 8, 2022, 5:13pm

One suggestion is to use the “pencil” icon and edit your post. Then highlight output from the commands, and click on the “code” icon (looks like “</>”), then save. This will preserve formatting and add scroll bars to the output.

On the host PC I see it uses Wi-Fi (enp0s25 and enxea1150cd693a have no address and wlp4s0 uses 192.168.10.74/24). You are showing correctly the USB virtual connection as “usb1”, address 192.168.55.100.

The PC route does have a correct route to work with the virtual USB network. You should be able (as shown) to “ping 192.168.55.1” or “ping 192.168.55.100”. Can you verify ping? The .100 is the PC end of the virtual network, the .1 is the Jetson end.

On the Jetson’s network wired ethernet eth0 is not connected. However, there is a second wired network, eth1, which runs address “192.168.206.146” (with an unusual netmask of 28 bits or “/28”). Note that none of the routes on the PC coincide with this subnet. It is possible that the router would know to forward to this wired address (if they share routers or gateways), but the PC won’t be able to directly connect without a gateway’s help (router forwarding). Maybe the PC can ping this if the router helps. Can you verify if it is possible to “ping 192.168.206.146” from the PC? This is the Jetson being pinged over this wired network. It could serve as an alternate login.

The Jetson’s virtual network on usb0, via the l4tbr0, has address 192.168.55.1, so this should work. From the host PC can you “ping 192.168.55.1”? I asked above about ping of both this and 192.168.55.100. The “.100” would be the PC pinging itself, the “.1” would be the PC pinging the Jetson.

You have a more complicated network than average, but it should work unless there is a firewall blocking. The ping tests should answer that to some degree. Summary of tests from PC:

Can you “ping 192.168.55.1” (the Jetson from the PC via virtual ethernet)?
Can you “ping 192.168.55.100” (the PC from the PC via virtual ethernet)?
Can you “ping 192.168.206.146” (the wired ethernet from the PC to the Jetson)?
Are any of the involved routers with firewall or managed (which will have firewall-like functionality)?

Error_cannot_connect · November 9, 2022, 1:51pm

ping 192.168.55.146
PING 192.168.55.146 (192.168.55.146) 56(84) bytes of data.
From 192.168.55.100 icmp_seq=1 Destination Host Unreachable
From 192.168.55.100 icmp_seq=2 Destination Host Unreachable
From 192.168.55.100 icmp_seq=3 Destination Host Unreachable
From 192.168.55.100 icmp_seq=4 Destination Host Unreachable
From 192.168.55.100 icmp_seq=5 Destination Host Unreachable
From 192.168.55.100 icmp_seq=8 Destination Host Unreachable
From 192.168.55.100 icmp_seq=9 Destination Host Unreachable
^C
--- 192.168.55.146 ping statistics ---
10 packets transmitted, 0 received, +7 errors, 100% packet loss, time 9193ms
pipe 4

 ping 192.168.55.100
PING 192.168.55.100 (192.168.55.100) 56(84) bytes of data.
64 bytes from 192.168.55.100: icmp_seq=1 ttl=64 time=0.040 ms
64 bytes from 192.168.55.100: icmp_seq=2 ttl=64 time=0.040 ms
64 bytes from 192.168.55.100: icmp_seq=3 ttl=64 time=0.049 ms
64 bytes from 192.168.55.100: icmp_seq=4 ttl=64 time=0.058 ms
64 bytes from 192.168.55.100: icmp_seq=5 ttl=64 time=0.027 ms
64 bytes from 192.168.55.100: icmp_seq=6 ttl=64 time=0.055 ms
64 bytes from 192.168.55.100: icmp_seq=7 ttl=64 time=0.051 ms
^C
--- 192.168.55.100 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6140ms
rtt min/avg/max/mdev = 0.027/0.045/0.058/0.009 ms

$ ping 192.168.55.1
PING 192.168.55.1 (192.168.55.1) 56(84) bytes of data.
64 bytes from 192.168.55.1: icmp_seq=1 ttl=64 time=0.089 ms
64 bytes from 192.168.55.1: icmp_seq=2 ttl=64 time=0.165 ms
64 bytes from 192.168.55.1: icmp_seq=3 ttl=64 time=0.101 ms
64 bytes from 192.168.55.1: icmp_seq=4 ttl=64 time=0.206 ms
64 bytes from 192.168.55.1: icmp_seq=5 ttl=64 time=0.136 ms
64 bytes from 192.168.55.1: icmp_seq=6 ttl=64 time=0.200 ms
64 bytes from 192.168.55.1: icmp_seq=7 ttl=64 time=0.124 ms
^C
--- 192.168.55.1 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6151ms
rtt min/avg/max/mdev = 0.089/0.145/0.206/0.042 ms

there is no firewall
there are no routers involved

linuxdev · November 9, 2022, 6:42pm

Ping works in all cases, and so you should be able to ssh to any of those addresses (the first time you ssh to an account at an address though it’ll ask you if it is ok to do so). Ping does use a different protocol (ICMP) than ssh (TCP/IP), but since you don’t have any special networking that won’t matter.

One thing which might matter is if the ssh daemon is running. If you are physically sitting at the Jetson (local login by normal means or via serial console), can you “ssh name@localhost”? This is just ssh from the Jetson to itself. We know networking is ok, and if you can ssh locally, then we know the daemon is running.

system · November 23, 2022, 6:42pm

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