Solution to some False Positive Attacks - Static Routing

Netgear routers are known to display false positives in their logs for some attack types. I get a Fraggle Attack on port 67 from a private IP 10 times per second, but only on Netgear routers. I use TraceRT/TraceRouting to find out that the "attacking" private IP is actually a routing IP from my ISP. Some ISP's use private IP addresses for the first 2-3 hops. My ISP does that.

The way I make Fraggle Attack messages disappear is by using Netgear's Static Routing feature, inputting the problematic private IP, and using Metric value of 2 for it. That solves the problem.

Afterwards I run another TraceRT/TraceRoute to verify that Static Routing works and that routing does not go through the problematic IP address.