A Digital Garden - frequent growth but a bit weedy in the back corner
255.255.255.255, in 224.0.0.0/4 (multicast) or in 127.0.0.0/8 (loopback), none of which a host can have. It’s yes only in InvalidARPIP’s rows, so ListOfValidARPFieldCombinations leaves it out. It changes slowest so that rows 1-1,350, the no rows, kept their numbers when it was added. A subnet’s own broadcast or network address, e.g. a .255, can’t be judged from the packet, which carries no netmask, so arp_packet_categoriser reports those separately under “ARP using the subnet’s own addresses”, using the config’s subnet.A field value set can break more than one rule. It matches each topic whose rule it breaks, and its field value set topic (e.g. ARPFieldValueSet151) lists them all. The first in this order is its primary one, the one it’s counted as, which is what arp_packet_categoriser reports. Each topic’s field value sets, defining fields and filters cover every field value set that fits it, so they overlap.
| Topic | Rule broken |
|---|---|
| InvalidEthernetSourceMAC | Ethernet src is ff:ff:ff:ff:ff:ff or 00:00:00:00:00:00 |
| BlankEthernetDestinationMAC | Ethernet dst is 00:00:00:00:00:00, so no card receives it |
| InvalidARPSenderMAC | Sender MAC is ff:ff:ff:ff:ff:ff or 00:00:00:00:00:00, which would put that address in receivers’ caches |
| InvalidARPIP | Sender IP or Target IP is 255.255.255.255, multicast or loopback, none of which a host can have |
| ZeroIPsARPPacket | Both IPs are 0.0.0.0, so it asks and claims nothing |
| ZeroSenderIPARPReply | A reply from 0.0.0.0 answers nothing |
| ZeroTargetIPARPRequest | A request for 0.0.0.0 asks for nothing |
| UnusualARPOpCode | Opcode is neither 1 nor 2: RARP (3, 4), Inverse ARP (8, 9), or malformed |
All 72 valid rows have Ethernet src and Sender MAC unicast. Half have them matching and half not. The 36 that don’t match have topics of their own, named after the matching row’s topic with SenderMACMismatch on the end.