It was a pleasure to meet Tom at the conference.? I really applaud the work he is?doing.? Just a minor clarification, it is the DPLUS infrastructure that is looking for a specific authentication (not Icom/US Trust). A little background. When a client is participating in the DPLUS (REF) network, there is a handshake at the beginning/startup of the session.? One of the effects of the handshake is a current list of known DPLUS reflectors and their IP addresses are provided to the client.? During the same time frame as the DCC, some widely used clients were failing to authenticate and get these updates.? I contacted Robin Cutshaw (AA4RC) and we found a couple of things.? First, many of the clients were using an old hostname to authenticate against and that prevented failover to redundant servers that the network provides.? Second, the reason that the clients were failing is that they were hitting a single server which was crashing, most likely due to bad code attempting to authenticate.? This has been a continuing problem for the DPLUS network, where someone will write some new code and not have all of the details.? It is probably a case of not knowing, rather than being malicious.? I am not aware of any case where Tom's code has been the problem, it just was a good opportunity to pass along some information he could apply to his code. With the information Tom received, he will be able to provide better service by giving his client(s) the ability to 'failover' during authentication and also get the updated DPLUS reflector list from the DPLUS server infrastructure. Thanks. On Wed, Oct 3, 2018 at 10:14 AM Tom Early <n7tae@...> wrote: At the Digital Communications Conference in Albuquerque last month, John Hays, K7VE, told me that the G2/G3 Trust system has changed how gateways/users are authenticated. I got the technical details on Sept. 22. I will fix this in QnetGateway, but it will take some time. I would really like to thank John for keeping me "in the loop" on this! John D. Hays Edmonds, WA K7VE ![]() |