Feature Request: Exception for some networks

[Null-Kelvin]

I have two simultaneously connected tunnels on each served computer. Nebula (for performance) and OpenVPN (in case of failure). Recently I noticed that if Nebula cannot use the public address for some reason, it starts working through OpenVPN, and in my case this is an undesirable behavior (in some cases OpenVPN is connected via LTE with limited 128 kb\s speed).
After re-reading the documentation, I haven't found a way to make exceptions for Nebula traffic.
Is it possible to add an “ignore_ranges” directive similar to “preferred_ranges”?

[brad-defined]

Hi and thanks for using Nebula! Have you discovered the lighthouse.remote_allow_list? If you configure this with your OpenVPN cidr, then Nebula will not use IPs in that CIDR for establishing tunnels.
https://nebula.defined.net/docs/config/lighthouse/#lighthouseremote_allow_list

You can also check out the lighthouse.local_allow_list, to prevent Nebula from advertising those IPs to the lighthouse.
https://nebula.defined.net/docs/config/lighthouse/#lighthouselocal_allow_list

[Null-Kelvin]

"lighthouse_allow_list" is exactly what I need! Thank you!