Frequently Asked Questions

• Wirnet iBTS : 7276FF002E<last 6 characters of the CPU serial number>
• Wirnet Station : 7276FF000<last 7 characters of the station barcode>
• Wirnet iFemtoCell : 7276FF00<last 8 characters of the CPU board serial number>

For the iFemtoCell, you can retrieve the CPU serial number with the following command:

root@klk-wifc-01AAFF:~ # grep serial_number /tmp/sys_startup_status.json 
        "serial_number": "0x4501aaff", 

Note you can obtain directly the EUI from the /tmp/board_info.json file:

root@klk-wiis-040166:~ # cat /tmp/board_info.json | grep -i eui
        "EUI64": "7076FF0054040166", 
root@klk-wiis-040166:~ # 

• We can limit the number of gateways, the number of endpoints and number of users linked to a customer via the administration menu (only accessible for users that have SuperAdmin privileges)

• There is no limit

• Add

• An exception is raised and the process stops

• An exception is raised and the process stops when the error is encountered. All lines located before this point are taken into account by the system

• Yes

• No

• In the LNS / endpoint menu, click on your endpoint and then click to the cross at the right side of the text “FRAME COUNTER DOWN”
• select F5 for page refresh several times

⇒ Status “Uplink ok” appears and uplink message queue is updated with new messages in “Rx messages” tab

When connected to the Wanesy Management Center VPN, the IP address assigned to the gateway is in the 10.8.0.0/16 subnet.

The gateway LAN subnet should not overlap with this subnet.

WMC does not follow http redirected URLs. You have to input the real URL.

To check whether your URL is redirected or not: curl -I https://url-example.com/

Here is an example of what happens when URL is redirected:

HTTP/1.1 301 Moved Permanently
Server: nginx/1.12.2
Date: Wed, 25 Apr 2018 12:56:10 GMT
Content-Type: text/html; charset=iso-8859-1
Connection: keep-alive
Location: http://redirected.url/
Strict-Transport-Security: max-age=31536000
Content-Security-Policy: default-src https: redirected.url 'unsafe-inline' 'unsafe-eval'
x-frame-options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Referrer-Policy: strict-origin-when-cross-origin

AES keys, coded on 32 bits, permit to decode timestamps sent by the stations and used for geolocation.

Requirements:

• Station declared
• AES keys known

Once connected on WMC:

1. Select menu page LNS > Stations
2. Filter the station (thanks to its EUI for example)
3. Access to the station details by clicking on its EUI in the list of stations
   
4. Click on “Add” button.
   
5. The below window opens:
   • Complete RFCH which corresponds to the slot number of the radio modem. Usually RFCH=1. If there are several radio modems: RFCH=2, RFCH=3, RFCH=4…
   • Put the AES key
   • Choose its end date of validity
     
     After AES key declaration, it is possible to check on device RX messages that fine timestamps are well generated:
6. Select menu LNS > Endpoints
7. Choose the cluster
8. Access to endpoint details by clicking on its Dev EUI
   
9. Select menu “Rx Messages” and verify that there are fine timestamps from the station