Nop-client-c: Difference between revisions

From Bitpost wiki
No edit summary
(Replaced content with "=== Run as root === === Debug === === Resources === === Message flow === === Functionality ===")
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
=== Resources ===
=== Run as root ===
ssh to bigress
 
            # connect vpn
            ssh bigress-1.testv4
            ~/mdm_listTopics.sh
            ~/mdm_tailTopic.sh
            tail -f /var/log/haproxy.log
nop publish to bigress
            causam-testv4.energynet.io (DO NOT USE .link, DOES NOT SUPPORT SSL at all as you'll be bypassing haproxy)
test msg to bigress
            cd /etc/nop-client/ssl/causam-testv4.energynet.io
            PEM_FILE=d292c3a4-097d-6c44-cec8-e8bb4ffe946e.pem
            curl -vvv -k -X PUT -d "{payload: \"`hostname`\"}" --cert $PEM_FILE --cookie @cookie.jar --cookie-jar cookie.jar "https://bigress-1.testv4.energynet.io:443/rest/v1/random1"
            (NOTE: does not verify certs)
=== Debug ===
=== Debug ===
Qt Creator seems pretty good.


Install DEBUG versions of all libraries into /usr/local - see build_lws_debug for an example of that library.
=== Resources ===


Make sure you rebuild everything from command line, it took a couple times before Qt seemed to pick it up and debug into libs.  You should NOT have to add any paths directly.
=== Message flow ===


=== nop-client message flow ===
=== Functionality ===
    EDGE                                CLIENT
   
                                        initial certificate provisioning
                                       
                                        olympicmachines < hello
                                        simplepointframe < heartbeat keepalives (as needed)
    EDGE becomes device-aware
    build config
    send to machine                    olympicmachines > polling config
                                        olympicmachines < polling config ACK
                                       
    start polling                      simplepointframe < data
                                       
                                        (dead) < (buffer until server becomes responsive)

Latest revision as of 21:08, 7 January 2017

Run as root

Debug

Resources

Message flow

Functionality