andytaylortweet / pi-star_dv_dash Goto Github PK

If the BrandMeister hotspot security password contains non-alphanumeric characters (e.g., !@#$%&) the password is escaped before saving it to the .ini file. When the page is reloaded, the page load escapes the string again, and that blocks access to BrandMeister network.

Step to reproduce:

• Set DMR master to DMRGateway
• Set BM Hotspot security to Test#1234
• Apply changes

In the /etc/dmrgateway, the following line will be written;
Password=Test\#1234

• Now, toggle BrandMeister Network enable and apply changes

In the /etc/dmrgateway, the password now reads;
Password=Test\\\#1234

Possible culprit:

In configure.php, line 1009, the newly set password is escaped

$configModem['BrandMeister']['Password'] = escapeshellcmd($_POST['bmHSSecurity']);

Then in configure.php, line 3174, the password field is filled with the content of the configuration file, which is already escaped.

<input type="password" name="bmHSSecurity" size="30" maxlength="30" value="<?php if (isset($configModem['BrandMeister']['Password'])) {echo $configModem['BrandMeister']['Password'];} ?>"></input>

I have use

Pi-Star:3.4.11 / Dashboard:20180323

I have manually changed in /usr/local/etc/XLXHosts.txt

950;158.64.26.134;4004

to

950;158.64.26.134;4009

because I would like to connect to the module I

but DMRgateway still connect my hotspot to module E (4004)

This problem is not really new, I did just check why/when it happens and found that it is related to DMRGateway/DMR2YSF/DMR2NXDN password "none", actually it is very easy to reproduce:

• just select DMRGateway/DMR2YSF/DMR2NXDN and apply settings -> this will set password="none" on mmdvmhost ini
• then disable DMR mode and apply settings -> this will set password=none (no quotes)
• apply settings again with DMR mode still disabled -> the unquoted none password will be read as empty value, as none is a special word for parse_ini_file(), then it will set password= on mmdvmhost ini and next time you enable DMR then mmdvmhost will refuse to startup due to empty password

You can either sort it by changing configure.php to ensure password is always quoted (i.e. when applying settings with DMR mode disabled) or just update DMR_Hosts.txt on your server to use any password different than "none" for DMRGateway/DMR2YSF/DMR2NXDN, as I guess any password works for these?

Alternatively... if you have more of these issues with quotes (and I guess you may have some at least with editor pages also...) did you ever consider using parse_ini_file(..., true, INI_SCANNER_RAW) to completely handle ini's without quotes? seeing that sample ini's coming with DV programs also don't have quotes I guess they don't really require it, you probably add them just to be able to read them on php I guess...

please at callsign DO7EN to MMDVM_HS_Hat Dual in configure.php
MMDVM_HS_Hat Dual (DB9MAT & DF2ET)
MMDVM_HS_Hat Dual (DB9MAT DF2ET DO7EN)

Would it be possible to add the wild card search filter so one can search for a channel?
There are 1249 items in YSFHosts.txt. If not could they be at least sorted in the list by YSF ID? Or at least give the option to sort by YSF ID on load/reload? It is very hard to find one I am looking for.
Also on my iPad Pro, scrolling this list is very very slow. The first 100? items scroll very fast. But if you get to the middle or bottom and try to back it takes a very long time.

I am running "Pi-Star:4.1.6 / Dashboard: 20220115"

The nice select script overides the inline click handler that shows/hides the manual input

See https://forum.pistar.uk/viewtopic.php?t=4232

Actually on dashboard Pi-star 3.x in "Status Network" not exist POCSAG information

Today I have in log file DAPNETGateway

M: 2019-02-23 12:17:25.964 Opening POCSAG network connection
I: 2019-02-23 12:17:25.964 Opening UDP port on 4800
M: 2019-02-23 12:17:25.964 Opening DAPNET connection
M: 2019-02-23 12:17:26.077 Starting DAPNETGateway-20181107_Pi-Star
M: 2019-02-23 12:17:26.077 Logging into DAPNET
M: 2019-02-23 12:17:31.097 Logged into the DAPNET network
M: 2019-02-23 12:17:31.343 Schedule information received: 0123456789ABCDEF
M: 2019-02-23 12:51:16.461 All slots are available for transmission
E: 2019-02-23 15:56:31.464 Error returned from recv, err=110
M: 2019-02-23 15:56:31.464 Closing DAPNET connection
M: 2019-02-23 15:56:31.464 Opening DAPNET connection
E: 2019-02-23 15:58:44.579 Cannot connect the TCP client socket, err=110
M: 2019-02-23 15:58:44.580 Closing DAPNET connection
M: 2019-02-23 15:58:44.580 Opening DAPNET connection
E: 2019-02-23 16:00:57.700 Cannot connect the TCP client socket, err=110
M: 2019-02-23 16:00:57.700 Closing DAPNET connection
M: 2019-02-23 16:00:57.700 Opening DAPNET connection
E: 2019-02-23 16:03:10.819 Cannot connect the TCP client socket, err=110
M: 2019-02-23 16:03:10.820 Closing DAPNET connection
M: 2019-02-23 16:03:10.820 Opening DAPNET connection
E: 2019-02-23 16:05:23.939 Cannot connect the TCP client socket, err=110
M: 2019-02-23 16:05:23.940 Closing DAPNET connection
M: 2019-02-23 16:05:23.940 Opening DAPNET connection
E: 2019-02-23 16:07:37.060 Cannot connect the TCP client socket, err=110
M: 2019-02-23 16:07:37.060 Closing DAPNET connection
M: 2019-02-23 16:07:37.060 Opening DAPNET connection
......
M: 2019-02-23 16:34:03.366 Opening DAPNET connection
E: 2019-02-23 16:34:03.406 Cannot connect the TCP client socket, err=111
M: 2019-02-23 16:34:03.406 Closing DAPNET connection
M: 2019-02-23 16:34:03.406 Opening DAPNET connection
E: 2019-02-23 16:34:03.450 Cannot connect the TCP client socket, err=111
M: 2019-02-23 16:34:03.450 Closing DAPNET connection
M: 2019-02-23 16:34:03.450 Opening DAPNET connection

but w don't know about this on the dashboard in STATUS NETWORK :-(

I have noticed that the Dashboard for the GB7YJ DMR repeater (I am only a user, not the repeater keeper) sometimes shows an incrementing TX Duration even though that specific transmission has stopped.
The repeaters Dashboard identifies its versions as: Pi-Star:3.4.17 / Dashboard: 20200813

More often than not, this occurs when my MD-390 transmits an SMS message containing GPS data from an area with marginal repeater coverage, so in that case the repeater is receiving the transmission over RF. The TX counter continues to increment even after I have turned my radio off.

Under such circumstances, I have stopped the incrementing TX counter by making another transmission, at which point the Dashboard appears to be completely normal.

I have also seen this occur in relation to TG traffic arriving at the repeater over the Net, but this has been rarer in my experience.

I will attempt to grab screenshots of this behaviour at the next opportunity.

I have seen another quirk which may or may not be related. This other quirk seems to show a row of activity which clearly pertains to DMR voice traffic with a TG destination, that appears on an adjacent row to another row showing an SMS transmission. This 2nd quirk populates the last 3 columns of the DMR voice activity with the "SMS" string, such that 2 adjacent rows show "SMS" in the last three columns. If it becomes clear that this is an entirely unrelated problem, I will raise a different a different issue.

In Line 239, the call to "platformDetect.sh" may be unsafe as it does not specify an absolute path to the script.

<td colspan="2"><?php echo exec('platformDetect.sh');?></td>

Hello Pi-Star team!

It would greatly benefit us to be able to search reflectors by ID number rather than having to scroll through a drop-down menu of hundreds or thousands of rooms. I think it would be a great time saver.

I have M17 and other modes enabled in pi-star and I'm using MMDVM_HS_DUAL_HAT v1.6.0. M17 hang time is set to the standard 20 seconds. When M17 is detected "M17 Listening" is shown on the dashboard but it continues to show after the 20 second hangtime and continues to show until another mode is detected--"Listening" never shows even though pi-star is listening because when I transmit in any mode other than M17 the dashboard will detect the mode and display the correct "Listening" mode.

Hi Andy, Not exactly related to the dashboard (unless you will also want to set ReloadTime differently after reading this, but not the real solution)... there is currently a huge delay when YSFGateway loads/reloads YSF hosts list, this causes two problems: one is the undesired delay itself when YSFGateway starts up and even worst is that you (configure.php) also setup YSFGateway to reload hosts list every hour (ReloadTime=60) and during this reload YSFGateway seems to freeze completely for some time, meaning audio lost and it doesn't even send keep-alive packets to the connected reflector, causing connection drops every hour (most noticeable on new XLXs as they default to 30s YSF keep-alive timeout, instead of 60s of YSFReflector)...

I really guess this delay is caused by DNS resolution of the list host names as the list is increasing more and more and many YSF owners now specify host names instead of IP's... then maybe it's time you do the same you did for D-Star reflectors list: resolve host names on your server from time to time and feed resolved list with just IP's to Pi-Star's?

The log below shows YSFGateway taking 55s to load the YSF hosts list, but I did already see it taking even more than 1min sometimes (causing drop from time to time even on my tests XLX that is tweaked to 60s YSF keep-alive timeout).

M: 2020-02-19 05:48:52.216 Opening YSF network connection
I: 2020-02-19 05:48:52.216 Opening UDP port on 4200
M: 2020-02-19 05:48:52.217 Opening YSF network connection
I: 2020-02-19 05:48:52.217 Opening UDP port on 42000
M: 2020-02-19 05:48:52.217 Resolving FCS00x addresses
M: 2020-02-19 05:48:52.718 Opening FCS network connection
I: 2020-02-19 05:48:52.718 Opening UDP port on 42001
I: 2020-02-19 05:48:52.719 The ID of this repeater is 42620
I: 2020-02-19 05:48:52.721 Loaded 306 FCS room descriptions
E: 2020-02-19 05:49:17.710 Cannot find address for host fusion2.m1axm.co.uk
I: 2020-02-19 05:49:47.428 Loaded 655 YSF reflectors
I: 2020-02-19 05:49:47.428 Loaded YSF parrot
I: 2020-02-19 05:49:47.428 Loaded YSF2DMR
I: 2020-02-19 05:49:47.428 Loaded YSF2NXDN
I: 2020-02-19 05:49:47.428 Loaded YSF2P25
M: 2020-02-19 05:49:47.508 Starting the APRS Writer thread
M: 2020-02-19 05:49:47.508 No connection startup
M: 2020-02-19 05:49:47.508 Starting YSFGateway-20190130_Pi-Star

Thanks!

Hi, I just updated and the screen port selection doesn't work.
Regards.

Thanks for this great project!

I'm interested in exporting structured data from my Pi-Star to other devices on my network. All of the information I need can be found on the dashboards, though it'd be preferable if the device provided an API to avoid the need for HTML parsing.

Would you be willing to review PR(s) that add an api directory with endpoints that publish parts of the dashboard as JSON?

Every time you modify any configuration setting in the UI, APRS reporting is turned back on for the YSF gateway. This appears to be done by this line in configure.php:

Could this part of configure.php at least be rewritten to respect the current preference for APRS, rather than forcibly enabling it every time any configuration option is changed? (Ideally... would it possible to have (ideally a hotspot-wide) "enable APRS" toggle somewhere? I don't want my hotspot blasting out its location to the world.)

If you disable the "aprs.fi" option in Expert config, it does stay disabled until you make literally any other config change, then the code listed above re-enables it.

My hotspot with OLED Type 3 display is fully functional with MMDVM firmware 1.5.2 but when using v1.6.0 with M17 the screen is blank no matter what the OLED settings in the main config page.

This may apply to other special characters as well. When configuring something like an iPhone SSID, these devices default to naming the SSID for example Matt's iPhone. When an SSID such as this is input into the Pi-Star WiFi Configuration page the hexadecimal conversion that is done silently fails to convert the string and the resulting output is a blank ssid= line in wpa_supplicant.conf and an incorrect hexadecimal conversion.

This results in the end-user not being able to connect to the device, and no error messages indicating there is an issue.

I have corrected this issue and will submit a Pull Request for my fixes after submitting this Issue report.

I'm using M17 modified Pi-Star with MMDVM v1.6.0. The dashboard and admin pages go from showing the P25 & NXDN networks as "Linked to xxx" but after a few hours the P25 & NXDN network shows "Not Linked" but they still function as if they are linked. They still respond to P25 and NXDN traffic.

Every time a new access point is added via WIFI configuration dashboard the wpa_supplicant config is being rewritten and is setting country=JP. Which is setting wrong frequencies for devices with 5ghz radios causing connectivity issues for some raspberry pi's.

Dashboard should allow people to select their country region and use that instead of using a hidden hard coded default.

/var/www/dashboard/admin/wifi.php

if(isset($_POST['SaveWPAPSKSettings'])) { $config = "ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev\nupdate_config=1\nap_scan=1\nfast_reauth=1\ncountry=JP\n\n"; $networks = $_POST['Networks'];

In the configure page, in some places the file system is remounted as RW e.g.

https://github.com/AndyTaylorTweet/Pi-Star_DV_Dash/blob/master/admin/configure.php#L247-L250

However the cron service is not stopped until after the file system is made RW, and there is a small chance that cron may run between the file system being mounted RW and cron being stopped

I think cron should probably be stopped before the files system is mounted as RW

In Line 40, the call to "platformDetect.sh" may be unsafe as it does not specify an absolute path to the script.

<td colspan="2"><?php echo exec('platformDetect.sh');?></td>

Hi,
Could you add Field "NAME" (From /usr/local/etc/DMRIds.dat) to the Dashboard (/var/www/dashboard/mmdvmhost/lh.php script) between CALL and GPS?

Thanks a lot from qrz.com/db/iv3nfc

I have a number of DMR talk groups I monitor, but it's hard to keep track of their numbers. I started looking at the code and make a little hack to run from the browser console window that substitutes "TG 12345" with the friendly name I want to see displayed:
reloadLastHerd = function (){
$.get("/mmdvmhost/lh.php",null,function(responseText, textStatus, jqXHR){
console.log("hello");
$("#lastHerd").html(responseText
//add your mappings here
.replace(/TG 3112/g,"Florida 3112")
.replace(/TG 31124/g,"South-East-Flori (DMR NET)")
.replace(/TG 31622/g,"South East FL (SW Ranches)")
.replace(/TG 31777/g,"DX Link/NQR Net")
.replace(/TG KI7WKZ/g,"East Coast Reflector")
//etc...
);
setTimeout(reloadLastHerd,1500)
});
}

Very hacky, so I'd like to handle this directly in lh.php. Basically lh.php would have access to a lookup table pairing TG X with a friendly name, and would simply replace with the friendly name (or maybe offer hover-over to see the id). Take javascript out of the equation.

Question is where would be a good place to keep this lookup table, and is there already a gui in place to let users edit such a table? I'm a little new to the software and have been just skimming the code, so figure I'd ask. 73 Randy KN4YRM

Hi,

not sure if this is the correct repository.

I just noticed the Pi-Star Updater giving out the following output:

Updates complete, sleeping for a few seconds before making the disk Read-Only
Finished

Instead of waiting, I'd like to suggest using the sync command.

I mean... There's the potential for data loss if writing takes longer than the time waiting. :)

If I use a password with special characters (i.e. >/%.!), I cannot login to my pi-star. If I use a password with just letters it works correctly.

I am setting my password by using the configuration page and trying to access my pi-star by using the SSH Access link in the expert tab.

If a DMR-ID was used on a simplex-hotspot with a specific set of Talkgroups and this ID is switched over to a duplex-hotspot, the admin-pane on the dashboards show all TGs connected to the ID - mixed of simplex and duplex with duplicates.

Solution is to filter on timeslot (0, 1, 2) depending on the duplex-parameter of MMDVM.ini

Hi!

There are a few hardcoded strings, that are not defined as a variable in translation file, so they can't be translated. I would love to see them dynamic, so we can have a fully translated interface.

Example:

WARNING: This changes the password for this admin page AND the "pi-star" SSH account

73

This came up on facebook but I think the post was deleted, anyway if you use a mobile or shrink browser size down so the small screen media query kicks in there is a global rule for all TDs to set x overflow to hidden and this screws up the dropdown and search and makes it very hard to navigate, luckily its a super easy fix, PR incomming.

I am pi-star ver 3.4.17 Dashboard ver 20210224
Later I checked the code and I found the reason, but I didn't understand why it was designed this way.

BI1IZF
73

Very minor cosmetic change required in image source.

current motd has text ... Pi_star logo
...
From your Windows Computer:
Pi-Star Dashboard: http://pi-star-dstar/

From your Apple iPhone, iPad, Macbook, iMac etc.
Pi-Star Dashboard: http://pi-star-dstar.local/

Pi-Star's disk is read-only by default, enable read-write with "rpi-rw".
Pi-Star built by Andy Taylor (MW0MWZ), pi-star-dstar tools all start "pistar-".

cat /etc/hostname
pi-star

configure.php has
...
$currHostname = exec('cat /etc/hostname');
$rollHostname = 'sudo sed -i "s/'.$currHostname.'/'.$newHostnameLower.'/" /etc/hostname';
$rollHosts = 'sudo sed -i "s/'.$currHostname.'/'.$newHostnameLower.'/" /etc/hosts';
$rollMotd = 'sudo sed -i "s/'.$currHostname.'/'.$newHostnameLower.'/" /etc/motd';

Recommend changing /etc/motd text on image source to:

...
From your Windows Computer:
Pi-Star Dashboard: http://pi-star/

From your Apple iPhone, iPad, Macbook, iMac etc.
Pi-Star Dashboard: http://pi-star.local/

Pi-Star's disk is read-only by default, enable read-write with "rpi-rw".
Pi-Star built by Andy Taylor (MW0MWZ), pi-star tools all start "pistar-".

Hi,
I find a bug here , I not suggest to lock the Duplex mode or Simplex mode by the $confHardware type ,because Duplex HS still need SIMPLEX mode , some time for test or just want to act as SIMPLEX hotspot.

If lock Duplex/Simplex mode by code ,it will cause confusion for users, because the values of the two configuration pages (admin/configure.php, expert/mmdvmhost.php) are inconsistent.

`
if ( $confHardware == 'mmdvmvyehat' ) {
$rollModemType = 'sudo sed -i "/modemType=/c\modemType=MMDVM" /etc/dstarrepeater';
$rollRepeaterType1 = 'sudo sed -i "/repeaterType1=/c\repeaterType1=0" /etc/ircddbgateway';
system($rollModemType);
system($rollRepeaterType1);
$configmmdvm['Modem']['Port'] = "/dev/ttyAMA0";
$configmmdvm['General']['Duplex'] = 0;
$configmmdvm['DMR Network']['Slot1'] = 0;
}

  if ( $confHardware == 'mmdvmvyehatdual' ) {
    $rollModemType = 'sudo sed -i "/modemType=/c\\modemType=MMDVM" /etc/dstarrepeater';
    $rollRepeaterType1 = 'sudo sed -i "/repeaterType1=/c\\repeaterType1=0" /etc/ircddbgateway';
    system($rollModemType);
    system($rollRepeaterType1);
    $configmmdvm['Modem']['Port'] = "/dev/ttyAMA0";
    $configmmdvm['General']['Duplex'] = 1;
  }

`

DE BI7JTA

Because we can setup POCSAG in pi-star, it will be a good idea add this info in left side dashboard in MODE and NETWORK STATUS ???

I found a bug with the WiFi Configuration page where it does not cycle the wireless adapter/interface after a change to the WiFi setup has been submitted.

If you add an SSID and PSK to the WiFi Configuration page and click the Save (and connect) button, it will save the changes to wpa_supplicant.conf but the commands used after that to restart the adapter/interface are outdated and silently fail, possibly left over from before the upgrade to Buster.

I have patched this, along with a tiny cosmetic fix to the Configuration page itself, where the one of the boxes was missing a colspan="2" causing the border of the header to not match the rest of the page.

This along with my other Issue report will be linked to the Pull Request I am submitting now.

Hi,

It will be nice add url link in a dashboard for callsign DAPNET

https://hampager.de/#/transmitters/map

like another callsign has url link to QRZ.com

I can see when pi-star (4.1.0-RC7) starts, shows DG-ID 0
How can I change it to my desired DG-ID??
Thank you.

When TGIF_Network is configured in Network 3, any application of the Apply Changes button disables Network 3 . The following code in configure.php, I believe, does this. Would it be possible to have TGIF added as a condition here, or possibly have this block of code removed, as Network 3 could also be used as HBLink., or some other future application.

// Work out if DMR Network 3 should be ON or not
if (empty($_POST['MMDVMModeDMR2YSF']) != TRUE || empty($_POST['MMDVMModeDMR2NXDN']) != TRUE) {
	if (escapeshellcmd($_POST['MMDVMModeDMR2YSF']) == 'ON' || escapeshellcmd($_POST['MMDVMModeDMR2NXDN']) == 'ON') {
		$configdmrgateway['DMR Network 3']['Enabled'] = "1";
	} else {
		$configdmrgateway['DMR Network 3']['Enabled'] = "0";
	}
}

HI,

Is it possible to add an the possibility to the dashboard to remove the "BeaconInterval" paramter in the mmdvm config (dmr part)?
Currently I need to remove it manually in the config file and it reappears after doing a change in the dashboard. I am not yet sure if it also reappears after an update.
This is needed so the the dmr beacons get send based on a network event rather than time based: g4klx/MMDVMHost#529 (comment)

with BeaconInterval=60 set in the mmdvm config:

I: 2021-05-16 06:55:47.546 DMR Roaming Beacons Type: timed
I: 2021-05-16 06:55:47.546 DMR Roaming Beacons Interval: 60s
I: 2021-05-16 06:55:47.546 DMR Roaming Beacons Duration: 3s

with BeaconInterval missing:

I: 2021-05-16 07:01:11.517 DMR Roaming Beacons Type: network
I: 2021-05-16 07:01:11.517 DMR Roaming Beacons Duration: 3s

73, LX1GE

Currently the mode/network statuses (rendered in repeaterinfo.php) are indicated by color only. There are several states possible, but there's no legend explaining the color meaning.
There has been an attempt towards the accessibility made using aria-disabled attribute for disabled modes, but there's an error in the attribute value "true>" instead of just "true". Moreover, it's not a propper usage of that attribute as it's meant to be used for annotating disabled elements which could be otherwise activated. Screenreaders don't announce this attribute for text elements.
My proposal is to show the state in text form ("Enabled", "Disabled", ...) next to the mode or network name, it should be styled as screenreader-only not to be visible all the time; that would help the blind users a lot. This text could also be displayed on mouse hover working as the color explanation legend. This text should probably be localised.
I can implement and pull request solution for this issue if you consider this to be something you are willing to take care about. I just need answers to few questions:

• Shall the states be localised?
• What shall the text representation be? Proposal:
  • background:#0b0; color:#030: "Enabled and running"
  • background:#b00; color:#500: "Enabled and stopped"
  • background:#ff9; color:#030: ???
  • background:#606060; color:#b0b0b0: "Disabled"

Hi,
Since I refuse to have anything to do with Facebook, I report this problem here.
At the first place, many thanks for this nice piece of software, it works like a treat.

It seems that multiple rewrite rules (per section) doesn't work:

Example with a DMR and D-Star enabled hotspot:
(full edit in expert mode)

• Define two PCRewrite rules in a DMR section,
• Turn off D-Star mode
• Just a single PCRewrite rule survive.

Also, if two *Rewrite rules are defined, the DMR GW quick edit will handle only one *Rewrite rule.

Cheers.

Daniel

Hello!

I am using DMRGateway, and have one of my DMR networks configured and enabled for TGIF (running v4.1.2, dashboard 20201005).

In the <host>/admin/ dashboard, I am not seeing any TGIF status or management functions like I am with BM.

Directly accessing <host>/mmdvmhost/tgif_links.php and <host>/mmdvmhost/tgif_manager.phpyields blanks pages, whereas directly accessing <host>/mmdvmhost/bm_manager.php and <host>/mmdvmhost/bm_links.php return the expected results.

I also noticed that the TGIF API URL may be incorrect in:

I tried changing line 61 in tgif_links.php with the API URL of http://tgif.network:5040/api/sessions, which on its own, returns the expected json, but then hitting <host>/mmdvmhost/tgif_links.php still returns nothing.

Cheers.

Hi,

I think the updater should check for updates before stopping services:

Starting update, please wait...
Stopping Services...
Done
Updating DV Binaries...
No updates for /usr/local/bin available
Done
Updating Pi-Star Binaries...
No updates for /usr/local/sbin available
Done
Updating Hostfiles...
Done
Updating Dashboard...
No updates for /var/www/dashboard available
Done
Updating PiStar-Firewall...
Done
Starting Services...
Done

In this case of no updates, the services get stopped unnecessarily. :)

Error from syslog:

dapnetgateway.service[2947]: /usr/local/sbin/dapnetgateway.service: line 33: [: !=: unary operator expected  

Version of pi-star: 3.4.16.
Dashboard: 20180806

System:

root@pistar(ro):log# uname -a
Linux pistar 4.9.35+ #1014 Fri Jun 30 14:34:49 BST 2017 armv6l GNU/Linux

Andy,

I recently experienced an incorrect password problem with the DMR master, but the Network Status for DMR continued to show in green. It would be helpful if the failure to log in, which I eventually found the log files in Admin, Live Logs, were flagged by colouring the Network Status yellow, and perhaps providing an HTML pop-up hint telling the user what the problem was.

Actually, more general use of HTML pop-up hints might reduce support effort.

Thanks,
David

Facebook user "Din Kaftac" reports "TX &infin sec" message in gateway activity display. Looks like the semicolon is missing from the HTML for the infinity symbol.

mmdvmhost/lh.php:line 69 - needs semicolon after "&infin",
i.e. $duration_string = $duration<999 ? round($duration) . "+" : "&infin;";

mmdvmhost/localtx.php:line 66 - needs semicolon after "&infin"
i.e. $duration_string = $duration<999 ? round($duration) . "+" : "&infin;";

ON PI-STar 4.1.7RMB, PI 3+, BM API Modify Static button greyed out - can not add or delete TGs from API in Admin screen.

Steve Fairfield
KI5LXQ

Tags would allow people to see quickly what version of code the repo is on without having to navigate to the versions file.

Hello Andy and contributors!

I'd like to somehow create a page that looks similar to the MMDVM zumspot screen but accessible on my network so I can view it anywhere in the house or on other devices. I understand I can do this with Pi-Star dashboard but it's just too small and not mobile responsive. Most likely because of the way the tables are used.

Perhaps there is already something out there that would allow me to just toss in my pi-star IP and connect via their API?

Thank you for this amazing project. I am enjoying it!

Hello Andy,
When I choose YSF Startup Host: YSF80337 - CN China #1 - W24166/TG46001,
the pi-star php application will save
the error format to the ysfgateway config file, as follow,
Startup CN China #1
the correct :
Startup CN China #1
Pi-Star:3.4.17 / Dashboard: 20200221

Please fix it ,thanks!

DE BI7JTA

Hi Andrew Taylor ,
long time not discuss with you about Pi-Star project, recently I meet a question about compile driver for USB WiFi with Chip RTL8818eus , it can't find your OS Kernel , in Pi-Star 4.1.5 for NanoPi ,the IMG not including this Clip driver download from your pistar.uk/beta [Pi-Star_NanoPi_V4.1.5_25-Jun-2021.zip] .
Can you help me?
This Clip can work perfect in Pi-Star for NanoPi v3.4.17.
The compile guide https://blog.samat.org/2014/12/15/realtek-8188eu-based-wi-fi-adapters-on-the-raspberry-pi/
Thank you very much for you big support ! I post a issue in your github project page. I will full test the Beta version , so that it can enter release downlad.

The RTL8818eus module photo
https://scontent.fhkg4-1.fna.fbcdn.net/v/t39.30808-6/281454525_4965629766867604_1277560414227379849_n.jpg?stp=dst-jpg_p843x403&_nc_cat=100&ccb=1-7&_nc_sid=730e14&_nc_ohc=Wj_i2fRi1fwAX_vZJ-K&_nc_ht=scontent.fhkg4-1.fna&oh=00_AT_BSGa28j80Aw8xT6ct-oa2Zcrrabq8u6POOTJpvXpkIw&oe=628F71CE

73!

I've been setting up Pi-Star_DV_Dash on a self-installed hotspot using the current master version of YSFGateway.

In January 2022 the following commit changed the RemoteCommand syntax to expect a space after the LinkYSF and LinkFCS commands.

g4klx/YSFClients@3af8708

I've worked around this locally by rewriting ysfLinkHost before RemoteCommand is called, but there may be a cleaner way of doing it.