SenseCAP M1 Gateway to TTN

Jeff-UK
Mon, 26 Jan 2026 00:26:57 +0000

kasi1337:

The multiplexer only duplicates the UDP packets

My point entirely - it does nothing to assist in the management of the gateway (as re-enforced by Jac), the ensuring correct handling of none overlapping messages, the minimisation and practical distribution across viable GW’s of downlinks (if the LNS ‘knows’ a given GW may be in breach of D.C. it can elect to use another close (signal condition wise) proximity GW as alternate path) and network management signals to mitigate/minimise conflicting messages - basically GW queue management; because the 2 (or more) networks have no idea what the other is doing. This is an acute problem where gws and the LNS work together to implement any kind of JIT queue. Basically all the points previously highlighted by both Jac and me.

kasi1337:

It seems there may be a misunderstanding regarding how the packet multiplexer operates.

No misunderstanding about the mux operation - as highlighted this has been a ‘thing’ for a long time and is well understood (potentially not just for UDP - legacy SMTC style PF - traffic for any other TCP/IP or related network traffic between GW & LNS). It’s a lack of understanding of what the practical and potential legal consequences are of attempting to insert one into a LoRaWAN system architecture. Where there may be a role, depending on application, is where the alternate LNS connection is treated entirely as uplink only - possibly for back up data capture, but without ANY form of associated downlink(s) - so e.g. no ability for an end node to ‘join’ the alternate network. Device/Network and associated credentials & keys, channel plans etc., would need to be shared between the networks via an alternate backchannel. No ADR control etc. OTAA hard, ABP may be slightly easier….!

Just because you havent seen the problem in your tests does not mean problems dont/wont happen or that you havent caused problems for other community users (how would you know?!) and given the scale & scope of TTN around the world (not to say some of the other networks you mention) hence the position outlined - not on TTN.