crazyhorse.network - New Entry in DMR_Hosts.txt

[W4JEW]

Hello,

I just noticed a new entry in the DMR_Hosts.txt file for a network called crazyhorse.network. Does anyone know anything about this?

Code: Select all

CrazyHorse_Network    0000    crazyhorse.network     password     62031

[W4JEW]

FYI - the FQDN resolves to 138.68.0.151

[MW0MWZ]

I was requested to add it by Mike Wagner (W9ZEP), I can honestly say I have no idea what is going on with the recent explosion of groups attempting to join the DMR Master space, I don't see the benefit to it.

With each DMR Master there is one or multiple talk groups they do or don't link to who knows where, this fractures our community rather than helping hams come together to talk about stuff.

This is why I firmly believe in joining networks together, rather than standing up new ones, I like the fact that BrandMeister and DMR+ offer connected solutions, I like it even more when those networks of masters (as in more than one) are connected, and more still when one technology is bridged to others (like XLX is doing with D-Star, DMR and now YSF). The end goal should always be bridging rather than isolation... thats my $0.02

[W4JEW]

I couldn't agree more with you!!!

The number of DMR networks and talkgroups within the networks has grown completely out of control and is absolutely ABSURD!

Everyone in their brother wants their own talkgroup - and why? Because of the exclusivity? Because it's cool? It does nothing but add to the fragmentation of DMR and the frustration from hams that are new to DMR trying to find talkgroups with activity.

I look at random samplings of talkgroups on the Call Statistics page on Brandmeister and see little to no activity on the vast majority of them. Surely not enough activity to warrant having a talkgroup. And what many either seem to forget or don't even realize is the case, at least with Brandmeister, you can use your own DMR ID number as a talkgroup.

In my opinion, I'd prefer to see you push back on anyone that requests the addition of any additional servers/networks to the master list. Unless they can substantiate/justify the existence, then forget about it.

While it requires a little bit of effort, it's very much possible to customize the DMR_Hosts.txt file to add your own server(s). I've done this with my own HBlink3 server that I use for purposes of aggregating access to multiple networks into a single bridge - effectively as an open-source c-Bridge. I have my hotspots and several of my friend's hotspots pointed to it and it works very well - most of the time. But I digress...

If the process to add additional servers were documented and made blatantly obvious, then I think that would go a long way towards teaching people that it's possible to make additions to the list that wouldn't be overwritten by official updates to Pi-Star.

In fact...a feature request for you! Add a section to the web interface whereby people can do this without having to be savvy at editing the text files and/or be concerned that they made errors in modifying them to the point of making their hotspot unusable.

As I always tell people, I would much rather see 100 talkgroups with lots of activity rather than 1000s with virtually no activity on them.

I tried pointing my hotspot at the server - even running an nmap scan against it to see if 62031/udp is listening. Either the network is down or there's a firewall policy (of sorts) restricting access to it. If there truly is a firewall protecting it, then what's the point in having it in Pi-Star to begin with?

Whatever this crazyhorse.network is, I say let it be the last one to be added to the master list on Pi-Star.

...off soapbox

Best Regards/73,

JeffH - W4JEW
Atlanta, GA