# Should private LoRaWAN networks use a different sync word?

**URL:** <https://www.thethingsnetwork.org/forum/t/should-private-lorawan-networks-use-a-different-sync-word/34496>\
**Category:** TTN Network and Services\
**Created:** [February 17, 2020, 9:20pm UTC](https://www.thethingsnetwork.org/forum/t/should-private-lorawan-networks-use-a-different-sync-word/34496 "2020-02-17T21:20:18Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![hobo](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/hobo/32/25844_2.png) [@hobo](https://www.thethingsnetwork.org/forum/u/hobo)\
**Post date:** [February 17, 2020, 9:48pm UTC](https://www.thethingsnetwork.org/forum/t/should-private-lorawan-networks-use-a-different-sync-word/34496/5 "2020-02-17T21:48:18Z")

</div>

> [@arjanvanb](#):
>
> then there would be basically only two sync words

I don’t know if 0x12 and 0x34 are the only allowed values, but you surely cannot use whatever value you want to use for sync word. Someone from Semtech was trying to explain these matters at their Salesforce community site some years ago, but that site was redesigned since that (and a lot of valuable info was lost), not sure if it still possible to finf that discussion.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/should-private-lorawan-networks-use-a-different-sync-word/34496)._