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

tunnelmanager: babeld rx cost on core-routers too low #517

Open
Noki opened this issue Jul 24, 2023 · 0 comments
Open

tunnelmanager: babeld rx cost on core-routers too low #517

Noki opened this issue Jul 24, 2023 · 0 comments
Labels
bug Something isn't working uplink_gateway

Comments

@Noki
Copy link
Member

Noki commented Jul 24, 2023

With the standard configuration of an uplink tunnel as described in our documentation we get the following RX cost on w38b-core:

image

The RX cost is only 96 which causes traffic to flow via the backup uplink tunnel of w38b-core towards zwingli-core, whenever saarbruecker-gw is used as tunnel server on w38b-core. The whole network currently looks as follows:

image

Expected behaviour would be to have a RX cost metric on the core router / TX cost metric on the gateway that is so high, that the tunnel would only be used if the wireless connection towards saarbruecker-gw breaks.

From my understanding this should be implemented as TX cost on the gateways. TX cost should probably be 1024 so TX cost and RX cost will be identical on the core routers for the wireguard tunnels.

@Noki Noki added bug Something isn't working uplink_gateway labels Jul 24, 2023
@Noki Noki pinned this issue Aug 16, 2023
@noxilixon noxilixon unpinned this issue Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working uplink_gateway
Projects
None yet
Development

No branches or pull requests

1 participant