Hi,
On Wed, 11 Dec 2024, Hemna wrote:
> Hello, I am the maintainer of aprsd
https://pypi.org/project/aprsd/ along with km6lyw.
> Recently I discovered that my packets from a few of my callsign-ssids aren't showing up at all on
aprs.fi, not even the raw packets.
On 2nd of December 2024 there was a little DOS attack on the APRS-IS
network. Most of South America was covered with randomly placed houses
with random callsigns, a few hundred thousand of them if I remember right.
https://www.dropbox.com/scl/fi/qoegd9rfw1fbrlfmtlhov/aprs-dos-attack-2024-12-02-pattern.png?rlkey=rg9v9i3zd0udwaanjbjdo46wm&dl=0
All the packets had a destination callsign of APZ100 (or other numberic)
so I blocked those as an immediate temporary measure. I did develop a
better method to reduce the effects, but I forgot the setting there a bit
longer than necessary. The APZ prefixes are for experimental/development
use so I didn't worry too much about them.
If you have a permanent need for an allocated destination callsign, please
request allocation here:
https://github.com/aprsorg/aprs-deviceid
Also, the 'aprsd' name refers to an older Linux APRS daemon, written in C,
which used to be very popular. It might be a good idea to pick another
name for a new library or application to reduce confusion. On the APRS-IS
servers, it will be difficult to say if the "aprsd" client is one or the
other.
- Hessu