# Why is uplink message forwarded twice by V3 gateway?

**URL:** <https://www.thethingsnetwork.org/forum/t/why-is-uplink-message-forwarded-twice-by-v3-gateway/44493>\
**Category:** V3 Gateways\
**Created:** [February 18, 2021, 2:32pm UTC](https://www.thethingsnetwork.org/forum/t/why-is-uplink-message-forwarded-twice-by-v3-gateway/44493 "2021-02-18T14:32:49Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![htdvisser](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/htdvisser/32/45312_2.png) [@htdvisser](https://www.thethingsnetwork.org/forum/u/htdvisser)\
**Post date:** [February 22, 2021, 12:10pm UTC](https://www.thethingsnetwork.org/forum/t/why-is-uplink-message-forwarded-twice-by-v3-gateway/44493/20 "2021-02-22T12:10:44Z")

</div>

> [@TonySmith](#):
>
> I guess my specific question, does the V3 network server, in addition to NetID=0x13, also accept NetID=0x00 and send the rest to Packet Broker?

We have configured all The Things Network clusters such that all traffic that is received by gateways connected to a certain v3 cluster will be offered to the Network Server of that same cluster.

Packet Broker does not route NetID 0 (because nobody owns that NetID), so if your gateway is connected to one (v2 or v3) cluster, you will not receive uplinks for DevAddrs `00000000/6` in another cluster.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/why-is-uplink-message-forwarded-twice-by-v3-gateway/44493)._