[BUG] Thread commissioning fails during FindOperational - Can't ping the device

Reproduction steps

(Re-)Create a new thread network
Get the thread dataset
Commission a Matter device using qrcode thread with chiptool using the previous dataset

During the commissioning, when you are at the step "Find Operational", if you see that it takes "anormal time" to finish, try to ping the resolved IPv6 from the computer running otbr-agent.

If you can't ping the device and the pairing failed, then you are on the problem

It appear 1/10 times, it's really hard to debug because when the pairing fails (failsafe timer expiration) the device is disconnected from Thread network.

Also note that when the problem happens, the command ot-ctl childip does not show any IP for the thread device, but the thread device correctly appear when you execute the commande ot-ctl child table

Bug prevalence

1/10

GitHub hash of the SDK that was being used

v1.0.0

Platform

android, nrf, raspi

Platform Version(s)

No response

Anything else?

Logs of the commissioner (here it's android chip-tool modified):

03-07 16:19:25.439 11506 11531 D CTL     : Performing next commissioning step 'FindOperational'
03-07 16:19:25.439 11506 11531 D CSM     : FindOrEstablishSession: PeerId = [1:000000000000002D]
03-07 16:19:25.439 11506 11531 D CSM     : FindOrEstablishSession: No existing OperationalSessionSetup instance found
03-07 16:19:25.440 11506 11531 D CTL     : OperationalSessionSetup[1:000000000000002D]: State change 1 --> 2
03-07 16:19:25.440 11506 11531 D DIS     : Resolving 5BB2BF7451309CA6:000000000000002D ...
03-07 16:19:25.469 11506 11531 D NsdManagerServiceResolver: resolve: Starting service resolution for '5BB2BF7451309CA6-000000000000002D' type '_matter._tcp'
03-07 16:19:25.470 11506 11531 D DMG     : ICR moving to [AwaitingDe]
03-07 16:19:25.640 11506 12147 D DIS     : Checking node lookup status after 200 ms
03-07 16:19:27.938 11506 12147 D DL      : Received SendWriteRequest
03-07 16:19:28.004 11506 11531 D chip.BluetoothManager: MatterLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
03-07 16:19:28.448 11506 12145 I NsdManagerServiceResolver: Resolved service '5BB2BF7451309CA6-000000000000002D' to /fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9
03-07 16:19:28.479 11506 12145 D DIS     :  ----- entry [0] : T 0
03-07 16:19:28.479 11506 12145 D DIS     :  ----- entry [1] : SAI 300
03-07 16:19:28.479 11506 12145 D DIS     :  ----- entry [2] : SII 5000
03-07 16:19:28.479 11506 12145 D DIS     : Node ID resolved for 5BB2BF7451309CA6:000000000000002D
03-07 16:19:28.479 11506 12145 D DIS     :  Hostname: fdaa:bbcc:ddee:0
03-07 16:19:28.479 11506 12145 D DIS     :  IP Address #1: fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9
03-07 16:19:28.479 11506 12145 D DIS     :  Port: 5540
03-07 16:19:28.479 11506 12145 D DIS     :  Mrp Interval idle: 5000 ms
03-07 16:19:28.479 11506 12145 D DIS     :  Mrp Interval active: 300 ms
03-07 16:19:28.479 11506 12145 D DIS     :  TCP Supported: 0
03-07 16:19:28.480 11506 12145 D DIS     : Lookup clearing interface for non LL address
03-07 16:19:28.480 11506 12145 D DIS     : UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540: new best score: 4
03-07 16:19:28.480 11506 12145 D DIS     : Checking node lookup status after 3041 ms
03-07 16:19:28.481 11506 12145 D DIS     : OperationalSessionSetup[1:000000000000002D]: Updating device address to UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540 while in state 2
03-07 16:19:28.481 11506 12145 D CTL     : OperationalSessionSetup[1:000000000000002D]: State change 2 --> 3
03-07 16:19:28.481 11506 12145 D IN      : SecureSession[0x7b383fd368]: Allocated Type:2 LSID:52281
03-07 16:19:28.481 11506 12145 D SC      : Initiating session on local FabricIndex 1 from 0x000000000001B669 -> 0x000000000000002D
03-07 16:19:28.499 11506 12145 D TOO     : KVS: Getting key f/1/g
03-07 16:19:28.499 11506 12145 D TOO     : KVS: Getting key f/1/k/0
03-07 16:19:28.500 11506 12145 D TOO     : KVS: Getting key f/1/s/000000000000002D
03-07 16:19:28.500 11506 12145 D KeyValueStoreManager: Key 'f/1/s/000000000000002D' not found in shared preferences
03-07 16:19:28.500 11506 12145 D EM      : <<< [E:5624i M:33095801] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
03-07 16:19:28.500 11506 12145 D IN      : (U) Sending msg 33095801 to IP address 'UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540'
03-07 16:19:28.501 11506 12145 D SC      : Sent Sigma1 msg
03-07 16:19:28.501 11506 12145 D CTL     : OperationalSessionSetup[1:000000000000002D]: State change 3 --> 4
03-07 16:19:30.478 11506 11531 D chip.BluetoothManager: MatterLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
03-07 16:19:32.981 11506 12147 D DL      : Received SendWriteRequest
03-07 16:19:33.086 11506 11531 D chip.BluetoothManager: MatterLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
03-07 16:19:35.021 11506 12147 D EM      : Retransmitting MessageCounter:33095801 on exchange 5624i Send Cnt 1
03-07 16:19:35.022 11506 12147 D IN      : (U) Sending msg 33095801 to IP address 'UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540'
03-07 16:19:35.564 11506 11531 D chip.BluetoothManager: MatterLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
03-07 16:19:38.066 11506 12147 D DL      : Received SendWriteRequest
03-07 16:19:38.168 11506 11531 D chip.BluetoothManager: MatterLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
03-07 16:19:40.644 11506 11531 D chip.BluetoothManager: MatterLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
03-07 16:19:41.895 11506 12147 D EM      : Retransmitting MessageCounter:33095801 on exchange 5624i Send Cnt 2
03-07 16:19:41.896 11506 12147 D IN      : (U) Sending msg 33095801 to IP address 'UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540'
03-07 16:19:43.146 11506 12147 D DL      : Received SendWriteRequest
03-07 16:19:43.250 11506 11532 D chip.BluetoothManager: MatterLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
03-07 16:19:45.730 11506 11532 D chip.BluetoothManager: MatterLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
03-07 16:19:48.232 11506 12147 D DL      : Received SendWriteRequest
03-07 16:19:48.292 11506 11532 D chip.BluetoothManager: MatterLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
03-07 16:19:50.768 11506 11532 D chip.BluetoothManager: MatterLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
03-07 16:19:51.068 11506 12147 D EM      : Retransmitting MessageCounter:33095801 on exchange 5624i Send Cnt 3
03-07 16:19:51.068 11506 12147 D IN      : (U) Sending msg 33095801 to IP address 'UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540'
03-07 16:19:51.714 11506 11532 D BluetoothGatt: onClientConnectionState() - status=19 clientIf=7 device=D4:44:06:2E:2E:A2
03-07 16:19:51.731 11506 11532 I chip.BluetoothManager: MatterLight.onConnectionStateChange status = 19, newState=0
03-07 16:19:51.732 11506 11532 D AndroidBleManager: onConnectionStateChange Disconnected
03-07 16:19:51.734 11506 11532 D IN      : Clearing BLE pending packets.
03-07 16:19:51.735 11506 11532 I chip.BluetoothManager|onConnectionStateChange: STATE_DISCONNECTED
03-07 16:20:05.642 11506 12147 D EM      : Retransmitting MessageCounter:33095801 on exchange 5624i Send Cnt 4
03-07 16:20:05.643 11506 12147 D IN      : (U) Sending msg 33095801 to IP address 'UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540'
03-07 16:20:29.224 11506 12147 E EM      : Failed to Send CHIP MessageCounter:33095801 on exchange 5624i sendCount: 4 max retries: 4
03-07 16:20:40.991 11506 12147 E SC      : CASESession timed out while waiting for a response from the peer. Current state was 1
03-07 16:20:40.991 11506 12147 D IN      : SecureSession[0x7b383fd368]: Released - Type:2 LSID:52281
03-07 16:20:41.020 11506 12147 D CTL     : Device connection failed. Error ../../src/protocols/secure_channel/CASESession.cpp:295: CHIP Error 0x00000032: Timeout
03-07 16:20:41.088 11506 12147 I MTMethods: sendEvent
03-07 16:20:41.092 11506 12147 I MTMethods: { NativeMap: {"data":"{\"nodeId\":\"45\",\"stage\":\"FindOperational\"}","code":"50","codeDescription":"SUCCESS","from":"onCommissioningStatusUpdate"} }
03-07 16:20:41.095 11506 12147 D CTL     : Error on commissioning step 'FindOperational': '../../src/protocols/secure_channel/CASESession.cpp:295: CHIP Error 0x00000032: Timeout'
03-07 16:20:41.095 11506 12147 E CTL     : Failed to perform commissioning step 18
03-07 16:20:41.095 11506 12147 D CTL     : Going from commissioning step 'FindOperational' with lastErr = '../../src/protocols/secure_channel/CASESession.cpp:295: CHIP Error 0x00000032: Timeout' -> 'Cleanup'
03-07 16:20:41.096 11506 12147 D CTL     : Performing next commissioning step 'Cleanup' with completion status = '../../src/protocols/secure_channel/CASESession.cpp:295: CHIP Error 0x00000032: Timeout'
03-07 16:20:41.097 11506 12147 I MTMethods: sendEvent
03-07 16:20:41.097 11506 12147 I MTMethods: { NativeMap: {"data":"{\"nodeId\":\"45\",\"stage\":\"Cleanup\"}","code":"0","codeDescription":"SUCCESS","from":"onCommissioningStatusUpdate"} }
03-07 16:20:41.098 11506 12147 D CTL     : Successfully finished commissioning step 'Cleanup'
03-07 16:20:41.101 11506 12147 I MTMethods: sendEvent
03-07 16:20:41.101 11506 12147 I MTMethods: { NativeMap: {"data":"","code":"50","codeDescription":"FAILURE","from":"onCommissioningComplete"} }

Logs of the device (nRF52840 running the lighting app example):

[00:00:31.024,108] <inf> chip: [ZCL]OpCreds: Received an AddNOC command
[00:00:31.028,533] <inf> chip: [FP]Validating NOC chain
[00:00:31.087,188] <inf> chip: [FP]NOC chain validation successful
[00:00:31.087,341] <inf> chip: [FP]Added new fabric at index: 0x1
[00:00:31.087,585] <inf> chip: [FP]Assigned compressed fabric ID: 0x5BB2BF7451309CA6, node ID: 0x000000000000002D
[00:00:31.087,768] <inf> chip: [TS]Last Known Good Time: 2023-03-07T14:02:11
[00:00:31.087,951] <inf> chip: [TS]New proposed Last Known Good Time: 2021-06-10T00:00:00
[00:00:31.088,043] <inf> chip: [TS]Retaining current Last Known Good Time
[00:00:31.088,226] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_003E update version to 1a7d840
[00:00:31.088,439] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_003E update version to 1a7d841
[00:00:31.122,528] <dbg> chip: LogV: [EVL]LogEvent event number: 0x0000000000000002 priority: 1, endpoint id:  0x0 cluster id: 0x0000_001F event id: 0x0 Sys timestamp: 0x0000000000007991
[00:00:31.122,711] <inf> chip: [ZCL]OpCreds: ACL entry created for Fabric index 0x1 CASE Admin Subject 0x000000000001B669
[00:00:31.122,802] <dbg> chip: LogV: [DL]Using Thread extended MAC for hostname.
[00:00:31.122,985] <inf> chip: [DIS]Advertise operational node 5BB2BF7451309CA6-000000000000002D
[00:00:31.123,260] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_003E update version to 1a7d842
[00:00:31.123,474] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_003E update version to 1a7d843
[00:00:31.123,596] <dbg> chip: LogV: [DMG]Command handler moving to [ Preparing]
[00:00:31.123,718] <dbg> chip: LogV: [DMG]Command handler moving to [AddingComm]
[00:00:31.123,840] <dbg> chip: LogV: [DMG]Command handler moving to [AddedComma]
[00:00:31.123,931] <inf> chip: [ZCL]OpCreds: successfully created fabric index 0x1 via AddNOC
[00:00:31.124,267] <dbg> chip: LogV: [DMG]Decreasing reference count for CommandHandler, remaining 0
[00:00:31.125,213] <inf> chip: [EM]<<< [E:5621r M:116813147] (S) Msg TX to 1:FFFFFFFB00000000 [9CA6] --- Type 0001:09 (IM:InvokeCommandResponse)
[00:00:31.125,366] <inf> chip: [IN](S) Sending msg 116813147 on secure session with LSID: 41506
[00:00:31.125,549] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
[00:00:31.125,915] <dbg> chip: LogV: [DMG]Command handler moving to [CommandSen]
[00:00:31.126,007] <dbg> chip: LogV: [DMG]Command handler moving to [AwaitingDe]
[00:00:31.126,159] <err> chip: [DL]Long dispatch time: 106 ms, for event type 16388
[00:00:31.200,286] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:31.201,446] <dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
[00:00:31.203,033] <inf> chip: [EM]>>> [E:5622r M:6963398] (S) Msg RX from 1:FFFFFFFB00000000 [9CA6] --- Type 0001:08 (IM:InvokeCommandRequest)
[00:00:31.203,186] <dbg> chip: LogV: [EM]Handling via exchange: 5622r, Delegate: 0x20010c44
[00:00:31.203,857] <dbg> chip: LogV: [DMG]Received command for Endpoint=0 Cluster=0x0000_0031 Command=0x0000_0003
[00:00:31.210,113] <dbg> chip: LogV: [DMG]Command handler moving to [ Preparing]
[00:00:31.210,205] <dbg> chip: LogV: [DMG]Command handler moving to [AddingComm]
[00:00:31.210,357] <dbg> chip: LogV: [DMG]Command handler moving to [AddedComma]
[00:00:31.210,571] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_0030 update version to ac6117b6
[00:00:31.210,876] <dbg> chip: LogV: [DMG]Decreasing reference count for CommandHandler, remaining 0
[00:00:31.211,791] <inf> chip: [EM]<<< [E:5622r M:116813148] (S) Msg TX to 1:FFFFFFFB00000000 [9CA6] --- Type 0001:09 (IM:InvokeCommandResponse)
[00:00:31.211,975] <inf> chip: [IN](S) Sending msg 116813148 on secure session with LSID: 41506
[00:00:31.212,158] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
[00:00:31.212,524] <dbg> chip: LogV: [DMG]Command handler moving to [CommandSen]
[00:00:31.212,615] <dbg> chip: LogV: [DMG]Command handler moving to [AwaitingDe]
[00:00:31.291,168] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:31.291,320] <dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
[00:00:31.292,449] <inf> chip: [EM]>>> [E:5623r M:6963399] (S) Msg RX from 1:FFFFFFFB00000000 [9CA6] --- Type 0001:08 (IM:InvokeCommandRequest)
[00:00:31.292,633] <dbg> chip: LogV: [EM]Handling via exchange: 5623r, Delegate: 0x20010c44
[00:00:31.293,304] <dbg> chip: LogV: [DMG]Received command for Endpoint=0 Cluster=0x0000_0031 Command=0x0000_0006
[00:00:31.309,478] <dbg> chip: LogV: [DMG]Decreasing reference count for CommandHandler, remaining 1
[00:00:31.309,661] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x101fc100)
[00:00:31.309,722] <dbg> chip: LogV: [DL]   Network Name: OpenThread-c37e
[00:00:31.309,814] <dbg> chip: LogV: [DL]   PAN Id: 0xC37E
[00:00:31.309,997] <dbg> chip: LogV: [DL]   Extended PAN Id: 0x1B1EF3DC76FCCEF8
[00:00:31.310,089] <dbg> chip: LogV: [DL]   Channel: 11
[00:00:31.310,211] <dbg> chip: LogV: [DL]   Mesh Prefix: fd0d:ef30:fec0:af6a::/64
[00:00:31.312,774] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x1100101d)
[00:00:31.312,835] <dbg> chip: LogV: [DL]   Device Role: DETACHED
[00:00:31.312,896] <dbg> chip: LogV: [DL]   Thread Unicast Addresses:
[00:00:31.313,079] <dbg> chip: LogV: [DL]        fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7/64 valid
[00:00:31.313,232] <dbg> chip: LogV: [DL]        fe80::30c0:9410:3f56:dc97/64 valid preferred
[00:00:32.542,724] <inf> chip: [DL]SRP Client was started, detected server: fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c
[00:00:32.544,433] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x200012a4)
[00:00:32.544,525] <dbg> chip: LogV: [DL]   Device Role: CHILD
[00:00:32.544,616] <dbg> chip: LogV: [DL]   Partition Id: 0x40358B7D
[00:00:32.547,180] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x00000001)
[00:00:32.547,241] <dbg> chip: LogV: [DL]   Thread Unicast Addresses:
[00:00:32.547,393] <dbg> chip: LogV: [DL]        fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9/64 valid preferred
[00:00:32.547,576] <dbg> chip: LogV: [DL]        fd0d:ef30:fec0:af6a:0:ff:fe00:e801/64 valid rloc
[00:00:32.547,760] <dbg> chip: LogV: [DL]        fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7/64 valid
[00:00:32.547,912] <dbg> chip: LogV: [DL]        fe80::30c0:9410:3f56:dc97/64 valid preferred
[00:00:32.550,994] <dbg> chip: LogV: [DMG]Command handler moving to [ Preparing]
[00:00:32.551,116] <dbg> chip: LogV: [DMG]Command handler moving to [AddingComm]
[00:00:32.551,239] <dbg> chip: LogV: [DMG]Command handler moving to [AddedComma]
[00:00:32.551,452] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_0030 update version to ac6117b7
[00:00:32.551,605] <dbg> chip: LogV: [DMG]Decreasing reference count for CommandHandler, remaining 0
[00:00:32.723,266] <inf> chip: [EM]<<< [E:5623r M:116813149] (S) Msg TX to 1:FFFFFFFB00000000 [9CA6] --- Type 0001:09 (IM:InvokeCommandResponse)
[00:00:32.723,449] <inf> chip: [IN](S) Sending msg 116813149 on secure session with LSID: 41506
[00:00:32.723,602] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 70)
[00:00:32.723,999] <dbg> chip: LogV: [DMG]Command handler moving to [CommandSen]
[00:00:32.724,090] <dbg> chip: LogV: [DMG]Command handler moving to [AwaitingDe]
[00:00:32.724,182] <err> chip: [DL]Long dispatch time: 174 ms, for event type 3
[00:00:32.724,304] <dbg> chip: LogV: [DL]Using Thread extended MAC for hostname.
[00:00:32.724,517] <inf> chip: [DIS]Advertise operational node 5BB2BF7451309CA6-000000000000002D
[00:00:32.724,639] <inf> chip: [SVR]Operational advertising enabled
[00:00:32.854,553] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:33.274,200] <dbg> chip: LogV: [DL]SRP update succeeded
[00:00:33.274,291] <inf> chip: [DIS]Setting operational delegate post init
[00:00:33.274,688] <inf> chip: [DIS]Updating services using commissioning mode 0
[00:00:33.274,780] <dbg> chip: LogV: [DL]Using Thread extended MAC for hostname.
[00:00:33.274,993] <inf> chip: [DIS]Advertise operational node 5BB2BF7451309CA6-000000000000002D
[00:00:33.275,482] <inf> chip: [DL]advertising srp service: 5BB2BF7451309CA6-000000000000002D._matter._tcp
[00:00:33.275,756] <dbg> chip: LogV: [DL]Using Thread extended MAC for hostname.
[00:00:33.277,069] <inf> chip: [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=0
[00:00:33.277,648] <inf> chip: [DL]advertising srp service: 8CCEED038B98779A._matterc._udp
[00:00:34.519,989] <dbg> chip: LogV: [DL]SRP update succeeded
[00:00:35.250,610] <dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
[00:00:37.751,251] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
[00:00:37.815,643] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:38.833,404] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x00000064)
[00:00:38.833,465] <dbg> chip: LogV: [DL]   Device Role: ROUTER
[00:00:40.335,784] <dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
[00:00:42.835,449] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
[00:00:42.900,817] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:43.551,757] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x00000200)
[00:00:45.420,989] <dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
[00:00:47.921,661] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
[00:00:47.986,022] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:50.506,195] <dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
[00:00:53.006,835] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
[00:00:53.071,228] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:55.546,386] <dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
[00:00:58.047,027] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
[00:00:58.111,419] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:58.963,745] <inf> chip: [FS]Fail-safe timer expired
[00:00:58.963,836] <err> chip: [SVR]Failsafe timer expired
[00:00:58.964,019] <dbg> chip: LogV: [IN]SecureSession[0x20002d10]: MarkForEviction Type:1 LSID:41506
[00:00:58.964,172] <inf> chip: [SC]SecureSession[0x20002d10]: Moving from state 'kActive' --> 'kPendingEviction'
[00:00:58.964,324] <dbg> chip: LogV: [IN]SecureSession[0x20002d10]: Released - Type:1 LSID:41506
[00:00:58.964,447] <err> chip: [SVR]Commissioning failed (attempt 1): 32
[00:00:58.964,508] <dbg> chip: LogV: [IN]Clearing BLE pending packets.
[00:00:58.964,599] <inf> chip: [BLE]Releasing end point's BLE connection back to application.
[00:00:58.964,691] <inf> chip: [DL]Closing BLE GATT connection (ConnId 00)
[00:00:58.969,573] <dbg> chip: LogV: [IN]SecureSession[0x20002d10]: Allocated Type:1 LSID:41508
[00:00:58.969,665] <dbg> chip: LogV: [SC]Assigned local session key ID 41508
[00:00:58.969,787] <dbg> chip: LogV: [SC]Waiting for PBKDF param request
[00:00:58.969,879] <dbg> chip: LogV: [DL]CHIPoBLE advertising set to on
[00:00:58.970,001] <inf> chip: [DIS]Updating services using commissioning mode 1
[00:00:58.970,123] <dbg> chip: LogV: [DL]Using Thread extended MAC for hostname.
[00:00:58.970,306] <inf> chip: [DIS]Advertise operational node 5BB2BF7451309CA6-000000000000002D
[00:00:58.970,886] <dbg> chip: LogV: [DL]Using Thread extended MAC for hostname.
[00:00:58.972,198] <inf> chip: [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=1
[00:00:58.972,869] <inf> chip: [DL]advertising srp service: 8CCEED038B98779A._matterc._udp
[00:00:58.973,175] <err> chip: [ZCL]OpCreds: Got FailSafeTimerExpired
[00:00:58.973,297] <err> chip: [ZCL]OpCreds: Proceeding to FailSafeCleanup on fail-safe expiry!
[00:00:58.973,358] <dbg> chip: LogV: [IN]Expiring all sessions for fabric 0x1!!
[00:00:58.973,480] <err> chip: [FP]Reverting pending fabric data for fabric 0x1
[00:00:58.973,968] <dbg> chip: LogV: [EVL]LogEvent event number: 0x0000000000000003 priority: 1, endpoint id:  0x0 cluster id: 0x0000_0028 event id: 0x2 Sys timestamp: 0x000000000000E65D
[00:00:58.974,090] <dbg> chip: LogV: [DMG]All ReadHandler-s are clean, clear GlobalDirtySet
[00:00:58.975,311] <err> chip: [FP]Warning: metadata not found during delete of fabric 0x1
[00:00:59.071,594] <inf> chip: [FP]Fabric (0x1) deleted.
[00:00:59.071,685] <inf> chip: [ZCL]UserLabel: Last Fabric index 0x1 was removed
[00:00:59.072,906] <inf> chip: [ZCL]OpCreds: Fabric index 0x1 was removed
[00:00:59.074,096] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_003E update version to 1a7d844
[00:00:59.074,310] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_003E update version to 1a7d845
[00:00:59.214,141] <inf> chip: [TS]Pending Last Known Good Time: 2023-03-07T14:02:11
[00:00:59.215,393] <inf> chip: [TS]Previous Last Known Good Time: 2023-03-07T14:02:11
[00:00:59.215,484] <inf> chip: [TS]Reverted Last Known Good Time to previous value
[00:00:59.215,942] <dbg> chip: LogV: [EVL]LogEvent event number: 0x0000000000000004 priority: 1, endpoint id:  0x0 cluster id: 0x0000_0028 event id: 0x2 Sys timestamp: 0x000000000000E74F
[00:00:59.216,064] <dbg> chip: LogV: [DMG]All ReadHandler-s are clean, clear GlobalDirtySet
[00:00:59.217,254] <err> chip: [FP]Warning: metadata not found during delete of fabric 0x1
[00:00:59.221,740] <err> chip: [ZCL]OpCreds: failed to delete fabric at index 1: d8
[00:00:59.221,954] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_0030 update version to ac6117b8
[00:00:59.222,045] <dbg> chip: LogV: [ZCL]Failsafe timeout, tell platform driver to revert network credentials.
[00:00:59.222,808] <inf> chip: [NP]Reverting Thread operational dataset
[00:00:59.232,421] <err> chip: [DL]Long dispatch time: 269 ms, for event type 32782
[00:00:59.232,543] <inf> chip: [FS]Fail-safe cleanly disarmed
[00:00:59.234,680] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x11002046)
[00:00:59.234,741] <dbg> chip: LogV: [DL]   Device Role: DISABLED
[00:00:59.234,802] <dbg> chip: LogV: [DL]   Thread Unicast Addresses:
[00:00:59.234,985] <dbg> chip: LogV: [DL]        fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9/64 valid preferred
[00:00:59.236,297] <inf> chip: [DL]BLE GAP connection terminated (reason 0x16)
[00:00:59.236,419] <inf> chip: [DL]Current number of connections: 0/1
[00:00:59.239,196] <inf> chip: [DL]CHIPoBLE advertising started
[00:00:59.241,516] <inf> chip: [DL]NFC Tag emulation started
[00:01:29.240,020] <inf> chip: [DL]CHIPoBLE advertising mode changed to slow

I am using the stack v1.0.0

What we see on the logs:

The IPv6 address is correctly discovered using mDNS
The resolved IPv6 is the same as the IPv6 address on the device logs
The computer that runs otbr-agent was not able to ping the IPv6

Here are the logs of otbr-agent:

Mar  7 16:19:23 otbr-agent[114]: 00:00:07.813 [I] NetDataPublshr: DNS/SRP service (state:Adding) - update in 709 msec
Mar  7 16:19:23 otbr-agent[114]: [INFO]-BA------: Thread is up
Mar  7 16:19:23 otbr-agent[114]: [INFO]-BA------: Publish meshcop service OpenThread Border Router #245A._meshcop._udp.local.
Mar  7 16:19:23 otbr-agent[114]: [INFO]-MDNS----: Removing existing service OpenThread Border Router #245A._meshcop._udp: outdated
Mar  7 16:19:23 otbr-agent[114]: [INFO]-MDNS----: Removing service OpenThread Border Router #245A._meshcop._udp
Mar  7 16:19:23 otbr-agent[114]: [INFO]-MDNS----: Releasing avahi entry group @0x29d7f0
Mar  7 16:19:23 otbr-agent[114]: [INFO]-MDNS----: Commit avahi service OpenThread Border Router #245A._meshcop._udp
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.848 [I] Platform------: [netif] Succeeded to process request#3
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.848 [I] NetworkData---: Received network data registration
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.848 [I] NetworkData---: Allocated Context ID = 1
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.848 [I] NetworkData---: Sent network data registration acknowledgment
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.850 [I] Platform------: [netif] Message dropped by Thread
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.850 [I] Platform------: [netif] Succeeded to process request#4
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.852 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:2 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.852 [I] Platform------: [netif] ADD [M] ff33:40:fd0d:ef30:fec0:af6a:0:1 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.852 [I] Platform------: [netif] ADD [M] ff32:40:fd0d:ef30:fec0:af6a:0:1 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.852 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:fb (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.852 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:fc (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.852 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:1 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.852 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:16 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.852 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:2 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.852 [I] Notifier------: StateChanged (0x00000200) [NetData]
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.852 [I] Mle-----------: Send Data Response (ff02:0:0:0:0:0:0:1)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.852 [I] BbrLeader-----: PBBR state: None
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.852 [I] BbrLeader-----: Domain Prefix: ::/0, state: None
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.863 [I] Settings------: Saved SlaacIidSecretKey
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.863 [I] Slaac---------: Generated and saved secret key
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.863 [I] Slaac---------: Adding address fdaa:bbcc:ddee:0:87ef:d332:1f87:f871
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.865 [I] Platform------: [netif] Sent request#5 to add fdaa:bbcc:ddee:0:87ef:d332:1f87:f871/64
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.865 [I] BorderRouter--: Allow default route in netdata: no -> yes
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.865 [I] BorderRouter--: Start evaluating routing policy, scheduled in 336 milliseconds
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.865 [I] NetDataPublshr: DNS/SRP service (state:Adding) in netdata - total:0, preferred:0, desired:2
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.869 [I] Platform------: [netif] Message dropped by Thread
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.869 [I] Platform------: [netif] ADD [U] fd0d:ef30:fec0:af6a:0:ff:fe00:e800 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.871 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:2 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.871 [I] Platform------: [netif] ADD [M] ff33:40:fd0d:ef30:fec0:af6a:0:1 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.871 [I] Platform------: [netif] ADD [M] ff32:40:fd0d:ef30:fec0:af6a:0:1 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.871 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:fb (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.871 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:fc (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.871 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:1 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.871 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:16 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.872 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:2 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.872 [I] Notifier------: StateChanged (0x00000001) [Ip6+]
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.874 [I] Platform------: [netif] ADD [U] fd0d:ef30:fec0:af6a:0:ff:fe00:fc00 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.875 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:2 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.876 [I] Platform------: [netif] ADD [M] ff33:40:fd0d:ef30:fec0:af6a:0:1 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.876 [I] Platform------: [netif] ADD [M] ff32:40:fd0d:ef30:fec0:af6a:0:1 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.876 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:fb (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.876 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:fc (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.876 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:1 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.876 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:16 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.876 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:2 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.876 [I] Platform------: [netif] Message dropped by Thread
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.876 [I] Platform------: [netif] ADD [U] fdaa:bbcc:ddee:0:87ef:d332:1f87:f871 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.876 [I] Platform------: [netif] Succeeded to process request#5
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.892 [I] MeshForwarder-: Sent IPv6 UDP msg, len:96, chksum:a3a1, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.892 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.892 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.915 [I] MeshForwarder-: Sent IPv6 UDP msg, len:118, chksum:0f04, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.915 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:23 otbr-agent[114]: 00:00:07.915 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.022 [I] MeshForwarder-: Sent IPv6 UDP msg, len:356, chksum:cef9, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.022 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.022 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.104 [I] MeshForwarder-: Sent IPv6 UDP msg, len:299, chksum:cf07, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.104 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.104 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.202 [I] BorderRouter--: Evaluating routing policy
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.202 [I] BorderRouter--: RouterAdvert: Added RIO for fdaa:bbcc:ddee:0::/64 (lifetime=1800)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.203 [I] BorderRouter--: Sent Router Advertisement on infra netif 21
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.203 [I] BorderRouter--: Start evaluating routing policy, scheduled in 16000 milliseconds
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.204 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.209 [I] MeshForwarder-: Sent IPv6 UDP msg, len:406, chksum:2712, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.209 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.209 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.226 [I] Platform------: [netif] Message dropped by Thread
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.227 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:2 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.228 [I] Platform------: [netif] ADD [M] ff33:40:fd0d:ef30:fec0:af6a:0:1 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.228 [I] Platform------: [netif] ADD [M] ff32:40:fd0d:ef30:fec0:af6a:0:1 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.228 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:fb (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.228 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:fc (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.228 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:1 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.228 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:16 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.228 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:2 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.235 [I] MeshForwarder-: Sent IPv6 UDP msg, len:107, chksum:418c, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.235 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.235 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.323 [I] BorderRouter--: Router solicitation times out
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.324 [I] BorderRouter--: Received Router Solicitation from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.324 [I] BorderRouter--: Start evaluating routing policy, scheduled in 2879 milliseconds
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.324 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.370 [I] MeshForwarder-: Sent IPv6 UDP msg, len:406, chksum:2712, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.370 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.370 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.370 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.391 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:8af8, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.391 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.391 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.522 [I] NetDataPublshr: DNS/SRP service - State: Adding -> Added
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.522 [I] SrpServer-----: Start listening on port 53535
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.523 [I] NetworkData---: Sent server data notification
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.523 [I] NetworkData---: Received network data registration
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.523 [I] NetworkData---: Allocated Service ID = 0
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.523 [I] NetworkData---: Sent network data registration acknowledgment
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.523 [I] Notifier------: StateChanged (0x00000200) [NetData]
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.523 [I] Mle-----------: Send Data Response (ff02:0:0:0:0:0:0:1)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.523 [I] BbrLeader-----: PBBR state: None
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.523 [I] BbrLeader-----: Domain Prefix: ::/0, state: None
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.524 [I] Platform------: [netif] Sent request#6 to add fd0d:ef30:fec0:af6a:0:ff:fe00:fc10/64
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.524 [I] BorderRouter--: Start evaluating routing policy, scheduled in 2679 milliseconds
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.524 [I] NetDataPublshr: DNS/SRP service (state:Added) in netdata - total:1, preferred:0, desired:2
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.525 [I] Notifier------: StateChanged (0x00000001) [Ip6+]
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.527 [I] Platform------: [netif] ADD [U] fd0d:ef30:fec0:af6a:0:ff:fe00:fc10 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.527 [I] Platform------: [netif] Message dropped by Thread
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.527 [I] Platform------: [netif] Succeeded to process request#6
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.529 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:2 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.529 [I] Platform------: [netif] ADD [M] ff33:40:fd0d:ef30:fec0:af6a:0:1 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.529 [I] Platform------: [netif] ADD [M] ff32:40:fd0d:ef30:fec0:af6a:0:1 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.529 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:fb (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.529 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:fc (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.529 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:1 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.529 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:16 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.529 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:2 (already subscribed, ignored)
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.562 [I] MeshForwarder-: Sent IPv6 UDP msg, len:145, chksum:a15d, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.562 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.562 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.642 [I] MeshForwarder-: Sent IPv6 UDP msg, len:406, chksum:2712, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.642 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.642 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.667 [I] MeshForwarder-: Sent IPv6 UDP msg, len:107, chksum:418c, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.667 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:23 otbr-agent[114]: 00:00:08.667 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:24 otbr-agent[114]: [INFO]-MDNS----: Avahi group (@0x29c4a8) is established
Mar  7 16:19:24 otbr-agent[114]: [INFO]-BA------: Result of publish meshcop service OpenThread Border Router #245A._meshcop._udp.local: OK
Mar  7 16:19:24 otbr-agent[114]: 00:00:08.815 [I] MeshForwarder-: Sent IPv6 UDP msg, len:320, chksum:b45e, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:24 otbr-agent[114]: 00:00:08.815 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:24 otbr-agent[114]: 00:00:08.815 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:24 otbr-agent[114]: 00:00:08.869 [I] MeshForwarder-: Sent IPv6 UDP msg, len:195, chksum:59be, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:24 otbr-agent[114]: 00:00:08.869 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:24 otbr-agent[114]: 00:00:08.869 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:24 otbr-agent[114]: 00:00:09.226 [I] Platform------: [netif] Message dropped by Thread
Mar  7 16:19:24 otbr-agent[114]: 00:00:09.228 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:2 (already subscribed, ignored)
Mar  7 16:19:24 otbr-agent[114]: 00:00:09.228 [I] Platform------: [netif] ADD [M] ff33:40:fd0d:ef30:fec0:af6a:0:1 (already subscribed, ignored)
Mar  7 16:19:24 otbr-agent[114]: 00:00:09.228 [I] Platform------: [netif] ADD [M] ff32:40:fd0d:ef30:fec0:af6a:0:1 (already subscribed, ignored)
Mar  7 16:19:24 otbr-agent[114]: 00:00:09.228 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:fb (already subscribed, ignored)
Mar  7 16:19:24 otbr-agent[114]: 00:00:09.228 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:fc (already subscribed, ignored)
Mar  7 16:19:24 otbr-agent[114]: 00:00:09.228 [I] Platform------: [netif] ADD [M] ff03:0:0:0:0:0:0:1 (already subscribed, ignored)
Mar  7 16:19:24 otbr-agent[114]: 00:00:09.228 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:16 (already subscribed, ignored)
Mar  7 16:19:24 otbr-agent[114]: 00:00:09.228 [I] Platform------: [netif] ADD [M] ff02:0:0:0:0:0:0:2 (already subscribed, ignored)
Mar  7 16:19:25 otbr-agent[114]: 00:00:09.802 [I] MeshForwarder-: Received IPv6 UDP msg, len:84, chksum:9f84, ecn:no, from:32c094103f56dc97, sec:no, prio:net, rss:-57.0
Mar  7 16:19:25 otbr-agent[114]: 00:00:09.802 [I] MeshForwarder-:     src:[fe80:0:0:0:30c0:9410:3f56:dc97]:19788
Mar  7 16:19:25 otbr-agent[114]: 00:00:09.802 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788
Mar  7 16:19:25 otbr-agent[114]: 00:00:09.802 [I] Mle-----------: Receive Parent Request (fe80:0:0:0:30c0:9410:3f56:dc97)
Mar  7 16:19:25 otbr-agent[114]: 00:00:09.802 [I] Mle-----------: Delay Parent Response (fe80:0:0:0:30c0:9410:3f56:dc97)
Mar  7 16:19:25 otbr-agent[114]: 00:00:09.923 [I] Mle-----------: Send delayed message (fe80:0:0:0:30c0:9410:3f56:dc97)
Mar  7 16:19:25 otbr-agent[114]: 00:00:09.936 [I] MeshForwarder-: Sent IPv6 UDP msg, len:348, chksum:681f, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:25 otbr-agent[114]: 00:00:09.936 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:25 otbr-agent[114]: 00:00:09.936 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:25 otbr-agent[114]: 00:00:09.963 [I] MeshForwarder-: Sent IPv6 UDP msg, len:129, chksum:cb46, ecn:no, to:32c094103f56dc97, sec:no, prio:net
Mar  7 16:19:25 otbr-agent[114]: 00:00:09.963 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:25 otbr-agent[114]: 00:00:09.963 [I] MeshForwarder-:     dst:[fe80:0:0:0:30c0:9410:3f56:dc97]:19788
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.010 [I] MeshForwarder-: Sent IPv6 UDP msg, len:167, chksum:e242, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.010 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.010 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.334 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.355 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:b0cc, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.355 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.355 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.558 [I] MeshForwarder-: Received IPv6 UDP msg, len:114, chksum:fae0, ecn:no, from:32c094103f56dc97, sec:no, prio:net, rss:-57.0
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.558 [I] MeshForwarder-:     src:[fe80:0:0:0:30c0:9410:3f56:dc97]:19788
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.558 [I] MeshForwarder-:     dst:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.558 [I] Mle-----------: Receive Child ID Request (fe80:0:0:0:30c0:9410:3f56:dc97)
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.575 [I] Settings------: Added ChildInfo {rloc:0xe801, extaddr:32c094103f56dc97, timeout:240, mode:0x0f, version:4}
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.575 [I] Mle-----------: Send Child ID Response (fe80:0:0:0:30c0:9410:3f56:dc97,0xe801)
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.575 [I] Notifier------: StateChanged (0x00000400) [Child+]
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.575 [I] ChildSupervsn-: Starting Child Supervision
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.625 [I] MeshForwarder-: Sent IPv6 UDP msg, len:161, chksum:ffcf, ecn:no, to:32c094103f56dc97, sec:yes, prio:net
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.625 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:25 otbr-agent[114]: 00:00:10.625 [I] MeshForwarder-:     dst:[fe80:0:0:0:30c0:9410:3f56:dc97]:19788
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.204 [I] BorderRouter--: Evaluating routing policy
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.204 [I] BorderRouter--: RouterAdvert: Added RIO for fdaa:bbcc:ddee:0::/64 (lifetime=1800)
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.204 [I] BorderRouter--: Sent Router Advertisement on infra netif 21
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.204 [I] BorderRouter--: Start evaluating routing policy, scheduled in 16000 milliseconds
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.205 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.343 [I] MeshForwarder-: Received IPv6 HopOpts msg, len:86, chksum:0000, ecn:no, from:0xe801, sec:yes, prio:normal, rss:-57.0
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.343 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:0:ff:fe00:e801]
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.343 [I] MeshForwarder-:     dst:[ff03:0:0:0:0:0:0:2]
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.344 [I] AddrResolver--: Received address query from 0xe801 for target fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.344 [I] AddrResolver--: Sending address notification for target fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.367 [I] MeshForwarder-: Sent IPv6 UDP msg, len:92, chksum:1f5c, ecn:no, to:0xe801, sec:yes, prio:net
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.367 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:0:ff:fe00:e800]:61631
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.367 [I] MeshForwarder-:     dst:[fd0d:ef30:fec0:af6a:0:ff:fe00:e801]:61631
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.385 [I] AddrResolver--: Cache entry added: fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7, 0xe801 - snoop
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.429 [I] MeshForwarder-: Received IPv6 UDP msg, len:313, chksum:ba5b, ecn:no, from:0xe801, sec:yes, prio:normal, rss:-57.625
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.429 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7]:49155
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.429 [I] MeshForwarder-:     dst:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:53535
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.429 [I] SrpServer-----: Received DNS update from fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.450 [I] SrpServer-----: SRP update handler is notified (updatedId = 1051674558)
Mar  7 16:19:26 otbr-agent[114]: [INFO]-ADPROXY-: Advertise SRP service updates: host=32C094103F56DC97.default.service.arpa.
Mar  7 16:19:26 otbr-agent[114]: [INFO]-MDNS----: Removing host 32C094103F56DC97
Mar  7 16:19:26 otbr-agent[114]: [INFO]-ADPROXY-: Handle unpublish SRP host '32C094103F56DC97.default.service.arpa.': OK
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.451 [I] SrpServer-----: Handler result of SRP update (id = 1051674558) is received: OK
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.451 [I] SrpServer-----: Lease timer is stopped
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.451 [I] SrpServer-----: Send success response
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.451 [I] MeshForwarder-: Sent IPv6 HopOpts msg, len:86, chksum:0000, ecn:no, to:0xffff, sec:yes, prio:normal
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.451 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:0:ff:fe00:e801]
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.452 [I] MeshForwarder-:     dst:[ff03:0:0:0:0:0:0:2]
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.452 [I] MeshForwarder-: Received IPv6 UDP msg, len:54, chksum:aae6, ecn:no, from:0xe801, sec:yes, prio:net, rss:-58.0
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.452 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:0:ff:fe00:e801]:61631
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.452 [I] MeshForwarder-:     dst:[fd0d:ef30:fec0:af6a:0:ff:fe00:e800]:61631
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.473 [I] MeshForwarder-: Sent IPv6 UDP msg, len:60, chksum:2de5, ecn:no, to:0xe801, sec:yes, prio:low
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.473 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:53535
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.473 [I] MeshForwarder-:     dst:[fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7]:49155
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.494 [I] MeshForwarder-: Sent IPv6 HopOpts msg, len:86, chksum:0000, ecn:no, to:0xffff, sec:yes, prio:normal
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.494 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:0:ff:fe00:e801]
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.494 [I] MeshForwarder-:     dst:[ff03:0:0:0:0:0:0:2]
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.659 [I] MeshForwarder-: Received IPv6 UDP msg, len:719, chksum:4f4d, ecn:no, from:0xe801, sec:yes, prio:normal, rss:-57.375
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.659 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7]:49155
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.659 [I] MeshForwarder-:     dst:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:53535
Mar  7 16:19:26 otbr-agent[114]: 00:00:11.659 [I] SrpServer-----: Received DNS update from fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7
Mar  7 16:19:27 otbr-agent[114]: 00:00:11.680 [I] SrpServer-----: SRP update handler is notified (updatedId = 1051674559)
Mar  7 16:19:27 otbr-agent[114]: [INFO]-ADPROXY-: Advertise SRP service updates: host=32C094103F56DC97.default.service.arpa.
Mar  7 16:19:27 otbr-agent[114]: [INFO]-MDNS----: Add subtype _I5BB2BF7451309CA6 for service 5BB2BF7451309CA6-000000000000002D._matter._tcp
Mar  7 16:19:27 otbr-agent[114]: [INFO]-MDNS----: Commit avahi service 5BB2BF7451309CA6-000000000000002D._matter._tcp
Mar  7 16:19:27 otbr-agent[114]: [INFO]-MDNS----: Add subtype _L3840 for service 8CCEED038B98779A._matterc._udp
Mar  7 16:19:27 otbr-agent[114]: [INFO]-MDNS----: Add subtype _S15 for service 8CCEED038B98779A._matterc._udp
Mar  7 16:19:27 otbr-agent[114]: [INFO]-MDNS----: Add subtype _V65521 for service 8CCEED038B98779A._matterc._udp
Mar  7 16:19:27 otbr-agent[114]: [INFO]-MDNS----: Commit avahi service 8CCEED038B98779A._matterc._udp
Mar  7 16:19:27 otbr-agent[114]: [INFO]-MDNS----: Commit avahi host 32C094103F56DC97
Mar  7 16:19:27 otbr-agent[114]: 00:00:11.956 [I] MeshForwarder-: Sent IPv6 UDP msg, len:349, chksum:ca2a, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:27 otbr-agent[114]: 00:00:11.956 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:27 otbr-agent[114]: 00:00:11.956 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.057 [I] MeshForwarder-: Sent IPv6 UDP msg, len:334, chksum:fa25, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.057 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.057 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.113 [I] MeshForwarder-: Sent IPv6 UDP msg, len:226, chksum:6fa9, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.113 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.113 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.215 [I] MeshForwarder-: Sent IPv6 UDP msg, len:349, chksum:ca2a, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.215 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.215 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.325 [I] BorderRouter--: Router solicitation times out
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.325 [I] BorderRouter--: Received Router Solicitation from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.325 [I] BorderRouter--: Start evaluating routing policy, scheduled in 1879 milliseconds
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.326 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.449 [I] MeshForwarder-: Sent IPv6 UDP msg, len:349, chksum:ca2a, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.449 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.450 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:27 otbr-agent[114]: [INFO]-MDNS----: Avahi group (@0x29af28) is established
Mar  7 16:19:27 otbr-agent[114]: [INFO]-ADPROXY-: Handle publish SRP service '5BB2BF7451309CA6-000000000000002D._matter._tcp.default.service.arpa.': OK
Mar  7 16:19:27 otbr-agent[114]: [INFO]-ADPROXY-: Waiting for more publishing callbacks 2
Mar  7 16:19:27 otbr-agent[114]: [INFO]-MDNS----: Avahi group (@0x2a1880) is established
Mar  7 16:19:27 otbr-agent[114]: [INFO]-ADPROXY-: Handle publish SRP service '8CCEED038B98779A._matterc._udp.default.service.arpa.': OK
Mar  7 16:19:27 otbr-agent[114]: [INFO]-ADPROXY-: Waiting for more publishing callbacks 1
Mar  7 16:19:27 otbr-agent[114]: [INFO]-MDNS----: Avahi group (@0x2a0ce8) is established
Mar  7 16:19:27 otbr-agent[114]: [INFO]-ADPROXY-: Handle publish SRP host '32C094103F56DC97.default.service.arpa.': OK
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.577 [I] SrpServer-----: Handler result of SRP update (id = 1051674559) is received: OK
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.577 [I] SrpServer-----: Add new host 32C094103F56DC97.default.service.arpa.
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.577 [I] SrpServer-----: Add new service '5BB2BF7451309CA6-000000000000002D._matter._tcp.default.service.arpa.' subtype:_I5BB2BF7451309CA6
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.577 [I] SrpServer-----: Add new service '5BB2BF7451309CA6-000000000000002D._matter._tcp.default.service.arpa.'
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.577 [I] SrpServer-----: Add new service '8CCEED038B98779A._matterc._udp.default.service.arpa.' subtype:_L3840
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.577 [I] SrpServer-----: Add new service '8CCEED038B98779A._matterc._udp.default.service.arpa.' subtype:_S15
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.577 [I] SrpServer-----: Add new service '8CCEED038B98779A._matterc._udp.default.service.arpa.' subtype:_V65521
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.577 [I] SrpServer-----: Add new service '8CCEED038B98779A._matterc._udp.default.service.arpa.'
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.589 [I] Settings------: Saved SrpServerInfo {port:53535}
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.589 [I] SrpServer-----: Lease timer is scheduled for 7199 seconds
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.589 [I] SrpServer-----: Send success response
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.644 [I] MeshForwarder-: Sent IPv6 UDP msg, len:271, chksum:9175, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.644 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.644 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.667 [I] MeshForwarder-: Sent IPv6 UDP msg, len:60, chksum:01fa, ecn:no, to:0xe801, sec:yes, prio:low
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.667 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:53535
Mar  7 16:19:27 otbr-agent[114]: 00:00:12.667 [I] MeshForwarder-:     dst:[fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7]:49155
Mar  7 16:19:28 otbr-agent[114]: 00:00:12.773 [I] MeshForwarder-: Sent IPv6 UDP msg, len:344, chksum:7092, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:28 otbr-agent[114]: 00:00:12.773 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:28 otbr-agent[114]: 00:00:12.773 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:29 otbr-agent[114]: 00:00:13.751 [I] MeshForwarder-: Sent IPv6 UDP msg, len:299, chksum:e8b5, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:29 otbr-agent[114]: 00:00:13.751 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:29 otbr-agent[114]: 00:00:13.751 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:29 otbr-agent[114]: 00:00:13.834 [I] MeshForwarder-: Sent IPv6 UDP msg, len:316, chksum:2562, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:29 otbr-agent[114]: 00:00:13.834 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:29 otbr-agent[114]: 00:00:13.834 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:29 otbr-agent[114]: 00:00:14.205 [I] BorderRouter--: Evaluating routing policy
Mar  7 16:19:29 otbr-agent[114]: 00:00:14.205 [I] BorderRouter--: RouterAdvert: Added RIO for fdaa:bbcc:ddee:0::/64 (lifetime=1800)
Mar  7 16:19:29 otbr-agent[114]: 00:00:14.206 [I] BorderRouter--: Sent Router Advertisement on infra netif 21
Mar  7 16:19:29 otbr-agent[114]: 00:00:14.206 [I] BorderRouter--: Start evaluating routing policy, scheduled in 16000 milliseconds
Mar  7 16:19:29 otbr-agent[114]: 00:00:14.206 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:19:29 otbr-agent[114]: 00:00:14.459 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:19:29 otbr-agent[114]: 00:00:14.479 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:7570, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:19:29 otbr-agent[114]: 00:00:14.479 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:29 otbr-agent[114]: 00:00:14.479 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:31 otbr-agent[114]: 00:00:15.854 [I] MeshForwarder-: Sent IPv6 UDP msg, len:299, chksum:e8b5, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:31 otbr-agent[114]: 00:00:15.854 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:31 otbr-agent[114]: 00:00:15.854 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:31 otbr-agent[114]: 00:00:15.937 [I] MeshForwarder-: Sent IPv6 UDP msg, len:316, chksum:2562, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:31 otbr-agent[114]: 00:00:15.937 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:31 otbr-agent[114]: 00:00:15.937 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:31 otbr-agent[114]: 00:00:16.326 [I] BorderRouter--: Router solicitation times out
Mar  7 16:19:31 otbr-agent[114]: 00:00:16.329 [I] BorderRouter--: Received Router Solicitation from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:19:31 otbr-agent[114]: 00:00:16.329 [I] BorderRouter--: Start evaluating routing policy, scheduled in 877 milliseconds
Mar  7 16:19:31 otbr-agent[114]: 00:00:16.329 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:19:32 otbr-agent[114]: 00:00:16.980 [I] MeshForwarder-: Received IPv6 UDP msg, len:73, chksum:f771, ecn:no, from:0xe801, sec:yes, prio:net, rss:-57.0
Mar  7 16:19:32 otbr-agent[114]: 00:00:16.980 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:0:ff:fe00:e801]:61631
Mar  7 16:19:32 otbr-agent[114]: 00:00:16.980 [I] MeshForwarder-:     dst:[fd0d:ef30:fec0:af6a:0:ff:fe00:e800]:61631
Mar  7 16:19:32 otbr-agent[114]: 00:00:16.980 [I] Mle-----------: Receive Address Solicit (fd0d:ef30:fec0:af6a:0:ff:fe00:e801)
Mar  7 16:19:32 otbr-agent[114]: 00:00:16.980 [N] RouterTable---: Allocate router id 17
Mar  7 16:19:32 otbr-agent[114]: 00:00:16.980 [I] Mle-----------: Send Address Reply (fd0d:ef30:fec0:af6a:0:ff:fe00:e801)
Mar  7 16:19:32 otbr-agent[114]: 00:00:17.002 [I] MeshForwarder-: Sent IPv6 UDP msg, len:73, chksum:8368, ecn:no, to:0xe801, sec:yes, prio:net
Mar  7 16:19:32 otbr-agent[114]: 00:00:17.002 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:0:ff:fe00:e800]:61631
Mar  7 16:19:32 otbr-agent[114]: 00:00:17.002 [I] MeshForwarder-:     dst:[fd0d:ef30:fec0:af6a:0:ff:fe00:e801]:61631
Mar  7 16:19:32 otbr-agent[114]: 00:00:17.207 [I] BorderRouter--: Evaluating routing policy
Mar  7 16:19:32 otbr-agent[114]: 00:00:17.207 [I] BorderRouter--: RouterAdvert: Added RIO for fdaa:bbcc:ddee:0::/64 (lifetime=1800)
Mar  7 16:19:32 otbr-agent[114]: 00:00:17.208 [I] BorderRouter--: Sent Router Advertisement on infra netif 21
Mar  7 16:19:32 otbr-agent[114]: 00:00:17.208 [I] BorderRouter--: Start evaluating routing policy, scheduled in 210000 milliseconds
Mar  7 16:19:32 otbr-agent[114]: 00:00:17.208 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:19:32 otbr-agent[114]: 00:00:17.330 [I] BorderRouter--: Router solicitation times out
Mar  7 16:19:32 otbr-agent[114]: 00:00:17.330 [I] BorderRouter--: Start evaluating routing policy, scheduled in 2878 milliseconds
Mar  7 16:19:33 otbr-agent[114]: 00:00:17.920 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:19:33 otbr-agent[114]: 00:00:17.941 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:747d, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:19:33 otbr-agent[114]: 00:00:17.941 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:33 otbr-agent[114]: 00:00:17.941 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:33 otbr-agent[114]: 00:00:17.960 [I] MeshForwarder-: Received IPv6 UDP msg, len:95, chksum:6896, ecn:no, from:32c094103f56dc97, sec:no, prio:net, rss:-56.0
Mar  7 16:19:33 otbr-agent[114]: 00:00:17.960 [I] MeshForwarder-:     src:[fe80:0:0:0:30c0:9410:3f56:dc97]:19788
Mar  7 16:19:33 otbr-agent[114]: 00:00:17.960 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788
Mar  7 16:19:33 otbr-agent[114]: 00:00:17.960 [I] Mle-----------: Receive Link Request (fe80:0:0:0:30c0:9410:3f56:dc97)
Mar  7 16:19:33 otbr-agent[114]: 00:00:17.960 [I] Mle-----------: Delay Link Accept (fe80:0:0:0:30c0:9410:3f56:dc97)
Mar  7 16:19:34 otbr-agent[114]: 00:00:18.915 [I] Mle-----------: Send delayed message (fe80:0:0:0:30c0:9410:3f56:dc97)
Mar  7 16:19:34 otbr-agent[114]: 00:00:18.947 [I] MeshForwarder-: Sent IPv6 UDP msg, len:120, chksum:1d1d, ecn:no, to:32c094103f56dc97, sec:no, prio:net
Mar  7 16:19:34 otbr-agent[114]: 00:00:18.947 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:34 otbr-agent[114]: 00:00:18.947 [I] MeshForwarder-:     dst:[fe80:0:0:0:30c0:9410:3f56:dc97]:19788
Mar  7 16:19:34 otbr-agent[114]: 00:00:18.962 [I] MeshForwarder-: Received IPv6 UDP msg, len:107, chksum:cdc4, ecn:no, from:32c094103f56dc97, sec:no, prio:net, rss:-56.0
Mar  7 16:19:34 otbr-agent[114]: 00:00:18.962 [I] MeshForwarder-:     src:[fe80:0:0:0:30c0:9410:3f56:dc97]:19788
Mar  7 16:19:34 otbr-agent[114]: 00:00:18.962 [I] MeshForwarder-:     dst:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:34 otbr-agent[114]: 00:00:18.962 [I] Mle-----------: Receive Link Accept (fe80:0:0:0:30c0:9410:3f56:dc97,0x4400)
Mar  7 16:19:34 otbr-agent[114]: 00:00:18.962 [I] AddrResolver--: Cache entry removed: fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7, 0xe801, list:cached - removing rloc16
Mar  7 16:19:34 otbr-agent[114]: 00:00:18.962 [I] Settings------: Read ChildInfo {rloc:0xe801, extaddr:32c094103f56dc97, timeout:240, mode:0x0f, version:4}
Mar  7 16:19:34 otbr-agent[114]: 00:00:18.973 [I] Settings------: Removed ChildInfo {rloc:0xe801, extaddr:32c094103f56dc97, timeout:240, mode:0x0f, version:4}
Mar  7 16:19:34 otbr-agent[114]: 00:00:18.973 [I] Notifier------: StateChanged (0x00000800) [Child-]
Mar  7 16:19:34 otbr-agent[114]: 00:00:18.973 [I] ChildSupervsn-: Stopping Child Supervision
Mar  7 16:19:34 otbr-agent[114]: 00:00:19.574 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:19:34 otbr-agent[114]: 00:00:19.595 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:af6a, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:19:34 otbr-agent[114]: 00:00:19.595 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:34 otbr-agent[114]: 00:00:19.595 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:35 otbr-agent[114]: 00:00:19.716 [I] MeshForwarder-: Received IPv6 UDP msg, len:91, chksum:d9af, ecn:no, from:32c094103f56dc97, sec:no, prio:net, rss:-56.0
Mar  7 16:19:35 otbr-agent[114]: 00:00:19.716 [I] MeshForwarder-:     src:[fe80:0:0:0:30c0:9410:3f56:dc97]:19788
Mar  7 16:19:35 otbr-agent[114]: 00:00:19.716 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:35 otbr-agent[114]: 00:00:19.716 [I] Mle-----------: Receive Advertisement (fe80:0:0:0:30c0:9410:3f56:dc97,0x4400)
Mar  7 16:19:35 otbr-agent[114]: 00:00:20.209 [I] BorderRouter--: Evaluating routing policy
Mar  7 16:19:35 otbr-agent[114]: 00:00:20.209 [I] NetDataPublshr: Publishing ExternalRoute fd1b:1ef3:dc76:cef8::/64
Mar  7 16:19:35 otbr-agent[114]: 00:00:20.209 [I] NetDataPublshr: ExternalRoute fd1b:1ef3:dc76:cef8::/64 - State: NoEntry -> ToAdd
Mar  7 16:19:35 otbr-agent[114]: 00:00:20.209 [I] NetDataPublshr: ExternalRoute fd1b:1ef3:dc76:cef8::/64 (state:ToA in netdata - total:0, preferred:0, desired:10
Mar  7 16:19:35 otbr-agent[114]: 00:00:20.209 [I] NetDataPublshr: ExternalRoute fd1b:1ef3:dc76:cef8::/64 - State: ToAdd -> Adding
Mar  7 16:19:35 otbr-agent[114]: 00:00:20.209 [I] NetDataPublshr: ExternalRoute fd1b:1ef3:dc76:cef8::/64 (state:Add - update in 1490 msec
Mar  7 16:19:35 otbr-agent[114]: 00:00:20.209 [I] BorderRouter--: Start advertising on-link prefix fd1b:1ef3:dc76:cef8::/64 on infra netif 21
Mar  7 16:19:35 otbr-agent[114]: 00:00:20.209 [I] BorderRouter--: RouterAdvert: Added PIO for fd1b:1ef3:dc76:cef8::/64 (valid=1800, preferred=1800)
Mar  7 16:19:35 otbr-agent[114]: 00:00:20.209 [I] BorderRouter--: RouterAdvert: Added RIO for fdaa:bbcc:ddee:0::/64 (lifetime=1800)
Mar  7 16:19:35 otbr-agent[114]: 00:00:20.210 [I] BorderRouter--: Sent Router Advertisement on infra netif 21
Mar  7 16:19:35 otbr-agent[114]: 00:00:20.210 [I] BorderRouter--: Start evaluating routing policy, scheduled in 478000 milliseconds
Mar  7 16:19:35 otbr-agent[114]: 00:00:20.210 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:19:36 otbr-agent[114]: 00:00:21.465 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:19:36 otbr-agent[114]: 00:00:21.485 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:97f6, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:19:36 otbr-agent[114]: 00:00:21.485 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:36 otbr-agent[114]: 00:00:21.485 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.700 [I] NetDataPublshr: ExternalRoute fd1b:1ef3:dc76:cef8::/64 - State: Adding -> Added
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.700 [I] NetworkData---: Sent server data notification
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.700 [I] NetworkData---: Received network data registration
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.700 [I] NetworkData---: Sent network data registration acknowledgment
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.700 [I] Notifier------: StateChanged (0x00000200) [NetData]
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.700 [I] Mle-----------: Send Data Response (ff02:0:0:0:0:0:0:1)
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.700 [I] BbrLeader-----: PBBR state: None
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.700 [I] BbrLeader-----: Domain Prefix: ::/0, state: None
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.700 [I] BorderRouter--: Start evaluating routing policy, scheduled in 1510 milliseconds
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.700 [I] NetDataPublshr: DNS/SRP service (state:Added) in netdata - total:1, preferred:0, desired:2
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.700 [I] NetDataPublshr: ExternalRoute fd1b:1ef3:dc76:cef8::/64 (state:Add in netdata - total:1, preferred:0, desired:10
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.748 [I] MeshForwarder-: Sent IPv6 UDP msg, len:162, chksum:62c2, ecn:no, to:0xffff, sec:yes, prio:net
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.748 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.748 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.868 [I] MeshForwarder-: Received IPv6 UDP msg, len:91, chksum:58f0, ecn:no, from:32c094103f56dc97, sec:no, prio:net, rss:-56.0
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.868 [I] MeshForwarder-:     src:[fe80:0:0:0:30c0:9410:3f56:dc97]:19788
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.868 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:37 otbr-agent[114]: 00:00:21.868 [I] Mle-----------: Receive Advertisement (fe80:0:0:0:30c0:9410:3f56:dc97,0x4400)
Mar  7 16:19:37 otbr-agent[114]: 00:00:22.029 [I] MeshForwarder-: Received IPv6 UDP msg, len:162, chksum:3943, ecn:no, from:32c094103f56dc97, sec:yes, prio:net, rss:-56.0
Mar  7 16:19:37 otbr-agent[114]: 00:00:22.029 [I] MeshForwarder-:     src:[fe80:0:0:0:30c0:9410:3f56:dc97]:19788
Mar  7 16:19:37 otbr-agent[114]: 00:00:22.029 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:37 otbr-agent[114]: 00:00:22.029 [I] Mle-----------: Receive Data Response (fe80:0:0:0:30c0:9410:3f56:dc97)
Mar  7 16:19:38 otbr-agent[114]: 00:00:23.211 [I] BorderRouter--: Evaluating routing policy
Mar  7 16:19:38 otbr-agent[114]: 00:00:23.211 [I] BorderRouter--: RouterAdvert: Added PIO for fd1b:1ef3:dc76:cef8::/64 (valid=1800, preferred=1800)
Mar  7 16:19:38 otbr-agent[114]: 00:00:23.211 [I] BorderRouter--: RouterAdvert: Added RIO for fdaa:bbcc:ddee:0::/64 (lifetime=1800)
Mar  7 16:19:38 otbr-agent[114]: 00:00:23.212 [I] BorderRouter--: Sent Router Advertisement on infra netif 21
Mar  7 16:19:38 otbr-agent[114]: 00:00:23.212 [I] BorderRouter--: Start evaluating routing policy, scheduled in 208000 milliseconds
Mar  7 16:19:38 otbr-agent[114]: 00:00:23.212 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:19:39 otbr-agent[114]: 00:00:24.306 [I] MeshForwarder-: Received IPv6 UDP msg, len:91, chksum:131c, ecn:no, from:32c094103f56dc97, sec:no, prio:net, rss:-54.0
Mar  7 16:19:39 otbr-agent[114]: 00:00:24.306 [I] MeshForwarder-:     src:[fe80:0:0:0:30c0:9410:3f56:dc97]:19788
Mar  7 16:19:39 otbr-agent[114]: 00:00:24.306 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:39 otbr-agent[114]: 00:00:24.306 [I] Mle-----------: Receive Advertisement (fe80:0:0:0:30c0:9410:3f56:dc97,0x4400)
Mar  7 16:19:40 otbr-agent[114]: 00:00:25.127 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:19:40 otbr-agent[114]: 00:00:25.146 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:b489, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:19:40 otbr-agent[114]: 00:00:25.146 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:40 otbr-agent[114]: 00:00:25.146 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:48 otbr-agent[114]: 00:00:33.464 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:19:48 otbr-agent[114]: 00:00:33.485 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:ce36, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:19:48 otbr-agent[114]: 00:00:33.485 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:19:48 otbr-agent[114]: 00:00:33.485 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:49 otbr-agent[114]: 00:00:33.686 [I] MeshForwarder-: Received IPv6 UDP msg, len:91, chksum:7245, ecn:no, from:32c094103f56dc97, sec:no, prio:net, rss:-57.0
Mar  7 16:19:49 otbr-agent[114]: 00:00:33.686 [I] MeshForwarder-:     src:[fe80:0:0:0:30c0:9410:3f56:dc97]:19788
Mar  7 16:19:49 otbr-agent[114]: 00:00:33.686 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:19:49 otbr-agent[114]: 00:00:33.686 [I] Mle-----------: Receive Advertisement (fe80:0:0:0:30c0:9410:3f56:dc97,0x4400)
Mar  7 16:19:52 otbr-agent[114]: 00:00:37.234 [I] AddrResolver--: Cache entry added: fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7, 0x4400 - snoop
Mar  7 16:19:52 otbr-agent[114]: 00:00:37.323 [I] MeshForwarder-: Received IPv6 UDP msg, len:573, chksum:2505, ecn:no, from:0x4400, sec:yes, prio:normal, rss:-58.0
Mar  7 16:19:52 otbr-agent[114]: 00:00:37.323 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7]:49155
Mar  7 16:19:52 otbr-agent[114]: 00:00:37.323 [I] MeshForwarder-:     dst:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:53535
Mar  7 16:19:52 otbr-agent[114]: 00:00:37.323 [I] SrpServer-----: Received DNS update from fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7
Mar  7 16:19:52 otbr-agent[114]: 00:00:37.348 [I] SrpServer-----: SRP update handler is notified (updatedId = 1051674560)
Mar  7 16:19:52 otbr-agent[114]: [INFO]-ADPROXY-: Advertise SRP service updates: host=32C094103F56DC97.default.service.arpa.
Mar  7 16:19:52 otbr-agent[114]: [INFO]-MDNS----: Removing existing service 8CCEED038B98779A._matterc._udp: outdated
Mar  7 16:19:52 otbr-agent[114]: [INFO]-MDNS----: Removing service 8CCEED038B98779A._matterc._udp
Mar  7 16:19:52 otbr-agent[114]: [INFO]-MDNS----: Releasing avahi entry group @0x2a1880
Mar  7 16:19:52 otbr-agent[114]: [INFO]-MDNS----: Add subtype _CM for service 8CCEED038B98779A._matterc._udp
Mar  7 16:19:52 otbr-agent[114]: [INFO]-MDNS----: Add subtype _L3840 for service 8CCEED038B98779A._matterc._udp
Mar  7 16:19:52 otbr-agent[114]: [INFO]-MDNS----: Add subtype _S15 for service 8CCEED038B98779A._matterc._udp
Mar  7 16:19:52 otbr-agent[114]: [INFO]-MDNS----: Add subtype _V65521 for service 8CCEED038B98779A._matterc._udp
Mar  7 16:19:52 otbr-agent[114]: [INFO]-MDNS----: Commit avahi service 8CCEED038B98779A._matterc._udp
Mar  7 16:19:52 otbr-agent[114]: [INFO]-ADPROXY-: Handle publish SRP host '32C094103F56DC97.default.service.arpa.': OK
Mar  7 16:19:52 otbr-agent[114]: [INFO]-ADPROXY-: Waiting for more publishing callbacks 1
Mar  7 16:19:52 otbr-agent[114]: 00:00:37.502 [I] MeshForwarder-: Sent IPv6 UDP msg, len:344, chksum:7eb0, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:52 otbr-agent[114]: 00:00:37.502 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:52 otbr-agent[114]: 00:00:37.502 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:52 otbr-agent[114]: 00:00:37.622 [I] MeshForwarder-: Sent IPv6 UDP msg, len:209, chksum:ab5b, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:52 otbr-agent[114]: 00:00:37.622 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:52 otbr-agent[114]: 00:00:37.622 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:53 otbr-agent[114]: 00:00:37.871 [I] MeshForwarder-: Sent IPv6 UDP msg, len:209, chksum:ab5b, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:53 otbr-agent[114]: 00:00:37.871 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:53 otbr-agent[114]: 00:00:37.871 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.123 [I] MeshForwarder-: Sent IPv6 UDP msg, len:209, chksum:ab5b, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.123 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.123 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:53 otbr-agent[114]: [INFO]-MDNS----: Avahi group (@0x2a1880) is established
Mar  7 16:19:53 otbr-agent[114]: [INFO]-ADPROXY-: Handle publish SRP service '8CCEED038B98779A._matterc._udp.default.service.arpa.': OK
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.269 [I] SrpServer-----: Handler result of SRP update (id = 1051674560) is received: OK
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.269 [I] SrpServer-----: Update host 32C094103F56DC97.default.service.arpa.
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.269 [I] SrpServer-----: Add new service '8CCEED038B98779A._matterc._udp.default.service.arpa.' subtype:_CM
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.269 [I] SrpServer-----: Update existing service '8CCEED038B98779A._matterc._udp.default.service.arpa.' subtype:_L3840
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.269 [I] SrpServer-----: Update existing service '8CCEED038B98779A._matterc._udp.default.service.arpa.' subtype:_S15
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.269 [I] SrpServer-----: Update existing service '8CCEED038B98779A._matterc._udp.default.service.arpa.' subtype:_V65521
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.269 [I] SrpServer-----: Update existing service '8CCEED038B98779A._matterc._udp.default.service.arpa.'
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.269 [I] SrpServer-----: Lease timer is scheduled for 7173 seconds
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.269 [I] SrpServer-----: Send success response
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.402 [I] Mac-----------: Frame tx attempt 16/16 failed, error:NoAck, len:61, seqnum:20, type:Data, src:0xe800, dst:0x4400, sec:yes, ackreq:yes
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.402 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:60, chksum:7f59, ecn:no, to:0x4400, sec:yes, error:NoAck, prio:low
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.402 [N] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:53535
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.402 [N] MeshForwarder-:     dst:[fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7]:49155
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.506 [I] MeshForwarder-: Sent IPv6 UDP msg, len:362, chksum:9002, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.506 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:53 otbr-agent[114]: 00:00:38.506 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:54 otbr-agent[114]: 00:00:39.516 [I] MeshForwarder-: Sent IPv6 UDP msg, len:362, chksum:9002, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:54 otbr-agent[114]: 00:00:39.516 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:54 otbr-agent[114]: 00:00:39.516 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:19:56 otbr-agent[114]: 00:00:41.635 [I] MeshForwarder-: Sent IPv6 UDP msg, len:362, chksum:9002, ecn:no, to:0xffff, sec:yes, prio:low
Mar  7 16:19:56 otbr-agent[114]: 00:00:41.635 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c]:5353
Mar  7 16:19:56 otbr-agent[114]: 00:00:41.635 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Mar  7 16:20:05 otbr-agent[114]: 00:00:49.715 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:20:05 otbr-agent[114]: 00:00:49.736 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:6fc9, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:20:05 otbr-agent[114]: 00:00:49.736 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:20:05 otbr-agent[114]: 00:00:49.736 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:20:12 otbr-agent[114]: 00:00:57.586 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:20:28 otbr-agent[114]: 00:01:12.939 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:20:28 otbr-agent[114]: 00:01:12.959 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:7966, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:20:28 otbr-agent[114]: 00:01:12.959 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:20:28 otbr-agent[114]: 00:01:12.959 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:20:37 otbr-agent[114]: 00:01:21.801 [I] AddrResolver--: Sending address query for fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9
Mar  7 16:20:37 otbr-agent[114]: 00:01:21.801 [I] AddrResolver--: Cache entry added: fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9, 0xfffe - query request
Mar  7 16:20:37 otbr-agent[114]: 00:01:21.823 [I] MeshForwarder-: Sent IPv6 HopOpts msg, len:86, chksum:0000, ecn:no, to:0xffff, sec:yes, prio:net
Mar  7 16:20:37 otbr-agent[114]: 00:01:21.823 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:0:ff:fe00:e800]
Mar  7 16:20:37 otbr-agent[114]: 00:01:21.823 [I] MeshForwarder-:     dst:[ff03:0:0:0:0:0:0:2]
Mar  7 16:20:37 otbr-agent[114]: 00:01:21.861 [I] MeshForwarder-: Sent IPv6 HopOpts msg, len:86, chksum:0000, ecn:no, to:0xffff, sec:yes, prio:net
Mar  7 16:20:37 otbr-agent[114]: 00:01:21.861 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:0:ff:fe00:e800]
Mar  7 16:20:37 otbr-agent[114]: 00:01:21.861 [I] MeshForwarder-:     dst:[ff03:0:0:0:0:0:0:2]
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [I] AddrResolver--: Timed out waiting for address notification for fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9, retry: 15
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-: Dropping IPv6 ICMP6 msg, len:104, chksum:5375, ecn:no, sec:yes, error:AddressQuery, prio:low
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-:     src:[fdaa:bbcc:ddee:0:87ef:d332:1f87:f871]
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-:     dst:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-: Dropping IPv6 ICMP6 msg, len:104, chksum:e72a, ecn:no, sec:yes, error:AddressQuery, prio:low
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-:     src:[fdaa:bbcc:ddee:0:87ef:d332:1f87:f871]
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-:     dst:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-: Dropping IPv6 ICMP6 msg, len:104, chksum:fae2, ecn:no, sec:yes, error:AddressQuery, prio:low
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-:     src:[fdaa:bbcc:ddee:0:87ef:d332:1f87:f871]
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-:     dst:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]
Mar  7 16:20:40 otbr-agent[114]: 00:01:24.805 [N] MeshForwarder-: Dropping IPv6 ICMP6 msg, len:104, chksum:7a9c, ecn:no, sec:yes, error:Drop, prio:low
Mar  7 16:20:40 otbr-agent[114]: 00:01:24.805 [N] MeshForwarder-:     src:[fdaa:bbcc:ddee:0:87ef:d332:1f87:f871]
Mar  7 16:20:40 otbr-agent[114]: 00:01:24.805 [N] MeshForwarder-:     dst:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]
Mar  7 16:20:54 otbr-agent[114]: 00:01:39.671 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:20:55 otbr-agent[114]: 00:01:39.692 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:e044, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:20:55 otbr-agent[114]: 00:01:39.692 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:20:55 otbr-agent[114]: 00:01:39.692 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:21:05 otbr-agent[114]: 00:01:50.393 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:21:29 otbr-agent[114]: 00:02:14.669 [I] Mle-----------: Router timeout expired
Mar  7 16:21:29 otbr-agent[114]: 00:02:14.669 [I] Mle-----------: Send Link Request (fe80:0:0:0:30c0:9410:3f56:dc97)
Mar  7 16:21:30 otbr-agent[114]: 00:02:14.825 [I] Mac-----------: Frame tx attempt 16/16 failed, error:NoAck, len:80, seqnum:38, type:Data, src:e60d62beffc4245a, dst:32c094103f56dc97, sec:no, ackreq:yes
Mar  7 16:21:30 otbr-agent[114]: 00:02:14.825 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:96, chksum:da91, ecn:no, to:32c094103f56dc97, sec:no, error:NoAck, prio:net
Mar  7 16:21:30 otbr-agent[114]: 00:02:14.825 [N] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:21:30 otbr-agent[114]: 00:02:14.825 [N] MeshForwarder-:     dst:[fe80:0:0:0:30c0:9410:3f56:dc97]:19788
Mar  7 16:21:30 otbr-agent[114]: 00:02:15.672 [I] Mle-----------: Router timeout expired
Mar  7 16:21:30 otbr-agent[114]: 00:02:15.672 [I] Mle-----------: Send Link Request (fe80:0:0:0:30c0:9410:3f56:dc97)
Mar  7 16:21:31 otbr-agent[114]: 00:02:15.801 [I] Mac-----------: Frame tx attempt 16/16 failed, error:NoAck, len:80, seqnum:39, type:Data, src:e60d62beffc4245a, dst:32c094103f56dc97, sec:no, ackreq:yes
Mar  7 16:21:31 otbr-agent[114]: 00:02:15.801 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:96, chksum:dc91, ecn:no, to:32c094103f56dc97, sec:no, error:NoAck, prio:net
Mar  7 16:21:31 otbr-agent[114]: 00:02:15.801 [N] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:21:31 otbr-agent[114]: 00:02:15.801 [N] MeshForwarder-:     dst:[fe80:0:0:0:30c0:9410:3f56:dc97]:19788
Mar  7 16:21:31 otbr-agent[114]: 00:02:16.675 [I] Mle-----------: Router timeout expired
Mar  7 16:21:31 otbr-agent[114]: 00:02:16.675 [I] Mle-----------: Send Link Request (fe80:0:0:0:30c0:9410:3f56:dc97)
Mar  7 16:21:32 otbr-agent[114]: 00:02:16.829 [I] Mac-----------: Frame tx attempt 16/16 failed, error:NoAck, len:80, seqnum:40, type:Data, src:e60d62beffc4245a, dst:32c094103f56dc97, sec:no, ackreq:yes
Mar  7 16:21:32 otbr-agent[114]: 00:02:16.829 [I] AddrResolver--: Cache entry removed: fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7, 0x4400, list:cached - removing router id
Mar  7 16:21:32 otbr-agent[114]: 00:02:16.829 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:96, chksum:6e82, ecn:no, to:32c094103f56dc97, sec:no, error:NoAck, prio:net
Mar  7 16:21:32 otbr-agent[114]: 00:02:16.829 [N] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:21:32 otbr-agent[114]: 00:02:16.829 [N] MeshForwarder-:     dst:[fe80:0:0:0:30c0:9410:3f56:dc97]:19788
Mar  7 16:21:32 otbr-agent[114]: 00:02:17.431 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:21:32 otbr-agent[114]: 00:02:17.450 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:3f63, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:21:32 otbr-agent[114]: 00:02:17.450 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:21:32 otbr-agent[114]: 00:02:17.450 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:21:34 otbr-agent[114]: 00:02:19.559 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:21:34 otbr-agent[114]: 00:02:19.580 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:7235, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:21:34 otbr-agent[114]: 00:02:19.580 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:21:34 otbr-agent[114]: 00:02:19.580 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:21:38 otbr-agent[114]: 00:02:22.686 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:21:38 otbr-agent[114]: 00:02:22.707 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:5758, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:21:38 otbr-agent[114]: 00:02:22.707 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:21:38 otbr-agent[114]: 00:02:22.707 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:21:45 otbr-agent[114]: 00:02:30.088 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:21:45 otbr-agent[114]: 00:02:30.109 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:85f6, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:21:45 otbr-agent[114]: 00:02:30.109 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:21:45 otbr-agent[114]: 00:02:30.109 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:21:51 otbr-agent[114]: 00:02:35.770 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:21:59 otbr-agent[114]: 00:02:44.152 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:21:59 otbr-agent[114]: 00:02:44.173 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:24d1, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:21:59 otbr-agent[114]: 00:02:44.173 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:21:59 otbr-agent[114]: 00:02:44.173 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:22:35 otbr-agent[114]: 00:03:19.824 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:22:35 otbr-agent[114]: 00:03:19.843 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:b388, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:22:35 otbr-agent[114]: 00:03:19.843 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:22:35 otbr-agent[114]: 00:03:19.843 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:22:41 otbr-agent[114]: 00:03:25.802 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:22:53 otbr-agent[114]: 00:03:38.271 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:22:53 otbr-agent[114]: 00:03:38.292 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:8a85, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:22:53 otbr-agent[114]: 00:03:38.292 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:22:53 otbr-agent[114]: 00:03:38.292 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:23:02 otbr-agent[114]: 00:03:47.661 [I] Mle-----------: Router ID timeout expired (no route)
Mar  7 16:23:02 otbr-agent[114]: 00:03:47.661 [N] RouterTable---: Release router id 17
Mar  7 16:23:03 otbr-agent[114]: 00:03:48.469 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:23:03 otbr-agent[114]: 00:03:48.490 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:a1e3, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:23:03 otbr-agent[114]: 00:03:48.490 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:23:03 otbr-agent[114]: 00:03:48.490 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:23:05 otbr-agent[114]: 00:03:50.159 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:23:05 otbr-agent[114]: 00:03:50.178 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:9855, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:23:05 otbr-agent[114]: 00:03:50.178 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:23:05 otbr-agent[114]: 00:03:50.178 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:23:06 otbr-agent[114]: 00:03:51.213 [I] BorderRouter--: Evaluating routing policy
Mar  7 16:23:06 otbr-agent[114]: 00:03:51.213 [I] BorderRouter--: RouterAdvert: Added PIO for fd1b:1ef3:dc76:cef8::/64 (valid=1800, preferred=1800)
Mar  7 16:23:06 otbr-agent[114]: 00:03:51.213 [I] BorderRouter--: RouterAdvert: Added RIO for fdaa:bbcc:ddee:0::/64 (lifetime=1800)
Mar  7 16:23:06 otbr-agent[114]: 00:03:51.215 [I] BorderRouter--: Sent Router Advertisement on infra netif 21
Mar  7 16:23:06 otbr-agent[114]: 00:03:51.215 [I] BorderRouter--: Start evaluating routing policy, scheduled in 587000 milliseconds
Mar  7 16:23:06 otbr-agent[114]: 00:03:51.215 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:23:09 otbr-agent[114]: 00:03:53.707 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:23:09 otbr-agent[114]: 00:03:53.727 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:6324, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:23:09 otbr-agent[114]: 00:03:53.727 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:23:09 otbr-agent[114]: 00:03:53.727 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:23:17 otbr-agent[114]: 00:04:02.665 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:23:18 otbr-agent[114]: 00:04:02.684 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:1b5c, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:23:18 otbr-agent[114]: 00:04:02.684 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:23:18 otbr-agent[114]: 00:04:02.684 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:23:26 otbr-agent[114]: 00:04:11.089 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:23:26 otbr-agent[114]: 00:04:11.109 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:f6a8, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:23:26 otbr-agent[114]: 00:04:11.109 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:23:26 otbr-agent[114]: 00:04:11.109 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:23:27 otbr-agent[114]: 00:04:11.751 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:23:50 otbr-agent[114]: 00:04:35.662 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:23:51 otbr-agent[114]: 00:04:35.682 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:dfd3, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:23:51 otbr-agent[114]: 00:04:35.682 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:23:51 otbr-agent[114]: 00:04:35.682 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:23:58 otbr-agent[114]: 00:04:42.932 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:24:28 otbr-agent[114]: 00:05:12.682 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:24:28 otbr-agent[114]: 00:05:12.702 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:21f8, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:24:28 otbr-agent[114]: 00:05:12.702 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:24:28 otbr-agent[114]: 00:05:12.702 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Mar  7 16:24:41 otbr-agent[114]: 00:05:26.062 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:66fd:96ff:feb3:3ac7 on infra netif 21
Mar  7 16:24:58 otbr-agent[114]: 00:05:43.345 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Mar  7 16:24:58 otbr-agent[114]: 00:05:43.365 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:07f9, ecn:no, to:0xffff, sec:no, prio:net
Mar  7 16:24:58 otbr-agent[114]: 00:05:43.365 [I] MeshForwarder-:     src:[fe80:0:0:0:e40d:62be:ffc4:245a]:19788
Mar  7 16:24:58 otbr-agent[114]: 00:05:43.365 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788

In these logs we can see this:

Mar  7 16:20:37 otbr-agent[114]: 00:01:21.801 [I] AddrResolver--: Sending address query for fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9
Mar  7 16:20:37 otbr-agent[114]: 00:01:21.801 [I] AddrResolver--: Cache entry added: fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9, 0xfffe - query request
Mar  7 16:20:37 otbr-agent[114]: 00:01:21.823 [I] MeshForwarder-: Sent IPv6 HopOpts msg, len:86, chksum:0000, ecn:no, to:0xffff, sec:yes, prio:net
Mar  7 16:20:37 otbr-agent[114]: 00:01:21.823 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:0:ff:fe00:e800]
Mar  7 16:20:37 otbr-agent[114]: 00:01:21.823 [I] MeshForwarder-:     dst:[ff03:0:0:0:0:0:0:2]
Mar  7 16:20:37 otbr-agent[114]: 00:01:21.861 [I] MeshForwarder-: Sent IPv6 HopOpts msg, len:86, chksum:0000, ecn:no, to:0xffff, sec:yes, prio:net
Mar  7 16:20:37 otbr-agent[114]: 00:01:21.861 [I] MeshForwarder-:     src:[fd0d:ef30:fec0:af6a:0:ff:fe00:e800]
Mar  7 16:20:37 otbr-agent[114]: 00:01:21.861 [I] MeshForwarder-:     dst:[ff03:0:0:0:0:0:0:2]
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [I] AddrResolver--: Timed out waiting for address notification for fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9, retry: 15
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-: Dropping IPv6 ICMP6 msg, len:104, chksum:5375, ecn:no, sec:yes, error:AddressQuery, prio:low
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-:     src:[fdaa:bbcc:ddee:0:87ef:d332:1f87:f871]
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-:     dst:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-: Dropping IPv6 ICMP6 msg, len:104, chksum:e72a, ecn:no, sec:yes, error:AddressQuery, prio:low
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-:     src:[fdaa:bbcc:ddee:0:87ef:d332:1f87:f871]
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-:     dst:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-: Dropping IPv6 ICMP6 msg, len:104, chksum:fae2, ecn:no, sec:yes, error:AddressQuery, prio:low
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-:     src:[fdaa:bbcc:ddee:0:87ef:d332:1f87:f871]
Mar  7 16:20:39 otbr-agent[114]: 00:01:24.664 [N] MeshForwarder-:     dst:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]
Mar  7 16:20:40 otbr-agent[114]: 00:01:24.805 [N] MeshForwarder-: Dropping IPv6 ICMP6 msg, len:104, chksum:7a9c, ecn:no, sec:yes, error:Drop, prio:low
Mar  7 16:20:40 otbr-agent[114]: 00:01:24.805 [N] MeshForwarder-:     src:[fdaa:bbcc:ddee:0:87ef:d332:1f87:f871]
Mar  7 16:20:40 otbr-agent[114]: 00:01:24.805 [N] MeshForwarder-:     dst:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]

So the pings was dropped, (it's different than "not transmit/received"). Also I don't understand what is the address resolution that fails to resolve an IPv6 (?) What are we resolving here ?

It is possible that this issue is related to:

https://github.com/openthread/openthread/issues/7664 https://github.com/openthread/openthread/pull/8307

Note: I am using a old openthread version, because I am using multipan dongles from SiliconLabs. The openthread comes from https://github.com/SiliconLabs/gecko_sdk.git on the commit 799200bb6788939aa0fef97d7fc4ee9aca57148d

If the issue is related to the pull request in openthread repository (fixed 1d ago) then i will not be able to get the fix, as I have to use the openthread version from gecko_sdk due to multipan stuff..

I will add some suggestions for things to be investigated:

The Thread address resolution failing indicates Thread network could not find any "on-mesh" device with the requested IPv6 address. (This process is determining the RLOC mapping to an on-mesh IPv6 address - who has this address?)
Very likely the device owning this address is disconnected (detached, maybe reset, etc) or may not have been attached to the same Thread mesh.
- These are the first things I suggest to be investigated.

Also note that when the problem happens, the command ot-ctl childip does not show any IP for the thread device, but the thread device correctly appear when you execute the commande ot-ctl child table

childip command would list the IPv6 addresses of device's sleepy children that has registered their addresses with the parent. Only MTD (sleepy) children will do this (non-MTD (FTD) will not). So check if your device is MTD/sleepy, or not (is it attached properly).

Since the PR was mentioned in this, I will add few comments/clearifications:

https://github.com/openthread/openthread/pull/8307

This PR is not a bug fix, it is an enhancement. In short, it make the link establishment much fastr after device change its role within Thread mesh (e.g., allowing matter or other higher level protocols to potentially use shorter timeout). I expect matter to work with or without this.

Thanks for your responses,

The Thread address resolution failing indicates Thread network could not find any "on-mesh" device with the requested IPv6 address. (This process is determining the RLOC mapping to an on-mesh IPv6 address - who has this address?)

The IPv6 address “ fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9 ” appear in the logs of the device being commissioned and also in the logs of the Matter commissioner, as it resolved it using mDNS query.

03-07 16:19:28.479 11506 12145 D DIS     : Node ID resolved for 5BB2BF7451309CA6:000000000000002D
03-07 16:19:28.479 11506 12145 D DIS     :  Hostname: fdaa:bbcc:ddee:0
03-07 16:19:28.479 11506 12145 D DIS     :  IP Address #1: fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9
03-07 16:19:28.479 11506 12145 D DIS     :  Port: 5540
03-07 16:19:28.479 11506 12145 D DIS     :  Mrp Interval idle: 5000 ms
03-07 16:19:28.479 11506 12145 D DIS     :  Mrp Interval active: 300 ms
03-07 16:19:28.479 11506 12145 D DIS     :  TCP Supported: 0

IPv6 resolved during the FindOperational step

[00:00:31.309,661] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x101fc100)
[00:00:31.309,722] <dbg> chip: LogV: [DL]   Network Name: OpenThread-c37e
[00:00:31.309,814] <dbg> chip: LogV: [DL]   PAN Id: 0xC37E
[00:00:31.309,997] <dbg> chip: LogV: [DL]   Extended PAN Id: 0x1B1EF3DC76FCCEF8
[00:00:31.310,089] <dbg> chip: LogV: [DL]   Channel: 11
[00:00:31.310,211] <dbg> chip: LogV: [DL]   Mesh Prefix: fd0d:ef30:fec0:af6a::/64
[00:00:31.312,774] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x1100101d)
[00:00:31.312,835] <dbg> chip: LogV: [DL]   Device Role: DETACHED
[00:00:31.312,896] <dbg> chip: LogV: [DL]   Thread Unicast Addresses:
[00:00:31.313,079] <dbg> chip: LogV: [DL]        fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7/64 valid
[00:00:31.313,232] <dbg> chip: LogV: [DL]        fe80::30c0:9410:3f56:dc97/64 valid preferred
[00:00:32.542,724] <inf> chip: [DL]SRP Client was started, detected server: fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c
[00:00:32.544,433] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x200012a4)
[00:00:32.544,525] <dbg> chip: LogV: [DL]   Device Role: CHILD
[00:00:32.544,616] <dbg> chip: LogV: [DL]   Partition Id: 0x40358B7D
[00:00:32.547,180] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x00000001)
[00:00:32.547,241] <dbg> chip: LogV: [DL]   Thread Unicast Addresses:
[00:00:32.547,393] <dbg> chip: LogV: [DL]        fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9/64 valid preferred
[00:00:32.547,576] <dbg> chip: LogV: [DL]        fd0d:ef30:fec0:af6a:0:ff:fe00:e801/64 valid rloc
[00:00:32.547,760] <dbg> chip: LogV: [DL]        fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7/64 valid
[00:00:32.547,912] <dbg> chip: LogV: [DL]        fe80::30c0:9410:3f56:dc97/64 valid preferred

This is in the logs of the device when it connects to thread network and become child

[00:00:59.222,808] <inf> chip: [NP]Reverting Thread operational dataset
[00:00:59.232,421] <err> chip: [DL]Long dispatch time: 269 ms, for event type 32782
[00:00:59.232,543] <inf> chip: [FS]Fail-safe cleanly disarmed
[00:00:59.234,680] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x11002046)
[00:00:59.234,741] <dbg> chip: LogV: [DL]   Device Role: DISABLED
[00:00:59.234,802] <dbg> chip: LogV: [DL]   Thread Unicast Addresses:
[00:00:59.234,985] <dbg> chip: LogV: [DL]        fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9/64 valid preferred

This is in the logs of the device when the failsafe timer expire, the thread network informations are cleared.

So in these logs we can see that the device enter in thread network and obtain an IPv6, the IPv6 of the device is correctly resolved but the commissioner is not able to communicate with the device. Also my ping was not working, as we see in otbr-agent, the packets was discarded for some reason (?)

Very likely the device owning this address is disconnected (detached, maybe reset, etc) or may not have been attached to the same Thread mesh.

How do I know if the device is on the good mesh ?

In our step we create the thread network and then we read the dataset.

is it possible that after creating the thread network we read the dataset too fast using ot-ctl dataset active -x so it is not correct ?

—> I will check it tomorrow if adding a delay between network creation and dataset read helps

Note in our mechanism, if we don’t have thread or zigbee devices in our networks we re-create the thread network and get the dataset before the commissioning (*)

(*) In fact it is more complex: We execute a network scan (not just rssi) to find the good channel, then we use it for zigbee and thread. This is a limitation from the Silab multipan: we have to use the same channel for zigbee/thread, so once the channel is choose we can’t change it on the fly (channel manager/monitor is disabled of course). The idea is to choose the good channel by doing a scan when we need to commission the first device (zigbee or thread)

childip command would list the IPv6 addresses of device's sleepy children that has registered their addresses with the parent. Only sleepy children will do this (non-sleepy will not). So check if your device is sleepy, or not (is it attached properly).

in the logs it doesn’t seems to be sleepy but i will check tomorrow. I didn’t notice that non-sleepy devices was not in childip, i will check it too

I also had commissioning failing on step 15 and on step 18, but in my case I can ping OMR address from inside the OTBR container. In your case, aren´t you able to ping inside the own container? However, I noticed these logs when initializing my OTBR, did you also have them?

+ ip6tables -C FORWARD -o wpan0 -j OTBR_FORWARD_INGRESS
ip6tables v1.6.1: Couldn't load target `OTBR_FORWARD_INGRESS':No such file or directory

Try `ip6tables -h' or 'ip6tables --help' for more information.
+ ip6tables -L OTBR_FORWARD_INGRESS
ip6tables: No chain/target/match by that name.
+ ipset_destroy_if_exist otbr-ingress-deny-src
+ ipset list otbr-ingress-deny-src
ipset v6.34: Kernel support protocol versions 6-7 while userspace supports protocol versions 6-6
The set with the given name does not exist
+ ipset_destroy_if_exist otbr-ingress-deny-src-swap
+ ipset list otbr-ingress-deny-src-swap
ipset v6.34: Kernel support protocol versions 6-7 while userspace supports protocol versions 6-6
The set with the given name does not exist
+ ipset_destroy_if_exist otbr-ingress-allow-dst
+ ipset list otbr-ingress-allow-dst
ipset v6.34: Kernel support protocol versions 6-7 while userspace supports protocol versions 6-6
The set with the given name does not exist
+ ipset_destroy_if_exist otbr-ingress-allow-dst-swap
+ ipset list otbr-ingress-allow-dst-swap
ipset v6.34: Kernel support protocol versions 6-7 while userspace supports protocol versions 6-6
The set with the given name does not exist
+ ipset create -exist otbr-ingress-deny-src hash:net family inet6
+ ipset create -exist otbr-ingress-deny-src-swap hash:net family inet6
+ ipset create -exist otbr-ingress-allow-dst hash:net family inet6
+ ipset create -exist otbr-ingress-allow-dst-swap hash:net family inet6
+ ip6tables -N OTBR_FORWARD_INGRESS
+ ip6tables -I FORWARD 1 -o wpan0 -j OTBR_FORWARD_INGRESS
+ ip6tables -A OTBR_FORWARD_INGRESS -m pkttype --pkt-type unicast -i wpan0 -j DROP
+ ip6tables -A OTBR_FORWARD_INGRESS -m set --match-set otbr-ingress-deny-src src -j DROP
+ ip6tables -A OTBR_FORWARD_INGRESS -m set --match-set otbr-ingress-allow-dst dst -j ACCEPT
+ ip6tables -A OTBR_FORWARD_INGRESS -m pkttype --pkt-type unicast -j DROP
+ ip6tables -A OTBR_FORWARD_INGRESS -j ACCEPT

Hello @saramonteiro :

Note that this case only happens sometimes, but when it happens it's when I recreate the thread network, get the dataset and commission a device directly after.

Also when the problem happens, now I'm sure that it is not due to a wrong dataset.

Also, note that "ping failure" can be from many reasons, currently we identify multiple problems:

When the ping fails with timeout:

One possible case is when you re-create the thread networks without using the same prefix. The computers/Phones receive a router-advertisement packet with new prefix. New prefix means new route and new IPv6. Sometimes, when we have multiple routes/prefix, the Android phone use a wrong IPv6 source on the ping, and we get no responses from Thread devices. But when the old IPv6 arrive at expiration (due to expiration of the router advertisement), then the ping works because it start using the good IPv6 as source. We had this problem previously and we solved it by using the same prefix every time we initialise the thread network.
Another possible case: I don't know and this is what we try to understand in this issue

When the ping fails with "network unreachable" errors:

It means that there is no route to access the device.

The Android phone or computer running chip-tool is supposed to create a route in the routing table to access the thread network when he receive a router-advertisement.

The icmp-router-advertisement can be send by otbr-agent from multiple situations:

When the thread network is created
Periodically (because a RA have an expiration time, so it must be sent periodically)
When otbr-agent receive a imcp-router-solicitation packet (usually when the phone connects to a WiFi networks it automatically send a icmp-rs packet)

Sometimes on Android phones, the router advertisement packets are simply not received or processed. We found many issues about it that suggest it's due to power saving reasons in WiFi chipsets of android phones.

Note: We use the ping because it helps to understand why the commissioning fails...

In your case you can't ping the device from outside the container (computer/phone that runs chiptool ?) If yes, what kind of errors did you get when you ping ?

Timeout ?
Network unreachable/No route to host ?

Also, I don't have these lines in otbr-agent, because we don't have ipset feature in our system, so we disable OT_FIREWALL. We manage the firewall from outside.

@abtink You mention pinging a sleepy device - in my experience, a ping to a SED doesn't work. The parent stores the ping request but if the SED doesn't do a data poll soon then the request seems to be dropped. Or is it intended to work by default? (I used OTNS simulation.)

@caipiblack thanks for sharing the ideas.

My issue looks indeed different from yours. I never finished the commissioning process, errors happens on Step 18 - Find Operational with OS error = "Network is unreachable", and other times it stops before, on Step 15 - ThreadNetworkSetup with OS error = Internal error.

My setup is the following:

A RPI running the OTBR from a docker container and chip tool running in the same host, outside the container, of course.

Answering your questions:

I can´t ping from the host to OTBR, my issue is "Network unreachable". I think I am missing some IPV6 route configuration, but I didn´t find details on regarding that on the documentation, so I considered it was somehow automatically set up.

But again, this problem is like 1/10 of the commissioning failures.

@saramonteiro :

You have to check this:

Get the prefix IPv6 used in the thread network
Check in the routing table of your computer or android phone if you have a route for it

If not, you have to check if your computer/android phone receive router-advertisements packets (more easy on a computer) using wiresharks.

Hi @caipiblack Thanks for continuing the conversation. No, my route table for IPv6 is not aware about the OMR prefix from Thread Network. So, I should expect to have it automatically on my routing table instead of adding it manually?

So, I should expect to have it automatically on my routing table instead of adding it manually?

@saramonteiro , routes should be installed automatically when processing ICMPv6 Router Advertisements. You can reference the OpenThread Border Router setup scripts that enable this: https://github.com/openthread/ot-br-posix/blob/c012ce8e614c5310fac675e0257e6cc5591a5b0e/script/_border_routing#L45

@jwhui : Do you know in which cases a device can appear in ot-ctl child table but the command ot-ctl childip doesn’t return any ip’s?

For all:

There are many reasons of failure in the FindOperationnal step, i try to separate each problems.

Currently this is my known problems:

If the discovery always fails with “network unreachable” errors: Maybe the phone/computer does not receive RA or the computer running otbr-agent is not correctly configured. Also make sure that the firewalls is not blocking multicast/ra
If the discovery fails sometimes with “network unreachable” errors, it’s possibly because the phone is not on the good wifi network or the phone didn’t receive the RA. Note that the RA’s have an expiration, if the phone doesn’t receive some RA’s it remove the route. Currently we have this problem with android phones, we don’t know where the packet is missed.. We suspect power saving issues.. Or some filtering somewhere… If the phone stay long time connected to the wifi network, it loose the route (sometimes…)
if the discovery succeed but we get a timeout at find oprational, check if the phone is able to ping the thread device. We find one cause for this problem in our platform, it was because the source ipv6 was not the good one(*), the thread device was not responding or otbr-agent didn’t know how to route the packets. There are also another reasons (the original problem of this issue, but don’t know yet what is wrong…)

(*) In our case we found that this problem was due to the fact that:

We was not always using the same prefix in thread network
When we recreate the thread network, we was using ot-ctl factoryreset command. It’s not fully confirmed yet, but i think when we use this command to stop the network in order to create a new one then it doesn’t send RA packets with lifetime=0 to removes the routes and ips. But now when we have to recreate a new thread network we just use ot-ctl thread stop and then we recreate the network, so the old routes/ips are removed from computers/phones in LAN network.

Note that in our case we recreate the network in this case: if we commission a thread/zigbee device and there is no thread or zigbee devices commissioned yet:

we do it because we want to execute a network scan at the best moment: when we need to commission the first zigbee/thread device(as in our platform the channel can’t change on the fly (due to multipan stuff)) (channel monitor/manager=off)

Note that i am using a eve socket as matter device, so it’s a ftd and it can act as router.

Do you know in which cases a device can appear in ot-ctl child table but the command ot-ctl childip doesn’t return any ip’s?

The childip command only returns IP addresses for MTD children. Parents do not maintain IP addresses for FTD chidlren.

When we recreate the thread network, we was using ot-ctl factoryreset command. It’s not fully confirmed yet, but i think when we use this command to stop the network in order to create a new one then it doesn’t send RA packets with lifetime=0 to removes the routes and ips. But now when we have to recreate a new thread network we just use ot-ctl thread stop and then we recreate the network, so the old routes/ips are removed from computers/phones in LAN network.

Upon a reset, OpenThread relies on non-volatile storage to invalidate old prefixes that it advertised prior to reset. The factoryreset command will clear non-volatile storage and not allow OpenThread to invalidate old prefixes.

we do it because we want to execute a network scan at the best moment

Are you using the network scan to help choose a channel for the network? Note that a small channel sample is not great for predicting channel utilization over a long time horizon.

@caipiblack I think my issue is with the Router Advertisement. But I have no clue on how to solve it.

Here is a snippet of the logs from the docker container running OTBR (It looks like the advertisement is ok)

``` Mar 14 09:50:10 9a5213ad09fa otbr-agent[191]: 00:06:49.335 [I] BorderRouter--: Discovering infraif NAT64 prefix Mar 14 09:50:10 9a5213ad09fa otbr-agent[191]: 00:06:49.335 [I] BorderRouter--: NAT64 prefix timer scheduled in 300 seconds Mar 14 09:50:10 9a5213ad09fa otbr-agent[191]: 00:06:49.336 [I] Platform------: Handling host address response for ipv4only.arpa Mar 14 09:50:10 9a5213ad09fa otbr-agent[191]: 00:06:49.336 [I] BorderRouter--: Infraif NAT64 prefix: none Mar 14 09:50:10 9a5213ad09fa otbr-agent[191]: 00:06:49.337 [I] BorderRouter--: Start evaluating routing policy, scheduled in 3354 milliseconds Mar 14 09:50:13 9a5213ad09fa otbr-agent[191]: 00:06:52.691 [I] BorderRouter--: Evaluating routing policy Mar 14 09:50:13 9a5213ad09fa otbr-agent[191]: 00:06:52.691 [I] BorderRouter--: Evaluating NAT64 prefix Mar 14 09:50:13 9a5213ad09fa otbr-agent[191]: 00:06:52.692 [I] BorderRouter--: RouterAdvert: Added PIO for fd77:1cb6:583c:ff1::/64 (valid=1800, preferred=1800) Mar 14 09:50:13 9a5213ad09fa otbr-agent[191]: 00:06:52.692 [I] BorderRouter--: RouterAdvert: Added RIO for fd3a:60df:275a:1::/64 (lifetime=1800) Mar 14 09:50:13 9a5213ad09fa otbr-agent[191]: 00:06:52.693 [I] BorderRouter--: Sent Router Advertisement on infra netif 5 Mar 14 09:50:13 9a5213ad09fa otbr-agent[191]: 00:06:52.693 [I] BorderRouter--: Start evaluating routing policy, scheduled in 302467 milliseconds Mar 14 09:50:13 9a5213ad09fa otbr-agent[191]: 00:06:52.693 [I] BorderRouter--: Received Router Advertisement from fe80:0:0:0:42:acff:fe11:2 on infra netif 5 Mar 14 09:50:23 9a5213ad09fa otbr-agent[191]: 00:07:02.402 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1) Mar 14 09:50:23 9a5213ad09fa otbr-agent[191]: 00:07:02.415 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:d09c, ecn:no, to:0xffff, sec:no, prio:net Mar 14 09:50:23 9a5213ad09fa otbr-agent[191]: 00:07:02.415 [I] MeshForwarder-: src:[fe80:0:0:0:a8ef:5ce9:de34:9a06]:19788 Mar 14 09:50:23 9a5213ad09fa otbr-agent[191]: 00:07:02.415 [I] MeshForwarder-: dst:[ff02:0:0:0:0:0:0:1]:19788 Mar 14 09:50:50 9a5213ad09fa otbr-agent[191]: 00:07:29.132 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1) Mar 14 09:50:50 9a5213ad09fa otbr-agent[191]: 00:07:29.144 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:e0c8, ecn:no, to:0xffff, sec:no, prio:net Mar 14 09:50:50 9a5213ad09fa otbr-agent[191]: 00:07:29.144 [I] MeshForwarder-: src:[fe80:0:0:0:a8ef:5ce9:de34:9a06]:19788 Mar 14 09:50:50 9a5213ad09fa otbr-agent[191]: 00:07:29.144 [I] MeshForwarder-: dst:[ff02:0:0:0:0:0:0:1]:19788 ```

Here is the route table from OTBR

``` # ip -6 route show fd19:c442:63c5:fe3b::/64 dev wpan0 proto kernel metric 256 pref medium fd3a:60df:275a:1::/64 dev wpan0 proto kernel metric 256 pref medium fd77:1cb6:583c:ff1::/64 dev eth0 proto kernel metric 256 expires 1736sec pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium fe80::/64 dev wpan0 proto kernel metric 256 pref medium ```

Here is the route table from the host (Raspberry Running the docker container and chip-tool)

``` pi@raspberrypi:~ $ ip -6 route show ::1 dev lo proto kernel metric 256 pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium fe80::/64 dev wlan0 proto kernel metric 256 pref medium fe80::/64 dev veth48467df proto kernel metric 256 pref medium fe80::/64 dev docker0 proto kernel metric 256 pref medium ```

Here is the ot-ctl network details from OTBR

``` # sudo ot-ctl netdata show Prefixes: fd3a:60df:275a:1::/64 paos low 4c00 Routes: fd3a:60df:275a:2:0:0::/96 sn low 4c00 fd77:1cb6:583c:ff1::/64 s med 4c00 Services: 44970 01 6a000500000e10 s 4c00 44970 5d fd19c44263c5fe3b0d5432a3ea0c525dd11f s 4c00 Done # sudo ot-ctl ipaddr fd19:c442:63c5:fe3b:0:ff:fe00:fc11 fd3a:60df:275a:1:377a:bd47:532d:a383 fd19:c442:63c5:fe3b:0:ff:fe00:fc10 fd19:c442:63c5:fe3b:0:ff:fe00:fc38 fd19:c442:63c5:fe3b:0:ff:fe00:fc00 fd19:c442:63c5:fe3b:0:ff:fe00:4c00 fd19:c442:63c5:fe3b:d54:32a3:ea0c:525d fe80:0:0:0:a8ef:5ce9:de34:9a06 Done ```

@jwhui Also noticing that when I try running the docker container with backbone = wlan0, I have the following error:

otbr-agent[191]: 49d.17:10:40.768 [C] Platform------: platformBackboneInit() at backbone.cpp:62: Failure

@saramonteiro : I’m not familiar with otbr docker container but i think it add more complication than a normal install.

For the backbone issue, the wlan0 interface is on the raspberry right ? But you run otbr agent in a docker and in the docker i think you don’t have wlan0. But you should have an eth0 interface that is bridged to host interfaces.

You can try to use eth0 instead of wlan0 when you start otbr-agent from docker

Try to do it, if it doesn’t work i will try to run otbr on docker to help

But i think, we need to discuss about it on another issue (probably in openthread repo) because this problem is not related to my issue.

Also check that ip forwarding in ipv6 is enabled on the rpi, i think it can help

I'm experiencing similar issues, here are all my error logs:

chip:
[DL]Long dispatch time: 295 ms, for event type 16388
[DIS]Failed to advertise operational node: 3
[DIS]Failed to advertise extended commissionable node: 3
[DIS]Failed to finalize service update: 1c
[SVR]Failsafe timer expired
[SVR]Commissioning failed (attempt 4): 32
[DIS]Failed to advertise operational node: 3
[DIS]Failed to advertise extended commissionable node: 3
[DIS]Failed to finalize service update: 1c
[ZCL]OpCreds: Got FailSafeTimerExpired
[ZCL]OpCreds: Proceeding to FailSafeCleanup on fail-safe expiry!
[FP]Reverting pending fabric data for fabric 0x3
[FP]Warning: metadata not found during delete of fabric 0x3
[DIS]Failed to advertise extended commissionable node: 3
[DIS]Failed to finalize service update: 1c
[FP]Warning: metadata not found during delete of fabric 0x3
[ZCL]OpCreds: failed to delete fabric at index 3: d8
[DL]Long dispatch time: 177 ms, for event type 32782

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

Reproduction steps

(Re-)Create a new thread network
Get the thread dataset
Commission a Matter device using qrcode thread with chiptool using the previous dataset

During the commissioning, when you are at the step "Find Operational", if you see that it takes "anormal time" to finish, try to ping the resolved IPv6 from the computer running otbr-agent.

If you can't ping the device and the pairing failed, then you are on the problem

It appear 1/10 times, it's really hard to debug because when the pairing fails (failsafe timer expiration) the device is disconnected from Thread network.

Bug prevalence

1/10

GitHub hash of the SDK that was being used

v1.0.0

Platform

android, nrf, raspi

Platform Version(s)

No response

Anything else?

Logs of the commissioner (here it's android chip-tool modified):

03-07 16:19:25.439 11506 11531 D CTL     : Performing next commissioning step 'FindOperational'
03-07 16:19:25.439 11506 11531 D CSM     : FindOrEstablishSession: PeerId = [1:000000000000002D]
03-07 16:19:25.439 11506 11531 D CSM     : FindOrEstablishSession: No existing OperationalSessionSetup instance found
03-07 16:19:25.440 11506 11531 D CTL     : OperationalSessionSetup[1:000000000000002D]: State change 1 --> 2
03-07 16:19:25.440 11506 11531 D DIS     : Resolving 5BB2BF7451309CA6:000000000000002D ...
03-07 16:19:25.469 11506 11531 D NsdManagerServiceResolver: resolve: Starting service resolution for '5BB2BF7451309CA6-000000000000002D' type '_matter._tcp'
03-07 16:19:25.470 11506 11531 D DMG     : ICR moving to [AwaitingDe]
03-07 16:19:25.640 11506 12147 D DIS     : Checking node lookup status after 200 ms
03-07 16:19:27.938 11506 12147 D DL      : Received SendWriteRequest
03-07 16:19:28.004 11506 11531 D chip.BluetoothManager: MatterLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
03-07 16:19:28.448 11506 12145 I NsdManagerServiceResolver: Resolved service '5BB2BF7451309CA6-000000000000002D' to /fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9
03-07 16:19:28.479 11506 12145 D DIS     :  ----- entry [0] : T 0
03-07 16:19:28.479 11506 12145 D DIS     :  ----- entry [1] : SAI 300
03-07 16:19:28.479 11506 12145 D DIS     :  ----- entry [2] : SII 5000
03-07 16:19:28.479 11506 12145 D DIS     : Node ID resolved for 5BB2BF7451309CA6:000000000000002D
03-07 16:19:28.479 11506 12145 D DIS     :    Hostname: fdaa:bbcc:ddee:0
03-07 16:19:28.479 11506 12145 D DIS     :    IP Address #1: fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9
03-07 16:19:28.479 11506 12145 D DIS     :    Port: 5540
03-07 16:19:28.479 11506 12145 D DIS     :    Mrp Interval idle: 5000 ms
03-07 16:19:28.479 11506 12145 D DIS     :    Mrp Interval active: 300 ms
03-07 16:19:28.479 11506 12145 D DIS     :    TCP Supported: 0
03-07 16:19:28.480 11506 12145 D DIS     : Lookup clearing interface for non LL address
03-07 16:19:28.480 11506 12145 D DIS     : UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540: new best score: 4
03-07 16:19:28.480 11506 12145 D DIS     : Checking node lookup status after 3041 ms
03-07 16:19:28.481 11506 12145 D DIS     : OperationalSessionSetup[1:000000000000002D]: Updating device address to UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540 while in state 2
03-07 16:19:28.481 11506 12145 D CTL     : OperationalSessionSetup[1:000000000000002D]: State change 2 --> 3
03-07 16:19:28.481 11506 12145 D IN      : SecureSession[0x7b383fd368]: Allocated Type:2 LSID:52281
03-07 16:19:28.481 11506 12145 D SC      : Initiating session on local FabricIndex 1 from 0x000000000001B669 -> 0x000000000000002D
03-07 16:19:28.499 11506 12145 D TOO     : KVS: Getting key f/1/g
03-07 16:19:28.499 11506 12145 D TOO     : KVS: Getting key f/1/k/0
03-07 16:19:28.500 11506 12145 D TOO     : KVS: Getting key f/1/s/000000000000002D
03-07 16:19:28.500 11506 12145 D KeyValueStoreManager: Key 'f/1/s/000000000000002D' not found in shared preferences
03-07 16:19:28.500 11506 12145 D EM      : <<< [E:5624i M:33095801] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
03-07 16:19:28.500 11506 12145 D IN      : (U) Sending msg 33095801 to IP address 'UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540'
03-07 16:19:28.501 11506 12145 D SC      : Sent Sigma1 msg
03-07 16:19:28.501 11506 12145 D CTL     : OperationalSessionSetup[1:000000000000002D]: State change 3 --> 4
03-07 16:19:30.478 11506 11531 D chip.BluetoothManager: MatterLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
03-07 16:19:32.981 11506 12147 D DL      : Received SendWriteRequest
03-07 16:19:33.086 11506 11531 D chip.BluetoothManager: MatterLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
03-07 16:19:35.021 11506 12147 D EM      : Retransmitting MessageCounter:33095801 on exchange 5624i Send Cnt 1
03-07 16:19:35.022 11506 12147 D IN      : (U) Sending msg 33095801 to IP address 'UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540'
03-07 16:19:35.564 11506 11531 D chip.BluetoothManager: MatterLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
03-07 16:19:38.066 11506 12147 D DL      : Received SendWriteRequest
03-07 16:19:38.168 11506 11531 D chip.BluetoothManager: MatterLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
03-07 16:19:40.644 11506 11531 D chip.BluetoothManager: MatterLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
03-07 16:19:41.895 11506 12147 D EM      : Retransmitting MessageCounter:33095801 on exchange 5624i Send Cnt 2
03-07 16:19:41.896 11506 12147 D IN      : (U) Sending msg 33095801 to IP address 'UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540'
03-07 16:19:43.146 11506 12147 D DL      : Received SendWriteRequest
03-07 16:19:43.250 11506 11532 D chip.BluetoothManager: MatterLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
03-07 16:19:45.730 11506 11532 D chip.BluetoothManager: MatterLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
03-07 16:19:48.232 11506 12147 D DL      : Received SendWriteRequest
03-07 16:19:48.292 11506 11532 D chip.BluetoothManager: MatterLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
03-07 16:19:50.768 11506 11532 D chip.BluetoothManager: MatterLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
03-07 16:19:51.068 11506 12147 D EM      : Retransmitting MessageCounter:33095801 on exchange 5624i Send Cnt 3
03-07 16:19:51.068 11506 12147 D IN      : (U) Sending msg 33095801 to IP address 'UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540'
03-07 16:19:51.714 11506 11532 D BluetoothGatt: onClientConnectionState() - status=19 clientIf=7 device=D4:44:06:2E:2E:A2
03-07 16:19:51.731 11506 11532 I chip.BluetoothManager: MatterLight.onConnectionStateChange status = 19, newState=0
03-07 16:19:51.732 11506 11532 D AndroidBleManager: onConnectionStateChange Disconnected
03-07 16:19:51.734 11506 11532 D IN      : Clearing BLE pending packets.
03-07 16:19:51.735 11506 11532 I chip.BluetoothManager|onConnectionStateChange: STATE_DISCONNECTED
03-07 16:20:05.642 11506 12147 D EM      : Retransmitting MessageCounter:33095801 on exchange 5624i Send Cnt 4
03-07 16:20:05.643 11506 12147 D IN      : (U) Sending msg 33095801 to IP address 'UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540'
03-07 16:20:29.224 11506 12147 E EM      : Failed to Send CHIP MessageCounter:33095801 on exchange 5624i sendCount: 4 max retries: 4
03-07 16:20:40.991 11506 12147 E SC      : CASESession timed out while waiting for a response from the peer. Current state was 1
03-07 16:20:40.991 11506 12147 D IN      : SecureSession[0x7b383fd368]: Released - Type:2 LSID:52281
03-07 16:20:41.020 11506 12147 D CTL     : Device connection failed. Error ../../src/protocols/secure_channel/CASESession.cpp:295: CHIP Error 0x00000032: Timeout
03-07 16:20:41.088 11506 12147 I MTMethods: sendEvent
03-07 16:20:41.092 11506 12147 I MTMethods: { NativeMap: {"data":"{\"nodeId\":\"45\",\"stage\":\"FindOperational\"}","code":"50","codeDescription":"SUCCESS","from":"onCommissioningStatusUpdate"} }
03-07 16:20:41.095 11506 12147 D CTL     : Error on commissioning step 'FindOperational': '../../src/protocols/secure_channel/CASESession.cpp:295: CHIP Error 0x00000032: Timeout'
03-07 16:20:41.095 11506 12147 E CTL     : Failed to perform commissioning step 18
03-07 16:20:41.095 11506 12147 D CTL     : Going from commissioning step 'FindOperational' with lastErr = '../../src/protocols/secure_channel/CASESession.cpp:295: CHIP Error 0x00000032: Timeout' -> 'Cleanup'
03-07 16:20:41.096 11506 12147 D CTL     : Performing next commissioning step 'Cleanup' with completion status = '../../src/protocols/secure_channel/CASESession.cpp:295: CHIP Error 0x00000032: Timeout'
03-07 16:20:41.097 11506 12147 I MTMethods: sendEvent
03-07 16:20:41.097 11506 12147 I MTMethods: { NativeMap: {"data":"{\"nodeId\":\"45\",\"stage\":\"Cleanup\"}","code":"0","codeDescription":"SUCCESS","from":"onCommissioningStatusUpdate"} }
03-07 16:20:41.098 11506 12147 D CTL     : Successfully finished commissioning step 'Cleanup'
03-07 16:20:41.101 11506 12147 I MTMethods: sendEvent
03-07 16:20:41.101 11506 12147 I MTMethods: { NativeMap: {"data":"","code":"50","codeDescription":"FAILURE","from":"onCommissioningComplete"} }

Logs of the device (nRF52840 running the lighting app example):

[00:00:31.024,108] <inf> chip: [ZCL]OpCreds: Received an AddNOC command
[00:00:31.028,533] <inf> chip: [FP]Validating NOC chain
[00:00:31.087,188] <inf> chip: [FP]NOC chain validation successful
[00:00:31.087,341] <inf> chip: [FP]Added new fabric at index: 0x1
[00:00:31.087,585] <inf> chip: [FP]Assigned compressed fabric ID: 0x5BB2BF7451309CA6, node ID: 0x000000000000002D
[00:00:31.087,768] <inf> chip: [TS]Last Known Good Time: 2023-03-07T14:02:11
[00:00:31.087,951] <inf> chip: [TS]New proposed Last Known Good Time: 2021-06-10T00:00:00
[00:00:31.088,043] <inf> chip: [TS]Retaining current Last Known Good Time
[00:00:31.088,226] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_003E update version to 1a7d840
[00:00:31.088,439] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_003E update version to 1a7d841
[00:00:31.122,528] <dbg> chip: LogV: [EVL]LogEvent event number: 0x0000000000000002 priority: 1, endpoint id:  0x0 cluster id: 0x0000_001F event id: 0x0 Sys timestamp: 0x0000000000007991
[00:00:31.122,711] <inf> chip: [ZCL]OpCreds: ACL entry created for Fabric index 0x1 CASE Admin Subject 0x000000000001B669
[00:00:31.122,802] <dbg> chip: LogV: [DL]Using Thread extended MAC for hostname.
[00:00:31.122,985] <inf> chip: [DIS]Advertise operational node 5BB2BF7451309CA6-000000000000002D
[00:00:31.123,260] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_003E update version to 1a7d842
[00:00:31.123,474] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_003E update version to 1a7d843
[00:00:31.123,596] <dbg> chip: LogV: [DMG]Command handler moving to [ Preparing]
[00:00:31.123,718] <dbg> chip: LogV: [DMG]Command handler moving to [AddingComm]
[00:00:31.123,840] <dbg> chip: LogV: [DMG]Command handler moving to [AddedComma]
[00:00:31.123,931] <inf> chip: [ZCL]OpCreds: successfully created fabric index 0x1 via AddNOC
[00:00:31.124,267] <dbg> chip: LogV: [DMG]Decreasing reference count for CommandHandler, remaining 0
[00:00:31.125,213] <inf> chip: [EM]<<< [E:5621r M:116813147] (S) Msg TX to 1:FFFFFFFB00000000 [9CA6] --- Type 0001:09 (IM:InvokeCommandResponse)
[00:00:31.125,366] <inf> chip: [IN](S) Sending msg 116813147 on secure session with LSID: 41506
[00:00:31.125,549] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
[00:00:31.125,915] <dbg> chip: LogV: [DMG]Command handler moving to [CommandSen]
[00:00:31.126,007] <dbg> chip: LogV: [DMG]Command handler moving to [AwaitingDe]
[00:00:31.126,159] <err> chip: [DL]Long dispatch time: 106 ms, for event type 16388
[00:00:31.200,286] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:31.201,446] <dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
[00:00:31.203,033] <inf> chip: [EM]>>> [E:5622r M:6963398] (S) Msg RX from 1:FFFFFFFB00000000 [9CA6] --- Type 0001:08 (IM:InvokeCommandRequest)
[00:00:31.203,186] <dbg> chip: LogV: [EM]Handling via exchange: 5622r, Delegate: 0x20010c44
[00:00:31.203,857] <dbg> chip: LogV: [DMG]Received command for Endpoint=0 Cluster=0x0000_0031 Command=0x0000_0003
[00:00:31.210,113] <dbg> chip: LogV: [DMG]Command handler moving to [ Preparing]
[00:00:31.210,205] <dbg> chip: LogV: [DMG]Command handler moving to [AddingComm]
[00:00:31.210,357] <dbg> chip: LogV: [DMG]Command handler moving to [AddedComma]
[00:00:31.210,571] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_0030 update version to ac6117b6
[00:00:31.210,876] <dbg> chip: LogV: [DMG]Decreasing reference count for CommandHandler, remaining 0
[00:00:31.211,791] <inf> chip: [EM]<<< [E:5622r M:116813148] (S) Msg TX to 1:FFFFFFFB00000000 [9CA6] --- Type 0001:09 (IM:InvokeCommandResponse)
[00:00:31.211,975] <inf> chip: [IN](S) Sending msg 116813148 on secure session with LSID: 41506
[00:00:31.212,158] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
[00:00:31.212,524] <dbg> chip: LogV: [DMG]Command handler moving to [CommandSen]
[00:00:31.212,615] <dbg> chip: LogV: [DMG]Command handler moving to [AwaitingDe]
[00:00:31.291,168] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:31.291,320] <dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
[00:00:31.292,449] <inf> chip: [EM]>>> [E:5623r M:6963399] (S) Msg RX from 1:FFFFFFFB00000000 [9CA6] --- Type 0001:08 (IM:InvokeCommandRequest)
[00:00:31.292,633] <dbg> chip: LogV: [EM]Handling via exchange: 5623r, Delegate: 0x20010c44
[00:00:31.293,304] <dbg> chip: LogV: [DMG]Received command for Endpoint=0 Cluster=0x0000_0031 Command=0x0000_0006
[00:00:31.309,478] <dbg> chip: LogV: [DMG]Decreasing reference count for CommandHandler, remaining 1
[00:00:31.309,661] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x101fc100)
[00:00:31.309,722] <dbg> chip: LogV: [DL]   Network Name: OpenThread-c37e
[00:00:31.309,814] <dbg> chip: LogV: [DL]   PAN Id: 0xC37E
[00:00:31.309,997] <dbg> chip: LogV: [DL]   Extended PAN Id: 0x1B1EF3DC76FCCEF8
[00:00:31.310,089] <dbg> chip: LogV: [DL]   Channel: 11
[00:00:31.310,211] <dbg> chip: LogV: [DL]   Mesh Prefix: fd0d:ef30:fec0:af6a::/64
[00:00:31.312,774] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x1100101d)
[00:00:31.312,835] <dbg> chip: LogV: [DL]   Device Role: DETACHED
[00:00:31.312,896] <dbg> chip: LogV: [DL]   Thread Unicast Addresses:
[00:00:31.313,079] <dbg> chip: LogV: [DL]        fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7/64 valid
[00:00:31.313,232] <dbg> chip: LogV: [DL]        fe80::30c0:9410:3f56:dc97/64 valid preferred
[00:00:32.542,724] <inf> chip: [DL]SRP Client was started, detected server: fd0d:ef30:fec0:af6a:8469:8034:1d82:5e7c
[00:00:32.544,433] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x200012a4)
[00:00:32.544,525] <dbg> chip: LogV: [DL]   Device Role: CHILD
[00:00:32.544,616] <dbg> chip: LogV: [DL]   Partition Id: 0x40358B7D
[00:00:32.547,180] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x00000001)
[00:00:32.547,241] <dbg> chip: LogV: [DL]   Thread Unicast Addresses:
[00:00:32.547,393] <dbg> chip: LogV: [DL]        fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9/64 valid preferred
[00:00:32.547,576] <dbg> chip: LogV: [DL]        fd0d:ef30:fec0:af6a:0:ff:fe00:e801/64 valid rloc
[00:00:32.547,760] <dbg> chip: LogV: [DL]        fd0d:ef30:fec0:af6a:ad47:e9a9:eefa:e0a7/64 valid
[00:00:32.547,912] <dbg> chip: LogV: [DL]        fe80::30c0:9410:3f56:dc97/64 valid preferred
[00:00:32.550,994] <dbg> chip: LogV: [DMG]Command handler moving to [ Preparing]
[00:00:32.551,116] <dbg> chip: LogV: [DMG]Command handler moving to [AddingComm]
[00:00:32.551,239] <dbg> chip: LogV: [DMG]Command handler moving to [AddedComma]
[00:00:32.551,452] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_0030 update version to ac6117b7
[00:00:32.551,605] <dbg> chip: LogV: [DMG]Decreasing reference count for CommandHandler, remaining 0
[00:00:32.723,266] <inf> chip: [EM]<<< [E:5623r M:116813149] (S) Msg TX to 1:FFFFFFFB00000000 [9CA6] --- Type 0001:09 (IM:InvokeCommandResponse)
[00:00:32.723,449] <inf> chip: [IN](S) Sending msg 116813149 on secure session with LSID: 41506
[00:00:32.723,602] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 70)
[00:00:32.723,999] <dbg> chip: LogV: [DMG]Command handler moving to [CommandSen]
[00:00:32.724,090] <dbg> chip: LogV: [DMG]Command handler moving to [AwaitingDe]
[00:00:32.724,182] <err> chip: [DL]Long dispatch time: 174 ms, for event type 3
[00:00:32.724,304] <dbg> chip: LogV: [DL]Using Thread extended MAC for hostname.
[00:00:32.724,517] <inf> chip: [DIS]Advertise operational node 5BB2BF7451309CA6-000000000000002D
[00:00:32.724,639] <inf> chip: [SVR]Operational advertising enabled
[00:00:32.854,553] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:33.274,200] <dbg> chip: LogV: [DL]SRP update succeeded
[00:00:33.274,291] <inf> chip: [DIS]Setting operational delegate post init
[00:00:33.274,688] <inf> chip: [DIS]Updating services using commissioning mode 0
[00:00:33.274,780] <dbg> chip: LogV: [DL]Using Thread extended MAC for hostname.
[00:00:33.274,993] <inf> chip: [DIS]Advertise operational node 5BB2BF7451309CA6-000000000000002D
[00:00:33.275,482] <inf> chip: [DL]advertising srp service: 5BB2BF7451309CA6-000000000000002D._matter._tcp
[00:00:33.275,756] <dbg> chip: LogV: [DL]Using Thread extended MAC for hostname.
[00:00:33.277,069] <inf> chip: [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=0
[00:00:33.277,648] <inf> chip: [DL]advertising srp service: 8CCEED038B98779A._matterc._udp
[00:00:34.519,989] <dbg> chip: LogV: [DL]SRP update succeeded
[00:00:35.250,610] <dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
[00:00:37.751,251] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
[00:00:37.815,643] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:38.833,404] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x00000064)
[00:00:38.833,465] <dbg> chip: LogV: [DL]   Device Role: ROUTER
[00:00:40.335,784] <dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
[00:00:42.835,449] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
[00:00:42.900,817] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:43.551,757] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x00000200)
[00:00:45.420,989] <dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
[00:00:47.921,661] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
[00:00:47.986,022] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:50.506,195] <dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
[00:00:53.006,835] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
[00:00:53.071,228] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:55.546,386] <dbg> chip: LogV: [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
[00:00:58.047,027] <dbg> chip: LogV: [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
[00:00:58.111,419] <dbg> chip: LogV: [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
[00:00:58.963,745] <inf> chip: [FS]Fail-safe timer expired
[00:00:58.963,836] <err> chip: [SVR]Failsafe timer expired
[00:00:58.964,019] <dbg> chip: LogV: [IN]SecureSession[0x20002d10]: MarkForEviction Type:1 LSID:41506
[00:00:58.964,172] <inf> chip: [SC]SecureSession[0x20002d10]: Moving from state 'kActive' --> 'kPendingEviction'
[00:00:58.964,324] <dbg> chip: LogV: [IN]SecureSession[0x20002d10]: Released - Type:1 LSID:41506
[00:00:58.964,447] <err> chip: [SVR]Commissioning failed (attempt 1): 32
[00:00:58.964,508] <dbg> chip: LogV: [IN]Clearing BLE pending packets.
[00:00:58.964,599] <inf> chip: [BLE]Releasing end point's BLE connection back to application.
[00:00:58.964,691] <inf> chip: [DL]Closing BLE GATT connection (ConnId 00)
[00:00:58.969,573] <dbg> chip: LogV: [IN]SecureSession[0x20002d10]: Allocated Type:1 LSID:41508
[00:00:58.969,665] <dbg> chip: LogV: [SC]Assigned local session key ID 41508
[00:00:58.969,787] <dbg> chip: LogV: [SC]Waiting for PBKDF param request
[00:00:58.969,879] <dbg> chip: LogV: [DL]CHIPoBLE advertising set to on
[00:00:58.970,001] <inf> chip: [DIS]Updating services using commissioning mode 1
[00:00:58.970,123] <dbg> chip: LogV: [DL]Using Thread extended MAC for hostname.
[00:00:58.970,306] <inf> chip: [DIS]Advertise operational node 5BB2BF7451309CA6-000000000000002D
[00:00:58.970,886] <dbg> chip: LogV: [DL]Using Thread extended MAC for hostname.
[00:00:58.972,198] <inf> chip: [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=1
[00:00:58.972,869] <inf> chip: [DL]advertising srp service: 8CCEED038B98779A._matterc._udp
[00:00:58.973,175] <err> chip: [ZCL]OpCreds: Got FailSafeTimerExpired
[00:00:58.973,297] <err> chip: [ZCL]OpCreds: Proceeding to FailSafeCleanup on fail-safe expiry!
[00:00:58.973,358] <dbg> chip: LogV: [IN]Expiring all sessions for fabric 0x1!!
[00:00:58.973,480] <err> chip: [FP]Reverting pending fabric data for fabric 0x1
[00:00:58.973,968] <dbg> chip: LogV: [EVL]LogEvent event number: 0x0000000000000003 priority: 1, endpoint id:  0x0 cluster id: 0x0000_0028 event id: 0x2 Sys timestamp: 0x000000000000E65D
[00:00:58.974,090] <dbg> chip: LogV: [DMG]All ReadHandler-s are clean, clear GlobalDirtySet
[00:00:58.975,311] <err> chip: [FP]Warning: metadata not found during delete of fabric 0x1
[00:00:59.071,594] <inf> chip: [FP]Fabric (0x1) deleted.
[00:00:59.071,685] <inf> chip: [ZCL]UserLabel: Last Fabric index 0x1 was removed
[00:00:59.072,906] <inf> chip: [ZCL]OpCreds: Fabric index 0x1 was removed
[00:00:59.074,096] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_003E update version to 1a7d844
[00:00:59.074,310] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_003E update version to 1a7d845
[00:00:59.214,141] <inf> chip: [TS]Pending Last Known Good Time: 2023-03-07T14:02:11
[00:00:59.215,393] <inf> chip: [TS]Previous Last Known Good Time: 2023-03-07T14:02:11
[00:00:59.215,484] <inf> chip: [TS]Reverted Last Known Good Time to previous value
[00:00:59.215,942] <dbg> chip: LogV: [EVL]LogEvent event number: 0x0000000000000004 priority: 1, endpoint id:  0x0 cluster id: 0x0000_0028 event id: 0x2 Sys timestamp: 0x000000000000E74F
[00:00:59.216,064] <dbg> chip: LogV: [DMG]All ReadHandler-s are clean, clear GlobalDirtySet
[00:00:59.217,254] <err> chip: [FP]Warning: metadata not found during delete of fabric 0x1
[00:00:59.221,740] <err> chip: [ZCL]OpCreds: failed to delete fabric at index 1: d8
[00:00:59.221,954] <dbg> chip: LogV: [DMG]Endpoint 0, Cluster 0x0000_0030 update version to ac6117b8
[00:00:59.222,045] <dbg> chip: LogV: [ZCL]Failsafe timeout, tell platform driver to revert network credentials.
[00:00:59.222,808] <inf> chip: [NP]Reverting Thread operational dataset
[00:00:59.232,421] <err> chip: [DL]Long dispatch time: 269 ms, for event type 32782
[00:00:59.232,543] <inf> chip: [FS]Fail-safe cleanly disarmed
[00:00:59.234,680] <dbg> chip: LogV: [DL]OpenThread State Changed (Flags: 0x11002046)
[00:00:59.234,741] <dbg> chip: LogV: [DL]   Device Role: DISABLED
[00:00:59.234,802] <dbg> chip: LogV: [DL]   Thread Unicast Addresses:
[00:00:59.234,985] <dbg> chip: LogV: [DL]        fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9/64 valid preferred
[00:00:59.236,297] <inf> chip: [DL]BLE GAP connection terminated (reason 0x16)
[00:00:59.236,419] <inf> chip: [DL]Current number of connections: 0/1
[00:00:59.239,196] <inf> chip: [DL]CHIPoBLE advertising started
[00:00:59.241,516] <inf> chip: [DL]NFC Tag emulation started
[00:01:29.240,020] <inf> chip: [DL]CHIPoBLE advertising mode changed to slow

I am using the stack v1.0.0

related issues: #18766

@caipiblack Hi, my situation is similar to yours. My relevant devices are as follows:

An Android device running the chip-tool app
A Linux device running otbr-agent with otbr-firmware turned off
An ESP32-H2 running a thread light demo

When I use the app to perform Thread provisioning, I find that when the app tries to send the Sigma1 message to the address UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540, an error occurs:

03-07 16:19:35.021 11506 12147 D EM      : Retransmitting MessageCounter:33095801 on exchange 5624i Send Cnt 1
03-07 16:19:35.022 11506 12147 D IN      : (U) Sending msg 33095801 to IP address 'UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540'
03-07 16:19:35.564 11506 11531 D chip.BluetoothManager: MatterLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
03-07 16:19:38.066 11506 12147 D DL      : Received SendWriteRequest
03-07 16:19:38.168 11506 11531 D chip.BluetoothManager: MatterLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -0
03-07 16:19:40.644 11506 11531 D chip.BluetoothManager: MatterLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
03-07 16:19:41.895 11506 12147 D EM      : Retransmitting MessageCounter:33095801 on exchange 5624i Send Cnt 2
03-07 16:19:41.896 11506 12147 D IN      : (U) Sending msg 33095801 to IP address 'UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540'
03-07 16:19:43.146 11506 12147 D DL      : Received SendWriteRequest
03-07 16:19:43.250 11506 11532 D chip.BluetoothManager: MatterLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -0
03-07 16:19:45.730 11506 11532 D chip.BluetoothManager: MatterLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
03-07 16:19:48.232 11506 12147 D DL      : Received SendWriteRequest
03-07 16:19:48.292 11506 11532 D chip.BluetoothManager: MatterLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -0
03-07 16:19:50.768 11506 11532 D chip.BluetoothManager: MatterLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
03-07 16:19:51.068 11506 12147 D EM      : Retransmitting MessageCounter:33095801 on exchange 5624i Send Cnt 3
03-07 16:19:51.068 11506 12147 D IN      : (U) Sending msg 33095801 to IP address 'UDP:[fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9]:5540'
03-07 16:19:51.714 11506 11532 D BluetoothGatt: onClientConnectionState() - status=19 clientIf=7 device=D4:44:06:2E:2E:A2
03-07 16:19:51.731 11506 11532 I chip.BluetoothManager: MatterLight.onConnectionStateChange status = 19, newState=0
03-07 16:19:51.732 11506 11532 D AndroidBleManager: onConnectionStateChange Disconnected
03-07 16:19:51.734 11506 11532 D IN      : Clearing BLE pending packets.
03-07 16:19:51.735 11506 11532 I chip.BluetoothManager|onConnectionStateChange: STATE_DISCONNECTED
03-07 16:20:05.642 11506 12147 D EM      : Retransmitting MessageCounter:33095801 on exchange 5624i Send Cnt 4

I attempted to ping the address fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9 from the shell of the Android device running chip-tool, but it was unsuccessful.

However, this address can be pinged successfully from the Linux device running otbr-agent, as the virtual network interface wpan0 created by the command ot-ctl ifconfig up seems to communicate with this IPv6 address.

Additionally, I tried to ping the related IPv6 address of the wpan0 interface on the Linux device from the Android device running chip-tool, but it was unsuccessful until I used the command ot-ctl netdata register while forming the Thread network.

I am currently unsure how to enable IPv6 communication between the Android device running chip-tool and the ESP32-H2, allowing the Sigma1 message to be successfully sent to the ESP32-H2.

This issue occurs every time during Thread network configuration. How did you resolve this problem before?

Note: I am also using multipan dongles from SiliconLabs.

This seems like a manually configured prefix on the Thread network:

fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9

Typically, a Thread Border Router should randomly generate its own ULA. The Thread Border Router will then advertise that ULA prefix in an RA RIO on the infrastructure link.

This seems like a manually configured prefix on the Thread network:
fdaa:bbcc:ddee:0:819c:31a3:f1df:2ad9
Typically, a Thread Border Router should randomly generate its own ULA. The Thread Border Router will then advertise that ULA prefix in an RA RIO on the infrastructure link.

@jwhui Thank you for your response. I have tried both setting the prefix and not setting the prefix.

Do you mean that after the ot-ctl thread start command, a ULA prefix is automatically generated, and the Border Router broadcasts this ULA prefix through RA RIO? Then Android devices on the same subnet will receive the RA information and use the received ULA prefix to generate their own IPv6 addresses via Stateless Address Autoconfiguration (SLAAC)? And the generated addresses can access the ESP32H2?

If I do not use the ot-ctl prefix add fd11:22::/64 pasor command, the virtual network interface started with ifconfig up does indeed generate an IPv6 address with a ULA prefix automatically. However, because the app cannot access the ESP32H2, I also tried setting a fixed ULA prefix. Not using the ot-ctl prefix add fd11:22::/64 pasor. The detailed logs are as follows:

Network setup commands

ot-ctl dataset init new
ot-ctl dataset networkkey 00112233445566778899aabbccddeeff
ot-ctl dataset extpanid 1111111122222222
ot-ctl dataset panid 0x1234
ot-ctl dataset channel 15
ot-ctl dataset commit active
ot-ctl ifconfig up
ot-ctl thread start

Android log

2024-06-07 09:52:58.398 1462-1509/com.google.chip.chiptool D/CTL: Commissioning stage next step: 'SendNOC' -> 'ThreadNetworkSetup'
2024-06-07 09:52:58.398 1462-1509/com.google.chip.chiptool D/CTL: Performing next commissioning step 'ThreadNetworkSetup'
2024-06-07 09:52:58.404 1462-1509/com.google.chip.chiptool D/DMG: ICR moving to [AddingComm]
2024-06-07 09:52:58.404 1462-1509/com.google.chip.chiptool D/DMG: ICR moving to [AddedComma]
2024-06-07 09:52:58.404 1462-1509/com.google.chip.chiptool D/EM: <<< [E:30292i S:17401 M:45962961] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [BLE] --- Type 0001:08 (IM:InvokeCommandRequest)
2024-06-07 09:52:58.404 1462-1509/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:52:58.405 1462-1509/com.google.chip.chiptool D/DMG: ICR moving to [CommandSen]
2024-06-07 09:52:58.405 1462-1509/com.google.chip.chiptool D/DMG: ICR moving to [AwaitingDe]
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/EM: >>> [E:30292i S:17401 M:202546566] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/EM: Found matching exchange: 30292i, Delegate: 0x82018dc4
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG: ICR moving to [ResponseRe]
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG: InvokeResponseMessage =
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG: {
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:   suppressResponse = false, 
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:   InvokeResponseIBs =
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:   [
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:     InvokeResponseIB =
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:     {
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:       CommandDataIB =
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:       {
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:         CommandPathIB =
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:         {
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:           EndpointId = 0x0,
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:           ClusterId = 0x31,
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:           CommandId = 0x5,
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:         },
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:         
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:         CommandFields = 
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:         {
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:           0x0 = 0, 
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:           0x2 = 0, 
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:         },
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:       },
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:       
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:     },
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:     
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:   ],
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:   
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG:   InteractionModelRevision = 10
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG: },
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_0031 Command=0x0000_0005
2024-06-07 09:52:58.592 1462-1509/com.google.chip.chiptool D/CTL: Received NetworkConfig response, networkingStatus=0
2024-06-07 09:52:58.593 1462-1509/com.google.chip.chiptool D/CTL: Successfully finished commissioning step 'ThreadNetworkSetup'
2024-06-07 09:52:58.593 1462-1509/com.google.chip.chiptool D/CTL: Commissioning stage next step: 'ThreadNetworkSetup' -> 'FailsafeBeforeThreadEnable'
2024-06-07 09:52:58.593 1462-1509/com.google.chip.chiptool D/CTL: Performing next commissioning step 'FailsafeBeforeThreadEnable'
2024-06-07 09:52:58.593 1462-1509/com.google.chip.chiptool D/CTL: Skipping arming failsafe: new time (43 seconds from now) before old time (597 seconds from now)
2024-06-07 09:52:58.593 1462-1509/com.google.chip.chiptool D/CTL: Successfully finished commissioning step 'FailsafeBeforeThreadEnable'
2024-06-07 09:52:58.593 1462-1509/com.google.chip.chiptool D/CTL: Commissioning stage next step: 'FailsafeBeforeThreadEnable' -> 'ThreadNetworkEnable'
2024-06-07 09:52:58.593 1462-1509/com.google.chip.chiptool D/CTL: Performing next commissioning step 'ThreadNetworkEnable'
2024-06-07 09:52:58.593 1462-1509/com.google.chip.chiptool D/DMG: ICR moving to [AddingComm]
2024-06-07 09:52:58.593 1462-1509/com.google.chip.chiptool D/DMG: ICR moving to [AddedComma]
2024-06-07 09:52:58.594 1462-1509/com.google.chip.chiptool D/EM: <<< [E:30293i S:17401 M:45962962] (S) Msg TX to 0:FFFFFFFB00000000 [0000] [BLE] --- Type 0001:08 (IM:InvokeCommandRequest)
2024-06-07 09:52:58.594 1462-1509/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:52:58.598 1462-1509/com.google.chip.chiptool D/DMG: ICR moving to [CommandSen]
2024-06-07 09:52:58.599 1462-1509/com.google.chip.chiptool D/DMG: ICR moving to [AwaitingDe]
2024-06-07 09:53:00.152 1462-1509/com.google.chip.chiptool D/EM: >>> [E:30293i S:17401 M:202546567] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
2024-06-07 09:53:00.152 1462-1509/com.google.chip.chiptool D/EM: Found matching exchange: 30293i, Delegate: 0x82018d04
2024-06-07 09:53:00.152 1462-1509/com.google.chip.chiptool D/DMG: ICR moving to [ResponseRe]
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG: InvokeResponseMessage =
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG: {
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:   suppressResponse = false, 
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:   InvokeResponseIBs =
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:   [
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:     InvokeResponseIB =
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:     {
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:       CommandDataIB =
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:       {
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:         CommandPathIB =
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:         {
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:           EndpointId = 0x0,
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:           ClusterId = 0x31,
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:           CommandId = 0x7,
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:         },
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:         
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:         CommandFields = 
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:         {
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:           0x0 = 0, 
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:           0x2 = NULL
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:         },
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:       },
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:       
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:     },
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:     
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:   ],
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:   
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG:   InteractionModelRevision = 10
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG: },
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DMG: Received Command Response Data, Endpoint=0 Cluster=0x0000_0031 Command=0x0000_0007
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/CTL: Received ConnectNetwork response, networkingStatus=0
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/CTL: Successfully finished commissioning step 'ThreadNetworkEnable'
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/CTL: Commissioning stage next step: 'ThreadNetworkEnable' -> 'FindOperational'
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/CTL: Performing next commissioning step 'FindOperational'
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/IN: Expiring all sessions for node <0000000000000007, 1>!!
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/CSM: FindOrEstablishSession: PeerId = [1:0000000000000007]
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/CSM: FindOrEstablishSession: No existing OperationalSessionSetup instance found
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 1 --> 2
2024-06-07 09:53:00.153 1462-1509/com.google.chip.chiptool D/DIS: Resolving 7E17563DF640C0B7:0000000000000007 ...
2024-06-07 09:53:00.154 1462-1509/com.google.chip.chiptool D/NsdManagerServiceResolver: resolve: Starting service resolution for '7E17563DF640C0B7-0000000000000007' type '_matter._tcp'
2024-06-07 09:53:00.158 1462-1509/com.google.chip.chiptool D/DMG: ICR moving to [AwaitingDe]
2024-06-07 09:53:00.170 1462-3336/com.google.chip.chiptool D/NsdServiceFinderAndResolver: Service discovery started. regType: _matter._tcp
2024-06-07 09:53:00.355 1462-3359/com.google.chip.chiptool D/DIS: Checking node lookup status after 201 ms
2024-06-07 09:53:01.885 1462-3124/com.google.chip.chiptool D/TransportRuntime.CctTransportBackend: Making request to: https://firebaselogging.googleapis.com/v0cc/log/batch?format=json_proto3
2024-06-07 09:53:01.917 1462-3124/com.google.chip.chiptool D/NetworkSecurityConfig: No Network Security Config specified, using platform default
2024-06-07 09:53:01.919 1462-3124/com.google.chip.chiptool I/DpmTcmClient: RegisterTcmMonitor from: $Proxy0
2024-06-07 09:53:02.656 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:53:03.653 1462-3336/com.google.chip.chiptool D/NsdServiceFinderAndResolver: onServiceFound: found target service name: 7E17563DF640C0B7-0000000000000007, type: _matter._tcp., host: null, port: 0, txtRecord: 
2024-06-07 09:53:03.661 1462-3336/com.google.chip.chiptool I/NsdServiceFinderAndResolver: Discovery stopped: _matter._tcp
2024-06-07 09:53:03.673 1462-3336/com.google.chip.chiptool I/NsdServiceFinderAndResolver: Resolved service '7E17563DF640C0B7-0000000000000007' to /fd18:6132:bfee:1:517c:50d2:6d46:5ea, type : ._matter._tcp
2024-06-07 09:53:03.822 1462-3336/com.google.chip.chiptool D/DIS:  ----- entry [0] : T 1
2024-06-07 09:53:03.822 1462-3336/com.google.chip.chiptool D/DIS:  ----- entry [1] : SAI 800
2024-06-07 09:53:03.822 1462-3336/com.google.chip.chiptool D/DIS:  ----- entry [2] : SAT 4000
2024-06-07 09:53:03.822 1462-3336/com.google.chip.chiptool D/DIS:  ----- entry [3] : SII 800
2024-06-07 09:53:03.822 1462-3336/com.google.chip.chiptool D/DIS: Node ID resolved for 7E17563DF640C0B7:0000000000000007
2024-06-07 09:53:03.822 1462-3336/com.google.chip.chiptool D/DIS:   Hostname: fd18:6132:bfee:1
2024-06-07 09:53:03.822 1462-3336/com.google.chip.chiptool D/DIS:   IP Address #1: fd18:6132:bfee:1:517c:50d2:6d46:5ea
2024-06-07 09:53:03.822 1462-3336/com.google.chip.chiptool D/DIS:   Port: 5540
2024-06-07 09:53:03.822 1462-3336/com.google.chip.chiptool D/DIS:   Mrp Interval idle: 800 ms
2024-06-07 09:53:03.822 1462-3336/com.google.chip.chiptool D/DIS:   Mrp Interval active: 800 ms
2024-06-07 09:53:03.822 1462-3336/com.google.chip.chiptool D/DIS:   TCP Supported: 1
2024-06-07 09:53:03.823 1462-3336/com.google.chip.chiptool D/DIS: Lookup clearing interface for non LL address
2024-06-07 09:53:03.823 1462-3336/com.google.chip.chiptool D/DIS: UDP:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]:5540: new best score: 3
2024-06-07 09:53:03.823 1462-3336/com.google.chip.chiptool D/DIS: Checking node lookup status after 3670 ms
2024-06-07 09:53:03.823 1462-3336/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: Updating device address to UDP:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]:5540 while in state 2
2024-06-07 09:53:03.823 1462-3336/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 2 --> 3
2024-06-07 09:53:03.823 1462-3336/com.google.chip.chiptool D/IN: SecureSession[0x82018d00]: Allocated Type:2 LSID:17402
2024-06-07 09:53:03.823 1462-3336/com.google.chip.chiptool D/SC: Initiating session on local FabricIndex 1 from 0x000000000001B669 -> 0x0000000000000007
2024-06-07 09:53:03.862 1462-3336/com.google.chip.chiptool D/TOO: KVS: Getting key f/1/g
2024-06-07 09:53:03.862 1462-3336/com.google.chip.chiptool D/TOO: KVS: Getting key f/1/k/0
2024-06-07 09:53:03.862 1462-3336/com.google.chip.chiptool D/TOO: KVS: Getting key f/1/s/0000000000000007
2024-06-07 09:53:03.862 1462-3336/com.google.chip.chiptool D/KeyValueStoreManager: Key 'f/1/s/0000000000000007' not found in shared preferences
2024-06-07 09:53:03.863 1462-3336/com.google.chip.chiptool D/EM: <<< [E:30294i S:0 M:143197804] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]:5540] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
2024-06-07 09:53:03.863 1462-3336/com.google.chip.chiptool D/SC: Sent Sigma1 msg
2024-06-07 09:53:03.863 1462-3336/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 3 --> 4
2024-06-07 09:53:04.943 1462-3359/com.google.chip.chiptool D/EM: Retransmitting MessageCounter:143197804 on exchange 30294i Send Cnt 1
2024-06-07 09:53:05.903 1462-3359/com.google.chip.chiptool D/EM: Retransmitting MessageCounter:143197804 on exchange 30294i Send Cnt 2
2024-06-07 09:53:07.388 1462-3359/com.google.chip.chiptool D/EM: Retransmitting MessageCounter:143197804 on exchange 30294i Send Cnt 3
2024-06-07 09:53:07.916 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:53:09.756 1462-3359/com.google.chip.chiptool D/EM: Retransmitting MessageCounter:143197804 on exchange 30294i Send Cnt 4
2024-06-07 09:53:13.085 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:53:13.620 1462-3359/com.google.chip.chiptool E/EM: Failed to Send CHIP MessageCounter:143197804 on exchange 30294i sendCount: 4 max retries: 4
2024-06-07 09:53:17.133 1462-3359/com.google.chip.chiptool E/SC: CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-07 09:53:17.134 1462-3359/com.google.chip.chiptool D/IN: SecureSession[0x82018d00]: Released - Type:2 LSID:17402
2024-06-07 09:53:17.134 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 4 --> 2
2024-06-07 09:53:17.134 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 2 --> 1
2024-06-07 09:53:17.134 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup:attempts done: 1, attempts left: 2, retry delay 1s, status src/system/SystemLayerImplSelect.cpp:214: Success
2024-06-07 09:53:17.134 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 1 --> 6
2024-06-07 09:53:17.134 1462-3359/com.google.chip.chiptool E/CTL: Session establishment failed for <0000000000000007, 1>, error: src/protocols/secure_channel/CASESession.cpp:553: CHIP Error 0x00000032: Timeout.  Next retry expected to get a response to Sigma1 or fail within 8 seconds
2024-06-07 09:53:17.134 1462-3359/com.google.chip.chiptool D/CTL: Skipping arming failsafe: new time (68 seconds from now) before old time (579 seconds from now)
2024-06-07 09:53:18.135 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 6 --> 2
2024-06-07 09:53:18.135 1462-3359/com.google.chip.chiptool D/DIS: Resolving 7E17563DF640C0B7:0000000000000007 ...
2024-06-07 09:53:18.135 1462-3359/com.google.chip.chiptool D/NsdManagerServiceResolver: resolve: Starting service resolution for '7E17563DF640C0B7-0000000000000007' type '_matter._tcp'
2024-06-07 09:53:18.142 1462-3336/com.google.chip.chiptool D/NsdServiceFinderAndResolver: Service discovery started. regType: _matter._tcp
2024-06-07 09:53:18.143 1462-3336/com.google.chip.chiptool D/NsdServiceFinderAndResolver: onServiceFound: found target service name: 7E17563DF640C0B7-0000000000000007, type: _matter._tcp., host: null, port: 0, txtRecord: 
2024-06-07 09:53:18.146 1462-3336/com.google.chip.chiptool I/NsdServiceFinderAndResolver: Discovery stopped: _matter._tcp
2024-06-07 09:53:18.157 1462-3336/com.google.chip.chiptool I/NsdServiceFinderAndResolver: Resolved service '7E17563DF640C0B7-0000000000000007' to /fd18:6132:bfee:1:517c:50d2:6d46:5ea, type : ._matter._tcp
2024-06-07 09:53:18.161 1462-3336/com.google.chip.chiptool D/DIS:  ----- entry [0] : T 1
2024-06-07 09:53:18.161 1462-3336/com.google.chip.chiptool D/DIS:  ----- entry [1] : SAI 800
2024-06-07 09:53:18.161 1462-3336/com.google.chip.chiptool D/DIS:  ----- entry [2] : SAT 4000
2024-06-07 09:53:18.161 1462-3336/com.google.chip.chiptool D/DIS:  ----- entry [3] : SII 800
2024-06-07 09:53:18.161 1462-3336/com.google.chip.chiptool D/DIS: Node ID resolved for 7E17563DF640C0B7:0000000000000007
2024-06-07 09:53:18.161 1462-3336/com.google.chip.chiptool D/DIS:   Hostname: fd18:6132:bfee:1
2024-06-07 09:53:18.161 1462-3336/com.google.chip.chiptool D/DIS:   IP Address #1: fd18:6132:bfee:1:517c:50d2:6d46:5ea
2024-06-07 09:53:18.161 1462-3336/com.google.chip.chiptool D/DIS:   Port: 5540
2024-06-07 09:53:18.161 1462-3336/com.google.chip.chiptool D/DIS:   Mrp Interval idle: 800 ms
2024-06-07 09:53:18.161 1462-3336/com.google.chip.chiptool D/DIS:   Mrp Interval active: 800 ms
2024-06-07 09:53:18.161 1462-3336/com.google.chip.chiptool D/DIS:   TCP Supported: 1
2024-06-07 09:53:18.162 1462-3336/com.google.chip.chiptool D/DIS: Lookup clearing interface for non LL address
2024-06-07 09:53:18.162 1462-3336/com.google.chip.chiptool D/DIS: UDP:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]:5540: new best score: 3
2024-06-07 09:53:18.162 1462-3336/com.google.chip.chiptool D/DIS: Checking node lookup status after 27 ms
2024-06-07 09:53:18.162 1462-3336/com.google.chip.chiptool D/DIS: Keeping DNSSD lookup active
2024-06-07 09:53:18.252 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:53:18.335 1462-3359/com.google.chip.chiptool D/DIS: Checking node lookup status after 200 ms
2024-06-07 09:53:18.335 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: Updating device address to UDP:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]:5540 while in state 2
2024-06-07 09:53:18.335 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 2 --> 3
2024-06-07 09:53:18.335 1462-3359/com.google.chip.chiptool D/IN: SecureSession[0x82018d00]: Allocated Type:2 LSID:17403
2024-06-07 09:53:18.335 1462-3359/com.google.chip.chiptool D/SC: Initiating session on local FabricIndex 1 from 0x000000000001B669 -> 0x0000000000000007
2024-06-07 09:53:18.371 1462-3359/com.google.chip.chiptool D/TOO: KVS: Getting key f/1/g
2024-06-07 09:53:18.372 1462-3359/com.google.chip.chiptool D/TOO: KVS: Getting key f/1/k/0
2024-06-07 09:53:18.372 1462-3359/com.google.chip.chiptool D/TOO: KVS: Getting key f/1/s/0000000000000007
2024-06-07 09:53:18.372 1462-3359/com.google.chip.chiptool D/KeyValueStoreManager: Key 'f/1/s/0000000000000007' not found in shared preferences
2024-06-07 09:53:18.372 1462-3359/com.google.chip.chiptool D/EM: <<< [E:30295i S:0 M:143197805] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]:5540] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
2024-06-07 09:53:18.372 1462-3359/com.google.chip.chiptool D/SC: Sent Sigma1 msg
2024-06-07 09:53:18.372 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 3 --> 4
2024-06-07 09:53:19.352 1462-3359/com.google.chip.chiptool D/EM: Retransmitting MessageCounter:143197805 on exchange 30295i Send Cnt 1
2024-06-07 09:53:20.255 1462-3359/com.google.chip.chiptool D/EM: Retransmitting MessageCounter:143197805 on exchange 30295i Send Cnt 2
2024-06-07 09:53:21.852 1462-3359/com.google.chip.chiptool D/EM: Retransmitting MessageCounter:143197805 on exchange 30295i Send Cnt 3
2024-06-07 09:53:23.322 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:53:24.476 1462-3359/com.google.chip.chiptool D/EM: Retransmitting MessageCounter:143197805 on exchange 30295i Send Cnt 4
2024-06-07 09:53:28.395 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:53:28.526 1462-3359/com.google.chip.chiptool E/EM: Failed to Send CHIP MessageCounter:143197805 on exchange 30295i sendCount: 4 max retries: 4
2024-06-07 09:53:31.641 1462-3359/com.google.chip.chiptool E/SC: CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-07 09:53:31.641 1462-3359/com.google.chip.chiptool D/IN: SecureSession[0x82018d00]: Released - Type:2 LSID:17403
2024-06-07 09:53:31.642 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 4 --> 2
2024-06-07 09:53:31.642 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 2 --> 1
2024-06-07 09:53:31.642 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup:attempts done: 2, attempts left: 1, retry delay 36s, status src/system/SystemLayerImplSelect.cpp:214: Success
2024-06-07 09:53:31.642 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 1 --> 6
2024-06-07 09:53:31.642 1462-3359/com.google.chip.chiptool E/CTL: Session establishment failed for <0000000000000007, 1>, error: src/protocols/secure_channel/CASESession.cpp:553: CHIP Error 0x00000032: Timeout.  Next retry expected to get a response to Sigma1 or fail within 43 seconds
2024-06-07 09:53:31.642 1462-3359/com.google.chip.chiptool D/CTL: Skipping arming failsafe: new time (103 seconds from now) before old time (564 seconds from now)
2024-06-07 09:53:33.464 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:53:38.583 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:53:43.699 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:53:48.772 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:53:53.840 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:53:58.911 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:54:03.981 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:54:07.643 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 6 --> 2
2024-06-07 09:54:07.643 1462-3359/com.google.chip.chiptool D/DIS: Resolving 7E17563DF640C0B7:0000000000000007 ...
2024-06-07 09:54:07.643 1462-3359/com.google.chip.chiptool D/NsdManagerServiceResolver: resolve: Starting service resolution for '7E17563DF640C0B7-0000000000000007' type '_matter._tcp'
2024-06-07 09:54:07.649 1462-3336/com.google.chip.chiptool D/NsdServiceFinderAndResolver: Service discovery started. regType: _matter._tcp
2024-06-07 09:54:07.649 1462-3336/com.google.chip.chiptool D/NsdServiceFinderAndResolver: onServiceFound: found target service name: 7E17563DF640C0B7-0000000000000007, type: _matter._tcp., host: null, port: 0, txtRecord: 
2024-06-07 09:54:07.652 1462-3336/com.google.chip.chiptool I/NsdServiceFinderAndResolver: Discovery stopped: _matter._tcp
2024-06-07 09:54:07.662 1462-3336/com.google.chip.chiptool I/NsdServiceFinderAndResolver: Resolved service '7E17563DF640C0B7-0000000000000007' to /fd18:6132:bfee:1:517c:50d2:6d46:5ea, type : ._matter._tcp
2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS:  ----- entry [0] : T 1
2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS:  ----- entry [1] : SAI 800
2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS:  ----- entry [2] : SAT 4000
2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS:  ----- entry [3] : SII 800
2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS: Node ID resolved for 7E17563DF640C0B7:0000000000000007
2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS:   Hostname: fd18:6132:bfee:1
2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS:   IP Address #1: fd18:6132:bfee:1:517c:50d2:6d46:5ea
2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS:   Port: 5540
2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS:   Mrp Interval idle: 800 ms
2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS:   Mrp Interval active: 800 ms
2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS:   TCP Supported: 1
2024-06-07 09:54:07.665 1462-3336/com.google.chip.chiptool D/DIS: Lookup clearing interface for non LL address
2024-06-07 09:54:07.665 1462-3336/com.google.chip.chiptool D/DIS: UDP:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]:5540: new best score: 3
2024-06-07 09:54:07.665 1462-3336/com.google.chip.chiptool D/DIS: Checking node lookup status after 22 ms
2024-06-07 09:54:07.665 1462-3336/com.google.chip.chiptool D/DIS: Keeping DNSSD lookup active
2024-06-07 09:54:07.843 1462-3359/com.google.chip.chiptool D/DIS: Checking node lookup status after 200 ms
2024-06-07 09:54:07.843 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: Updating device address to UDP:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]:5540 while in state 2
2024-06-07 09:54:07.843 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 2 --> 3
2024-06-07 09:54:07.843 1462-3359/com.google.chip.chiptool D/IN: SecureSession[0x82018d00]: Allocated Type:2 LSID:17404
2024-06-07 09:54:07.843 1462-3359/com.google.chip.chiptool D/SC: Initiating session on local FabricIndex 1 from 0x000000000001B669 -> 0x0000000000000007
2024-06-07 09:54:07.880 1462-3359/com.google.chip.chiptool D/TOO: KVS: Getting key f/1/g
2024-06-07 09:54:07.880 1462-3359/com.google.chip.chiptool D/TOO: KVS: Getting key f/1/k/0
2024-06-07 09:54:07.881 1462-3359/com.google.chip.chiptool D/TOO: KVS: Getting key f/1/s/0000000000000007
2024-06-07 09:54:07.881 1462-3359/com.google.chip.chiptool D/KeyValueStoreManager: Key 'f/1/s/0000000000000007' not found in shared preferences
2024-06-07 09:54:07.881 1462-3359/com.google.chip.chiptool D/EM: <<< [E:30296i S:0 M:143197806] (U) Msg TX to 0:0000000000000000 [0000] [UDP:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]:5540] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
2024-06-07 09:54:07.881 1462-3359/com.google.chip.chiptool D/SC: Sent Sigma1 msg
2024-06-07 09:54:07.881 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 3 --> 4
2024-06-07 09:54:08.808 1462-3359/com.google.chip.chiptool D/EM: Retransmitting MessageCounter:143197806 on exchange 30296i Send Cnt 1
2024-06-07 09:54:09.099 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:54:09.872 1462-3359/com.google.chip.chiptool D/EM: Retransmitting MessageCounter:143197806 on exchange 30296i Send Cnt 2
2024-06-07 09:54:11.484 1462-3359/com.google.chip.chiptool D/EM: Retransmitting MessageCounter:143197806 on exchange 30296i Send Cnt 3
2024-06-07 09:54:13.980 1462-3359/com.google.chip.chiptool D/EM: Retransmitting MessageCounter:143197806 on exchange 30296i Send Cnt 4
2024-06-07 09:54:14.169 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:54:17.905 1462-3359/com.google.chip.chiptool E/EM: Failed to Send CHIP MessageCounter:143197806 on exchange 30296i sendCount: 4 max retries: 4
2024-06-07 09:54:19.287 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest
2024-06-07 09:54:21.150 1462-3359/com.google.chip.chiptool E/SC: CASESession timed out while waiting for a response from the peer. Current state was 1
2024-06-07 09:54:21.150 1462-3359/com.google.chip.chiptool D/IN: SecureSession[0x82018d00]: Released - Type:2 LSID:17404
2024-06-07 09:54:21.150 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 4 --> 2
2024-06-07 09:54:21.150 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: State change 2 --> 1
2024-06-07 09:54:21.150 1462-3359/com.google.chip.chiptool D/CTL: Device connection failed. Error src/protocols/secure_channel/CASESession.cpp:553: CHIP Error 0x00000032: Timeout
2024-06-07 09:54:21.150 1462-3359/com.google.chip.chiptool D/CTL: Error on commissioning step 'FindOperational': 'src/protocols/secure_channel/CASESession.cpp:553: CHIP Error 0x00000032: Timeout'
2024-06-07 09:54:21.150 1462-3359/com.google.chip.chiptool E/CTL: Failed to perform commissioning step 26
2024-06-07 09:54:21.150 1462-3359/com.google.chip.chiptool D/CTL: Going from commissioning step 'FindOperational' with lastErr = 'src/protocols/secure_channel/CASESession.cpp:553: CHIP Error 0x00000032: Timeout' -> 'Cleanup'
2024-06-07 09:54:21.150 1462-3359/com.google.chip.chiptool D/CTL: Performing next commissioning step 'Cleanup' with completion status = 'src/protocols/secure_channel/CASESession.cpp:553: CHIP Error 0x00000032: Timeout'
2024-06-07 09:54:21.151 1462-3359/com.google.chip.chiptool D/CTL: Successfully finished commissioning step 'Cleanup'
2024-06-07 09:54:21.153 1462-3359/com.google.chip.chiptool D/ChipDeviceController: Closing GATT and removing connection for 1
2024-06-07 09:54:24.461 1462-3359/com.google.chip.chiptool D/DL: Received SendWriteRequest

linux otbr-agent log

Jun  7 01:52:42 otbr-agent[1708]: 00:05:44.823 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Jun  7 01:52:42 otbr-agent[1708]: 00:05:44.844 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:1118, ecn:no, to:0xffff, sec:no, prio:net, radio:all
Jun  7 01:52:42 otbr-agent[1708]: 00:05:44.844 [I] MeshForwarder-:     src:[fe80:0:0:0:8c46:19f0:a14e:ee30]:19788
Jun  7 01:52:42 otbr-agent[1708]: 00:05:44.844 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Jun  7 01:52:59 otbr-agent[1708]: 00:06:01.467 [I] MeshForwarder-: Received IPv6 UDP msg, len:84, chksum:9c6d, ecn:no, from:1e19fea453aebf06, sec:no, prio:net, rss:-34.0, radio:15.4
Jun  7 01:52:59 otbr-agent[1708]: 00:06:01.467 [I] MeshForwarder-:     src:[fe80:0:0:0:1c19:fea4:53ae:bf06]:19788
Jun  7 01:52:59 otbr-agent[1708]: 00:06:01.467 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:2]:19788
Jun  7 01:52:59 otbr-agent[1708]: 00:06:01.467 [I] Mle-----------: Receive Parent Request (fe80:0:0:0:1c19:fea4:53ae:bf06)
Jun  7 01:52:59 otbr-agent[1708]: 00:06:01.474 [I] Mle-----------: Delay Parent Response (fe80:0:0:0:1c19:fea4:53ae:bf06)
Jun  7 01:52:59 otbr-agent[1708]: 00:06:01.474 [I] RadioSelector-: RadioSelector: NewRadio(OnRx) 15.4 - neighbor:[1e19fea453aebf06 rloc16:0x0000 radio-pref:{15.4:200} state:ParentReq]
Jun  7 01:52:59 otbr-agent[1708]: 00:06:01.656 [I] Mle-----------: Send delayed message (fe80:0:0:0:1c19:fea4:53ae:bf06)
Jun  7 01:52:59 otbr-agent[1708]: 00:06:01.684 [I] RadioSelector-: RadioSelector: UpdateOnTxSucc 15.4 - neighbor:[1e19fea453aebf06 rloc16:0x0000 radio-pref:{15.4:225} state:ParentReq]
Jun  7 01:52:59 otbr-agent[1708]: 00:06:01.684 [I] MeshForwarder-: Sent IPv6 UDP msg, len:129, chksum:5a49, ecn:no, to:1e19fea453aebf06, sec:no, prio:net, radio:15.4
Jun  7 01:52:59 otbr-agent[1708]: 00:06:01.684 [I] MeshForwarder-:     src:[fe80:0:0:0:8c46:19f0:a14e:ee30]:19788
Jun  7 01:52:59 otbr-agent[1708]: 00:06:01.684 [I] MeshForwarder-:     dst:[fe80:0:0:0:1c19:fea4:53ae:bf06]:19788
Jun  7 01:52:59 otbr-agent[1708]: 00:06:02.230 [I] MeshForwarder-: Received IPv6 UDP msg, len:108, chksum:b1a4, ecn:no, from:1e19fea453aebf06, sec:no, prio:net, rss:-34.0, radio:15.4
Jun  7 01:52:59 otbr-agent[1708]: 00:06:02.230 [I] MeshForwarder-:     src:[fe80:0:0:0:1c19:fea4:53ae:bf06]:19788
Jun  7 01:52:59 otbr-agent[1708]: 00:06:02.230 [I] MeshForwarder-:     dst:[fe80:0:0:0:8c46:19f0:a14e:ee30]:19788
Jun  7 01:52:59 otbr-agent[1708]: 00:06:02.231 [I] Mle-----------: Receive Child ID Request (fe80:0:0:0:1c19:fea4:53ae:bf06)
Jun  7 01:52:59 otbr-agent[1708]: 00:06:02.232 [I] Settings------: Added ChildInfo {rloc:0xbc01, extaddr:1e19fea453aebf06, timeout:240, mode:0x0f, version:4}
Jun  7 01:52:59 otbr-agent[1708]: 00:06:02.232 [I] Mle-----------: Send Child ID Response (fe80:0:0:0:1c19:fea4:53ae:bf06,0xbc01)
Jun  7 01:52:59 otbr-agent[1708]: 00:06:02.232 [I] Notifier------: StateChanged (0x00000400) [Child+]
Jun  7 01:52:59 otbr-agent[1708]: 00:06:02.233 [I] ChildSupervsn-: Starting Child Supervision
Jun  7 01:52:59 otbr-agent[1708]: 00:06:02.340 [I] MeshForwarder-: Sent IPv6 UDP msg, len:310, chksum:438c, ecn:no, to:1e19fea453aebf06, sec:yes, prio:net, radio:15.4
Jun  7 01:52:59 otbr-agent[1708]: 00:06:02.340 [I] MeshForwarder-:     src:[fe80:0:0:0:8c46:19f0:a14e:ee30]:19788
Jun  7 01:52:59 otbr-agent[1708]: 00:06:02.340 [I] MeshForwarder-:     dst:[fe80:0:0:0:1c19:fea4:53ae:bf06]:19788
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.031 [I] AddrResolver--: Cache entry added: fd45:ec85:b4c2:8b58:3671:b821:bc51:1472, 0xbc01 - snoop
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.065 [I] MeshForwarder-: Received IPv6 UDP msg, len:313, chksum:ccb4, ecn:no, from:0xbc01, sec:yes, prio:normal, rss:-34.25, radio:15.4
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.065 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:3671:b821:bc51:1472]:49154
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.065 [I] MeshForwarder-:     dst:[fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4]:53535
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.066 [I] SrpServer-----: Received DNS update from fd45:ec85:b4c2:8b58:3671:b821:bc51:1472
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.200 [I] SrpServer-----: Processed DNS update info
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.200 [I] SrpServer-----:     Host:1E19FEA453AEBF06.default.service.arpa.
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.200 [I] SrpServer-----:     Lease:0, key-lease:1209600, ttl:7200
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.200 [I] SrpServer-----:     No host address
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.200 [I] SrpServer-----: SRP update handler is notified (updatedId = 1061239936)
Jun  7 01:53:00 otbr-agent[1708]: [INFO]-ADPROXY-: Advertise SRP service updates: host=1E19FEA453AEBF06.default.service.arpa.
Jun  7 01:53:00 otbr-agent[1708]: [INFO]-MDNS----: Removing host 1E19FEA453AEBF06
Jun  7 01:53:00 otbr-agent[1708]: [INFO]-ADPROXY-: Handle unpublish SRP host '1E19FEA453AEBF06.default.service.arpa.': OK
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.201 [I] SrpServer-----: Handler result of SRP update (id = 1061239936) is received: OK
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.201 [I] SrpServer-----: Lease timer is stopped
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.201 [I] SrpServer-----: Send success response with granted lease: 0 and key lease: 680400
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.227 [I] MeshForwarder-: Sent IPv6 UDP msg, len:83, chksum:fcca, ecn:no, to:0xbc01, sec:yes, prio:low, radio:15.4
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.227 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4]:53535
Jun  7 01:53:00 otbr-agent[1708]: 00:06:03.227 [I] MeshForwarder-:     dst:[fd45:ec85:b4c2:8b58:3671:b821:bc51:1472]:49154
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.742 [I] MeshForwarder-: Received IPv6 UDP msg, len:735, chksum:2019, ecn:no, from:0xbc01, sec:yes, prio:normal, rss:-34.25, radio:15.4
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.742 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:3671:b821:bc51:1472]:49154
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.742 [I] MeshForwarder-:     dst:[fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4]:53535
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.742 [I] SrpServer-----: Received DNS update from fd45:ec85:b4c2:8b58:3671:b821:bc51:1472
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.877 [I] SrpServer-----: Processed DNS update info
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.878 [I] SrpServer-----:     Host:1E19FEA453AEBF06.default.service.arpa.
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.878 [I] SrpServer-----:     Lease:7200, key-lease:1209600, ttl:7200
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.878 [I] SrpServer-----:     1 host address(es):
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.878 [I] SrpServer-----:       fd18:6132:bfee:1:517c:50d2:6d46:5ea
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.878 [I] SrpServer-----:     Adding service '7E17563DF640C0B7-0000000000000007._matter._tcp.default.service.arpa.' subtype:_I7E17563DF640C0B7
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.878 [I] SrpServer-----:     Adding service '7E17563DF640C0B7-0000000000000007._matter._tcp.default.service.arpa.'
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.878 [I] SrpServer-----:     Adding service '8E66A2621D2BD529._matterc._udp.default.service.arpa.' subtype:_L3840
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.878 [I] SrpServer-----:     Adding service '8E66A2621D2BD529._matterc._udp.default.service.arpa.' subtype:_S15
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.878 [I] SrpServer-----:     Adding service '8E66A2621D2BD529._matterc._udp.default.service.arpa.' subtype:_V65521
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.878 [I] SrpServer-----:     Adding service '8E66A2621D2BD529._matterc._udp.default.service.arpa.'
Jun  7 01:53:01 otbr-agent[1708]: 00:06:03.878 [I] SrpServer-----: SRP update handler is notified (updatedId = 1061239937)
Jun  7 01:53:01 otbr-agent[1708]: [INFO]-ADPROXY-: Advertise SRP service updates: host=1E19FEA453AEBF06.default.service.arpa.
Jun  7 01:53:01 otbr-agent[1708]: [INFO]-MDNS----: Add subtype _I7E17563DF640C0B7 for service 7E17563DF640C0B7-0000000000000007._matter._tcp
Jun  7 01:53:01 otbr-agent[1708]: [INFO]-MDNS----: Commit avahi service 7E17563DF640C0B7-0000000000000007._matter._tcp
Jun  7 01:53:01 otbr-agent[1708]: [INFO]-MDNS----: Add subtype _L3840 for service 8E66A2621D2BD529._matterc._udp
Jun  7 01:53:01 otbr-agent[1708]: [INFO]-MDNS----: Add subtype _S15 for service 8E66A2621D2BD529._matterc._udp
Jun  7 01:53:01 otbr-agent[1708]: [INFO]-MDNS----: Add subtype _V65521 for service 8E66A2621D2BD529._matterc._udp
Jun  7 01:53:01 otbr-agent[1708]: [INFO]-MDNS----: Commit avahi service 8E66A2621D2BD529._matterc._udp
Jun  7 01:53:01 otbr-agent[1708]: [INFO]-MDNS----: Commit avahi host 1E19FEA453AEBF06
Jun  7 01:53:01 otbr-agent[1708]: 00:06:04.219 [I] MeshForwarder-: Sent IPv6 UDP msg, len:365, chksum:ff26, ecn:no, to:0xffff, sec:yes, prio:low, radio:all
Jun  7 01:53:01 otbr-agent[1708]: 00:06:04.219 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4]:5353
Jun  7 01:53:01 otbr-agent[1708]: 00:06:04.219 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.476 [I] MeshForwarder-: Sent IPv6 UDP msg, len:365, chksum:ff26, ecn:no, to:0xffff, sec:yes, prio:low, radio:all
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.476 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4]:5353
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.476 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.711 [I] MeshForwarder-: Sent IPv6 UDP msg, len:365, chksum:ff26, ecn:no, to:0xffff, sec:yes, prio:low, radio:all
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.711 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4]:5353
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.711 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Jun  7 01:53:02 otbr-agent[1708]: [INFO]-MDNS----: Avahi group (@0x787078) is established
Jun  7 01:53:02 otbr-agent[1708]: [INFO]-ADPROXY-: Handle publish SRP service '7E17563DF640C0B7-0000000000000007._matter._tcp.default.service.arpa.': OK
Jun  7 01:53:02 otbr-agent[1708]: [INFO]-ADPROXY-: Waiting for more publishing callbacks 2
Jun  7 01:53:02 otbr-agent[1708]: [INFO]-MDNS----: Avahi group (@0x78e348) is established
Jun  7 01:53:02 otbr-agent[1708]: [INFO]-ADPROXY-: Handle publish SRP service '8E66A2621D2BD529._matterc._udp.default.service.arpa.': OK
Jun  7 01:53:02 otbr-agent[1708]: [INFO]-ADPROXY-: Waiting for more publishing callbacks 1
Jun  7 01:53:02 otbr-agent[1708]: [INFO]-MDNS----: Avahi group (@0x786418) is established
Jun  7 01:53:02 otbr-agent[1708]: [INFO]-ADPROXY-: Handle publish SRP host '1E19FEA453AEBF06.default.service.arpa.': OK
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.832 [I] SrpServer-----: Handler result of SRP update (id = 1061239937) is received: OK
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.833 [I] SrpServer-----: Add new host 1E19FEA453AEBF06.default.service.arpa.
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.833 [I] SrpServer-----: Add new service '7E17563DF640C0B7-0000000000000007._matter._tcp.default.service.arpa.' subtype:_I7E17563DF640C0B7
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.833 [I] SrpServer-----: Add new service '7E17563DF640C0B7-0000000000000007._matter._tcp.default.service.arpa.'
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.833 [I] SrpServer-----: Add new service '8E66A2621D2BD529._matterc._udp.default.service.arpa.' subtype:_L3840
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.833 [I] SrpServer-----: Add new service '8E66A2621D2BD529._matterc._udp.default.service.arpa.' subtype:_S15
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.833 [I] SrpServer-----: Add new service '8E66A2621D2BD529._matterc._udp.default.service.arpa.' subtype:_V65521
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.833 [I] SrpServer-----: Add new service '8E66A2621D2BD529._matterc._udp.default.service.arpa.'
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.834 [I] Settings------: Saved SrpServerInfo {port:53535}
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.834 [I] SrpServer-----: Lease timer is scheduled for 7198 seconds
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.834 [I] SrpServer-----: Send success response with granted lease: 7200 and key lease: 680400
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.890 [I] MeshForwarder-: Sent IPv6 UDP msg, len:279, chksum:0815, ecn:no, to:0xffff, sec:yes, prio:low, radio:all
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.890 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4]:5353
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.890 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.976 [I] MeshForwarder-: Sent IPv6 UDP msg, len:324, chksum:9803, ecn:no, to:0xffff, sec:yes, prio:low, radio:all
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.976 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4]:5353
Jun  7 01:53:02 otbr-agent[1708]: 00:06:04.976 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Jun  7 01:53:02 otbr-agent[1708]: 00:06:05.002 [I] MeshForwarder-: Sent IPv6 UDP msg, len:110, chksum:2fb0, ecn:no, to:0xffff, sec:yes, prio:low, radio:all
Jun  7 01:53:02 otbr-agent[1708]: 00:06:05.002 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4]:5353
Jun  7 01:53:02 otbr-agent[1708]: 00:06:05.002 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Jun  7 01:53:02 otbr-agent[1708]: 00:06:05.026 [I] MeshForwarder-: Sent IPv6 UDP msg, len:83, chksum:e940, ecn:no, to:0xbc01, sec:yes, prio:low, radio:15.4
Jun  7 01:53:02 otbr-agent[1708]: 00:06:05.026 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4]:53535
Jun  7 01:53:02 otbr-agent[1708]: 00:06:05.026 [I] MeshForwarder-:     dst:[fd45:ec85:b4c2:8b58:3671:b821:bc51:1472]:49154
Jun  7 01:53:03 otbr-agent[1708]: 00:06:06.060 [I] MeshForwarder-: Sent IPv6 UDP msg, len:307, chksum:92f2, ecn:no, to:0xffff, sec:yes, prio:low, radio:all
Jun  7 01:53:03 otbr-agent[1708]: 00:06:06.060 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4]:5353
Jun  7 01:53:03 otbr-agent[1708]: 00:06:06.060 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Jun  7 01:53:03 otbr-agent[1708]: 00:06:06.145 [I] MeshForwarder-: Sent IPv6 UDP msg, len:324, chksum:9803, ecn:no, to:0xffff, sec:yes, prio:low, radio:all
Jun  7 01:53:03 otbr-agent[1708]: 00:06:06.146 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4]:5353
Jun  7 01:53:03 otbr-agent[1708]: 00:06:06.146 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Jun  7 01:53:05 otbr-agent[1708]: 00:06:08.082 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Jun  7 01:53:05 otbr-agent[1708]: 00:06:08.109 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:07f8, ecn:no, to:0xffff, sec:no, prio:net, radio:all
Jun  7 01:53:05 otbr-agent[1708]: 00:06:08.109 [I] MeshForwarder-:     src:[fe80:0:0:0:8c46:19f0:a14e:ee30]:19788
Jun  7 01:53:05 otbr-agent[1708]: 00:06:08.109 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Jun  7 01:53:05 otbr-agent[1708]: 00:06:08.222 [I] MeshForwarder-: Sent IPv6 UDP msg, len:293, chksum:cb0a, ecn:no, to:0xffff, sec:yes, prio:low, radio:all
Jun  7 01:53:05 otbr-agent[1708]: 00:06:08.222 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4]:5353
Jun  7 01:53:05 otbr-agent[1708]: 00:06:08.222 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Jun  7 01:53:05 otbr-agent[1708]: 00:06:08.330 [I] MeshForwarder-: Sent IPv6 UDP msg, len:371, chksum:742a, ecn:no, to:0xffff, sec:yes, prio:low, radio:all
Jun  7 01:53:05 otbr-agent[1708]: 00:06:08.330 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4]:5353
Jun  7 01:53:05 otbr-agent[1708]: 00:06:08.330 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Jun  7 01:53:05 otbr-agent[1708]: 00:06:08.357 [I] MeshForwarder-: Sent IPv6 UDP msg, len:110, chksum:9be8, ecn:no, to:0xffff, sec:yes, prio:low, radio:all
Jun  7 01:53:05 otbr-agent[1708]: 00:06:08.357 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4]:5353
Jun  7 01:53:05 otbr-agent[1708]: 00:06:08.357 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:fb]:5353
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.197 [I] AddrResolver--: Sent AddressQuery for fd18:6132:bfee:1:517c:50d2:6d46:5ea
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.197 [I] AddrResolver--: Cache entry added: fd18:6132:bfee:1:517c:50d2:6d46:5ea, 0xfffe - query request
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.219 [I] MeshForwarder-: Sent IPv6 HopOpts msg, len:86, chksum:0000, ecn:no, to:0xffff, sec:yes, prio:net, radio:all
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.219 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:0:ff:fe00:bc00]
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.219 [I] MeshForwarder-:     dst:[ff03:0:0:0:0:0:0:2]
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.249 [I] MeshForwarder-: Received IPv6 UDP msg, len:92, chksum:c4b2, ecn:no, from:0xbc01, sec:yes, prio:net, rss:-35.0, radio:15.4
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.249 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:0:ff:fe00:bc01]:61631
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.249 [I] MeshForwarder-:     dst:[fd45:ec85:b4c2:8b58:0:ff:fe00:bc00]:61631
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.249 [I] AddrResolver--: Received AddressNotify from 0xbc01 for fd18:6132:bfee:1:517c:50d2:6d46:5ea to 0xbc01
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.249 [I] AddrResolver--: Cache entry updated: fd18:6132:bfee:1:517c:50d2:6d46:5ea, 0xbc01 - rx notification
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.249 [I] AddrResolver--: Sent AddressNotify ack
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.256 [I] MeshForwarder-: Sent IPv6 HopOpts msg, len:86, chksum:0000, ecn:no, to:0xffff, sec:yes, prio:net, radio:all
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.256 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:0:ff:fe00:bc00]
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.256 [I] MeshForwarder-:     dst:[ff03:0:0:0:0:0:0:2]
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.275 [I] MeshForwarder-: Sent IPv6 UDP msg, len:54, chksum:7bab, ecn:no, to:0xbc01, sec:yes, prio:normal, radio:15.4
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.275 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:0:ff:fe00:bc00]:61631
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.275 [I] MeshForwarder-:     dst:[fd45:ec85:b4c2:8b58:0:ff:fe00:bc01]:61631
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.301 [I] MeshForwarder-: Sent IPv6 ICMP6 msg, len:104, chksum:86d6, ecn:no, to:0xbc01, sec:yes, prio:low, radio:15.4
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.301 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.301 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.352 [I] MeshForwarder-: Received IPv6 ICMP6 msg, len:104, chksum:85d6, ecn:no, from:0xbc01, sec:yes, prio:normal, rss:-35.0, radio:15.4
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.352 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:33 otbr-agent[1708]: 00:06:36.353 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:34 otbr-agent[1708]: 00:06:37.223 [I] MeshForwarder-: Sent IPv6 ICMP6 msg, len:104, chksum:9692, ecn:no, to:0xbc01, sec:yes, prio:low, radio:15.4
Jun  7 01:53:34 otbr-agent[1708]: 00:06:37.223 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:34 otbr-agent[1708]: 00:06:37.223 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:34 otbr-agent[1708]: 00:06:37.272 [I] MeshForwarder-: Received IPv6 ICMP6 msg, len:104, chksum:9592, ecn:no, from:0xbc01, sec:yes, prio:normal, rss:-35.0, radio:15.4
Jun  7 01:53:34 otbr-agent[1708]: 00:06:37.272 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:34 otbr-agent[1708]: 00:06:37.273 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:35 otbr-agent[1708]: 00:06:38.223 [I] MeshForwarder-: Sent IPv6 ICMP6 msg, len:104, chksum:b34e, ecn:no, to:0xbc01, sec:yes, prio:low, radio:15.4
Jun  7 01:53:35 otbr-agent[1708]: 00:06:38.223 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:35 otbr-agent[1708]: 00:06:38.223 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:35 otbr-agent[1708]: 00:06:38.292 [I] MeshForwarder-: Received IPv6 ICMP6 msg, len:104, chksum:b24e, ecn:no, from:0xbc01, sec:yes, prio:normal, rss:-35.0, radio:15.4
Jun  7 01:53:35 otbr-agent[1708]: 00:06:38.292 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:35 otbr-agent[1708]: 00:06:38.293 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:39 otbr-agent[1708]: 00:06:41.810 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Jun  7 01:53:39 otbr-agent[1708]: 00:06:41.831 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:3904, ecn:no, to:0xffff, sec:no, prio:net, radio:all
Jun  7 01:53:39 otbr-agent[1708]: 00:06:41.831 [I] MeshForwarder-:     src:[fe80:0:0:0:8c46:19f0:a14e:ee30]:19788
Jun  7 01:53:39 otbr-agent[1708]: 00:06:41.831 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Jun  7 01:53:42 otbr-agent[1708]: 00:06:44.727 [I] MeshForwarder-: Sent IPv6 ICMP6 msg, len:104, chksum:b517, ecn:no, to:0xbc01, sec:yes, prio:low, radio:15.4
Jun  7 01:53:42 otbr-agent[1708]: 00:06:44.728 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:42 otbr-agent[1708]: 00:06:44.728 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:42 otbr-agent[1708]: 00:06:44.783 [I] MeshForwarder-: Received IPv6 ICMP6 msg, len:104, chksum:b417, ecn:no, from:0xbc01, sec:yes, prio:normal, rss:-35.0, radio:15.4
Jun  7 01:53:42 otbr-agent[1708]: 00:06:44.783 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:42 otbr-agent[1708]: 00:06:44.783 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:43 otbr-agent[1708]: 00:06:45.726 [I] MeshForwarder-: Sent IPv6 ICMP6 msg, len:104, chksum:cbd3, ecn:no, to:0xbc01, sec:yes, prio:low, radio:15.4
Jun  7 01:53:43 otbr-agent[1708]: 00:06:45.726 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:43 otbr-agent[1708]: 00:06:45.726 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:43 otbr-agent[1708]: 00:06:45.773 [I] MeshForwarder-: Received IPv6 ICMP6 msg, len:104, chksum:cad3, ecn:no, from:0xbc01, sec:yes, prio:normal, rss:-36.0, radio:15.4
Jun  7 01:53:43 otbr-agent[1708]: 00:06:45.773 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:43 otbr-agent[1708]: 00:06:45.773 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:44 otbr-agent[1708]: 00:06:46.726 [I] MeshForwarder-: Sent IPv6 ICMP6 msg, len:104, chksum:e08f, ecn:no, to:0xbc01, sec:yes, prio:low, radio:15.4
Jun  7 01:53:44 otbr-agent[1708]: 00:06:46.727 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:44 otbr-agent[1708]: 00:06:46.727 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:44 otbr-agent[1708]: 00:06:46.783 [I] MeshForwarder-: Received IPv6 ICMP6 msg, len:104, chksum:df8f, ecn:no, from:0xbc01, sec:yes, prio:normal, rss:-35.0, radio:15.4
Jun  7 01:53:44 otbr-agent[1708]: 00:06:46.783 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:44 otbr-agent[1708]: 00:06:46.783 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:45 otbr-agent[1708]: 00:06:47.726 [I] MeshForwarder-: Sent IPv6 ICMP6 msg, len:104, chksum:f84b, ecn:no, to:0xbc01, sec:yes, prio:low, radio:15.4
Jun  7 01:53:45 otbr-agent[1708]: 00:06:47.727 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:45 otbr-agent[1708]: 00:06:47.727 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:45 otbr-agent[1708]: 00:06:47.773 [I] MeshForwarder-: Received IPv6 ICMP6 msg, len:104, chksum:f74b, ecn:no, from:0xbc01, sec:yes, prio:normal, rss:-35.0, radio:15.4
Jun  7 01:53:45 otbr-agent[1708]: 00:06:47.773 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:45 otbr-agent[1708]: 00:06:47.773 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:46 otbr-agent[1708]: 00:06:48.726 [I] MeshForwarder-: Sent IPv6 ICMP6 msg, len:104, chksum:1108, ecn:no, to:0xbc01, sec:yes, prio:low, radio:15.4
Jun  7 01:53:46 otbr-agent[1708]: 00:06:48.726 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:46 otbr-agent[1708]: 00:06:48.727 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:46 otbr-agent[1708]: 00:06:48.783 [I] MeshForwarder-: Received IPv6 ICMP6 msg, len:104, chksum:1008, ecn:no, from:0xbc01, sec:yes, prio:normal, rss:-35.0, radio:15.4
Jun  7 01:53:46 otbr-agent[1708]: 00:06:48.783 [I] MeshForwarder-:     src:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]
Jun  7 01:53:46 otbr-agent[1708]: 00:06:48.783 [I] MeshForwarder-:     dst:[fd18:6132:bfee:1:d40:6155:41e1:3e64]
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.496 [I] MeshForwarder-: Received IPv6 UDP msg, len:73, chksum:7750, ecn:no, from:0xbc01, sec:yes, prio:net, rss:-34.0, radio:15.4
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.496 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:0:ff:fe00:bc01]:61631
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.496 [I] MeshForwarder-:     dst:[fd45:ec85:b4c2:8b58:0:ff:fe00:bc00]:61631
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.497 [I] Mle-----------: Receive Address Solicit (fd45:ec85:b4c2:8b58:0:ff:fe00:bc01)
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.497 [N] RouterTable---: Allocate router id 26
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.497 [I] Mle-----------: Send Address Reply (fd45:ec85:b4c2:8b58:0:ff:fe00:bc01)
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.497 [I] AddrResolver--: Cache entry removed: fd18:6132:bfee:1:517c:50d2:6d46:5ea, 0xbc01, list:cached - removing rloc16
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.497 [I] AddrResolver--: Cache entry removed: fd45:ec85:b4c2:8b58:3671:b821:bc51:1472, 0xbc01, list:cached - removing rloc16
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.497 [I] RouterTable---: Route table
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.497 [I] RouterTable---:     47 0xbc00 - me - leader
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.497 [I] RouterTable---:     26 0x6800
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.519 [I] MeshForwarder-: Sent IPv6 UDP msg, len:73, chksum:133c, ecn:no, to:0xbc01, sec:yes, prio:net, radio:15.4
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.519 [I] MeshForwarder-:     src:[fd45:ec85:b4c2:8b58:0:ff:fe00:bc00]:61631
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.520 [I] MeshForwarder-:     dst:[fd45:ec85:b4c2:8b58:0:ff:fe00:bc01]:61631
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.572 [I] MeshForwarder-: Received IPv6 UDP msg, len:91, chksum:db76, ecn:no, from:1e19fea453aebf06, sec:no, prio:net, rss:-35.0, radio:15.4
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.572 [I] MeshForwarder-:     src:[fe80:0:0:0:1c19:fea4:53ae:bf06]:19788
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.573 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.573 [I] Mle-----------: Receive Advertisement (fe80:0:0:0:1c19:fea4:53ae:bf06,0x6800)
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.573 [I] Settings------: Read ChildInfo {rloc:0xbc01, extaddr:1e19fea453aebf06, timeout:240, mode:0x0f, version:4}
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.574 [I] Settings------: Removed ChildInfo {rloc:0xbc01, extaddr:1e19fea453aebf06, timeout:240, mode:0x0f, version:4}
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.574 [I] RouterTable---: Route table
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.574 [I] RouterTable---:     47 0xbc00 - me - leader
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.574 [I] RouterTable---:     26 0x6800 - nbr{lq[i/o]:3/3 cost:1}
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.574 [I] Notifier------: StateChanged (0x00000800) [Child-]
Jun  7 01:53:52 otbr-agent[1708]: 00:06:54.574 [I] ChildSupervsn-: Stopping Child Supervision
Jun  7 01:53:52 otbr-agent[1708]: 00:06:55.186 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Jun  7 01:53:52 otbr-agent[1708]: 00:06:55.209 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:5601, ecn:no, to:0xffff, sec:no, prio:net, radio:all
Jun  7 01:53:52 otbr-agent[1708]: 00:06:55.209 [I] MeshForwarder-:     src:[fe80:0:0:0:8c46:19f0:a14e:ee30]:19788
Jun  7 01:53:52 otbr-agent[1708]: 00:06:55.209 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Jun  7 01:53:52 otbr-agent[1708]: 00:06:55.388 [I] MeshForwarder-: Received IPv6 UDP msg, len:91, chksum:2df2, ecn:no, from:1e19fea453aebf06, sec:no, prio:net, rss:-33.0, radio:15.4
Jun  7 01:53:52 otbr-agent[1708]: 00:06:55.388 [I] MeshForwarder-:     src:[fe80:0:0:0:1c19:fea4:53ae:bf06]:19788
Jun  7 01:53:52 otbr-agent[1708]: 00:06:55.388 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Jun  7 01:53:52 otbr-agent[1708]: 00:06:55.389 [I] Mle-----------: Receive Advertisement (fe80:0:0:0:1c19:fea4:53ae:bf06,0x6800)
Jun  7 01:53:54 otbr-agent[1708]: 00:06:57.258 [I] MeshForwarder-: Received IPv6 UDP msg, len:91, chksum:41ce, ecn:no, from:1e19fea453aebf06, sec:no, prio:net, rss:-33.0, radio:15.4
Jun  7 01:53:54 otbr-agent[1708]: 00:06:57.258 [I] MeshForwarder-:     src:[fe80:0:0:0:1c19:fea4:53ae:bf06]:19788
Jun  7 01:53:54 otbr-agent[1708]: 00:06:57.258 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Jun  7 01:53:54 otbr-agent[1708]: 00:06:57.259 [I] Mle-----------: Receive Advertisement (fe80:0:0:0:1c19:fea4:53ae:bf06,0x6800)
Jun  7 01:53:54 otbr-agent[1708]: 00:06:57.259 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Jun  7 01:53:54 otbr-agent[1708]: 00:06:57.281 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:17d9, ecn:no, to:0xffff, sec:no, prio:net, radio:all
Jun  7 01:53:54 otbr-agent[1708]: 00:06:57.281 [I] MeshForwarder-:     src:[fe80:0:0:0:8c46:19f0:a14e:ee30]:19788
Jun  7 01:53:54 otbr-agent[1708]: 00:06:57.281 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Jun  7 01:53:57 otbr-agent[1708]: 00:07:00.312 [I] MeshForwarder-: Received IPv6 UDP msg, len:91, chksum:c133, ecn:no, from:1e19fea453aebf06, sec:no, prio:net, rss:-34.0, radio:15.4
Jun  7 01:53:57 otbr-agent[1708]: 00:07:00.312 [I] MeshForwarder-:     src:[fe80:0:0:0:1c19:fea4:53ae:bf06]:19788
Jun  7 01:53:57 otbr-agent[1708]: 00:07:00.312 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Jun  7 01:53:57 otbr-agent[1708]: 00:07:00.312 [I] Mle-----------: Receive Advertisement (fe80:0:0:0:1c19:fea4:53ae:bf06,0x6800)
Jun  7 01:53:58 otbr-agent[1708]: 00:07:01.009 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Jun  7 01:53:58 otbr-agent[1708]: 00:07:01.029 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:00ea, ecn:no, to:0xffff, sec:no, prio:net, radio:all
Jun  7 01:53:58 otbr-agent[1708]: 00:07:01.029 [I] MeshForwarder-:     src:[fe80:0:0:0:8c46:19f0:a14e:ee30]:19788
Jun  7 01:53:58 otbr-agent[1708]: 00:07:01.029 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Jun  7 01:54:03 otbr-agent[1708]: 00:07:05.793 [I] Platform------: [netif] Message dropped by Thread
Jun  7 01:54:03 otbr-agent[1708]: 00:07:06.087 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Jun  7 01:54:03 otbr-agent[1708]: 00:07:06.108 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:456a, ecn:no, to:0xffff, sec:no, prio:net, radio:all
Jun  7 01:54:03 otbr-agent[1708]: 00:07:06.108 [I] MeshForwarder-:     src:[fe80:0:0:0:8c46:19f0:a14e:ee30]:19788
Jun  7 01:54:03 otbr-agent[1708]: 00:07:06.108 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Jun  7 01:54:06 otbr-agent[1708]: 00:07:08.528 [I] MeshForwarder-: Received IPv6 UDP msg, len:91, chksum:545f, ecn:no, from:1e19fea453aebf06, sec:no, prio:net, rss:-34.0, radio:15.4
Jun  7 01:54:06 otbr-agent[1708]: 00:07:08.528 [I] MeshForwarder-:     src:[fe80:0:0:0:1c19:fea4:53ae:bf06]:19788
Jun  7 01:54:06 otbr-agent[1708]: 00:07:08.528 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Jun  7 01:54:06 otbr-agent[1708]: 00:07:08.529 [I] Mle-----------: Receive Advertisement (fe80:0:0:0:1c19:fea4:53ae:bf06,0x6800)
Jun  7 01:54:16 otbr-agent[1708]: 00:07:19.208 [I] MeshForwarder-: Received IPv6 UDP msg, len:91, chksum:08e5, ecn:no, from:1e19fea453aebf06, sec:no, prio:net, rss:-34.0, radio:15.4
Jun  7 01:54:16 otbr-agent[1708]: 00:07:19.208 [I] MeshForwarder-:     src:[fe80:0:0:0:1c19:fea4:53ae:bf06]:19788
Jun  7 01:54:16 otbr-agent[1708]: 00:07:19.209 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Jun  7 01:54:16 otbr-agent[1708]: 00:07:19.209 [I] Mle-----------: Receive Advertisement (fe80:0:0:0:1c19:fea4:53ae:bf06,0x6800)
Jun  7 01:54:21 otbr-agent[1708]: 00:07:24.122 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Jun  7 01:54:21 otbr-agent[1708]: 00:07:24.144 [I] MeshForwarder-: Sent IPv6 UDP msg, len:91, chksum:8f2f, ecn:no, to:0xffff, sec:no, prio:net, radio:all
Jun  7 01:54:21 otbr-agent[1708]: 00:07:24.144 [I] MeshForwarder-:     src:[fe80:0:0:0:8c46:19f0:a14e:ee30]:19788
Jun  7 01:54:21 otbr-agent[1708]: 00:07:24.144 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788

linux network

~ # ip -6 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qlen 1
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 fe80::e11:5ff:fef0:a000/64 scope link 
       valid_lft forever preferred_lft forever
6: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 fd11:1111:1122:2222:e11:5ff:fef0:a000/64 scope global dynamic 
       valid_lft 1665sec preferred_lft 1665sec
    inet6 fe80::e11:5ff:fef0:a000/64 scope link 
       valid_lft forever preferred_lft forever
7: wpan0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qlen 500
    inet6 fd45:ec85:b4c2:8b58:0:ff:fe00:fc11/64 scope global deprecated flags 02 
       valid_lft forever preferred_lft 0sec
    inet6 fd45:ec85:b4c2:8b58:0:ff:fe00:fc38/64 scope global deprecated flags 02 
       valid_lft forever preferred_lft 0sec
    inet6 fd45:ec85:b4c2:8b58:0:ff:fe00:fc10/64 scope global deprecated flags 02 
       valid_lft forever preferred_lft 0sec
    inet6 fd18:6132:bfee:1:d40:6155:41e1:3e64/64 scope global flags 02 
       valid_lft forever preferred_lft forever
    inet6 fd45:ec85:b4c2:8b58:0:ff:fe00:fc00/64 scope global deprecated flags 02 
       valid_lft forever preferred_lft 0sec
    inet6 fd45:ec85:b4c2:8b58:0:ff:fe00:bc00/64 scope global deprecated flags 02 
       valid_lft forever preferred_lft 0sec
    inet6 fd45:ec85:b4c2:8b58:e625:5a80:356:c6f4/64 scope global deprecated flags 02 
       valid_lft forever preferred_lft 0sec
    inet6 fe80::8c46:19f0:a14e:ee30/64 scope link flags 02 
       valid_lft forever preferred_lft forever

~ # ping6 fd18:6132:bfee:1:517c:50d2:6d46:5ea
PING fd18:6132:bfee:1:517c:50d2:6d46:5ea (fd18:6132:bfee:1:517c:50d2:6d46:5ea): 56 data bytes
64 bytes from fd18:6132:bfee:1:517c:50d2:6d46:5ea: seq=0 ttl=255 time=84.894 ms
64 bytes from fd18:6132:bfee:1:517c:50d2:6d46:5ea: seq=1 ttl=255 time=74.268 ms
64 bytes from fd18:6132:bfee:1:517c:50d2:6d46:5ea: seq=2 ttl=255 time=83.970 ms
64 bytes from fd18:6132:bfee:1:517c:50d2:6d46:5ea: seq=3 ttl=255 time=73.826 ms
64 bytes from fd18:6132:bfee:1:517c:50d2:6d46:5ea: seq=4 ttl=255 time=84.085 ms
--- fd18:6132:bfee:1:517c:50d2:6d46:5ea ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 73.826/80.208/84.894 ms

Android network

# ip -6 addr show                                                                                                                                                                             
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 state UNKNOWN qlen 1000
    inet6 fe80::447b:b6ff:fef4:4ba/64 scope link 
       valid_lft forever preferred_lft forever
26: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
    inet6 fe80::66f6:bbff:feac:ea5e/64 scope link 
       valid_lft forever preferred_lft forever

# ip -6 addr show                                      
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 state UNKNOWN qlen 1000
    inet6 fe80::447b:b6ff:fef4:4ba/64 scope link 
       valid_lft forever preferred_lft forever
26: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
    inet6 fd11:1111:1122:2222:66f6:bbff:feac:ea5e/64 scope global dynamic mngtmpaddr 
       valid_lft 2229736673sec preferred_lft 2229736673sec
    inet6 fe80::66f6:bbff:feac:ea5e/64 scope link 
       valid_lft forever preferred_lft forever

# ping6 fd18:6132:bfee:1:d40:6155:41e1:3e64
PING fd18:6132:bfee:1:d40:6155:41e1:3e64(fd18:6132:bfee:1:d40:6155:41e1:3e64) 56 data bytes
64 bytes from fd18:6132:bfee:1:d40:6155:41e1:3e64: icmp_seq=1 ttl=64 time=41.1 ms
64 bytes from fd18:6132:bfee:1:d40:6155:41e1:3e64: icmp_seq=2 ttl=64 time=17.8 ms
64 bytes from fd18:6132:bfee:1:d40:6155:41e1:3e64: icmp_seq=3 ttl=64 time=22.0 ms
64 bytes from fd18:6132:bfee:1:d40:6155:41e1:3e64: icmp_seq=4 ttl=64 time=90.9 ms
--- fd18:6132:bfee:1:d40:6155:41e1:3e64 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 17.856/42.996/90.904/29.021 ms

# ping6 fd18:6132:bfee:1:517c:50d2:6d46:5ea
PING fd18:6132:bfee:1:517c:50d2:6d46:5ea(fd18:6132:bfee:1:517c:50d2:6d46:5ea) 56 data bytes
--- fd18:6132:bfee:1:517c:50d2:6d46:5ea ping statistics ---
27 packets transmitted, 0 received, 100% packet loss, time 27037ms

# ip -6 route show
（IP route is empty）

In the log, you can see that the ESP32H2 is assigned the address fd18:6132:bfee:1:517c:50d2:6d46:5ea, and the Android device can ping the IPv6 address fd18:6132:bfee:1:d40:6155:41e1:3e64 of the virtual network interface wpan0 created by otbr-agent. However, it cannot access the IPv6 address of the ESP32H2.

2024-06-07 09:54:07.662 1462-3336/com.google.chip.chiptool I/NsdServiceFinderAndResolver: Resolved service '7E17563DF640C0B7-0000000000000007' to /fd18:6132:bfee:1:517c:50d2:6d46:5ea, type : ._matter._tcp 2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS: ----- entry [0] : T 1 2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS: ----- entry [1] : SAI 800 2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS: ----- entry [2] : SAT 4000 2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS: ----- entry [3] : SII 800 2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS: Node ID resolved for 7E17563DF640C0B7:0000000000000007 2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS: Hostname: fd18:6132:bfee:1 2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS: IP Address #1: fd18:6132:bfee:1:517c:50d2:6d46:5ea 2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS: Port: 5540 2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS: Mrp Interval idle: 800 ms 2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS: Mrp Interval active: 800 ms 2024-06-07 09:54:07.664 1462-3336/com.google.chip.chiptool D/DIS: TCP Supported: 1 2024-06-07 09:54:07.665 1462-3336/com.google.chip.chiptool D/DIS: Lookup clearing interface for non LL address 2024-06-07 09:54:07.665 1462-3336/com.google.chip.chiptool D/DIS: UDP:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]:5540: new best score: 3 2024-06-07 09:54:07.665 1462-3336/com.google.chip.chiptool D/DIS: Checking node lookup status after 22 ms 2024-06-07 09:54:07.665 1462-3336/com.google.chip.chiptool D/DIS: Keeping DNSSD lookup active 2024-06-07 09:54:07.843 1462-3359/com.google.chip.chiptool D/DIS: Checking node lookup status after 200 ms 2024-06-07 09:54:07.843 1462-3359/com.google.chip.chiptool D/DIS: OperationalSessionSetup[1:0000000000000007]: Updating device address to UDP:[fd18:6132:bfee:1:517c:50d2:6d46:5ea]:5540 while in state 2

I have successfully configured the network for ESP32H2, but I used an inappropriate method to verify it. The details are as follows:

Enabled routing forwarding on the Linux device running otbr-agent with the command: sysctl -w net.ipv6.conf.all.forwarding=1.
On the rooted Android device, I configured a route to forward packets destined for Thread devices through the Linux device: ip -6 route add fd18:6132:bfee:1::/64 via fe80::e11:5ff:fef0:a000 dev wlan0.

Although this method successfully allows ESP32H2 to join the network and be controlled, it is probably not the correct way. If there are relevant solutions, please provide guidance. Thank you very much.

@caipiblack

Enabled routing forwarding on the Linux device running otbr-agent with the command: sysctl -w net.ipv6.conf.all.forwarding=1.

If you had to manually configure forwarding and routing on the Thread Border Router, you probably did not configure it properly. For example, the OTBR setup scripts enable IPv6 forwarding.

https://github.com/openthread/ot-br-posix/blob/e5890ccd5054fc81e10c3bb55d28025e1a0ef243/script/_ipforward#L38

On the rooted Android device, I configured a route to forward packets destined for Thread devices through the Linux device: ip -6 route add fd18:6132:bfee:1::/64 via fe80::e11:5ff:fef0:a000 dev wlan0.

Android O and later supports configuring routes using Route Information Options contained in Route Advertisements. You can validate whether such Route Advertisements are being sent using Wireshark.

This issue is opened from long time and many different problems has been discussed here,

Now we don't reproduce the original problem. So maybe itwas related to the setup or some mysteries.

At this point I'm going to close this issue.

Also I made a plantuml diagram that can help to identify problems at FindOperational, I make it very fast, If someone wants, do not hesitate to update it:

@startuml
start

if (Commissioning fails at FindOperational step?) then (yes)
  if (The device has been discovered over mDNS?) then (yes)
      if (You see 'network unreachable' errors?) then (yes)
          :Basically it means that the IPv6 of the device cannot be accessed from the commissioner due to missing route!

          For Thread only:
          The device (computer/phone) that runs the commissioner does not receive the Router Advertisement from the border router.
          There are multiples reasons of this:
          - Configuration issues on the border router ?
          - multicast mDNS filtering ?
          - (maybe) Power saving issues on phones (blocking multicast or reducing the rate due to energy saving strategy)
          - You have no chance, the RA packets has been lost!

          What you can do ?
          - Check the routing table of the device that runs the commissioner.
          - On the device that runs the commissioner, restart your network (WiFi or Ethernet),
            doing it will automatically search for routers and you have a new chance to receive the RA.
          - Use Wiresharks to see if you see the RA.

          The RA are sent:
          - Periodically, depending on their expiration time.
          - When a device search for routers.
          - When the border router starts;
      else (no)
          if (It tries to communicate but there are retries and timeout?) then (yes)
              :It appears in many cases:
              - The device is not reachable (due to a reboot/power off for example?)
              - There is some filtering on the network ?
              - The stack is not trying to communicate with the GOOD IPv6, for exemple:
                - Stale records:
                  - When you commission multiples devices using the same node-id
                  - Discriminator collision

                  __Depending on the mDNS implementation it seems that the mDNS records are not always processed__
                  __in the same order. For example the minimal mDNS seems to present only the "older" record, so__
                  __in case of duplicates, this is always the bad one.__

              - The border router is dropping the packets, for exemple:
                - After re-creating many networks,  the commissioner receive a lot of RA and automatically 
                  add one IPv6 on the interface for each received RA. The problem is, when a packet is transmit
                  it doesn't necessary use the good IPv6 as source (I don't know how but..))

              In such cases, you need to identify if the IPv6 correspond to the device or not.
              You can do an 'avahi-browse -r _matter._tcp' or 'avahi-browse -r _matterc._udp' depending which kind of discovery is failing
              If you are sure that the IPv6 is the IPV6 of the device, then you need to find why there are timeouts (network filtering? device frozen?);
          else (no)
              :I don't know;
          endif
      endif
  else (no)
      :The device is not accessible by the commissioner or the commissioner does not receive the mDNS packet:
      - They are not on the same network (like if you have multiple WiFi networks in your house, repeaters..)
      - There are some filtering on the network (multicast IPv6)
      - (Thread only) The device is 'connected' to a Thread partition with no border routers:
        - The node create his own partition (routers only) because it is too far from other devices
        - The node connects to an existing partition without border router 
          (for example if the border router has been moved far away.. Or was simply never here)
        - Border router not correctly configured;
  endif
else (no)
  :Not covered by this diagram;
endif

stop
@enduml

commissioning_failure

@caipiblack

Enabled routing forwarding on the Linux device running otbr-agent with the command: sysctl -w net.ipv6.conf.all.forwarding=1.

If you had to manually configure forwarding and routing on the Thread Border Router, you probably did not configure it properly. For example, the OTBR setup scripts enable IPv6 forwarding.

https://github.com/openthread/ot-br-posix/blob/e5890ccd5054fc81e10c3bb55d28025e1a0ef243/script/_ipforward#L38

On the rooted Android device, I configured a route to forward packets destined for Thread devices through the Linux device: ip -6 route add fd18:6132:bfee:1::/64 via fe80::e11:5ff:fef0:a000 dev wlan0.

Android O and later supports configuring routes using Route Information Options contained in Route Advertisements. You can validate whether such Route Advertisements are being sent using Wireshark.

@jwhui Yes, I am running otbr-agent on a minimal Linux device by cross-compiling it. Therefore, I start the service directly by executing otbr-agent without running the associated setup scripts. As a result, I manually added sysctl -w net.ipv6.conf.all.forwarding=1.

Additionally, I used Wireshark to capture packets and confirmed that an RA packet is indeed broadcasted in the network after starting the Thread network with thread start, containing both RIO and PIO.

ICMPv6 Option (Prefix information : fd11:1111:1122:2222::/64)
ICMPv6 Option (Route Information : Medium fdf9:1380:2998:1::/64)

Through the PIO, the Android device configured an IPv6 address with the prefix fd11:1111:1122:2222 on its network interface. The RIO information seems to be used for configuring some routing policies. Additionally, the manual routing configuration I mentioned earlier on the Android device is redundant; the routing policies provided by the RIO information already include the necessary routes.

fdf9:1380:2998:1::/64 via fe80::e11:5ff:fef0:a000 dev wlan0 table wlan0 proto ra metric 1024 expires 1572sec pref medium

Currently, there is an issue where the success rate of Thread devices joining the network is quite low. Even though I have enabled net.ipv6.conf.all.forwarding, the packet capture on the Linux device shows that the ESP32H2 device cannot send the CASE Sigma1 ACK and Sigma2 messages back to the Android device, indicating that the address is unreachable. However, after multiple attempts, it sometimes succeeds. I am not sure why the address generated by the Android device through the RA information cannot be accessed by the Border Router.

As shown below, fd11:1111:1122:2222:dcd8:42f5:6e30:2e15 is the IPv6 address generated by the Android device based on the RA information, and fdf9:1380:2998:1:f62:b6b1:43aa:9b1a is the IPv6 address allocated to the ESP32H2.

13:31:09.712854 IP6 (flowlabel 0xd4028, hlim 63, next-header UDP (17) payload length: 174) fd11:1111:1122:2222:dcd8:42f5:6e30:2e15.5541 > fdf9:1380:2998:1:f62:b6b1:43aa:9b1a.5540: [udp sum ok] UDP, length 166
13:31:10.010776 IP6 (hlim 255, next-header UDP (17) payload length: 34) fdf9:1380:2998:1:f62:b6b1:43aa:9b1a.5540 > fd11:1111:1122:2222:dcd8:42f5:6e30:2e15.5541: [udp sum ok] UDP, length 26
13:31:10.010927 IP6 (flowlabel 0x6d5a6, hlim 64, next-header ICMPv6 (58) payload length: 82) fdf9:1380:2998:1:5050:cb75:a6e8:aefe > fdf9:1380:2998:1:f62:b6b1:43aa:9b1a: [icmp6 sum ok] ICMP6, destination unreachable, unreachable route fd11:1111:1122:2222:dcd8:42f5:6e30:2e15
13:31:10.300202 IP6 (hlim 255, next-header UDP (17) payload length: 510) fdf9:1380:2998:1:f62:b6b1:43aa:9b1a.5540 > fd11:1111:1122:2222:dcd8:42f5:6e30:2e15.5541: [udp sum ok] UDP, length 502
13:31:10.300351 IP6 (flowlabel 0x6d5a6, hlim 64, next-header ICMPv6 (58) payload length: 558) fdf9:1380:2998:1:5050:cb75:a6e8:aefe > fdf9:1380:2998:1:f62:b6b1:43aa:9b1a: [icmp6 sum ok] ICMP6, destination unreachable, unreachable route fd11:1111:1122:2222:dcd8:42f5:6e30:2e15

The Android network environment and routing policies are as follows:

# ip -6 addr show                                                                                                                                                                             
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 state UNKNOWN qlen 1000
    inet6 fe80::bc33:fdff:fe43:b4aa/64 scope link 
       valid_lft forever preferred_lft forever
52: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
    inet6 fd11:1111:1122:2222:dcd8:42f5:6e30:2e15/64 scope global temporary dynamic 
       valid_lft 2258777313sec preferred_lft 2258777313sec
    inet6 fd11:1111:1122:2222:66f6:bbff:feac:ea5e/64 scope global dynamic mngtmpaddr 
       valid_lft 2258777313sec preferred_lft 2258777313sec
    inet6 fe80::66f6:bbff:feac:ea5e/64 scope link 
       valid_lft forever preferred_lft forever

# ip route show                                                                                                                                                                               
192.168.0.0/23 dev wlan0 proto kernel scope link src 192.168.0.78 

# ip -6 route list table all | grep wlan0
fd11:1111:1122:2222::/64 dev wlan0 table wlan0 proto kernel metric 256 expires 1769sec pref medium
fd11:1111:1122:2222::/64 dev wlan0 table wlan0 proto static metric 1024 pref medium
fdf9:1380:2998:1::/64 via fe80::e11:5ff:fef0:a000 dev wlan0 table wlan0 proto ra metric 1024 expires 1769sec pref medium
fe80::/64 dev wlan0 table wlan0 proto kernel metric 256 pref medium
fe80::/64 dev wlan0 table wlan0 proto static metric 1024 pref medium
ff00::/8 dev wlan0 table local metric 256 pref medium

The Linux network environment and routing policies are as follows:

# ip -6 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qlen 1
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 fe80::e11:5ff:fef0:a000/64 scope link 
       valid_lft forever preferred_lft forever
6: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 fe80::e11:5ff:fef0:a000/64 scope link 
       valid_lft forever preferred_lft forever
10: wpan0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qlen 500
    inet6 fdbf:630a:24a2:97db:0:ff:fe00:fc11/64 scope global deprecated flags 02 
       valid_lft forever preferred_lft 0sec
    inet6 fdf9:1380:2998:1:5050:cb75:a6e8:aefe/64 scope global flags 02 
       valid_lft forever preferred_lft forever
    inet6 fdbf:630a:24a2:97db:0:ff:fe00:fc38/64 scope global deprecated flags 02 
       valid_lft forever preferred_lft 0sec
    inet6 fdbf:630a:24a2:97db:0:ff:fe00:fc10/64 scope global deprecated flags 02 
       valid_lft forever preferred_lft 0sec
    inet6 fdbf:630a:24a2:97db:0:ff:fe00:fc00/64 scope global deprecated flags 02 
       valid_lft forever preferred_lft 0sec
    inet6 fdbf:630a:24a2:97db:0:ff:fe00:bc00/64 scope global deprecated flags 02 
       valid_lft forever preferred_lft 0sec
    inet6 fdbf:630a:24a2:97db:c2b:226a:afcc:7dae/64 scope global deprecated flags 02 
       valid_lft forever preferred_lft 0sec
    inet6 fe80::14a8:13c0:63f7:4c1e/64 scope link flags 02 
       valid_lft forever preferred_lft forever

# ip -6 route list table all
local ::1 dev lo  metric 0 
local fdbf:630a:24a2:97db:: dev lo  metric 0 
local fdbf:630a:24a2:97db:0:ff:fe00:bc00 dev lo  metric 0 
local fdbf:630a:24a2:97db:0:ff:fe00:fc00 dev lo  metric 0 
local fdbf:630a:24a2:97db:0:ff:fe00:fc10 dev lo  metric 0 
local fdbf:630a:24a2:97db:0:ff:fe00:fc11 dev lo  metric 0 
local fdbf:630a:24a2:97db:0:ff:fe00:fc38 dev lo  metric 0 
local fdbf:630a:24a2:97db:c2b:226a:afcc:7dae dev lo  metric 0 
fdbf:630a:24a2:97db::/64 dev wpan0  metric 256 
local fdf9:1380:2998:1:: dev lo  metric 0 
local fdf9:1380:2998:1:5050:cb75:a6e8:aefe dev lo  metric 0 
fdf9:1380:2998:1::/64 dev wpan0  metric 256 
local fe80:: dev lo  metric 0 
local fe80:: dev lo  metric 0 
local fe80:: dev lo  metric 0 
local fe80::e11:5ff:fef0:a000 dev lo  metric 0 
local fe80::e11:5ff:fef0:a000 dev lo  metric 0 
local fe80::14a8:13c0:63f7:4c1e dev lo  metric 0 
fe80::/64 dev eth0  metric 256 
fe80::/64 dev br0  metric 256 
fe80::/64 dev wpan0  metric 256 
ff00::/8 dev eth0  metric 256 
ff00::/8 dev br0  metric 256 
ff00::/8 dev wpan0  metric 256 
unreachable default dev lo  metric -1  error -101

project-chip / connectedhomeip