# Meshed-handler

**URL:** <https://www.thethingsnetwork.org/forum/t/meshed-handler/14652>\
**Category:** TTN Network and Services\
**Created:** [May 30, 2018, 12:22am UTC](https://www.thethingsnetwork.org/forum/t/meshed-handler/14652 "2018-05-30T00:22:19Z")\
**Posts on this page:** 1\
**Showing post:** 35

<div class="post-metadata">

**Author:** ![kersing](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/kersing/32/44777_2.png) [@kersing](https://www.thethingsnetwork.org/forum/u/kersing)\
**Post date:** [August 12, 2019, 7:31am UTC](https://www.thethingsnetwork.org/forum/t/meshed-handler/14652/35 "2019-08-12T07:31:57Z")

</div>

> [@hmullerenersa](#):
>
> I don´t understand that mechanism use, and what kind of gateway do this, to download frequency plan and from where is downloaded eventually. Can you give me some example to understand better this frequency plan update mechanism

Kerlinks do not update the configuration so you need to make sure the configuration is right. Examples of gateways downloading the frequency plan are The Things Gateway (original), The Things Indoor Gateway (TTIG) and some Raspberry Pi based gateways. The source of the frequency plan is the account server.

> [@hmullerenersa](#):
>
> So, then I can register my gateway on any handler with their correspondent router, based on the minor network transit time independently of the frequency plan used?

Yes. Please do. Network delays should be as small as possible to prevent them interfering with the LoRaWAN timing.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/meshed-handler/14652)._