Package: netbase Version: 6.4 Severity: normal File: /etc/ethertypes X-Debbugs-Cc: [email protected]
EtherCAT Protocol is Ethernet based, and transports frames as its own ethertype. This is due to real-time contstrains, and custom requirements for checksums, cut-through processing, low latency, and elimination of IP stack and processing of various packets directly in hardware. While Linux machine is not often on a EtherCAT ring network, it can be used as a master, or a slave leaf, or just for monitoring purposes, extra out of the field operations (i.e. testing, firmware upgrade), and with suitable hardware and RT kernel also as a real slave device. I do not see EtherCAT or 0x88A4 at IANA's IEEE 802 Numbers registry, but it is what it is and it is used for a long time in the industry (since around 2003). Lets add /etc/ethertypes 0x88A4, EtherCAT Protocol This can be confirmed on EtherCAT Technology Group (ETG), and Wikipedia too, as well in international standards like IEC/PAS 62407, or IEC 61158, IEC 61784-2, and IEC 61800-7. Regards, Witold -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.0-rc4 (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
