Despite having my DSTAR default reflector set for startup, this doesn't happen. I have to initiate it manually.
Is there something I have forgotten to set?
Maintaining a reflector/gateway link over the Pi-Star update process
Re: Maintaining a reflector/gateway link over the Pi-Star update process
Pi-Star tasks/services are not started (stopped and restarted) in the same sequence depending on whether you're (re)booting, running an update from the CLI or the dashboard, or initiating a restart from a config change, so I'm assuming/thinking what we have here is a timing/sequencing problem.
Exactly how do you manually initiate corrective actions (dashboard or CLI)? Perhaps there's a clue there.
(Admittedly, I'm just grabbing at straws here, as I have only a passing knowledge of D-Star....)
Exactly how do you manually initiate corrective actions (dashboard or CLI)? Perhaps there's a clue there.
(Admittedly, I'm just grabbing at straws here, as I have only a passing knowledge of D-Star....)
Re: Maintaining a reflector/gateway link over the Pi-Star update process
I simply click the Request Change button on the Admin page's DSTAR Link Manager section. The other fields on this section are already filled out, the link comes up immediately.
--
Brian G8SEZ
Brian G8SEZ
Re: Maintaining a reflector/gateway link over the Pi-Star update process
Is this or was this something that worked at one time, but now seems to be broken? I'm not seeing anything that would kick off this process during boot ups or config restarts.
Re: Maintaining a reflector/gateway link over the Pi-Star update process
I have never had it working since I started using DSTAR with one of my Pi-Star hotspots. I had assumed that it should work in the same way that the DMR service does, it connects to the server at start up. When you have a setting that is startup/manual then I expected startup to do what it says.
--
Brian G8SEZ
Brian G8SEZ
Re: Maintaining a reflector/gateway link over the Pi-Star update process
What reflector are you trying to connect to on boot?G8SEZ wrote: ↑Sat Nov 16, 2024 3:25 pmI have never had it working since I started using DSTAR with one of my Pi-Star hotspots. I had assumed that it should work in the same way that the DMR service does, it connects to the server at start up. When you have a setting that is startup/manual then I expected startup to do what it says.
Re: Maintaining a reflector/gateway link over the Pi-Star update process
It's GB7IC module B, my end is G8SEZ D and G8SEZ G for the DSTAR repeater settings.MW0MWZ wrote: ↑Tue Apr 22, 2025 4:59 pmWhat reflector are you trying to connect to on boot?G8SEZ wrote: ↑Sat Nov 16, 2024 3:25 pmI have never had it working since I started using DSTAR with one of my Pi-Star hotspots. I had assumed that it should work in the same way that the DMR service does, it connects to the server at start up. When you have a setting that is startup/manual then I expected startup to do what it says.
--
Brian G8SEZ
Brian G8SEZ
Re: Maintaining a reflector/gateway link over the Pi-Star update process
That repeater is not in the US Trust list (it was previously) so now you have to wait for it to show up in the routing before it can be connected to.
Re: Maintaining a reflector/gateway link over the Pi-Star update process
Ah, I see, do you have any idea why this has changed?
Also, just ran the mmdvmhost update you mentioned and then needed a reboot before the connection would come up again.
--
Brian G8SEZ
Brian G8SEZ
Re: Maintaining a reflector/gateway link over the Pi-Star update process
That's one for the keeper of GB7IC, if it was in the US Trust list, it would also be in the Pi-Star host files. They may not be using US Trust for callsign routing any more? all questions for the keeper tho.
If you just did a normal update in pi-star, just wait longer, the update will stop/start ircDDBGateway, and again, you need that host GB7IC to show up in the routing before you can connect to it, otherwise your gateway has no idea how to find it.