You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+140-1
Original file line number
Diff line number
Diff line change
@@ -319,7 +319,7 @@ as 192.168.0.160. The capture shows it as 192.168.1.128.
319
319
320
320

321
321
322
-
So with that said, I am using a capture filter as opposed to a display filter in wireshark. The capture file is in the [capfiles](./capfiles/) directory.
322
+
So with that said, I am using a capture filter `host 192.168.1.128`as opposed to a display filter in wireshark. The capture file is in the [capfiles](./capfiles/) directory.
323
323
324
324
So, now that we know how to configure wireshark, lets see what happens
325
325
when we attempt to connect with HTTPs and no domain cert loaded
@@ -345,6 +345,145 @@ contents of a webpage. It also generates a lot of traffic in wireshark. These
345
345
346
346

347
347
348
+
##
349
+
## MQTT to GCP on Arduino
350
+
351
+
Running [this](https://github.com/arduino/ArduinoCloudProviderExamples/tree/master/examples/Google%20Cloud%20Platform%20IoT%20Core/GCP_IoT_Core_WiFi) code with one change. Since I am using MKR1000 I switch the
352
+
header as wonderfully commented.
353
+
354
+
Before I show the capture file and output, let me specify my
355
+
current "ssl" setup.
356
+
357
+
I have the google.com:443 domain loaded. I read something about
358
+
where people said a fix was to include the cert used to sign
359
+
the other cert. I'm still unclear on the terms or process.
360
+
But, I'm thinking what they are intending is that the
361
+
crypto chip needs the firmware to have the correct cert
362
+
loaded before it generates a key. So with that said
0 commit comments