Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

net/frr: Improve docs #616

Open
2 tasks done
Monviech opened this issue Oct 21, 2024 · 1 comment
Open
2 tasks done

net/frr: Improve docs #616

Monviech opened this issue Oct 21, 2024 · 1 comment
Assignees
Labels
feature Adding new functionality

Comments

@Monviech
Copy link
Member

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Is your feature request related to a problem? Please describe.

net/frr could use some more docs, as discussed. Mostly focused on simple BGP, OSPF related routing. Explaining some of the available options.

Not going to dive too deep into advanced options since the crowd who uses these options know what they are doing, and I am not that deep. :)

@Monviech Monviech added the feature Adding new functionality label Oct 21, 2024
@Monviech Monviech self-assigned this Oct 21, 2024
@Monviech
Copy link
Member Author

Monviech commented Oct 28, 2024

Current document:

https://docs.opnsense.org/manual/dynamic_routing.html

  • Explain some of the menus and options better. Focus on OSPF, BGP and BFD. Since iBGP can do IPv4 and IPv6 I do not want to get into OSPFv3 too much.

  • Remove pictures and replace with text and tables to improve future maintainability.

  • Some general how tos:

    • OSPF with IPsec VTI to create failover VPN routing between two OPNsense firewalls with multiple WAN connections
    • BGP to dynamically change default route to the internet based on path costs
      • Considerations with NAT
      • Using Route Maps and Prefix Lists to prevent unwanted routes being received or advertised (especially important when peering with public AS)
    • BFD to increase the responsiveness of BGP neighbors
  • Potential Drawbacks:

    • Issues with states when using CARP and BGP at the same time
    • Asymmetric routing
    • When peering with multiple eBGP AS from OPNsense Firewalls in HA, how it could be necessary to use Unicast CARP on the WAN interfaces

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Adding new functionality
Development

No branches or pull requests

1 participant