Nop-client-c: Difference between revisions

From Bitpost wiki
No edit summary
No edit summary
Line 1: Line 1:
nop c client
nop c client
    resources:
 
        ssh to bigress:
=== Resources ====
ssh to bigress
             # connect vpn
             # connect vpn
             ssh bigress-1.testv4
             ssh bigress-1.testv4
Line 7: Line 8:
             ~/mdm_tailTopic.sh
             ~/mdm_tailTopic.sh
             tail -f /var/log/haproxy.log
             tail -f /var/log/haproxy.log
        nop publish to bigress:
nop publish to bigress
             causam-testv4.energynet.io (DO NOT USE .link, DOES NOT SUPPORT SSL at all as you'll be bypassing haproxy)
             causam-testv4.energynet.io (DO NOT USE .link, DOES NOT SUPPORT SSL at all as you'll be bypassing haproxy)
        test msg to bigress:
test msg to bigress
             cd /etc/nop-client/ssl/causam-testv4.energynet.io
             cd /etc/nop-client/ssl/causam-testv4.energynet.io
             PEM_FILE=d292c3a4-097d-6c44-cec8-e8bb4ffe946e.pem
             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"
             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)
             (NOTE: does not verify certs)
 
== debug in qt creator ==


=== nop-client message flow ===
=== nop-client message flow ===

Revision as of 16:04, 21 November 2016

nop c client

Resources =

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 in qt creator

nop-client 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)