Logic Machine Forum
KnxNet/IP - bug ? - Printable Version

+- Logic Machine Forum (https://forum.logicmachine.net)
+-- Forum: LogicMachine eco-system (https://forum.logicmachine.net/forumdisplay.php?fid=1)
+--- Forum: Gateway (https://forum.logicmachine.net/forumdisplay.php?fid=10)
+--- Thread: KnxNet/IP - bug ? (/showthread.php?tid=707)

KnxNet/IP - bug ? - oyvindi - 29.03.2017

Hi,

this is a few (low-level) questions about the KnxNet/IP implementation on Logic Machine 5.

I too a look at UDP-packages in Wireshark while connecting to LM5 with ETS5, and found some anomalies.

1) In system settings -> KNX Settings, I specified that I want EIBNet/IP Tunnelling. However, LM5 keeps sending ROUTING_INDICATION packages ?


2) When doing a CONNECTIONSTATE_REQUEST, the CONNECTIONSTATE_RESPONSE  should contain one of the status codes:

E_NO_ERROR = 0x00,
E_CONNECTION_ID = 0x21,
E_DATA_CONNECTION = 0x26,
E_KNX_CONNECTION = 0x27

However, LogicMachine replies with code 0x15, which is an unknown status. Output from WireShark:

Request:
Code:
Frame 729: 58 bytes on wire (464 bits), 58 bytes captured (464 bits) on interface 0
Ethernet II, Src: Giga-Byt_28:b3:64 (fc:aa:14:28:b3:64), Dst: OpenrbCo_26 (00:1b:c5:00:10:26)
Internet Protocol Version 4, Src: 10.20.25.30, Dst: 10.20.25.123
User Datagram Protocol, Src Port: 52989, Dst Port: 3671
KNXnet/IP
    Header
        Header Length: 0x06
        Protocol Version: 0x10
        Service Type Identifier: CONNECTIONSTATE_REQUEST (0x0207)
        Total Length: 16 octets
    Body
        Communication Channel ID: 1
        reserved: 00
        HPAI: Control endpoint
            Structure Length: 8 octets
            Host Protocol Code: IPV4_UDP (0x01)
            IP Address: 10.20.25.30
            IP Port: 52988

HEX:
0000   06 10 02 07 00 10 01 00 08 01 0a 14 19 1e ce fc

Response:


Code:
Frame 730: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: OpenrbCo_26 (00:1b:c5:00:10:26), Dst: Giga-Byt_28:b3:64 (fc:aa:14:28:b3:64)
Internet Protocol Version 4, Src: 10.20.25.123, Dst: 10.20.25.30
User Datagram Protocol, Src Port: 3671, Dst Port: 52988
KNXnet/IP
    Header
        Header Length: 0x06
        Protocol Version: 0x10
        Service Type Identifier: CONNECTIONSTATE_RESPONSE (0x0208)
        Total Length: 8 octets
    Body
        Communication Channel ID: 1
        Status: Unknown (0x15)

HEX:
0000   06 10 02 08 00 08 01 15
3) I tried to perform a line scan in ETS5, but no devices show up. I haven't analyzed the traffic (yet) for this issue.
I am currently implementing a KnxNet/IP client, which is why I stumbled across these issues.

RE: KnxNet/IP - bug ? - admin - 29.03.2017

1. It will always send telegrams to Routing if IP features are enabled

2. Looks like a bug, will fix

3. Are you connected to a KNX/TP gateway via Tunneling?

RE: KnxNet/IP - bug ? - oyvindi - 29.03.2017

Yes, I am connected via Tunnelling.

- Øyvind