Since the module is so explicit about what send and receive addresses and ports are, the input method should ignore anything that at least is coming from the wrong port. (There might be a case to allow different IP addresses, so I'll set that aside.)
I have a use case where I'm needing to send on the broadcast address (x.x.x.255) because I'm sending to multiple machines and they're dhcp so they may move. The consequence of this is that no other UDP module instances can be used on that subnet without getting an error 20 (classified as critical) and erroring out. If we add filtering, it would prevent this.
If I understand it correctly, any single UDP datagram to a port running this module will cause DCAF to go into a safe state.
Since the module is so explicit about what send and receive addresses and ports are, the input method should ignore anything that at least is coming from the wrong port. (There might be a case to allow different IP addresses, so I'll set that aside.)
I have a use case where I'm needing to send on the broadcast address (x.x.x.255) because I'm sending to multiple machines and they're dhcp so they may move. The consequence of this is that no other UDP module instances can be used on that subnet without getting an error 20 (classified as critical) and erroring out. If we add filtering, it would prevent this.
If I understand it correctly, any single UDP datagram to a port running this module will cause DCAF to go into a safe state.