Skip to content

Dashboard falsely reporting High Availability when a routing peer is configured twice #3626

Open
@md-dfir

Description

@md-dfir

Describe the problem

Adding the same routing peer twice results in "high availability" being marked as green in UI.

Image

To Reproduce

Steps to reproduce the behavior:

  1. Go to 'networks'
  2. Click on 'add resource'
  3. add a resource and define a routing peer
  4. Repeat steps 2 & 3
  5. Click on 'networks'
  6. see mouse over popup on routing peers

Expected behavior

Using the same routing peer twice should not result in declaring high availability.

Are you using NetBird Cloud?

Yes

NetBird version

netbird version

Have you tried these troubleshooting steps?

  • [X ] Checked for newer NetBird versions
  • [X ] Searched for similar issues on GitHub (including closed ones)
  • Restarted the NetBird client
  • Disabled other VPN software
  • Checked firewall settings

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions