求一份短地址冲突的抓包

目前发现经常会有短地址冲突的情况，奈何很难抓到包，想了解下短地址冲突的具体成因，及后续流程，以便解决

Viki Shi：

呃。。。我这边没有，等等看其他网友有没有吧

Tenang：

回复 Viki Shi:

Viki，你好，请教下冲突的形成除了在新设备入网还会出现在哪些情况

Viki Shi：

回复 Tenang:

建议你提供下抓包数据展示冲突的现象，zigbee有算法防止短地址冲突：
Stochastic Addressing
Zigbee PRO uses a stochastic (random) addressing scheme for assigning the network addresses. This addressing scheme randomly assigns short addresses to new devices, and then uses the rest of the devices in the network to ensure there are no duplicate addresses. When a device joins, it receives its randomly generated address from its parent. The new network node then generates a “Device Announce” frame (which contains its new short address and its extended address) to the rest of the network. If there is another device with the same short address, a router node in the network will send out a broadcast “Network Status – Address Conflict” to the entire network and all devices with the conflicting short address will change its short address. When the conflicted devices change their address, they issue their own “Device Announce” to check their new address for conflicts within the network.

End devices do not participate in the “Address Conflict”. Their parents do that for them. If an “Address Conflict” occurs for an end device, its parent will issue the end device a “Rejoin Response” message to change the end device’s short address and the end device issues a “Device Announce” to check their new address for conflicts within the network.

When a “Device Announce” is received, the association and binding tables are updated with the new short address, but routing table information is not updated (new routes must be established). If a parent determines that the “Device Announce” pertains to one of its end device children, but it didn’t come directly from the child, the parent will assume that the child moved to another parent.

Tenang：

回复 Viki Shi:

谢谢viki，我就是来求抓包的 (- . -) I||

Tenang：

哪位能分享一份抓包给我

gaoyang9992006：

难了，我搜了一下咱们论坛貌似还没人提问过短地址冲突这种事，毕竟协议里有解决的方法。

Tenang：

回复 gaoyang9992006:

冲突时的所谓解决方法都因为是广播fffd，这种类型广播会有缺陷，所以我想找ti这边的冲突，想验证下复杂环境下能不能合理接收到对应的device announce。我抓过几个地址冲突包是有缺陷的。并不能完整恢复。而且我更想了解ti最终底层冲突的机制。哪些情况会发起短地址冲突。除了入网，我见到很多非入网期间出现的冲突（silabs的）。TI的因为是采用了协调器，对应修改措施也已经设计上去了，只是也会有无法收到冲突声明等数据包而导致无法更新（抓包）。而且由于不确定成因，这个不好确认是否接受