forum.pistar.uk

The "Network 6" section of the mmdvm configuration file can be corrupted by the dashboard's configuration panel, forcing users to only manipulate the config via the expert edits. Specifically, the password= and options= entries were being dropped if you made changes via the dashboard's config panel ...

Erroneous Local RF entries may appear from time to time in the dashboard, entries that seemingly are not associated with any particular call sign but are of DMR origin.

---

The problem stems from a change in the way Talker Aliases are logged by the older versions of the MMDVM host program compared ...

From the Pi-Star dashboard, follow the menu items: Configuration --> Expert --> SSH Access. At the prompt, enter your Pi-Star user name and password, then enter these commands:

rpi-rw
sudo sed -i 's/\/usr\/local\/sbin\/pistar-motdgen/&\n\nsudo rfkill unblock wlan 2>\/dev\/nul/g' /etc/rc.local

If ...

Are you running on a Pi5? Do you keep your HS up 24/7?

A subtle problem seems to have creep into recent Debian updates for Bookworm relating to Pi5's that results in the wifi (wlan0) being flagged as "blocked". The change appears to have occurred about a month or two ago, but if one had not cycled ...

The messages coming out of the update/upgrade process are misleading as to the exact cause of the problem: not enough memory to build temp files? unpack files? not enough space allocated in TMP directory?

Playing around with this it a bit on the latest upgrade, I found that INCREASING the /tmp ...

Bookworm offers NetManager but the old mechanisms are still supported: Pi-Star has not moved to that alternate mechanism. Regardless, they all still involve/invoke DHCPCD services. And they all depend on various directories allocated in TMPFS. So when you temporally reallocate those directories ...

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.

I found that I had to run "sudo systemctl restart dhcpcd.service" after killing off the RAM disks and rebooting in order to establish a connection. Manageable perhaps, but another pain nevertheless.

There's gotta be a better, less risky . less involved way to do all this. Updates/upgrades used to ...

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 ...

I do not know how the host files are derived. My assumptions is that they are sourced from Brandmeister and thus this is a question better answered by them.

But the more important question is why is it missing from BM's inventory: is this a new master and thus an oversight on their part? Or is the ...