2.3 LCDPROC

icest0rm

If people want something to play with, here's my start at a pfsense 2.3 package. It's still the old UI, no Bootstrap changes yet.

Installation commands

source

Compiled package: pfSense-pkg-LCDproc-0.9.15.txz

anyone knows if the package could work also in OPNSense?

chpalmer

@icest0rm:

@treer:

If people want something to play with, here's my start at a pfsense 2.3 package. It's still the old UI, no Bootstrap changes yet.

Installation commands

source

Compiled package: pfSense-pkg-LCDproc-0.9.15.txz

anyone knows if the package could work also in OPNSense?

No Clue. You would have to ask them.

revengineer

There is a bug with displaying load averages but I cannot make sense of the relevant php code below. The load averages are good until the 1-day uptime boundary is reached. So for uptime

1:00AM up 7 mins, 2 users, load averages: 0.23, 0.26, 0.17

the load average is properly displayed as "0.23, 0.26, 0.17". But for

8:24PM up 1 day, 1:02, 1 user, load averages: 0.54, 0.40, 0.25

the text shown is "averages: 0.54, 0.40,". The php code seems to account for the string "day" in the output, but I cannot account for the array indices in the code. Maybe someone can explain and propose a fix.

Thank you.

UPDATE: Ok, I looks like the double spacing throws the array indexing off. I am not sure if the double space before "1:02" turns into a single space when the uptime is "10:02". This is important for interpreting the indices.


function get_loadavg_stats() {
	exec("/usr/bin/uptime", $output, $ret);
	if (stristr($output[0], "day")) {
		$temp = explode(" ", $output[0]);
		$status = "$temp[11] $temp[12] $temp[13]";
	} else {
		$temp = explode(" ", $output[0]);
		$status = "$temp[10] $temp[11] $temp[12]";
	}
	return($status);
}

revengineer

I fixed the issue with the Load Averages posted above. Replacing the following function properly handles the day boundary:

function get_loadavg_stats() {
	exec("/usr/bin/uptime", $output, $ret);
	if (stristr($output[0], "day")) {
		$temp = preg_split("/ /", $output[0], -1, PREG_SPLIT_NO_EMPTY);
		$status = "$temp[9] $temp[10] $temp[11]";
	} else {
		$temp = preg_split("/ /", $output[0], -1, PREG_SPLIT_NO_EMPTY);
		$status = "$temp[8] $temp[9] $temp[10]";
	}
	return($status);
}

n0s3

Hey all,
i am unsure if i should open a new thread, so i post here:
i have an old intranator 2500 case with a display.
As i understand LCDproc (http://lcdproc.omnipotent.net/hardware.php3) i need driver i2500VFD.
But i cant find it in the driver dropdown of the LCDproc package.

my "usbconfig" shows this:

[ugen0.5: <vfd display="" intra2net="" ag=""> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (0mA)
[/code]

[b]any idea how to control that old display?[/b]

regards
n0s3</vfd>

revengineer

@n0s3:

Hey all,
i am unsure if i should open a new thread, so i post here:
i have an old intranator 2500 case with a display.
As i understand LCDproc (http://lcdproc.omnipotent.net/hardware.php3) i need driver i2500VFD.
But i cant find it in the driver dropdown of the LCDproc package.

my "usbconfig" shows this:

[ugen0.5: <vfd display="" intra2net="" ag=""> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (0mA)
[/code]

[b]any idea how to control that old display?[/b]

regards
n0s3

As it looks, your LCD is supported by the demon which is the most important thing. It has likely not been added to the pfSense package because it is a one off and no one had a means to test the implementation. This will now be your task.  :)

You will need to add the option to the web interface in /usr/local/www/packages/lcdproc/lcdproc.php. The you need to configure the display in /usr/local/pkg/lcdproc.inc, althought the LCDproc manaul does not show any specific cofnig commands for this display, so the  may not be needed.

Be mindful that he ugen0.5 port may be misleading. I got similar output on my firewall but had to choose /dev/cuaU0 as the device. So there are several knobs to turn and it took me a few hours to get my display working.

If you do get it to work, I suggest you create a new post with the display name in the title, so that others can find the solution more easily. If you post the changes, treer may be able to include it in the package.

Good luck!</vfd>

chpalmer

Anyone else having problems with this package lately? Since upgrading a handful of boxes to both 2.3 snaps and 2.4 beta the boxes are only showing

[[ LCDproc Server ]] on the display..
Cli:0 Scr:0

All various Watchguard boxes.

revengineer

Everything is fine here, the package has been working perfectly for over a week now on pfSense 2.3.2_1. Could it be that the com port has changed?

chpalmer

@revengineer:

Everything is fine here, the package has been working perfectly for over a week now on pfSense 2.3.2_1. Could it be that the com port has changed?

We have changed nothing other than-

My test unit here is on 2.4beta snap which Ive updated roughly once a week. I don't always look but know it was working mid January.

My couterpart decided to update his home box yesterday (2-06-17) to the latest snap and discovered his LCD followed suit to mine.. Was working before.

I have some friends Ive set up (X-e model) that I upgraded from 2.27 (yes they were around) snap to 2.3 snap which is now doing the same. Seems like the latest LCDproc is the reason but I want to be sure..

revengineer

Looking at the history of this package there seem to have been incompatibilities with pfSense arising with changes in the LCDproc binary. That was before I joined the pfSense club. Have you tried reinstalling the package via the GUI and following the instructions in treers post linked below?

https://forum.pfsense.org/index.php?topic=110177.msg647262#msg647262

chpalmer

Yep- tried re-installing on all the boxes.

Getting this now also- syntax error, unexpected 'return' (T_RETURN) in /usr/local/pkg/lcdproc_client.php on line 109 on the dashboard.

treer

Getting this now also- syntax error, unexpected 'return' (T_RETURN) in /usr/local/pkg/lcdproc_client.php on line 109 on the dashboard.

Ahh! That's the clue that was needed. Looks like some '+' symbols somehow got into the code when I created a pull request.

Lines 107, 108, and 109 should not start with +

You could edit them out yourself (e.g. Diagnostics -> Edit File), but I'll submit a fix this weekend, if someone doesn't do it faster.

chpalmer

Thanks! Fixed it. :)

revengineer

Yup, the manual install does not have this problem, which is why it was working fine for me.

Smoothrunnings

Where am I supposed to put these lines of code into the config.xml file?

<menu>
<name>LCDproc</name>
<tooltiptext>Set LCDproc settings such as display driver and COM port.</tooltiptext>
Services
<url>/packages/lcdproc/lcdproc.php</url>
</menu>

<service><name>lcdproc</name>
<rcfile>lcdproc.sh</rcfile>
<executable>LCDd</executable></service>

When I look under <installedpackages>at what's already there, none of the code has

<menu>or <service>, they only say <package>, and there is a package option already there for LCDPRoc.

Is it possible the installation information on the site in this thread it out of date or is it just not clearly written?

Thanks in advance,</package></service> </menu></installedpackages>

Smoothrunnings

@Smoothrunnings:

Where am I supposed to put these lines of code into the config.xml file?

<menu>
<name>LCDproc</name>
<tooltiptext>Set LCDproc settings such as display driver and COM port.</tooltiptext>
Services
<url>/packages/lcdproc/lcdproc.php</url>
</menu>

<service><name>lcdproc</name>
<rcfile>lcdproc.sh</rcfile>
<executable>LCDd</executable></service>

When I look under <installedpackages>at what's already there, none of the code has

<menu>or <service>, they only say <package>, and there is a package option already there for LCDPRoc.

Is it possible the installation information on the site in this thread it out of date or is it just not clearly written?

Thanks in advance,</package></service> </menu></installedpackages>

Actually looking through the config.xml file the code is already there, just noticed it after posting the message above, the issue is I don't see it in installed applications, so there is no way to know when I need to patch it, or is there?

Thanks and advance,

chpalmer

@Smoothrunnings:

When I look under <installedpackages>at what's already there, none of the code has

<menu>or <service>, they only say <package>, and there is a package option already there for LCDPRoc.

Actually looking through the config.xml file the code is already there, just noticed it after posting the message above, the issue is I don't see it in installed applications, so there is no way to know when I need to patch it, or is there?

Thanks and advance,</package></service> </menu></installedpackages>

Arn't you using a snapshot of 2.3.3?

Smoothrunnings

@chpalmer:

@Smoothrunnings:

When I look under <installedpackages>at what's already there, none of the code has

<menu>or <service>, they only say <package>, and there is a package option already there for LCDPRoc.

Actually looking through the config.xml file the code is already there, just noticed it after posting the message above, the issue is I don't see it in installed applications, so there is no way to know when I need to patch it, or is there?

Thanks and advance,</package></service> </menu></installedpackages>

Arn't you using a snapshot of 2.3.3?

Nope. I blew away my pfSense and went back to the stable OS updated of course. I was having problems with HAProxy under the Snapshot dev 2.3.3, so I followed the instruction to install LCDPro and looked through the config.xml and noticed it had installed the lines in the recent installer for the LCDPro under <installedpackages>. I restarted the firewall but only see HAProxy under my Installed Packages.

Thanks and advance,</installedpackages>

doktornotor

There is no reasonable to way to install the menu entry without installing the package. Not really sure what you are trying there. If you cannot install the package properly (there are no issues with haproxy and 2.3.3 except PEBKAC ones), then bookmark the page and move on.

stephenw10

Manually installing will never show the package as installed in the package manager.

However the lcdproc package is in 2.3.3 and 2.4 now so the easiest thing is to just use one of them. Or wait for 2.3.3 to be released which should be happening 'real soon now' assuming no large bug discoveries.

Steve