Nop-client-c

Resources

ssh to bigress

           # connect vpn
           ssh bigress-1.testv4 # .energynet.link
           ~/mdm_listTopics.sh
           ~/mdm_tailTopic.sh

ssh to haproxy

ssh bigress-lb-1.testv4 # .energynet.link
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

Qt Creator seems pretty good.

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

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

   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)