Oh I have to muck with iptables - never mind -Connect() times out on FX30S on R14/Legato 16.10.1.m3

IoT Gateways FX30
1

I was running the latest wp85 build & had no problem connecting. I downgraded to R14.0.4.002/Legato 16.10.1.m3 and now get timeouts on the connect.

root@fx30s:~# cm data info
Index: 1
APN: vfd1.korem2m.com
PDP Type: IPV4
Connected: no
Auth type: CHAP
User name: xxxx
Password: xxxx

Log file is attached. (Pardon the other debugging statements in there). Connect first fails with error 101, then consistently fails with error 110.FX30S.txt (22.8 KB)

Thanks,
Randi

2

Hi,

In your logs:

Apr 9 19:23:37 fx30s user.info Legato: INFO | modemDaemon[578]/le_pa T=main | pa_mrc_qmi.c pa_mrc_GetNetworkRegState() 2211 | called
Apr 9 19:23:37 fx30s user.info Legato: INFO | fx30app[22731]/fx30appComponent T=main | main.c dbgPrintf() 28 | DBG: regstate=4, signal=2
Apr 9 19:23:37 fx30s user.info Legato: INFO | fx30app[22731]/fx30appComponent T=main | main.c dbgPrintf() 28 | DBG: connected state = 2
Apr 9 19:23:37 fx30s user.info Legato: INFO | fx30app[22731]/fx30appComponent T=main | main.c dbgPrintf() 28 | Connecting to SW: 69.10.131.102
Apr 9 19:23:37 fx30s user.info Legato: INFO | fx30app[22731]/fx30appComponent T=main | main.c dbgPrintf() 28 | Failed to connect . err=101

Please add you script to clarify this, after pa_mrc_GetNetworkRegState() return network state, the value "“regstate=4"” is weird, usually the normal state status of network registered, "“4"” mean ““Unknown””. Hence, your module not really registered at the moment and the error (101 or 100) is make sense in this case.

And by the restrict of FX30 product on legato 16.10, you should use modemServices instead of dcsService:
https://source.sierrawireless.com/resources/airlink/application_notes_and_code_samples/airlink_appnote_network_interfaces_and_firewall_rules/#sthash.1fplFAYL.dpbs

Thanks,