This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
wiki:wiki3:faq_general_top30:home [2021/03/25 10:02] tda created |
wiki:wiki3:faq_general_top30:home [2023/01/30 11:40] (current) ehe [Check for the OpenVPN certificate validity] |
||
---|---|---|---|
Line 314: | Line 314: | ||
For firmware version 4.3.3 and above, activate the CPF on european TTN server with the command: \\ | For firmware version 4.3.3 and above, activate the CPF on european TTN server with the command: \\ | ||
<code> | <code> | ||
- | klk_apps_config --activate-cpf --lns-server router.eu.thethings.network --lns-dport 1700 --lns-uport 1700 | + | klk_apps_config --activate-cpf --lns-server eu1.cloud.thethings.network --lns-dport 1700 --lns-uport 1700 |
</code> | </code> | ||
[[https://wikikerlink.fr/wirnet-productline/doku.php?id=wiki:keros_custo:keros_applications_configuration#examples | Keros application configuration examples]] | [[https://wikikerlink.fr/wirnet-productline/doku.php?id=wiki:keros_custo:keros_applications_configuration#examples | Keros application configuration examples]] | ||
Line 635: | Line 635: | ||
==== Check for the OpenVPN certificate validity ==== | ==== Check for the OpenVPN certificate validity ==== | ||
- | if your gateway is a Wirnet Station, perform the command: | + | To check OpenVPN certificate validity, you can use following commands depending of your product & firmware version: |
+ | |||
+ | **Firmware 4x:** | ||
<code> | <code> | ||
- | openssl pkcs12 -passin pass:"" -in /etc/openvpn /client-openvpn.p12 -nokeys | openssl x509 -noout -enddate'' | + | grep -iA3 "Validity" /.update/update.log | tail -3 |grep -i "not after"| sed 's/^[ \t]*//' |
</code> | </code> | ||
- | If your gateway is a i-series gateway (Istation, iFemto, iBTS), ask to the Support team the validity date of the certificate (please, give the serial number of your gateway). | + | |
+ | **Firmware 5x:** | ||
+ | <code> | ||
+ | openssl pkcs12 -info -in /etc/openvpn/bscc.p12 -nokeys -password file:/etc/openvpn/bscc.password| openssl x509 -noout -enddate | ||
+ | </code> | ||
+ | |||
+ | **Firmware 3x (Wirnet Station & iSeries):** | ||
+ | <code> | ||
+ | openssl pkcs12 -info -in /etc/openvpn/client-openvpn.p12 -nokeys -password pass: | openssl x509 -noout -enddate | ||
+ | </code> | ||
==== Check for OpenVPN certificate install issue ==== | ==== Check for OpenVPN certificate install issue ==== | ||
Line 715: | Line 727: | ||
So first read the next section to know how to send a downlink command.\\ | So first read the next section to know how to send a downlink command.\\ | ||
To send a specific MAC command as a downlink message, you need the LoRaWan Regional Parameters documentation from the Lora Alliance: | To send a specific MAC command as a downlink message, you need the LoRaWan Regional Parameters documentation from the Lora Alliance: | ||
- | [[https://lora-alliance.org/sites/default/files/2018-04/lorawantm_regional_parameters_v1.1rb_-_final.pdf]].\\ | + | [[https://lora-alliance.org/wp-content/uploads/2020/11/rp_2-1.0.1.pdf]].\\ |
The MAC commands are dependant of your region. | The MAC commands are dependant of your region. | ||
Line 1090: | Line 1102: | ||
If you hesitate and don't not know what to do, perform an ofono reset and a reboot! | If you hesitate and don't not know what to do, perform an ofono reset and a reboot! | ||
+ | |||
+ | ===== What to do when the enddevice has the status "Data Up mic error" with the value "Exceed FcntUp max gap" ? ===== | ||
+ | |||
+ | This message indicates that there is a too large gap between the previous FCountUp counter value and the new counter value. \\ | ||
+ | That may happen when the gateway that was transferring the LoRa messages to the WMC server has been switched off a long time. \\ | ||
+ | |||
+ | To fix this issue: \\ | ||
+ | |||
+ | **1/ Reset the enddevice** \\ | ||
+ | Normally the enddevice should rejoin the LoRa network and counter will restart from 0 after the join procedure. \\ | ||
+ | |||
+ | If this operation does not fix the issue: \\ | ||
+ | |||
+ | **2/ Remove the end-device definition from the WMC dahsboard (de-provisioning) and re-create it (re-provisioning) then reset the end-device.** \\ | ||
+ | This last operation should make the enddevice recommunicating with the WMC server (LNS). | ||
+ | |||