# Packets do not appear any more in console

**URL:** <https://www.thethingsnetwork.org/forum/t/packets-do-not-appear-any-more-in-console/35743>\
**Category:** v2 Console\
**Created:** [March 29, 2020, 4:57pm UTC](https://www.thethingsnetwork.org/forum/t/packets-do-not-appear-any-more-in-console/35743 "2020-03-29T16:57:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\
**Post date:** [March 29, 2020, 7:02pm UTC](https://www.thethingsnetwork.org/forum/t/packets-do-not-appear-any-more-in-console/35743/2 "2020-03-29T19:02:02Z")

</div>

[That example](https://github.com/SensorsIot/LoRa/blob/master/Nodes/Dragino/HelloWorld/HelloWorld.ino#L19-L21) uses [ABP](https://www.thethingsnetwork.org/docs/lorawan/addressing.html#activation).

You’re running into a security issue against replay attacks. Whenever you reset a device (or upload a new sketch), its counters will be reset to zero. But as there is no join process for ABP (like as used for OTAA), TTN does not know about that, and will reject all uplinks that have a counter value that is smaller than, or equal to, the last value that TTN knows.

When you reset an ABP device, you also need to reset the counters in TTN Console. Or for testing sometimes disabling the frame counter security helps. Neither is ever recommended for production nodes, but might even be troublesome for test nodes; see [ABP node stopped working -\> Fixed by creating new ABP.. Why? :)](https://www.thethingsnetwork.org/forum/t/abp-node-stopped-working-fixed-by-creating-new-abp-why/3200)

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/packets-do-not-appear-any-more-in-console/35743)._