Seems fine to me,
Although, at present levels of activity, reducing the number of
transmissions is only saving the nanoseconds worth of electricity expended
in re-digipeating. :-)
I'm sure that it will save an ulcer or two for the good remote sysops of
various BBSs, if anyone happens to leave a BPQDIGI 'on' somewhere where it
should not be 'on' though.
<Grin>
De Dave (G0DJA)
toggle quoted message
Show quoted text
From: Roger Barker <roger@...>
This version has a couple of improvements:-
1. It won't digipeat frames sent by MYCALL. Example - I have WIDE in my
alias list, MYCALL is set to G4IDE. I send a beacon -
G4IDE>CQ,RELAY,WIDE
I then hear my own beacon being digipeated by a RELAY -
G4IDE>CQ,RELAY*,WIDE
Although I'm digipeating as WIDE, I don't digipeat it because I sent it.
2. Suppression of duplicate digipeats is now supported. If a frame that
has already been digipeated is heard again within a configurable time
period, then it won't be digipeated again. Example - WIDE is in the
alias list. I hear a beacon -
G8MZX>CQ,RELAY*,WIDE
So I digipeat it. I then immediately hear the same beacon via a
different RELAY, but I don't digipeat it again.
Hope that all makes sense!
