This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
wiki:lora:basic_station_forwarder [2024/01/31 12:20] ehe |
wiki:lora:basic_station_forwarder [2024/03/07 13:52] ehe |
||
---|---|---|---|
Line 179: | Line 179: | ||
<note>Only available since [[bspf_v2.4.1|version 2.4]] ( for "Land Mobile Station" use cases, please contact Kerlink support)</note> | <note>Only available since [[bspf_v2.4.1|version 2.4]] ( for "Land Mobile Station" use cases, please contact Kerlink support)</note> | ||
- | By default, LBT is **NOT** activated for AS923-1 region. It needs to be activated manually by using following commands: | + | For LNS which doesn't embed AS923-1 with LBT, it needs to be activated manually by using following commands: |
<code bash> | <code bash> | ||
Line 238: | Line 238: | ||
\\ | \\ | ||
To use this tool, you need: | To use this tool, you need: | ||
- | * an API token* | + | * an API token |
* the API server URL | * the API server URL | ||
* the chose frequency plan | * the chose frequency plan | ||
Line 298: | Line 298: | ||
<note important> | <note important> | ||
''klk_bs_config'' is still required after this to complete the Basic Station configuration. | ''klk_bs_config'' is still required after this to complete the Basic Station configuration. | ||
- | </note> | ||
- | <note warning> | ||
- | The Loriot Basic Station server does not respond to websocket pings. It is therefore advised to disable this functionality when connecting to such a server. | ||
</note> | </note> | ||
Line 307: | Line 304: | ||
# Use Loriot configuration tool in region US902 with 3 channel plans (US915_CH16_23, US915_CH40_47 and US915_CH56_63) | # Use Loriot configuration tool in region US902 with 3 channel plans (US915_CH16_23, US915_CH40_47 and US915_CH56_63) | ||
klk_loriot_config -k ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEFGHIJK-321abcdefgh -u https://eu1.loriot.io/1/nwk -n ABCD1234 -r US902-928 -p 3,6,8 | klk_loriot_config -k ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEFGHIJK-321abcdefgh -u https://eu1.loriot.io/1/nwk -n ABCD1234 -r US902-928 -p 3,6,8 | ||
- | # Disable websocket pings | ||
- | klk_bs_config --enable --ping_interval None | ||
</code> | </code> | ||
++++ | ++++ | ||
Line 315: | Line 310: | ||
</note> | </note> | ||
+ | ++++How to generate an LORIOT API key?| | ||
+ | **Prerequisite:** LORIOT account \\ | ||
+ | [[https://docs.loriot.io/display/NMS/Create+an+API+key|LORIOT - Create an API key]] | ||
+ | ++++ | ||
==== AWS LNS configuration tool ==== | ==== AWS LNS configuration tool ==== | ||
Line 342: | Line 341: | ||
</note> | </note> | ||
+ | ++++How to generate an AWS API key?| | ||
+ | **Prerequisite:** You have to create a AWS account \\ | ||
+ | |||
+ | To automatically connect Kerlink Gateways to AWS LNS, you have to delegate some rights to Kerlink thanks to an “API key”. Please follow those steps: \\ \\ | ||
+ | Step 1 - Connect to your AWS server \\ | ||
+ | |||
+ | Step 2 - Go to Console > Services > IAM then hitting the Add users button to create a new AWS user \\ | ||
+ | {{:images:1_aws_user_account.png?800|}} \\ | ||
+ | |||
+ | Step 3 - Name the user (= user ID) and set the access type to Programmatic Access \\ | ||
+ | <note important>DO NOT check “AWS Management Console access”</note> | ||
+ | {{:images:2_aws_access_type.png?500|}} \\ | ||
+ | |||
+ | Step 4 - DO NOT add user to any group. Also SKIP other steps until creation \\ | ||
+ | {{:images:3_aws_no_group.png?500|}} \\ | ||
+ | |||
+ | Step 5 - Select the new user \\ | ||
+ | {{:images:4_aws_select_user.png?500|}} \\ | ||
+ | |||
+ | Step 6 - In Security Credentials section: | ||
+ | * Select Application running outside AWS | ||
+ | * Give a tag value (optional) | ||
+ | * Copy Access Key ID and Secret | ||
+ | \\ | ||
+ | {{:images:5_aws_security.png?500|}} \\ | ||
+ | |||
+ | Step 7 - Add a new inline policy \\ | ||
+ | {{:images:6_aws_inline_policy.png?500|}} \\ | ||
+ | |||
+ | Step 8 - Switch to the JSON view and add the following content \\ | ||
+ | <code> | ||
+ | { | ||
+ | "Version": "2012-10-17", | ||
+ | "Statement": [ | ||
+ | { | ||
+ | "Sid": "VisualEditor0", | ||
+ | "Effect": "Allow", | ||
+ | "Action": [ | ||
+ | "iot:DeleteCertificate", | ||
+ | "iot:UpdateCertificate", | ||
+ | "iotwireless:GetWirelessGatewayCertificate", | ||
+ | "iotwireless:GetWirelessGateway", | ||
+ | "iotwireless:UpdateWirelessGateway", | ||
+ | "iotwireless:AssociateWirelessGatewayWithCertificate", | ||
+ | "iotwireless:ListWirelessGateways", | ||
+ | "iotwireless:GetServiceEndpoint", | ||
+ | "iot:CreateKeysAndCertificate", | ||
+ | "iotwireless:CreateWirelessGateway" | ||
+ | ], | ||
+ | "Resource": "*" | ||
+ | } | ||
+ | ] | ||
+ | } | ||
+ | </code> \\ | ||
+ | |||
+ | Step 9 - Review policy \\ | ||
+ | This API user now has the minimum rights required | ||
+ | \\ | ||
+ | |||
+ | |||
+ | ++++ | ||
==== Gateway name customization option ==== | ==== Gateway name customization option ==== | ||