Why is uplink message forwarded twice by V3 gateway?

TTN V2 to V3 Upgrade V3 Gateways
10

In all The Things Stack (v3) deployments managed by The Things Industries, all traffic is forwarded to Packet Broker. The routing policies in Packet Broker then determine if and where that traffic gets routed.

We call this peering. Packet Broker is configured with routing policies that send uplink messages from the “forwarding” cluster to the “home” cluster:

DevAddr Prefix   NetID    Tenant ID       Cluster ID
26080000/16      000013                   tti-ch-eu1
26090000/16      000013                   tti-ch-nam1
260A0000/16      000013                   tti-ch-au1
260B0000/16      000013   ttn             ttn-eu1
260C0000/16      000013   ttn             ttn-nam1
260D0000/16      000013   ttn             ttn-au1

So when the ttn-nam1 cluster sends an uplink for DevAddr 26091234 to Packet Broker, that gets routed to tti-ch-nam1, and when the tti-ch-au1 cluster sends an uplink for DevAddr 260D1234 to Packet Broker, that gets routed to ttn-au1.

When the ttn-eu1 cluster sends an uplink for DevAddr 260B1234 to Packet Broker, it will not get routed to any other network, because it doesn’t match any routing policy.

2 Likes