private network with 2 gw

[luis santos]

Hi guys,

Hi got a lora public network with 2 multitech conduit gw, and a i have some lora devices that pass all the time jumping between the 2 gw. All the devices join by otaa.
To stop this, I need to configure wich gw with a unique APPEUI and APPKey?

cheers,

[luis santos]

After read the documentation. I found that this options:
Address Range Start
Address Range End.

Buy i not sure how can a put single address. Must be range of address?

[Peter Ferland]

Are you using the built in network server on both gateways? When a device joins a network using OTAA session keys are negotiated between the gateway and the end device. The session keys are stored in a database entry on the gateway for that device. This means that a device can only be joined to one gateway (Acting as a join server) at a time.

Configuring both gateways with different AppEUIs would reduce confusion between the gateways and ensure that you must treat them as separate networks.

In the next major firmware release for AEP there will be a feature that allows one Conduit to packet forward to another. This would probably be a better long term solution if both gateways are on a LAN. The firmware should be released in the next few weeks.

[luis santos]

Hi,

Yes I’m using the built in network server on both gateways.
Changing the AppEUIs is not a option.

Before the new release of AEP. I try to use the whitelist, but some nodes continue jump between gateways when doing otaa join.

cumps,

[Jason Reiss]

Do you use unique keys per device in the whitelist or the same key?
Both Conduits are configured for same NetworkEUI/AppEUI and NetworkKey/AppKey?
End-devices are configured same NetworkEUI/AppEUI and NetworkKey/AppKey?
Can end-devices use different AppEUI or AppKey?

[luis santos]

Yes, both conduits have the same APPEUI and AppKey.
Yes, the End-devices got the same AppEUI and APPKey.
On the end-devices the only way to change the appEUI or appKey, is locally reprogramming the firmware.

[Jason Reiss]

You could implement a blacklist using an application

In node-red use MQTT in and out nodes with a function node between.
This code will clear the join accept packet out of the downlink queue.

if (msg.topic.search("<BLACK-LISTED-EUI>")) {
    msg.topic = msg.topic.replace("joined", "clear");
    return msg;
} else {
    return null;
}

[luis santos]

About the downlink queue. When a clear is sent to a specific EUI. It cleans only the queue msg for this EUI?

[Jason Reiss]

Yes that is correct.

[luis santos]

Tks for all the support.
But now a notice another thing. I’m receiving a lot off “|WARNING| Duty cycle limit met – Band: 0 time-on-air available: 1044 ms” on the lora-network-server.

Can anyone explain me this warning? and ways to mitigate.

cumps,

[Jason Reiss]

Tx on the end-device and gateway are limited by Duty Cycle. Band 0 is 1% duty-cycle.

The only way to not hit the limit and maintain regulations is to transmit less often.

[luis santos]

Tks Jason. You help a lot.

Edit:
One last question :).
the gw band 0 tx 1% dutycycle if for all end devices?

cheers,

• This reply was modified 6 years, 9 months ago by luis santos.

[Author]

Posts