Summary
The KNX client is making duplicate Connect_Req messages, after receiveing the E_CONNECTION_ID, and does not handle E_CONNECTION_ID errors properly in Tunnel_Ack and ConnState_Resp.
Behavior
Client sends an additional Connect_Req even after successful connection establishment
After receiving the second Connection_Response, client:
Does NOT update to the new channel_id
Continues communication using the old channel_id
Multiple Connection_Req messages are observed within the same second
Evidence (Wireshark Logs)
Multiple Connect_Req packets sent within a short interval
Channel ID mismatch observed between responses and subsequent requests
Download the below zip file for your reference
Filter used:
ip.addr == 192.168.8.167
Attachments
Wireshark Logs.zip
Summary
The KNX client is making duplicate Connect_Req messages, after receiveing the E_CONNECTION_ID, and does not handle E_CONNECTION_ID errors properly in Tunnel_Ack and ConnState_Resp.
Behavior
Client sends an additional Connect_Req even after successful connection establishment
After receiving the second Connection_Response, client:
Does NOT update to the new channel_id
Continues communication using the old channel_id
Multiple Connection_Req messages are observed within the same second
Evidence (Wireshark Logs)
Multiple Connect_Req packets sent within a short interval
Channel ID mismatch observed between responses and subsequent requests
Download the below zip file for your reference
Filter used:
ip.addr == 192.168.8.167
Attachments
Wireshark Logs.zip