Packet Broker TTN to TTI ttn-v2-eu

[iiLaw (Lawrence Griffiths)]

I have both a TTN & TTI gateway when did TTN start forwarding to TTI ?
In TTI v3 console uplink appears as follows (NB. fragment of msg)

“rx_metadata”: [
{
“gateway_ids”: {
“gateway_id”: “packetbroker”
},
“packet_broker”: {
“message_id”: “01EBHKCBXABZ6606WBC53CSR4B”,
“forwarder_net_id”: “000013”,
“forwarder_id”: “ttn-v2-eu”,
“home_network_net_id”: “000013”,

[Jeff-UK]

IIRC I Think @Johan mentioned this in presentation at January 20 Things Conf… may be worth you heading over to YouTube to check

[jfmateos]

Does anybody know whether TTI also forwards to TTN? I think it would be desirable a bit more transparency in this issue.

[cultsdotelecomatgmai (Tim Everitt)]

Hi @iiLaw, I have a TTIv3 cloud-hosted LNS and also TTN gateways. I first observed uplinks arriving in TTI via packetbroker on 1st March 2020. It’s been a bit intermittent since then.

The TTIv3 Packet Broker Agent can be configured to be a Forwarder (ie offers RX’d uplinks to others) and/or Home Network (ie listens for RX’d uplinks offered by others).

I think that TTI are very actively working on PacketBroker to add downlink capability, etc. so aren’t saying much at the moment.

[htdvisser (Hylke Visser)]

As @Jeff-UK already commented, @johan talked a lot about Packet Broker during The Things Conference in February 2020. Here in the opening keynote, and later during this presentation. You should definitely watch those videos.

Packet Broker enables bi-directional peering between networks. You can configure routing policies that tell Packet Broker what kind of uplink traffic to forward to other networks (or a specific network) and what kind of downlink traffic to accept from other networks (or a specific network). An example policy would be to forward all uplink traffic (because you already received that anyway), and allow MAC downlinks (so that the Network Server can perform ADR).

---

We have implemented the “forwarder” role in our v2 stack, which will help with a smoother transition from v2 to v3. Since the public community network still runs on v2, you’ll only observe this “forwarding” behavior there. The Things Stack (v3) supports both the “forwarder” and “home network” roles. This is how v3 clusters can exchange traffic between each other. When we start rollout of the v3 public community network you’ll also start seeing incoming Packet Broker traffic there.

[iiLaw (Lawrence Griffiths)]

Thanks All for the response.

It may take a while, but think many will appreciate what #PacketBroker brings to the LoRaWAN landscape.