Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multiple downlinks #30

Open
parylizer opened this issue Dec 5, 2024 · 3 comments
Open

multiple downlinks #30

parylizer opened this issue Dec 5, 2024 · 3 comments

Comments

@parylizer
Copy link

Is it possible to have multiple downlinks with this?

For example: two packet forwarders --> multiplexer --> two backend servers and then downlinks will return back to both of the packet forwarders

@brocaar
Copy link
Collaborator

brocaar commented Dec 6, 2024

I'm not sure if I understand the question. But you could have multiple gateways connecting to one multiplexer, which then sends the data to multiple LNS instances (e.g. ChirpStack, TTN, .....). Unless configured for uplink only, each LNS will be able to send downlink as if the gateway was directly connected.

@parylizer
Copy link
Author

I'm not sure if I understand the question. But you could have multiple gateways connecting to one multiplexer, which then sends the data to multiple LNS instances (e.g. ChirpStack, TTN, .....). Unless configured for uplink only, each LNS will be able to send downlink as if the gateway was directly connected.

Yes, that sounds like what I'm looking for except I should clarify that I would like the downlink to be sent to all gateways either with the same gateway id or if it can send to multiple with different id's (preferred). When tested previously it seemed like the downlink would only go to one gateway.

@brocaar
Copy link
Collaborator

brocaar commented Dec 9, 2024

I would like the downlink to be sent to all gateways either with the same gateway id or if it can send to multiple with different id's (preferred).

A downlink is always set to a single gateway, because it is targeted at a specific Gateway ID. As well, for Class-A downlinks, the downlink message contains a tmst value that is specific to the targeted gateway.

Depending your needs, you might be able to implement an other solution, but this is not an use-case covered by the Multiplexer. The use-case of the multiplexer is to share one or multiple gateways with multiple backends and let each backend think each gateway is directly connected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants