Will the old name eventually get resolved? I have a dozen nodes to update and some I can’t even get to unless I physically go to the site due to unforeseen firewall issues. I can wait but need to know if it is imparrative to make this change or not? Thanks PS curious, why the domain name change to begin with? Lu Vencl KA4EPS

On Dec 30, 2020, at 4:02 AM, Bryan Fields <Bryan@bryanfields.net> wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

The allstarlink Board of Directors has broken DNS for allstarlink.org once again. The Admin Team has migrated all services off allstarlink.org to 'pttlink.org'. Unfortunately for the users of allstarlink this means they will need to update their configurations.

Users of allstarlink should update their nodes to use pttlink.org in all the configuration files. The commands below when run from the command prompt will update all references to pttlink.org. The reboot command is optional, but we encourage it for good measure.

sudo sed -i 's/allstarlink.org/pttlink.org/g' /usr/local/bin/rc.updatenodelist sudo sed -i 's/allstarlink.org/pttlink.org/g' /usr/local/bin/NodeNameUpdate.sh sudo sed -i 's/allstarlink.org/pttlink.org/g' /usr/local/bin/NodeUpdate.sh sudo sed -i 's/allstarlink.org/pttlink.org/g' /etc/asterisk/rpt.conf sudo sed -i 's/allstarlink.org/pttlink.org/g' /etc/asterisk/iax.conf sudo sed -i 's/allstarlink.org/pttlink.org/g' /etc/asterisk/extensions.conf sudo service asterisk restart #sudo reboot

Registration is still coming back now, please bear with the Admin team. Stats should be back and working. The nodes.allstarlink.org is broken at this point, so if you're using that, change over to nodes.pttlink.org as that is working. The phone portal is down, but we should be getting it back up later today.

SSL and DNSsec is going to be wonky, you will want to clear cookies and such. For the time being RT is not processing email, please just post here on the list and someone will look into it.

We're shocked that there's been no notice of the board again breaking DNS. This will prevent this from happening in the future. - -- Bryan Fields

727-409-1194 - Voice http://bryanfields.net -----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEaESdNosUjpjcN/JhYTmgYVLGkUAFAl/sQeEACgkQYTmgYVLG kUCdKw//Yvp5zFuwu6Vb3ioILhlobKbmXIWJ7e8PLe2RjrVU3hYwBQlGO6IMY1d9 ujIl8sHsPo72Xnp5lYmraxN0lvSPngqvlXIsmDe0fr0iWsjQl363BnUNQ3vlgyJI 77e76AcksA6YoVqJiqRPYK/ZvKarJIG63SjTq6ztciwLiLo1uOKunvj1AHUhy268 9lbn9IPJ/pfdaiP5n9vgbNGXr34eYuxDV9ZP9ZpK2jgJ0Y9LsMDOGs7wJzJMYsym rXHmYwSp8vJZKXzNKmqOHpLVV41bZSsgDuYHhZzqte8in9GXTZ6PXPyiBzR1PUGW xOPM97xmnIOQ2KA+4h31i4MHSOvmvSsfE05kuchd1tISGLl/jYWVVRYKH88ylSM2 GoaXwKUZEmq2HKFIs/9KRFobs47O/dhFFYFp2W6DpmkB8jxvloIfay4+OjKT5UvR ON6KMQgC2hH6oqZeyKTGzYE/KFWwRaCb6dPnzZNdxLJuANrFxN+JUFyxRrzxIB9w EgoskZA9aIT1LoX0JfXqoFHubsRw2wpJ1pxiSIsUGDQDija8AJ2Q+c6+UUYOfHVE hbD6Eyuuh9yE5jmUpASj/daMNgB1rHT9hd2pHoOa1Un5OSyaZRSgfw4Tvuo6sW8S CPmvNQwfzWliEbGDa1b6bVeotVOJ+bESJ/vOrNdptk5RwZMlgsc= =Y8nS -----END PGP SIGNATURE----- _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users Unsubscribe posts to the list will result in public shaming.

On another note...I've changed one of my unused reserved 5-digit node numbers to an NXX extended number...and the system, before yesterday, had created the xxxxxxx0 and xxxxxx1 nodes. I'd like to add on to this...not clear (to me, anyway) how to do so. Any guidance would be appreciated. 73 to all for a better New Year. Remember, the original Mad Max movie was set in 2021...;) -- Bryan Si hoc legere scis, nimis eruditionis habes

A bit on this change: Nobody on the admin side that runs what was the AllStarLink (ASL) infrastructure (now PTTLink) was ever informed this was going to happen.  Yesterday afternoon (12/29/20) at around 5:00 PM (Pacific) our monitoring system started going crazy with alerts telling us systems were down.  Investigation showed that the SOA record for allstarlink.org was changed to what it is now (Cloudflare) and this broke numerous things.  Both the wording and timing of this announcement is very much a jab (or middle finger) pointed directly at me since I'm the main person who has been running things.  I am one who has ensured that the ASL Network (and associated infrastructure) remained operational and was able to handle the increasingly growing number of nodes (well over 5,100).  This was done solely through me investing both my own time and money without the help or participation of the ASL Board.  In addition to this "re-engineering" I have also had my account on the ASL Slack workspace suspended without notice and any and all admin access to the ASL Web portal was removed too (among other things). For quite some time, well before Bryan Fields (W9CR) or Fred Moses (W8FSM) stopped their involvement in ASL directly, the AllStarLink, Inc Board (ASL Board) has done its best to alienate, patronize, ridicule, demean, and basically exclude the admin team from anything substantial regarding the ASL infrastructure for which they had no understanding of nor did they attempt to understand.   Numerous attempts were made by myself and others to try to fix the issues that were very apparent, and yet they were met with disdain and ignored.  This included on several occasions attempts at impassioned pleas by myself and others directly to the ASL Board members regarding the issues that we saw and asking for reparations to make things better.   Of which included being open regarding any decisions being made which directly affected the admin team.  Additionally, any and all attempts to ask what is happening on/at the board level regarding ASL were ignored or told that it didn't involve or concern us.  Instead, they continued on the same course of action that served to alienate more and more people from participating in ASL on the admin side with the results of me being the sole admin person left. This "re-engineering" and the resulting chaos and outages are serve as a testament to the ASL Board again attempting to change things without understanding the system itself and without telling anyone.

This is part of an ongoing two-year project to provide sufficient resources for projected node growth and additional stability. In addition, this will create a stable framework for new types of clients to participate in the future.

Again, nobody told me (or anyone else associated with the admin team) about this "two year project".  Each and every time the ASL Board has attempted a change (and broken something), the current node registration system was brought up.  For example, the Round Robin DNS (RRDNS) has been a sticking point for a certain unnamed ASL Board member, and during discussions this unnamed individual had the audacity to state that DSNMGR messages regarding changes to the IP address of the server at register.allstarlink.org was "trashing his node".   One of the long since alienated admin team members had to explain that you could adjust logging in Asterisk through a config file.  This is one of many examples that demonstrated the lack of knowledge of AllStarLink, Asterisk, and app_rpt by a  member of the ASL Board.  Yet we are to believe that a "two year project" has been in the works by this same group that is supposed be  a "re-engineered" system to promote growth and stability?

You should also be aware that some specific volunteers (past and current) have opposed this sort of design change and we suspect that you may be reading negative comments from them on various platforms. The board’s staffing goals are to promote technical innovation from as many hams as want to get involved and bring new features and clients to Allstar.

Don't be fooled by this attempt at taking the high ground.  The opposition they are implying results from attempts at changes from the ASL Board without understanding the underlying technical issues behind how/why things run and causing outages that they wouldn't (or couldn't) fix.  Each and every time an ASL Board member brought up "re-engineering" the registration system, the reply that I empathically gave was that yes, the system can be improved upon but there needs to be a plan.  I personally have stated that I am open to improvements to this system that were the result of planning, testing and made sense.  The ASL Board thought that moving the system to AWS or Google would "solve" everything yet when pressed for details on how this would be done, we were met with crickets or arguments that it was just better and that was that.  And when asked about a budget for such a move we were again met with silence.  The "resistance" that is alluded to was with regards to actually sitting down and creating a plan on how to move forward with "re-engineering" this system, and not just what amounted to throwing scat at the wall and seeing what stuck (resulting in either myself or others on the admin team having to figure out what broke and fix it, since most of these changes were done without telling us).  At no point during the any of occasions in which I said this has any ASL Board member taken the initiative to actually have this discussion with me (or anyone on the admin team) and come up with a viable plan to both "re-engineer" and do a proper cut over that isn't as disruptive as the one we are experiencing now. There is a history of the ASL Board doing things that have broken registration and parts of the infrastructure in the past, and this is no different. PTTLink was formed due to the ASL Board's actions which forked the AllStarLink network by changing the DNS records without prior notice. The PTTLink Network can be thought of as an "overlay" to what had been in operation as the AllStarLink Network. This change was done simply by changing the domain name in use on the servers to pttlink.org. Your existing credentials will continue to work unless you change them.  However, PTTLink, as a result of the ASL Board's egregious and careless action, is now a separate entity from the AllStarLink Network. I call upon the ASL Board to restore DNS back to the way it was before they forked it, moving everything back to the perfectly working infrastructure that uses what are now the pttlink.org servers.  Additionally, I call upon them to restore all access that was revoked from me (both recently, and that which was revoked before without notice). I am very disappointed in the egregious actions that the ASL Board has taken (or more importantly have directed others to take) with regards to the AllStarLink infrastructure and their statement.  Such actions are clearly indicative of a group that is unfit to be the stewards to the legacy of the late Jim Dixon or properly be of service to the community without trying to benefit from it.  Additionally, I feel that these actions, as made clear in their statement, were directed at me in an attempt to "punish" me for my insistence and diligence at keeping the ASL (now PTTLInk) infrastructure running when others made disruptive changes to it.  If so, then this is very troubling indeed. As I have very plainly stated before to the ASL Board members and others, as long as I have the resources to support ASL they will remain available.  In that I will pledge to my fellow hams that PTTLink will remain operational and available for use as long as I am able to continue to provide the time and other resources to keeping it operational.  Fortunately, I am no longer alone in this endeavor and others have volunteered to help. The new links for PTTLInk sites are as follows: PTTLink Portal - https://www.pttlink.org PTTLink Stats Server - http://stats.pttlink.org PTTLink Registration Server - register.pttlink.org PTTLink Node List Server - nodes(x).pttlink.org PTTLInk is on Reddit - https://www.reddit.com/r/pttlink Additionally, you can use the DNS node lookup developed by W9CR (which was working with allstarlink.org before the ASL Board forked the network): IP Address of registered node: dig <node#>.nodes.pttlink.org TXT record showing DNS registration info: dig TXT <node#>.nodes.pttlink.org Additionally, you can utilize the app_rpt-users mailing list for support by subscribing at 73, Stacy KG7QIN

Steve, It appears to have been moved to https://github.com/pttlink/Asterisk On Wed, Dec 30, 2020 at 7:43 PM Steve Zingman <szingman@gmail.com> wrote:

Stacy, Do you know why the AllStarLink <https://github.com/AllStarLink> github repositories are gone? Was this part of the actions of the board?

Steve N4IRS

On 12/30/20 8:06 PM, Stacy wrote:

...

A bit on this change:

Nobody on the admin side that runs what was the AllStarLink (ASL) infrastructure (now PTTLink) was ever informed this was going to happen. Yesterday afternoon (12/29/20) at around 5:00 PM (Pacific) our monitoring system started going crazy with alerts telling us systems were down. Investigation showed that the SOA record for allstarlink.org was changed to what it is now (Cloudflare) and this broke numerous things. Both the wording and timing of this announcement is very much a jab (or middle finger) pointed directly at me since I'm the main person who has been running things. I am one who has ensured that the ASL Network (and associated infrastructure) remained operational and was able to handle the increasingly growing number of nodes (well over 5,100). This was done solely through me investing both my own time and money without the help or participation of the ASL Board. In addition to this "re-engineering" I have also had my account on the ASL Slack workspace suspended without notice and any and all admin access to the ASL Web portal was removed too (among other things).

For quite some time, well before Bryan Fields (W9CR) or Fred Moses (W8FSM) stopped their involvement in ASL directly, the AllStarLink, Inc Board (ASL Board) has done its best to alienate, patronize, ridicule, demean, and basically exclude the admin team from anything substantial regarding the ASL infrastructure for which they had no understanding of nor did they attempt to understand. Numerous attempts were made by myself and others to try to fix the issues that were very apparent, and yet they were met with disdain and ignored. This included on several occasions attempts at impassioned pleas by myself and others directly to the ASL Board members regarding the issues that we saw and asking for reparations to make things better. Of which included being open regarding any decisions being made which directly affected the admin team. Additionally, any and all attempts to ask what is happening on/at the board level regarding ASL were ignored or told that it didn't involve or concern us. Instead, they continued on the same course of action that served to alienate more and more people from participating in ASL on the admin side with the results of me being the sole admin person left.

This "re-engineering" and the resulting chaos and outages are serve as a testament to the ASL Board again attempting to change things without understanding the system itself and without telling anyone.

...

This is part of an ongoing two-year project to provide sufficient resources for projected node growth and additional stability. In addition, this will create a stable framework for new types of clients to participate in the future.

Again, nobody told me (or anyone else associated with the admin team) about this "two year project". Each and every time the ASL Board has attempted a change (and broken something), the current node registration system was brought up. For example, the Round Robin DNS (RRDNS) has been a sticking point for a certain unnamed ASL Board member, and during discussions this unnamed individual had the audacity to state that DSNMGR messages regarding changes to the IP address of the server at register.allstarlink.org was "trashing his node". One of the long since alienated admin team members had to explain that you could adjust logging in Asterisk through a config file. This is one of many examples that demonstrated the lack of knowledge of AllStarLink, Asterisk, and app_rpt by a member of the ASL Board. Yet we are to believe that a "two year project" has been in the works by this same group that is supposed be a "re-engineered" system to promote growth and stability?

...

You should also be aware that some specific volunteers (past and current) have opposed this sort of design change and we suspect that you may be reading negative comments from them on various platforms. The board’s staffing goals are to promote technical innovation from as many hams as want to get involved and bring new features and clients to Allstar.

Don't be fooled by this attempt at taking the high ground. The opposition they are implying results from attempts at changes from the ASL Board without understanding the underlying technical issues behind how/why things run and causing outages that they wouldn't (or couldn't) fix. Each and every time an ASL Board member brought up "re-engineering" the registration system, the reply that I empathically gave was that yes, the system can be improved upon but there needs to be a plan. I personally have stated that I am open to improvements to this system that were the result of planning, testing and made sense. The ASL Board thought that moving the system to AWS or Google would "solve" everything yet when pressed for details on how this would be done, we were met with crickets or arguments that it was just better and that was that. And when asked about a budget for such a move we were again met with silence. The "resistance" that is alluded to was with regards to actually sitting down and creating a plan on how to move forward with "re-engineering" this system, and not just what amounted to throwing scat at the wall and seeing what stuck (resulting in either myself or others on the admin team having to figure out what broke and fix it, since most of these changes were done without telling us). At no point during the any of occasions in which I said this has any ASL Board member taken the initiative to actually have this discussion with me (or anyone on the admin team) and come up with a viable plan to both "re-engineer" and do a proper cut over that isn't as disruptive as the one we are experiencing now.

There is a history of the ASL Board doing things that have broken registration and parts of the infrastructure in the past, and this is no different.

PTTLink was formed due to the ASL Board's actions which forked the AllStarLink network by changing the DNS records without prior notice.

The PTTLink Network can be thought of as an "overlay" to what had been in operation as the AllStarLink Network. This change was done simply by changing the domain name in use on the servers to pttlink.org. Your existing credentials will continue to work unless you change them. However, PTTLink, as a result of the ASL Board's egregious and careless action, is now a separate entity from the AllStarLink Network. I call upon the ASL Board to restore DNS back to the way it was before they forked it, moving everything back to the perfectly working infrastructure that uses what are now the pttlink.org servers. Additionally, I call upon them to restore all access that was revoked from me (both recently, and that which was revoked before without notice).

I am very disappointed in the egregious actions that the ASL Board has taken (or more importantly have directed others to take) with regards to the AllStarLink infrastructure and their statement. Such actions are clearly indicative of a group that is unfit to be the stewards to the legacy of the late Jim Dixon or properly be of service to the community without trying to benefit from it. Additionally, I feel that these actions, as made clear in their statement, were directed at me in an attempt to "punish" me for my insistence and diligence at keeping the ASL (now PTTLInk) infrastructure running when others made disruptive changes to it. If so, then this is very troubling indeed.

As I have very plainly stated before to the ASL Board members and others, as long as I have the resources to support ASL they will remain available. In that I will pledge to my fellow hams that PTTLink will remain operational and available for use as long as I am able to continue to provide the time and other resources to keeping it operational. Fortunately, I am no longer alone in this endeavor and others have volunteered to help.

The new links for PTTLInk sites are as follows:

PTTLink Portal - https://www.pttlink.org

PTTLink Stats Server - http://stats.pttlink.org

PTTLink Registration Server - register.pttlink.org

PTTLink Node List Server - nodes(x).pttlink.org

PTTLInk is on Reddit - https://www.reddit.com/r/pttlink

Additionally, you can use the DNS node lookup developed by W9CR (which was working with allstarlink.org before the ASL Board forked the network):

IP Address of registered node: dig <node#>.nodes.pttlink.org

TXT record showing DNS registration info: dig TXT <node#>. nodes.pttlink.org

Additionally, you can utilize the app_rpt-users mailing list for support by subscribing at

73, Stacy KG7QIN

_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users Unsubscribe posts to the list will result in public shaming.

_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users Unsubscribe posts to the list will result in public shaming.

-- Andrew Sylthe KC9ONA

politics politics politics why can't we all be friends and work together? On Wed, Dec 30, 2020 at 6:52 PM Steve Zingman <szingman@gmail.com> wrote:

I understand that, my question is why was it "moved" and not forked. I setup the AllStarLink github account as part of AllStarLink. No matter what pttlink does the resource is AllStarLink.

Steve N4IRS

On 12/30/20 8:46 PM, Andrew Sylthe wrote:

Steve,

It appears to have been moved to https://github.com/pttlink/Asterisk

On Wed, Dec 30, 2020 at 7:43 PM Steve Zingman <szingman@gmail.com> wrote:

...

Stacy, Do you know why the AllStarLink <https://github.com/AllStarLink> github repositories are gone? Was this part of the actions of the board?

Steve N4IRS

On 12/30/20 8:06 PM, Stacy wrote:

...

A bit on this change:

Nobody on the admin side that runs what was the AllStarLink (ASL) infrastructure (now PTTLink) was ever informed this was going to happen. Yesterday afternoon (12/29/20) at around 5:00 PM (Pacific) our monitoring system started going crazy with alerts telling us systems were down. Investigation showed that the SOA record for allstarlink.org was changed to what it is now (Cloudflare) and this broke numerous things. Both the wording and timing of this announcement is very much a jab (or middle finger) pointed directly at me since I'm the main person who has been running things. I am one who has ensured that the ASL Network (and associated infrastructure) remained operational and was able to handle the increasingly growing number of nodes (well over 5,100). This was done solely through me investing both my own time and money without the help or participation of the ASL Board. In addition to this "re-engineering" I have also had my account on the ASL Slack workspace suspended without notice and any and all admin access to the ASL Web portal was removed too (among other things).

For quite some time, well before Bryan Fields (W9CR) or Fred Moses (W8FSM) stopped their involvement in ASL directly, the AllStarLink, Inc Board (ASL Board) has done its best to alienate, patronize, ridicule, demean, and basically exclude the admin team from anything substantial regarding the ASL infrastructure for which they had no understanding of nor did they attempt to understand. Numerous attempts were made by myself and others to try to fix the issues that were very apparent, and yet they were met with disdain and ignored. This included on several occasions attempts at impassioned pleas by myself and others directly to the ASL Board members regarding the issues that we saw and asking for reparations to make things better. Of which included being open regarding any decisions being made which directly affected the admin team. Additionally, any and all attempts to ask what is happening on/at the board level regarding ASL were ignored or told that it didn't involve or concern us. Instead, they continued on the same course of action that served to alienate more and more people from participating in ASL on the admin side with the results of me being the sole admin person left.

This "re-engineering" and the resulting chaos and outages are serve as a testament to the ASL Board again attempting to change things without understanding the system itself and without telling anyone.

...

This is part of an ongoing two-year project to provide sufficient resources for projected node growth and additional stability. In addition, this will create a stable framework for new types of clients to participate in the future.

Again, nobody told me (or anyone else associated with the admin team) about this "two year project". Each and every time the ASL Board has attempted a change (and broken something), the current node registration system was brought up. For example, the Round Robin DNS (RRDNS) has been a sticking point for a certain unnamed ASL Board member, and during discussions this unnamed individual had the audacity to state that DSNMGR messages regarding changes to the IP address of the server at register.allstarlink.org was "trashing his node". One of the long since alienated admin team members had to explain that you could adjust logging in Asterisk through a config file. This is one of many examples that demonstrated the lack of knowledge of AllStarLink, Asterisk, and app_rpt by a member of the ASL Board. Yet we are to believe that a "two year project" has been in the works by this same group that is supposed be a "re-engineered" system to promote growth and stability?

...

You should also be aware that some specific volunteers (past and current) have opposed this sort of design change and we suspect that you may be reading negative comments from them on various platforms. The board’s staffing goals are to promote technical innovation from as many hams as want to get involved and bring new features and clients to Allstar.

Don't be fooled by this attempt at taking the high ground. The opposition they are implying results from attempts at changes from the ASL Board without understanding the underlying technical issues behind how/why things run and causing outages that they wouldn't (or couldn't) fix. Each and every time an ASL Board member brought up "re-engineering" the registration system, the reply that I empathically gave was that yes, the system can be improved upon but there needs to be a plan. I personally have stated that I am open to improvements to this system that were the result of planning, testing and made sense. The ASL Board thought that moving the system to AWS or Google would "solve" everything yet when pressed for details on how this would be done, we were met with crickets or arguments that it was just better and that was that. And when asked about a budget for such a move we were again met with silence. The "resistance" that is alluded to was with regards to actually sitting down and creating a plan on how to move forward with "re-engineering" this system, and not just what amounted to throwing scat at the wall and seeing what stuck (resulting in either myself or others on the admin team having to figure out what broke and fix it, since most of these changes were done without telling us). At no point during the any of occasions in which I said this has any ASL Board member taken the initiative to actually have this discussion with me (or anyone on the admin team) and come up with a viable plan to both "re-engineer" and do a proper cut over that isn't as disruptive as the one we are experiencing now.

There is a history of the ASL Board doing things that have broken registration and parts of the infrastructure in the past, and this is no different.

PTTLink was formed due to the ASL Board's actions which forked the AllStarLink network by changing the DNS records without prior notice.

The PTTLink Network can be thought of as an "overlay" to what had been in operation as the AllStarLink Network. This change was done simply by changing the domain name in use on the servers to pttlink.org. Your existing credentials will continue to work unless you change them. However, PTTLink, as a result of the ASL Board's egregious and careless action, is now a separate entity from the AllStarLink Network. I call upon the ASL Board to restore DNS back to the way it was before they forked it, moving everything back to the perfectly working infrastructure that uses what are now the pttlink.org servers. Additionally, I call upon them to restore all access that was revoked from me (both recently, and that which was revoked before without notice).

I am very disappointed in the egregious actions that the ASL Board has taken (or more importantly have directed others to take) with regards to the AllStarLink infrastructure and their statement. Such actions are clearly indicative of a group that is unfit to be the stewards to the legacy of the late Jim Dixon or properly be of service to the community without trying to benefit from it. Additionally, I feel that these actions, as made clear in their statement, were directed at me in an attempt to "punish" me for my insistence and diligence at keeping the ASL (now PTTLInk) infrastructure running when others made disruptive changes to it. If so, then this is very troubling indeed.

As I have very plainly stated before to the ASL Board members and others, as long as I have the resources to support ASL they will remain available. In that I will pledge to my fellow hams that PTTLink will remain operational and available for use as long as I am able to continue to provide the time and other resources to keeping it operational. Fortunately, I am no longer alone in this endeavor and others have volunteered to help.

The new links for PTTLInk sites are as follows:

PTTLink Portal - https://www.pttlink.org

PTTLink Stats Server - http://stats.pttlink.org

PTTLink Registration Server - register.pttlink.org

PTTLink Node List Server - nodes(x).pttlink.org

PTTLInk is on Reddit - https://www.reddit.com/r/pttlink

Additionally, you can use the DNS node lookup developed by W9CR (which was working with allstarlink.org before the ASL Board forked the network):

IP Address of registered node: dig <node#>.nodes.pttlink.org

TXT record showing DNS registration info: dig TXT <node#>. nodes.pttlink.org

Additionally, you can utilize the app_rpt-users mailing list for support by subscribing at

73, Stacy KG7QIN

_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users Unsubscribe posts to the list will result in public shaming.

_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users Unsubscribe posts to the list will result in public shaming.

-- Andrew Sylthe KC9ONA

_______________________________________________ App_rpt-users mailing listApp_rpt-users@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users Unsubscribe posts to the list will result in public shaming.

_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users Unsubscribe posts to the list will result in public shaming.

FYI On Wed, Dec 30, 2020 at 6:08 PM Stacy <kg7qin@arrl.net> wrote:

A bit on this change:

Nobody on the admin side that runs what was the AllStarLink (ASL) infrastructure (now PTTLink) was ever informed this was going to happen. Yesterday afternoon (12/29/20) at around 5:00 PM (Pacific) our monitoring system started going crazy with alerts telling us systems were down. Investigation showed that the SOA record for allstarlink.org was changed to what it is now (Cloudflare) and this broke numerous things. Both the wording and timing of this announcement is very much a jab (or middle finger) pointed directly at me since I'm the main person who has been running things. I am one who has ensured that the ASL Network (and associated infrastructure) remained operational and was able to handle the increasingly growing number of nodes (well over 5,100). This was done solely through me investing both my own time and money without the help or participation of the ASL Board. In addition to this "re-engineering" I have also had my account on the ASL Slack workspace suspended without notice and any and all admin access to the ASL Web portal was removed too (among other things).

For quite some time, well before Bryan Fields (W9CR) or Fred Moses (W8FSM) stopped their involvement in ASL directly, the AllStarLink, Inc Board (ASL Board) has done its best to alienate, patronize, ridicule, demean, and basically exclude the admin team from anything substantial regarding the ASL infrastructure for which they had no understanding of nor did they attempt to understand. Numerous attempts were made by myself and others to try to fix the issues that were very apparent, and yet they were met with disdain and ignored. This included on several occasions attempts at impassioned pleas by myself and others directly to the ASL Board members regarding the issues that we saw and asking for reparations to make things better. Of which included being open regarding any decisions being made which directly affected the admin team. Additionally, any and all attempts to ask what is happening on/at the board level regarding ASL were ignored or told that it didn't involve or concern us. Instead, they continued on the same course of action that served to alienate more and more people from participating in ASL on the admin side with the results of me being the sole admin person left.

This "re-engineering" and the resulting chaos and outages are serve as a testament to the ASL Board again attempting to change things without understanding the system itself and without telling anyone.

...

This is part of an ongoing two-year project to provide sufficient resources for projected node growth and additional stability. In addition, this will create a stable framework for new types of clients to participate in the future.

Again, nobody told me (or anyone else associated with the admin team) about this "two year project". Each and every time the ASL Board has attempted a change (and broken something), the current node registration system was brought up. For example, the Round Robin DNS (RRDNS) has been a sticking point for a certain unnamed ASL Board member, and during discussions this unnamed individual had the audacity to state that DSNMGR messages regarding changes to the IP address of the server at register.allstarlink.org was "trashing his node". One of the long since alienated admin team members had to explain that you could adjust logging in Asterisk through a config file. This is one of many examples that demonstrated the lack of knowledge of AllStarLink, Asterisk, and app_rpt by a member of the ASL Board. Yet we are to believe that a "two year project" has been in the works by this same group that is supposed be a "re-engineered" system to promote growth and stability?

...

You should also be aware that some specific volunteers (past and current) have opposed this sort of design change and we suspect that you may be reading negative comments from them on various platforms. The board’s staffing goals are to promote technical innovation from as many hams as want to get involved and bring new features and clients to Allstar.

Don't be fooled by this attempt at taking the high ground. The opposition they are implying results from attempts at changes from the ASL Board without understanding the underlying technical issues behind how/why things run and causing outages that they wouldn't (or couldn't) fix. Each and every time an ASL Board member brought up "re-engineering" the registration system, the reply that I empathically gave was that yes, the system can be improved upon but there needs to be a plan. I personally have stated that I am open to improvements to this system that were the result of planning, testing and made sense. The ASL Board thought that moving the system to AWS or Google would "solve" everything yet when pressed for details on how this would be done, we were met with crickets or arguments that it was just better and that was that. And when asked about a budget for such a move we were again met with silence. The "resistance" that is alluded to was with regards to actually sitting down and creating a plan on how to move forward with "re-engineering" this system, and not just what amounted to throwing scat at the wall and seeing what stuck (resulting in either myself or others on the admin team having to figure out what broke and fix it, since most of these changes were done without telling us). At no point during the any of occasions in which I said this has any ASL Board member taken the initiative to actually have this discussion with me (or anyone on the admin team) and come up with a viable plan to both "re-engineer" and do a proper cut over that isn't as disruptive as the one we are experiencing now.

There is a history of the ASL Board doing things that have broken registration and parts of the infrastructure in the past, and this is no different.

PTTLink was formed due to the ASL Board's actions which forked the AllStarLink network by changing the DNS records without prior notice.

The PTTLink Network can be thought of as an "overlay" to what had been in operation as the AllStarLink Network. This change was done simply by changing the domain name in use on the servers to pttlink.org. Your existing credentials will continue to work unless you change them. However, PTTLink, as a result of the ASL Board's egregious and careless action, is now a separate entity from the AllStarLink Network. I call upon the ASL Board to restore DNS back to the way it was before they forked it, moving everything back to the perfectly working infrastructure that uses what are now the pttlink.org servers. Additionally, I call upon them to restore all access that was revoked from me (both recently, and that which was revoked before without notice).

I am very disappointed in the egregious actions that the ASL Board has taken (or more importantly have directed others to take) with regards to the AllStarLink infrastructure and their statement. Such actions are clearly indicative of a group that is unfit to be the stewards to the legacy of the late Jim Dixon or properly be of service to the community without trying to benefit from it. Additionally, I feel that these actions, as made clear in their statement, were directed at me in an attempt to "punish" me for my insistence and diligence at keeping the ASL (now PTTLInk) infrastructure running when others made disruptive changes to it. If so, then this is very troubling indeed.

As I have very plainly stated before to the ASL Board members and others, as long as I have the resources to support ASL they will remain available. In that I will pledge to my fellow hams that PTTLink will remain operational and available for use as long as I am able to continue to provide the time and other resources to keeping it operational. Fortunately, I am no longer alone in this endeavor and others have volunteered to help.

The new links for PTTLInk sites are as follows:

PTTLink Portal - https://www.pttlink.org

PTTLink Stats Server - http://stats.pttlink.org

PTTLink Registration Server - register.pttlink.org

PTTLink Node List Server - nodes(x).pttlink.org

PTTLInk is on Reddit - https://www.reddit.com/r/pttlink

Additionally, you can use the DNS node lookup developed by W9CR (which was working with allstarlink.org before the ASL Board forked the network):

IP Address of registered node: dig <node#>.nodes.pttlink.org

TXT record showing DNS registration info: dig TXT <node#>. nodes.pttlink.org

Additionally, you can utilize the app_rpt-users mailing list for support by subscribing at

73, Stacy KG7QIN

_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users Unsubscribe posts to the list will result in public shaming.

-- 73 and aloha Dave - AH6OD

Hey guys, OK, for those thinking about holding off on allstar, don't let politics get in the way. This is nothing more than a bunch of nonsense, kids being kids. These people just need to grow up! Why can't we all play nice in the same sandbox. Seriously guys, this political nonsense has gone on for way too long, and it needs to stop, right now. This sort of political nonsense will turn people away from the hobby. Go spread the allstar virus, and enjoy it. Leave the idiots behind, and let them sulk in their little corner. Seriously guys, can't we just concentrate on all moving this thing forward and work together? I guess that's too hard to ask. On 1/2/21, Tom Hayward <tom@tomh.us> wrote:

I have admittedly limited knowledge on the topic, but I'll take a stab at explaining it.

- The AllStarLink Inc (not Jim Dixon) has registered a trademark for the word "AllStar" for things related to "Transmission and delivery of amateur radio voice and text signals via internet protocol" https://tsdr.uspto.gov/#caseNumber=87773109&caseSearchType=US_APPLICATION&ca... - The contributors to the AllStarLink Github repo are not AllStarLink Inc: https://github.com/pttlink/Asterisk/graphs/contributors - (And here's where I'm making a guess...) To protect themselves from legal action by AllStarLink Inc, the contributors to the open source software have begun removing references to "AllStar" that could be a legal target, including the naming of the Github organization.

Tom KD7LXL

On Wed, Dec 30, 2020 at 7:58 PM Steve Zingman <szingman@gmail.com> wrote:

...

I have NOTHING to do with the politics of what is going on. I'm simply a user asking what happened to the AllStarLink repository. And, I'm still waiting for a answer.

Steve N4IRS

On 12/30/20 10:44 PM, Skyler F wrote:

politics politics politics

why can't we all be friends and work together?

On Wed, Dec 30, 2020 at 6:52 PM Steve Zingman <szingman@gmail.com> wrote:

...

I understand that, my question is why was it "moved" and not forked. I setup the AllStarLink github account as part of AllStarLink. No matter what pttlink does the resource is AllStarLink.

Steve N4IRS

Went to the http://stats.pttlink.org/ site A big 15 node reporting to the server, Looks like the rescue mission was done. The rest of the nodes are on allstarlink.org, Last I checked they had 4900+ nodes registering. of the Is the masquerade of the allstar link network still useful? Le sam. 2 janv. 2021 à 19:13, ARS W5OMR <ars.w5omr@gmail.com> a écrit :

So far as I can tell, my node is stil operational, and I'm not changing anything. I can connect to another node, and I just checked the pttlink thing, and see a grand total of... 32 nodes? I'm kinda happy with the status quo, and didn't/don't see a need for change. I did see that my info is listed at pttlink, but they say they've not seen my node since the 30th of December, last year. That was 3 days ago. I'm good with them not ever seeing me on that site. ~shrug~ If it ain't broke, don't fix it!

On Sat, Jan 2, 2021 at 4:36 PM Jed Barton <jed@jedbarton.com> wrote:

...

Hey guys,

OK, for those thinking about holding off on allstar, don't let politics get in the way. This is nothing more than a bunch of nonsense, kids being kids. These people just need to grow up! Why can't we all play nice in the same sandbox. Seriously guys, this political nonsense has gone on for way too long, and it needs to stop, right now. This sort of political nonsense will turn people away from the hobby. Go spread the allstar virus, and enjoy it. Leave the idiots behind, and let them sulk in their little corner. Seriously guys, can't we just concentrate on all moving this thing forward and work together? I guess that's too hard to ask.

On 1/2/21, Tom Hayward <tom@tomh.us> wrote:

...

I have admittedly limited knowledge on the topic, but I'll take a stab at explaining it.

- The AllStarLink Inc (not Jim Dixon) has registered a trademark for the word "AllStar" for things related to "Transmission and delivery of amateur radio voice and text signals via internet protocol"

https://tsdr.uspto.gov/#caseNumber=87773109&caseSearchType=US_APPLICATION&ca...

...

- The contributors to the AllStarLink Github repo are not AllStarLink Inc: https://github.com/pttlink/Asterisk/graphs/contributors - (And here's where I'm making a guess...) To protect themselves from legal action by AllStarLink Inc, the contributors to the open source software have begun removing references to "AllStar" that could be a legal target, including the naming of the Github organization.

Tom KD7LXL

On Wed, Dec 30, 2020 at 7:58 PM Steve Zingman <szingman@gmail.com> wrote:

...

I have NOTHING to do with the politics of what is going on. I'm simply a user asking what happened to the AllStarLink repository. And, I'm still waiting for a answer.

Steve N4IRS

On 12/30/20 10:44 PM, Skyler F wrote:

politics politics politics

why can't we all be friends and work together?

On Wed, Dec 30, 2020 at 6:52 PM Steve Zingman <szingman@gmail.com> wrote:

...

I understand that, my question is why was it "moved" and not forked. I setup the AllStarLink github account as part of AllStarLink. No matter what pttlink does the resource is AllStarLink.

Steve N4IRS

_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users Unsubscribe posts to the list will result in public shaming.

-- Operating your AM rig without a scope is like driving our car at night without headlights. (~K4KYV)

73 = Best Regards, -Geoff/W5OMR _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.keekles.org/cgi-bin/mailman/listinfo/app_rpt-users Unsubscribe posts to the list will result in public shaming.