Msg="gateway: configuration was not applied, gateway is not configured for managed configuration


#1

I have found two same issues on this forum, one the fix does not work for me, the other I do not understand what zyp568 means (I will place the links to both at foot of this)

Here are my logs, and I have spent three days now on this, and no further. The gateway (Lorixone) is receiving packets, but on route to the app-server I have the conf issue

lora-gateway-bridge is running on main linux server (I tried the OS on here, but had big issues)

Thank you for your help.

When run

 journalctl -f -n 100 -u lora-gateway-bridge

I see this
> Mar 29 18:00:24 lorasrv systemd[1]: Started LoRa Gateway Bridge.

 Mar 29 18:00:24 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:00:24Z" level=info            msg="starting LoRa Gateway Bridge" docs="https://www.loraserver.io/lora-gateway-bridge/" version=2.7.1
 Mar 29 18:00:24 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:00:24Z" level=info      msg="backend: set max reconnect interval: 10m0s"
 Mar 29 18:00:24 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:00:24Z" level=info msg="backend: TLS config is empty"
Mar 29 18:00:24 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:00:24Z" level=info msg="backend: connecting to mqtt broker" server="tcp://127.0.0.1:1883"
Mar 29 18:00:24 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:00:24Z" level=info msg="gateway: starting gateway udp listener" addr="0.0.0.0:1700"
Mar 29 18:00:24 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:00:24Z" level=info msg="backend: connected to mqtt broker"
Mar 29 18:00:27 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:00:27Z" level=info msg="backend: subscribing to topic" qos=0 topic=gateway/fcc23dfffe0a9473/tx
Mar 29 18:00:27 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:00:27Z" level=info msg="backend: subscribing to topic" qos=0 topic=gateway/fcc23dfffe0a9473/config
Mar 29 18:00:47 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:00:47Z" level=info msg="gateway: stat packet received" addr="10.0.60.171:38686" mac=fcc23dfffe0a9473
Mar 29 18:00:47 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:00:47Z" level=info msg="backend: publishing packet" qos=0 topic=gateway/fcc23dfffe0a9473/stats
Mar 29 18:00:47 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:00:47Z" level=info msg="backend: config packet received" topic=gateway/fcc23dfffe0a9473/config
Mar 29 18:00:47 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:00:47Z" level=warning msg="gateway: configuration was not applied, gateway is not configured for managed configuration" mac=fcc23dfffe0a9473

Mar 29 18:01:17 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:01:17Z" level=info msg="gateway: stat packet received" addr="10.0.60.171:38686" mac=fcc23dfffe0a9473

Mar 29 18:01:17 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:01:17Z" level=info msg="backend: publishing packet" qos=0 topic=gateway/fcc23dfffe0a9473/stats

Mar 29 18:01:17 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:01:17Z" level=info msg="backend: config packet received" topic=gateway/fcc23dfffe0a9473/config

Mar 29 18:01:17 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:01:17Z" level=warning msg="gateway: configuration was not applied, gateway is not configured for managed configuration" mac=fcc23dfffe0a9473

Mar 29 18:01:47 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:01:47Z" level=info msg="gateway: stat packet received" addr="10.0.60.171:38686" mac=fcc23dfffe0a9473

Mar 29 18:01:47 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:01:47Z" level=info msg="backend: publishing packet" qos=0 topic=gateway/fcc23dfffe0a9473/stats

Mar 29 18:01:47 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:01:47Z" level=info msg="backend: config packet received" topic=gateway/fcc23dfffe0a9473/config

Mar 29 18:01:47 lorasrv lora-gateway-bridge[2861]: time="2019-03-29T18:01:47Z" level=warning msg="gateway: configuration was not applied, gateway is not configured for managed configuration" mac=fcc23dfffe0a9473

When I run

sudo tcpdump -AUq port 1700

I see this

root@lorasrv:~# sudo tcpdump -AUq port 1700

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on enp2s0, link-type EN10MB (Ethernet), capture size 262144 bytes

17:28:09.248346 IP 10.0.60.171.43639 > lorasrv.1700: UDP, length 12

E…(.o@.@…;

.<.

.<o.w…t…4…=…

.s…

17:28:09.248921 IP lorasrv.1700 > 10.0.60.171.43639: UDP, length 4

E… …@.@…

.<o

.<…w…7…4.

17:28:17.226651 IP 10.0.60.171.38686 > lorasrv.1700: UDP, length 113

E…@.@…

.<.

.<o…y._…^…=…

.s{"stat":{"time":"2019-03-29 17:28:14 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0}}

17:28:17.227634 IP lorasrv.1700 > 10.0.60.171.38686: UDP, length 4

E… …@.@…

.<o

.<…7…^.

17:28:19.448224 IP 10.0.60.171.43639 > lorasrv.1700: UDP, length 12

E…(…@.@…

.<.

.<o.w…=…

.s…

17:28:19.448865 IP lorasrv.1700 > 10.0.60.171.43639: UDP, length 4

E… …@.@…

.<o

.<…w…7…

^C

6 packets captured

6 packets received by filter

0 packets dropped by kernel

When I check loraserver

Systemctl status loraserver

I get this

root@lorasrv:~# systemctl status loraserver

● loraserver.service - LoRa Server

Loaded: loaded (/lib/systemd/system/loraserver.service; enabled; vendor preset: enabled)

Active: active (running) since Fri 2019-03-29 17:13:43 UTC; 37min ago

Docs: https://www.loraserver.io/

Main PID: 2286 (loraserver)

CGroup: /system.slice/loraserver.service

└─2286 /usr/bin/loraserver

Mar 29 17:49:47 lorasrv loraserver[2286]: time="2019-03-29T17:49:47Z" level=info msg="gateway/mqtt: publishing gateway configuration" qos=0 topic=gateway/fcc23dfffe0a9473/config

Mar 29 17:49:47 lorasrv loraserver[2286]: time="2019-03-29T17:49:47Z" level=info msg="metrics saved" aggregation="[MINUTE HOUR DAY MONTH]" name="gw:fcc23dfffe0a9473"

Mar 29 17:50:17 lorasrv loraserver[2286]: time="2019-03-29T17:50:17Z" level=info msg="gateway/mqtt: gateway stats packet received" gateway_id=fcc23dfffe0a9473

Mar 29 17:50:17 lorasrv loraserver[2286]: time="2019-03-29T17:50:17Z" level=info msg="gateway updated" gateway_id=fcc23dfffe0a9473

Mar 29 17:50:17 lorasrv loraserver[2286]: time="2019-03-29T17:50:17Z" level=info msg="gateway/mqtt: publishing gateway configuration" qos=0 topic=gateway/fcc23dfffe0a9473/config

Mar 29 17:50:17 lorasrv loraserver[2286]: time="2019-03-29T17:50:17Z" level=info msg="metrics saved" aggregation="[MINUTE HOUR DAY MONTH]" name="gw:fcc23dfffe0a9473"

Mar 29 17:50:47 lorasrv loraserver[2286]: time="2019-03-29T17:50:47Z" level=info msg="gateway/mqtt: gateway stats packet received" gateway_id=fcc23dfffe0a9473

Mar 29 17:50:47 lorasrv loraserver[2286]: time="2019-03-29T17:50:47Z" level=info msg="gateway updated" gateway_id=fcc23dfffe0a9473

Mar 29 17:50:47 lorasrv loraserver[2286]: time="2019-03-29T17:50:47Z" level=info msg="gateway/mqtt: publishing gateway configuration" qos=0 topic=gateway/fcc23dfffe0a9473/config

Mar 29 17:50:47 lorasrv loraserver[2286]: time="2019-03-29T17:50:47Z" level=info msg="metrics saved" aggregation="[MINUTE HOUR DAY MONTH]" name="gw:fcc23dfffe0a9473"

When I run

Systemctl status lora-app-server

I get this

root@lorasrv:~# systemctl status lora-app-server

● lora-app-server.service - LoRa App Server

Loaded: loaded (/lib/systemd/system/lora-app-server.service; enabled; vendor preset: enabled)

Active: active (running) since Fri 2019-03-29 17:13:37 UTC; 38min ago

Docs: https://www.loraserver.io/

Main PID: 2268 (lora-app-server)

CGroup: /system.slice/lora-app-server.service

└─2268 /usr/bin/lora-app-server

Mar 29 17:49:28 lorasrv lora-app-server[2268]: time="2019-03-29T17:49:28Z" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=List grpc.service=api.OrganizationService grpc.

Mar 29 17:49:28 lorasrv lora-app-server[2268]: time="2019-03-29T17:49:28Z" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=List grpc.service=api.OrganizationService grpc.

Mar 29 17:49:28 lorasrv lora-app-server[2268]: time="2019-03-29T17:49:28Z" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=Get grpc.service=api.OrganizationService grpc.s

Mar 29 17:49:28 lorasrv lora-app-server[2268]: time="2019-03-29T17:49:28Z" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=Get grpc.service=api.OrganizationService grpc.s

Mar 29 17:49:29 lorasrv lora-app-server[2268]: time="2019-03-29T17:49:29Z" level=info msg="finished client unary call" grpc.code=OK grpc.method=GetGateway grpc.service=ns.NetworkServerService grpc.

Mar 29 17:49:29 lorasrv lora-app-server[2268]: time="2019-03-29T17:49:29Z" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=Get grpc.service=api.GatewayService grpc.start_

Mar 29 17:49:29 lorasrv lora-app-server[2268]: time="2019-03-29T17:49:29Z" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=List grpc.service=api.OrganizationService grpc.

Mar 29 17:49:29 lorasrv lora-app-server[2268]: time="2019-03-29T17:49:29Z" level=info msg="finished client unary call" grpc.code=OK grpc.method=GetGatewayStats grpc.service=ns.NetworkServerService

Mar 29 17:49:29 lorasrv lora-app-server[2268]: time="2019-03-29T17:49:29Z" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=GetStats grpc.service=api.GatewayService grpc.s

Mar 29 17:49:29 lorasrv lora-app-server[2268]: time="2019-03-29T17:49:29Z" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=Get grpc.service=api.OrganizationService grpc.s

lines 1-18/18 (END)

I run

System status lora-gateway-bridge

I get this

root@lorasrv:~# systemctl status lora-gateway-bridge

● lora-gateway-bridge.service - LoRa Gateway Bridge

Loaded: loaded (/lib/systemd/system/lora-gateway-bridge.service; enabled; vendor preset: enabled)

Active: active (running) since Fri 2019-03-29 17:13:31 UTC; 39min ago

Docs: https://www.loraserver.io/

Main PID: 2252 (lora-gateway-br)

CGroup: /system.slice/lora-gateway-bridge.service

└─2252 /usr/bin/lora-gateway-bridge

Mar 29 17:51:47 lorasrv lora-gateway-bridge[2252]: time="2019-03-29T17:51:47Z" level=info msg="backend: config packet received" topic=gateway/fcc23dfffe0a9473/config

Mar 29 17:51:47 lorasrv lora-gateway-bridge[2252]: time="2019-03-29T17:51:47Z" level=warning msg="gateway: configuration was not applied, gateway is not configured for managed configuration" mac=fc

Mar 29 17:52:17 lorasrv lora-gateway-bridge[2252]: time="2019-03-29T17:52:17Z" level=info msg="gateway: stat packet received" addr="10.0.60.171:38686" mac=fcc23dfffe0a9473

Mar 29 17:52:17 lorasrv lora-gateway-bridge[2252]: time="2019-03-29T17:52:17Z" level=info msg="backend: publishing packet" qos=0 topic=gateway/fcc23dfffe0a9473/stats

Mar 29 17:52:17 lorasrv lora-gateway-bridge[2252]: time="2019-03-29T17:52:17Z" level=info msg="backend: config packet received" topic=gateway/fcc23dfffe0a9473/config

Mar 29 17:52:17 lorasrv lora-gateway-bridge[2252]: time="2019-03-29T17:52:17Z" level=warning msg="gateway: configuration was not applied, gateway is not configured for managed configuration" mac=fc

Mar 29 17:52:47 lorasrv lora-gateway-bridge[2252]: time="2019-03-29T17:52:47Z" level=info msg="gateway: stat packet received" addr="10.0.60.171:38686" mac=fcc23dfffe0a9473

Mar 29 17:52:47 lorasrv lora-gateway-bridge[2252]: time="2019-03-29T17:52:47Z" level=info msg="backend: publishing packet" qos=0 topic=gateway/fcc23dfffe0a9473/stats

Mar 29 17:52:47 lorasrv lora-gateway-bridge[2252]: time="2019-03-29T17:52:47Z" level=info msg="backend: config packet received" topic=gateway/fcc23dfffe0a9473/config

Mar 29 17:52:47 lorasrv lora-gateway-bridge[2252]: time="2019-03-29T17:52:47Z" level=warning msg="gateway: configuration was not applied, gateway is not configured for managed configuration" mac=fc

lines 1-18/18 (END)

So I can see the gateway is talking to the bridge / lorasrv But im getting nothing plus I have the config issue above as you can see. I have deleted the gateway profile and also re entered it.

Here are the two same situations I face.
https://forum.loraserver.io/t/sos-warning-about-lora-gateway-bridge/3135
https://forum.loraserver.io/t/gateway-configuration-was-not-applied-gateway-is-not-configured-for-managed-configuration/2694

EDIT

Here is the start of the packet forwarder log file if it helps

*** Beacon Packet Forwarder for Lora Gateway ***
Version: 3.1.0
*** Lora concentrator HAL library version info ***
Version: 4.1.3;


INFO: Little endian host
INFO: found global configuration file global_conf.json, parsing it
INFO: global_conf.json does contain a JSON object named SX1301_conf, parsing SX1301 parameters
INFO: lorawan_public 1, clksrc 1
INFO: no configuration for LBT
INFO: antenna_gain 0 dBi
INFO: Configuring TX LUT with 16 indexes
INFO: radio 0 enabled (type SX1257), center frequency 904300000, RSSI offset -164.000000, tx enabled 1, tx_notch_freq 129000
INFO: radio 1 enabled (type SX1257), center frequency 905000000, RSSI offset -164.000000, tx enabled 0, tx_notch_freq 0
INFO: Lora multi-SF channel 0> radio 0, IF -400000 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora multi-SF channel 1> radio 0, IF -200000 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora multi-SF channel 2> radio 0, IF 0 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora multi-SF channel 3> radio 0, IF 200000 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora multi-SF channel 4> radio 1, IF -300000 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora multi-SF channel 5> radio 1, IF -100000 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora multi-SF channel 6> radio 1, IF 100000 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora multi-SF channel 7> radio 1, IF 300000 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora std channel> radio 0, IF 300000 Hz, 500000 Hz bw, SF 8
INFO: FSK channel 8 disabled
INFO: global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
INFO: gateway MAC address is configured to FCC23DFFFE0A9473
INFO: server hostname or IP address is configured to “10.0.60.111”
INFO: upstream port is configured to “1700”
INFO: downstream port is configured to “1700”
INFO: downstream keep-alive interval is configured to 10 seconds
INFO: statistics display interval is configured to 20 seconds
INFO: upstream PUSH_DATA time-out is configured to 100 ms
INFO: packets received with a valid CRC will be forwarded
INFO: packets received with a CRC error will NOT be forwarded
INFO: packets received with no CRC will NOT be forwarded
INFO: found local configuration file local_conf.json, parsing it
INFO: redefined parameters will overwrite global parameters
INFO: local_conf.json does not contain a JSON object named SX1301_conf
INFO: local_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
INFO: gateway MAC address is configured to FCC23DFFFE0A9473
INFO: packets received with a valid CRC will be forwarded
INFO: packets received with a CRC error will NOT be forwarded
INFO: packets received with no CRC will NOT be forwarded
INFO: Successfully contacted server 10.0.60.111
INFO: [main] concentrator started, packet can now be received

INFO: Disabling GPS mode for concentrator’s counter…
INFO: host/sx1301 time offset=(1553887385s:354022µs) - drift=-1717567706µs
INFO: Enabling GPS mode for concentrator’s counter.

INFO: [down] PULL_ACK received in 2 ms
INFO: [down] PULL_ACK received in 0 ms

2019-03-29 19:23:27 GMT

[UPSTREAM]

RF packets received by concentrator: 1

CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00%

RF packets forwarded: 0 (0 bytes)

PUSH_DATA datagrams sent: 0 (0 bytes)

PUSH_DATA acknowledged: 0.00%

[DOWNSTREAM]

PULL_DATA sent: 2 (100.00% acknowledged)

PULL_RESP(onse) datagrams received: 0 (0 bytes)

RF packets sent to concentrator: 0 (0 bytes)

TX errors: 0

BEACON queued: 0

BEACON sent so far: 0

BEACON rejected: 0

[JIT]

src/jitqueue.c:448:jit_print_queue(): INFO: [jit] queue is empty

[GPS]

GPS sync is disabled

END

JSON up: {“stat”:{“time”:“2019-03-29 19:23:27 GMT”,“rxnb”:1,“rxok”:0,“rxfw”:0,“ackr”:0.0,“dwnb”:0,“txnb”:0}}
INFO: [up] PUSH_ACK received in 1 ms
INFO: [down] PULL_ACK received in 0 ms
INFO: [down] PULL_ACK received in 0 ms

2019-03-29 19:23:47 GMT

[UPSTREAM]

RF packets received by concentrator: 0

CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%

RF packets forwarded: 0 (0 bytes)

PUSH_DATA datagrams sent: 1 (111 bytes)

PUSH_DATA acknowledged: 100.00%

[DOWNSTREAM]

PULL_DATA sent: 2 (100.00% acknowledged)

PULL_RESP(onse) datagrams received: 0 (0 bytes)

RF packets sent to concentrator: 0 (0 bytes)

TX errors: 0

BEACON queued: 0

BEACON sent so far: 0

BEACON rejected: 0

[JIT]

src/jitqueue.c:448:jit_print_queue(): INFO: [jit] queue is empty

[GPS]

GPS sync is disabled

END

JSON up: {“stat”:{“time”:“2019-03-29 19:23:47 GMT”,“rxnb”:0,“rxok”:0,“rxfw”:0,“ackr”:100.0,“dwnb”:0,“txnb”:0}}
INFO: [up] PUSH_ACK received in 1 ms
INFO: [down] PULL_ACK received in 0 ms
INFO: [down] PULL_ACK received in 0 ms

2019-03-29 19:24:07 GMT

[UPSTREAM]

RF packets received by concentrator: 0

CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%

RF packets forwarded: 0 (0 bytes)

PUSH_DATA datagrams sent: 1 (113 bytes)

PUSH_DATA acknowledged: 100.00%

[DOWNSTREAM]

PULL_DATA sent: 2 (100.00% acknowledged)

PULL_RESP(onse) datagrams received: 0 (0 bytes)

RF packets sent to concentrator: 0 (0 bytes)

TX errors: 0

BEACON queued: 0

BEACON sent so far: 0

BEACON rejected: 0

[JIT]

src/jitqueue.c:448:jit_print_queue(): INFO: [jit] queue is empty

[GPS]

GPS sync is disabled

END

INFO: Disabling GPS mode for concentrator’s counter…
INFO: host/sx1301 time offset=(1553887385s:353864µs) - drift=-158µs
INFO: Enabling GPS mode for concentrator’s counter.

JSON up: {“stat”:{“time”:“2019-03-29 19:24:07 GMT”,“rxnb”:0,“rxok”:0,“rxfw”:0,“ackr”:100.0,“dwnb”:0,“txnb”:0}}
INFO: [up] PUSH_ACK received in 1 ms
INFO: [down] PULL_ACK received in 0 ms
INFO: [down] PULL_ACK received in 0 ms

2019-03-29 19:24:27 GMT

[UPSTREAM]

RF packets received by concentrator: 0

CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%

RF packets forwarded: 0 (0 bytes)

PUSH_DATA datagrams sent: 1 (113 bytes)

PUSH_DATA acknowledged: 100.00%

[DOWNSTREAM]

PULL_DATA sent: 2 (100.00% acknowledged)

PULL_RESP(onse) datagrams received: 0 (0 bytes)

RF packets sent to concentrator: 0 (0 bytes)

TX errors: 0

BEACON queued: 0

BEACON sent so far: 0

BEACON rejected: 0

[JIT]

src/jitqueue.c:448:jit_print_queue(): INFO: [jit] queue is empty

[GPS]

GPS sync is disabled

END

JSON up: {“stat”:{“time”:“2019-03-29 19:24:27 GMT”,“rxnb”:0,“rxok”:0,“rxfw”:0,“ackr”:100.0,“dwnb”:0,“txnb”:0}}
INFO: [up] PUSH_ACK received in 1 ms
INFO: [down] PULL_ACK received in 0 ms
INFO: [down] PULL_ACK received in 0 ms

2019-03-29 19:24:47 GMT

[UPSTREAM]

RF packets received by concentrator: 0

CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%

RF packets forwarded: 0 (0 bytes)

PUSH_DATA datagrams sent: 1 (113 bytes)

PUSH_DATA acknowledged: 100.00%

[DOWNSTREAM]

PULL_DATA sent: 2 (100.00% acknowledged)

PULL_RESP(onse) datagrams received: 0 (0 bytes)

RF packets sent to concentrator: 0 (0 bytes)

TX errors: 0

BEACON queued: 0

BEACON sent so far: 0

BEACON rejected: 0

[JIT]

src/jitqueue.c:448:jit_print_queue(): INFO: [jit] queue is empty

[GPS]

GPS sync is disabled

END

JSON up: {“stat”:{“time”:“2019-03-29 19:24:47 GMT”,“rxnb”:0,“rxok”:0,“rxfw”:0,“ackr”:100.0,“dwnb”:0,“txnb”:0}}
INFO: [up] PUSH_ACK received in 1 ms
INFO: [down] PULL_ACK received in 0 ms
INFO: [down] PULL_ACK received in 0 ms

Thank you.