This setting controls whether the device itself will accept and process IP directed broadcast datagrams addressed to its own connected subnet's broadcast address, again referencing RFC2644's guidance on directed broadcast handling. An administrator sets this to notReceive on interfaces where accepting directed broadcasts poses a security risk (again, historically tied to smurf-attack amplification), and might leave receive enabled only where a specific legacy application genuinely depends on it. For example, setting this to notReceive(2) means the router will ignore inbound packets addressed to its local subnet's broadcast address rather than processing them as if addressed to itself.