Client Connection Log Session

With the help of these API calls, you can know the connection log sessions that have been created for a particular client. This will display the list of all the successful and failed connection attempts made by a client. This can be retained using a session ID.

Copy Sample JSON
Sample JSON 
[Client MAC: D0:51:62:29:2F:F6
SSID	: test_gamma
BSSID	: 00:11:74:D3:01:21
AP NAME	: Mojo_D3:01:20
Chan	: 11
Time	: 2016.08.26 14:52:44 (Asia/Kolkata)
Tdiff(msec)			Event
        0		Disassociation received from client because sending STA is leaving (or has left) BSS
        9		Node Left
       17		BW Clr STA limit on SSID profile [2]. Priority:[0]
    25261		AP received authentication request from client at [-56]db
    25271		Client successfully authenticated  
    27276		AP received (re)association request from client at [-66]db 
    27286		Signals a new WPA or WPA2 exchange
    27297		Client successfully (re)associated
    27306		Setting PMK from PSK as this is a WPA or WPA2 PSK authentication
    27318		First phase of WPA/WPA2 4-Way Handshake Completed 
    27327		Client successfully (re)associated
    27336		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    27346		BW Set STA limit on SSID profile [2]. Upload:[0]kbps, Download:[0]kbps, Priority:[0]
    27354		First phase of WPA/WPA2 4-Way Handshake Completed 
    27363		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    27372		First phase of WPA/WPA2 4-Way Handshake Completed 
    27381		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    28325		First phase of WPA/WPA2 4-Way Handshake Completed 
    28348		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    29332		First phase of WPA/WPA2 4-Way Handshake Completed 
    29361		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    30341		First phase of WPA/WPA2 4-Way Handshake Completed 
    30349		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    31348		First phase of WPA/WPA2 4-Way Handshake Completed 
    31371		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    32357		First phase of WPA/WPA2 4-Way Handshake Completed 
    32365		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    33364		First phase of WPA/WPA2 4-Way Handshake Completed 
    33386		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    34372		First phase of WPA/WPA2 4-Way Handshake Completed 
    34389		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    36961		Disassociation received from client because sending STA is leaving (or has left) BSS
    36969		Node Left
    36977		BW Clr STA limit on SSID profile [2]. Priority:[0]
    41240		AP received authentication request from client at [-53]db
    41254		Client successfully authenticated  
    43045		AP received (re)association request from client at [-66]db 
    43054		Client successfully (re)associated
    43063		Signals a new WPA or WPA2 exchange
    43072		Client successfully (re)associated
    43080		Setting PMK from PSK as this is a WPA or WPA2 PSK authentication
    43089		BW Set STA limit on SSID profile [2]. Upload:[0]kbps, Download:[0]kbps, Priority:[0]
    43097		First phase of WPA/WPA2 4-Way Handshake Completed 
    43106		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    43114		First phase of WPA/WPA2 4-Way Handshake Completed 
    43122		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    43252		First phase of WPA/WPA2 4-Way Handshake Completed 
    43265		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    44262		First phase of WPA/WPA2 4-Way Handshake Completed 
    44270		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    45268		First phase of WPA/WPA2 4-Way Handshake Completed 
    45292		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    46276		First phase of WPA/WPA2 4-Way Handshake Completed 
    46294		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    47284		First phase of WPA/WPA2 4-Way Handshake Completed 
    47316		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    48291		First phase of WPA/WPA2 4-Way Handshake Completed 
    48322		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    49300		First phase of WPA/WPA2 4-Way Handshake Completed 
    49311		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    50308		First phase of WPA/WPA2 4-Way Handshake Completed 
    50415		Invalid MIC received from client in msg 2/4 of 4-Way Handshake
    52915		Disassociation received from client because sending STA is leaving (or has left) BSS
    52932		Node Left
    52944		Signals a new WPA or WPA2 exchange
    52962		Setting PMK from PSK as this is a WPA or WPA2 PSK authentication
    52975		BW Clr STA limit on SSID profile [2]. Priority:[0]
    52993		AP received authentication request from client at [-68]db
    53008		First phase of WPA/WPA2 4-Way Handshake Completed 
    53021		Invalid MIC received from client in msg 2/4 of 4-Way Handshake]
API Calls
Get

/V5/connectionlogs/sessions/{sessionId}/logs

Delete

/V5/connectionlogs/sessions/{sessionId}

Get Log Of A Client Connection Log Session

Description This API is used to get the log of a connection log session.
Users with the following roles can call this API: superuser, administrator, operator, and viewer.
Syntax
GET <Base_URL>/connectionlogs/sessions/{sessionId}/logs

Here,

  • sessionId

    It is the ID of the connection log session. It takes up integer value.

  • nodeId

    It is required for specifying a child server. Takes up an integer value.

  • locationId

    It specifies the ID of the location.
Sample code
GET https://training.mojonetworks.com/new/webservice/v5/connectionlogs/sessions/3/logs?nodeid=0&locationid=1
Request Body This API call does not require any request body parameters.
Response Body If the connection log session is active, the HTTP response status is 205 (Partial).
If the session is stopped or completed, the HTTP response status is 200.

Delete A Client Connection Log Session

Description This API is used to delete a connection log session.
Users with the following roles can call this API: superuser, administrator, operator, and viewer.
Syntax
DELETE <Base_URL>/connectionlogs/sessions/{sessionId}

Here,

  • sessionId

    It is the ID of the session that you want to delete. It takes an integer value.

  • nodeid

    It is required for specifying a child server. It takes up an integer value.

  • locationId

    It specifies the ID of the location. It takes up integer value.
Sample code
DELETE https://training.mojonetworks.com/new/webservice/v5/connectionlogs/sessions/3?nodeid=0&locationid=1
Request Body This API call does not require any request body parameters.
Response Body If the API call is successful, the HTTP response status is 204.