Problem when Build and Install into target

Legato Application Framework
41

then what is ens33?
It seems it is blocking the ssh or ping to the module IP 192.168.2.2

From your previous screenshot, it is also having IP 192.168.2.3:

42

Maybe before i misconfigured something, but now i have defined the correct interface of the module.
Can ping but still cannot ssh into the module.

(lsh:wp76stable) ntram@ubuntu:~/space$ ping 192.168.2.2 -I ens35u1i19
PING 192.168.2.2 (192.168.2.2) from 192.168.2.3 ens35u1i19: 56(84) bytes of data.
64 bytes from 192.168.2.2: icmp_seq=1 ttl=64 time=196 ms
64 bytes from 192.168.2.2: icmp_seq=2 ttl=64 time=4.32 ms
64 bytes from 192.168.2.2: icmp_seq=3 ttl=64 time=1.68 ms
64 bytes from 192.168.2.2: icmp_seq=4 ttl=64 time=4.76 ms
64 bytes from 192.168.2.2: icmp_seq=5 ttl=64 time=2.10 ms
64 bytes from 192.168.2.2: icmp_seq=6 ttl=64 time=2.63 ms
^C
--- 192.168.2.2 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5011ms
rtt min/avg/max/mdev = 1.682/35.344/196.552/72.103 ms
(lsh:wp76stable) ntram@ubuntu:~/space$ ssh root@192.168.2.2
ssh: connect to host 192.168.2.2 port 22: Connection refused
(lsh:wp76stable) ntram@ubuntu:~/space$ ssh root@192.168.2.2
ssh: connect to host 192.168.2.2 port 22: Connection refused
(lsh:wp76stable) ntram@ubuntu:~/space$
43

if you type “ping 192.168.2.2” (without specifying the network interface), is it successful?

can you capture wireshark log in your PC to see if the module responds to the SSH connection

44

You can see:

(lsh:wp76stable) ntram@ubuntu:~/space$ ping 192.168.2.2
PING 192.168.2.2 (192.168.2.2) 56(84) bytes of data.
64 bytes from 192.168.2.2: icmp_seq=1 ttl=64 time=4.08 ms
64 bytes from 192.168.2.2: icmp_seq=2 ttl=64 time=4.24 ms
64 bytes from 192.168.2.2: icmp_seq=3 ttl=64 time=3.19 ms
64 bytes from 192.168.2.2: icmp_seq=4 ttl=64 time=1.75 ms
64 bytes from 192.168.2.2: icmp_seq=5 ttl=64 time=5.15 ms
64 bytes from 192.168.2.2: icmp_seq=6 ttl=64 time=4.19 ms
64 bytes from 192.168.2.2: icmp_seq=7 ttl=64 time=4.57 ms
^C
— 192.168.2.2 ping statistics —
7 packets transmitted, 7 received, 0% packet loss, time 6011ms
rtt min/avg/max/mdev = 1.752/3.885/5.157/1.030 ms
(lsh:wp76stable) ntram@ubuntu:~/space$

I will research capture wireshark log as you say.

45

BTW, are you using latest FW R16.1 in WP76 module?

46

maybe it’s not the latest firmware, i will update to the latest FW and try again.

at
OK
ati9
Manufacturer: Sierra Wireless, Incorporated
Model: WP7607
Revision: SWI9X07Y_02.37.03.00 73df45 jenkins 2020/04/08 10:59:14
IMEI: 359779080101203
IMEI SV: 14
FSN: VN802485081510
+GCAP: +CGSM

OK
at!impref?
!IMPREF: 
 preferred fw version:    02.37.03.00
 preferred carrier name:  GENERIC
 preferred config name:   GENERIC_002.095_000
 preferred subpri index:  000
 current fw version:      02.37.03.00
 current carrier name:    GENERIC
 current config name:     GENERIC_002.095_000
 current subpri index:    000

OK
47

ok, but your FW is quite new, i don’t quite believe it would cause the USB SSH issue…

48

You are right, latest FW also cannot ssh into module. Is there any other reason for this ssh issue?

50

you can downgrade to R12 and then perform factory reset to see if it fixes the issue:

Or you can download the nc binary here:

Transfer to the WP module, and then type the following for TCP server:
root@swi-mdm9x28:/tmp# chmod 777 ./nc
root@swi-mdm9x28:/tmp# ./nc -l -p 1234

This can isolate if problem only exists in SSH or not.

Or you can capture the wireshark log in module side to see if there is incoming SSH packet