Routes have associated flags which influence operation of the protocols
when sending to destinations matched by the routes. These flags may be set
(or sometimes cleared) by indicating the following corresponding modifiers:
-xresolve RTF_XRESOLVE - emit mesg on use (for external lookup)
-iface ~RTF_GATEWAY - destination is directly reachable
-static RTF_STATIC - manually added route
-nostatic ~RTF_STATIC - pretend route added by kernel or daemon
-reject RTF_REJECT - emit an ICMP unreachable when matched
-blackhole RTF_BLACKHOLE - silently discard pkts (during updates)
-proto1 RTF_PROTO1 - set protocol specific routing flag #1
-proto2 RTF_PROTO2 - set protocol specific routing flag #2Quote from: bamf on Today at 12:35:33 AMIs it possible to reject the blackholed traffic instead of dropping it?
Quote from: Maurice on February 03, 2026, 05:21:48 PMThere's another and - in my opinion - better approach for preventing traffic with private destination addresses from being routed to the ISP:
Create null routes for all private address space. This will blackhole all private destination networks for which no higher priority routes exist. No firewall rules needed.
Quote from: Patrick M. Hausen on September 17, 2026, 08:26:07 PMSo zum Beispiel 😉OK, mein Ehrgeiz ist geweckt, ich habe die KI gefragt.