[op25-dev] whitelist file changes?
John Ackermann N8UR
jra at febo.com
Wed Jan 23 15:07:48 UTC 2019
Ah, that explains it then.
The idea of whitelist ranges is really neat, but I'd still like a way to
put tags or other descriptors in the wl file so you can easily tell what
you're listening to.
I'll work on some ideas -- either setting up a 3rd optional field for
tags, or maybe scanning for "#" and calling anything after that a comment.
On 1/22/19 5:35 PM, Graham Norbury wrote:
> A while back I added the ability for whitelist ranges. The original
> format was "tgid" only but it didn't barf if the tag was there as well.
> The new format is "tgid1"<tab>"tgig2". If you specify two tgids on a
> line, it is considered an inclusive range from tgid1 to tgid2.
> Strip the spurious tags and your file will work ok.
> On Tue, Jan 22, 2019, 3:33 PM John Ackermann N8UR <jra at febo.com
> <mailto:jra at febo.com> wrote:
> Hi --
> After a few months away, I fired up the op25 machine today and updated
> to the latest boatbod version. Great improvements, especially the web
> I'm having a minor issue, though. It seems as though my whitelist file
> is no longer working. The log shows that it's being read, but doesn't
> list the included groups, and I'm hearing lots of traffic from TGs that
> aren't on the list. Has anything changed in whitelist handling?
> (My wl
> file is in two column format: TGID<tab>TAG which worked after patches
> that Graham applied last year.)
> And, by the way, thanks Graham for fixing the statistics.sh script; I
> never quite got around to that after the log file format changed.
More information about the op25-dev