Skip to main content...


Man, I wish DAPNET / would get their shit together. Over the course of the past few months or so, the DAPNET server becomes completely unreachable for extended periods of time.

Now, I’m not the biggest Kool-Aid drinking fan of DAPNET to begin with, but I have a DAPNET account and use the account for testing and validation purposes; since POCSAG (and the DAPNET service) is a part of my W0CHP-PiStar-Dash software.

But I’m about ready to simply give up on DAPNET. Here’s a sample of the DAPNETGateway logs in my development environment:

M: 2021-03-25 11:31:58.222 Opening POCSAG network connection
I: 2021-03-25 11:31:58.227 Opening UDP port on 4800
M: 2021-03-25 11:31:58.227 Opening DAPNET connection
E: 2021-03-25 11:34:09.495 Cannot connect the TCP client socket, err=110
M: 2021-03-25 11:34:09.495 Closing POCSAG network connection
E: 2021-03-25 11:34:09.495 Cannot open the DAPNET network port

The log becomes littered with those errors and it won’t connect – and at the time of this writing, DAPNET has been unreachable for 18 hours or so. I tried a different DAPNET server, and that yields a completely different error/issue:

M: 2021-03-25 11:26:39.142 Login failed: Invalid credentials

For shits and giggles, I looked at my DAPNETGateway and DAPNET API configuration(s) to ensure my credentials were both present and correct, and they are.

My issue with DAPNET, the frequent and prolonged full-scale outages.

I Can’t Support Something That Doesn’t Work

Because of the unreliability of DAPNET services, I am going to place any DAPNET functionality and support in W0CHP-PiStar-Dash lowest on the priority list. It’s simply not possible for me to add any functionality or even validate DAPNET functionality when the hosts don’t reliably work. Maybe that will change someday. 🤷

Ver. # a492a20 - Document last updated: 1/31/2022
[ Permanent Link ]