lupyuen/lupyuen.org
1
0
Fork 0
mirror of https://github.com/lupyuen/lupyuen.github.io.git synced 2025-01-13 10:18:33 +08:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Commit from GitHub Actions

Browse source
This commit is contained in:
Lee Lup Yuen 2022-02-02 04:25:47 +00:00
parent 208309d58e
commit 24f6822e39
2 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
articles/lorawan3.html
View file

@ -927,7 +927,7 @@ RadioSetChannel: freq=923400000</code></pre></div>
<p><a href="https://lupyuen.github.io/articles/lorawan3#device-eui-join-eui-and-app-key"><strong>“Device EUI, Join EUI and App Key”</strong></a></p>
</li>
<li>
<p>On our LoRaWAN Gateway, scan the log for <strong>Message Integrity Code</strong> errors…</p>
<p>On our LoRaWAN Gateway, scan the log for <strong>Message Integrity Code</strong> errors (“invalid MIC”)…</p>
<div class="example-wrap"><pre class="language-bash"><code>grep MIC /var/log/syslog
chirpstack-application-server[568]:
@ -939,7 +939,7 @@ chirpstack-application-server[568]:
<p><a href="https://lupyuen.github.io/articles/wisgate#message-integrity-code">(More about Message Integrity Code)</a></p>
</li>
<li>
<p>On our LoRaWAN Gateway, scan the log for <strong>Nonce Errors</strong>…</p>
<p>On our LoRaWAN Gateway, scan the log for <strong>Nonce Errors</strong> (“validate dev-nonce error”)…</p>
<div class="example-wrap"><pre class="language-bash"><code>grep nonce /var/log/syslog
chirpstack-application-server[5667]:

8
articles/wisgate.html
View file

@ -496,7 +496,7 @@ OnRadioRxTimeout</code></pre></div>
<h2 id="check-the-log" class="section-header"><a href="#check-the-log">7.2 Check the log</a></h2>
<p>SSH to WisGate and look at the <strong>Linux System Log</strong> while our LoRaWAN Device is transmitting packets…</p>
<div class="example-wrap"><pre class="language-bash"><code>tail -f /var/log/syslog</code></pre></div>
<p>Sometimes it’s helpful to scan the log for <strong>Message Integrity Code</strong> errors…</p>
<p>Sometimes it’s helpful to scan the log for <strong>Message Integrity Code</strong> errors (“invalid MIC”)…</p>
<div class="example-wrap"><pre class="language-bash"><code>grep MIC /var/log/syslog
Apr 28 04:02:05 rak-gateway
@ -506,7 +506,7 @@ level=error
msg=&quot;invalid MIC&quot;
dev_eui=4bc15ee7377bb15b
type=DATA_UP_MIC</code></pre></div>
<p>Also for <strong>Nonce Errors</strong>…</p>
<p>Also for <strong>Nonce Errors</strong> (“validate dev-nonce error”)…</p>
<div class="example-wrap"><pre class="language-bash"><code>grep nonce /var/log/syslog
Apr 28 04:02:41 rak-gateway chirpstack-application-server[568]:
@ -589,7 +589,7 @@ type=OTAA</code></pre></div>
</ol>
<p><em>What happens when we transmit an invalid Message Integrity Code?</em></p>
<p>Our LoRaWAN Gateway (ChirpStack on WisGate) will <strong>reject LoRaWAN Packets with invalid Message Integrity Codes</strong>.</p>
<p>To see Message Integrity Code errors, SSH to our LoRaWAN Gateway and search for…</p>
<p>To see Message Integrity Code errors, SSH to our LoRaWAN Gateway and search for “invalid MIC”…</p>
<div class="example-wrap"><pre class="language-bash"><code>grep MIC /var/log/syslog
Apr 28 04:02:05 rak-gateway
@ -613,7 +613,7 @@ error=&quot;get device-session error: invalid MIC&quot;</code></pre></div><h2 id
<p><em>What happens when we replay a Join Network Request?</em></p>
<p>Our LoRaWAN Gateway (ChirpStack on WisGate) will <strong>reject Join Network Requests that have a reused Nonce</strong>.</p>
<p>(Yep the gateway will remember the Nonces from previous requests)</p>
<p>To see Nonce errors, SSH to our LoRaWAN Gateway and search for…</p>
<p>To see Nonce errors, SSH to our LoRaWAN Gateway and search for <strong>“validate dev-nonce error”</strong>…</p>
<div class="example-wrap"><pre class="language-bash"><code>grep nonce /var/log/syslog
Apr 28 04:02:41 rak-gateway chirpstack-application-server[568]: