Although I prefer #Linux for many things, I do bump into a problem that makes it feel like MS DOS ca. 1987 sometimes.

Reboot, & my USB (both tty & audio) devices may re-shuffle.

Everything was working. #DireWolf #RigBlaster #WSJTX #WinKeyer #FTdx3000

Without changing any USB cables in any way, reboot, & Direwolf cannot start because the TTY port isn't there anymore.

Now starting documenting a new habit. Unplug all USB but one if I'm going to reboot, then plug in specific order. This is dumb.

My #APRS 2-way iGate digipeater station is "clicking" (i.e. the #RigBlaster is switching to TX) a LOT this morning. Quite a bit more than a typical morning.

I checked the #DireWolf console to make sure there wasn't another mal-configured digipeater out there to blacklist. Nope, it's various callsigns just busily doin' stuff.

Guesses:
a. New radios for Xmas.
b. Mobiles heading home after Xmas.

I need help from #FediHams

I use a pi with #DireWolf and #xastir for an #APRS 2-way i-gate.

We have a bad actor in the area.

ANY time I hear the #RigBlaster clicking multiple times within 15 seconds, I check the Direwolf terminal, & invariably it's this yahoo whose stuff is configured wrong. He's been contacted via email, but no response.

I do know that there are filtering things in Direwolf, but it looks like Xastir nonetheless overrides & re-transmits this dope's packets.
(continued...)

Woke an hour early, gut ache. Got into the office/ham-shack a while before 5am. Heard the #APRS iGate TX-ing very frequently. Sounded "spammy".

Found one stn in particular was frequently sending ":reg" packets, with varying characters after those 4 chars.

Suffice to say I have now learned how to create a block-all-from-this-callsign filter in #direwolf config file. Timmy in Blaine makes #RigBlaster click no more.