The top one is a probe for your Windows RPC daemon, that should be blocked, so that’s correct.
The next is a Multicast request for 22.214.171.124 All host group request you can safely block incoming IGMP traffic global.
For the 255.255.255.255 broadcasts you could make a block rule like Block, In, UDP, src any dst single ip 255.255.255.255 src port any dst port any.
The packet from 60.222.x.y is known as messenger spam, if you would have this port open you will continue to receive windows popup alerts, mostly with text like “you pc is slow, get our registry cleaner at… websitexyz”.
So that’s a correct block on unwanted traffic.
There are still a few broadcasts left to the subnet your on, you could put them all in blockrules like
Block, In, UDP, src any dst 192.168.137.255, src port any, dst port any.
Block, In, UDP, src any dst 192.168.138.255, src port any, dst port any.
Block, In, UDP, src any dst 192.168.177.255, src port any, dst port any.
Only leaves an ICMP Ping request ICMP type 8 code 0 to the multicast “all hosts” 126.96.36.199, you should make a specific rule to drop this
Block, In, ICMP, src any, dst 188.8.131.52, IMCP Details Any.
That should leave most of the normal broadcast noise out of your firewall logging.
Grue, i think he’s a some sort of cable/local lan switch, we have those over here also, but our providers don’t use private ip space on them.