 | 1 | initial version |
If I disable the Mac's Wi-Fi interface, neither WireShark nor any of the layer-2 communicating programs ever receive any of the locally-generated 1722.1 packets.
If I add other computers to the LAN, the Mac programs receive their layer 2 / 1722.1 packets in all cases (i.e. whether or not Wi-Fi on the Mac is enabled). That is, the packet-routing issue is limited to 1722 traffic that is both sent and received (or not received) within the Mac itself.
Ethernet adapters rarely, if ever, receive their own traffic. OS networking stacks catch attempts to send traffic to yourself and wrap it around internally; the traffic is not sent out on the Ethernet
At least in macOS and, I think, other *BSD OSes - and on Linux - that traffic will be rerouted over the loopback adapter.
So, if, for example, you use the ping command to ping your own IP address, and try to capture on the network interface with that IP address, you will not see that traffic - you will have to capture on the loopback interface (lo0 on *BSDs such as macOS, lo on Linux).
I don't know what mechanism your programs are using to send and receive IEEE 1722.1 packets. It may be that the mechanism in question is doing something odd if you try to send those packets to your own MAC address on en0.
