Skip to content

[Bug]: Repeater frequencies/presets being incorrectly updated #645

Open

Description

@f3sty

Platform

MeshMapper Web

What happened?

We are rolling out a 2.4GHz repeater network, with crossband bridges to the main 915MHz mesh. The 2.4GHz repeaters are all being marked as 915MHz as soon as they flood advert, I assume because multiple observers on 915 report these repeaters' adverts that come via the bridge to the 915 mesh.

This results in our 2.4GHz map having no repeaters on it, they all get marked as 'gone' or 'ghost' within a short time.
They will briefly return to the 2.4 map as they are heard by a meshmapper client connected to a 2.4GHz radio, but then very quickly get mis-identified as 915 repeaters on next advert.

Same-band bridges that join different regional/state presets also cause any repeater that transit the bridge to possibly be marked with incorrect frequency/SF/CR.

How to reproduce

  1. Set up a repeater on an alternate frequency or preset to the main mesh.
  2. Start a meshmapper client session to establish the repeater on the map.
  3. Set up a bridge between the two frequencies/presets.
  4. Send a flood advert that crosses the bridge.

Or check out the Australia/SYD map, frequency preset 2483.

What should happen instead?

A repeater's frequency/preset should only be considered trustworthy where clients hear the repeater directly.
Bridges can be transparent (e.g. openhop-repeater in bridge mode) so even a path with a single hop could still be crossing a bridge.

How bad is it?

High - Major problem

Anything else?

Screenshots showing repeaters heard during a meshmapper session earlier today are already gone

Image Image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions