Is your feature request related to a problem? Please describe.
Currently, the neighbor list includes repeaters that are only heard unidirectionally (one-way reception). This creates misleading routing information: a node can hear the repeater, but the repeater cannot receive packets back from the node.
Describe the solution you'd like
Filter the active neighbor list so it only displays repeaters with a confirmed bidirectional connection. Repeaters with only one-way reception should not be treated as viable neighbors for routing.
Describe alternatives you've considered
Alternatively, visually distinguish unidirectional links (e.g., mark them as "Heard only" or display them in a separate sub-list/grayed out) so users immediately see that two-way communication is not possible.
Additional context
Listing pure one-way repeaters in the main neighbor list provides little practical value for mesh routing and causes unnecessary connection attempts.
Is your feature request related to a problem? Please describe.
Currently, the neighbor list includes repeaters that are only heard unidirectionally (one-way reception). This creates misleading routing information: a node can hear the repeater, but the repeater cannot receive packets back from the node.
Describe the solution you'd like
Filter the active neighbor list so it only displays repeaters with a confirmed bidirectional connection. Repeaters with only one-way reception should not be treated as viable neighbors for routing.
Describe alternatives you've considered
Alternatively, visually distinguish unidirectional links (e.g., mark them as "Heard only" or display them in a separate sub-list/grayed out) so users immediately see that two-way communication is not possible.
Additional context
Listing pure one-way repeaters in the main neighbor list provides little practical value for mesh routing and causes unnecessary connection attempts.