Skip to content

Implement distance functionality from fcm #190

Description

@Honigeintopf

The FCM is able to define a distance to the firewalls it creates.
The firewall controller isn't able to do that yet, which this issue aims to improve.

Activity

  1. self-assigned this
    on Nov 5, 2024
  2. Honigeintopf commented on Nov 5, 2024

    @Honigeintopf
    Author

    Right now, firewalls are chosen randomly to send network requests. This random selection sometimes causes one firewall to send a request, but a different firewall to receive the response. This mismatch causes dropped packets and breaks network communication.

    What Needs to Be Done

    1. Get the Distance: The firewall controller already retrieves a distance setting from the Firewall CRDs (custom resources). This distance setting is already in place and does not need to be changed.
    2. Update Routing Paths: Inside the metal-networker code, there is a function to update routing paths in the FRR (Free Range Routing) configuration. This function needs to use the distance setting from the firewall controller to adjust the routing paths so that requests and responses go through the same firewall.

    Solution Summary

    1. Use the distance value to extend routing paths in the FRR configuration.
    2. This will make sure that the same firewall handles both the request and response, preventing packet drops and improving network stability.
  3. Honigeintopf commented on Nov 6, 2024

    @Honigeintopf
    Author

    AS path prepend

    Image

  4. linked a pull request that will close this issueImplement distance for firewall #191on Nov 6, 2024
  5. moved this from Upcoming to In Progress in Roadmapon Jan 19, 2026
  6. moved this to Upcoming in Developmenton May 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions