1.3 Development

in /system_routes_edit.php a checkbox option for blackhole routes would be a useful option .

This will give the ability to blackhole some problem  hosts or networks in a faster and more CPU efficient  manor since the rule will be executed in the IP stack instead of firewall.

for example setting the route:

Interface             WAN         (will be ignored)
Destination network    216.240.44.0/23
Gateway              127.0.0.1      (will be ignored)
Blackhole                YES

sets the route :

       route add -net  216.240.44.0/23  127.0.0.1 -blackhole


Another UI option is to have "BlackHole" as an Interface option and all Destination networks applied to it get blackhole'd

That's no more efficient (and possibly less) than blocking it with firewall rules, you aren't bypassing processing the filter by blackhole routing things, it'll run through the filter regardless of the routing table and before it hits the routing table. I'd just block it.

It has been my experience that black hole routing was "cheaper"  (  but then most of my experience is with the 4.X and 5.X Kernels )