MW0MWZ wrote: ↑Tue May 20, 2025 9:04 am
Updated the host generation back to IP-only... should be back to normality again now (when you next press update or the overnight updates run).
Ok, first thank you for all your work, Andy. Really, thank you.
Now I was thinking... maybe is not easy to do it or is not worth, but if the disconnections are caused by a kind of dns resolution storm, is possible to do only the dns resolution of the YSF reflector that we want to connect to?
I've also been working on YSFGateway to improve it some (these are available in Pi-Star 4.3.x)
When searching / listing reflectors, they are listed with the name field in uppercase always - this matches what Wires-X does, and *should* remove the need for upper-case host files to help FT-70D radios among others.
I spotted a crash where searching for reflector 00000 (or any that did not exist, searched by ID) could crash YSFGateway, this has also been fixed up.
In addition to the above, now when you search for a reflector by ID that does not exist, the state in YSFGateway and your radio matches up, you get an instant "offline" message back from YSFGateway, at this point your radio believes that you are not connected to a reflector, and so YSFGateway also unlinks.
Compared to previous work that exists in YSFGateway these additions are a drop in a very large ocean, but I hope they help a little with the user experience.
