Routing policy redesign on Nebula with WANs connectivity check

GiuseppeR
Posts: 317
Master Member





in Nebula Ideas
Hello everyone,
as you know there is a limitation on design regarding policy route on Nebula platform. If you set a rule for routing there is no way to tell that rule to re-route traffic if the specified WAN goes down.
You can check that issue here:
I think it would be great to add this layer of usability, disabling the routing policy if the specified next-hop is down.
3
Comments
-
here the same problem: our customes have 2 oder more wan ports and the healthy check on nebuly DONT WORK :(
0
Categories
- All Categories
- 415 Beta Program
- 2.5K Nebula
- 152 Nebula Ideas
- 102 Nebula Status and Incidents
- 5.8K Security
- 305 USG FLEX H Series
- 283 Security Ideas
- 1.5K Switch
- 77 Switch Ideas
- 1.1K Wireless
- 42 Wireless Ideas
- 6.5K Consumer Product
- 255 Service & License
- 396 News and Release
- 85 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.7K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 87 About Community
- 77 Security Highlight