Can the TTN Kickstarter gateway forward to alternative or multiple backend servers?

[arjanvanb (Arjan)]

@Adri20

if a gateway sends once per hour for 1 second insn’t that 1/(60*60)=0.028% duty cycle? (only sending 1 second out of 3600)

I was just fixing that when you responded. And I explained a bit more in my edit above.

@Adri20

because after registering one node a gateway has to rest quiet a long time to be able to send the next

Indeed, see Activation not valid - no gateways available. Note that it cannot listen and send simultaneously either, so it’s good it has time to listen too.

@Adri20

if one gateway has downlink messages queued up are downlinkpackages then rerouted to an other gateway which is also in range of the node?

Not re-routed, but TTN waits as long as possible before it tells a specific gateway to send a downlink. Like for a Join Accept, which is to be sent 5 or 6 seconds after receiving the Join Request, TTN will only send it to a gateway shortly before these 5 or 6 seconds expire.

@Adri20

It could be solved by a “send-queue-maxedout-flag” in the gateway which would be sent to the backends to signal that for the comming 5 minutes (or another value depending on the send-queue-depthsetting) no sending will be possible.

I guess that’s true. But as long as gateways are just dumb forwarders, that doesn’t exist. And what benefit is there to have multiple backends try to control the same network?