2.3 LCDPROC
-
I've got the configuration UI using pfSense's new OO Forms framework, this will allow the configuration to be a bit more flexible and more advanced features to be added, but right now not much has changed besides it hiding some settings if your LCD driver doesn't use them.
Why? Both LCDproc and pfSense are opensource.
Yeah, it's open source, which is cool, and I'm likewise keeping everything I do available to others, but pfSense won't add anyone else's work into their releases/packagemanager unless you agree to pay legal costs if someone sues them over it (like SCO-Linux tried to do with unix/linux). So you don't get paid anything, but you take on extra legal risk, which rubs me the wrong way. I'm not sure whether to be principled - I can see why they do it, and I very much doubt they'd actually ask an innocent contributor to pay up, but the terms of the contract are broad and don't offer any protection to people who have done nothing wrong - only contributed what they legally had the right to etc.
-
Those who have installed the pfSense 2.2 lcdproc into 2.3: there's a pfSense 2.3 issue affecting APU, ALIX and others which causes lcdproc_client.php to fill the log file with divide by zero exceptions if any of your screens display the CPU speed or frequency.
if the command /sbin/sysctl -n dev.cpu.0.freq_levels works on your system then you're not affected. Otherwise, you can either get powerd working on your system, or patch lcdproc_client.php
-
In a vain attempt to make LCDproc as handy as the old N1 Vision, I've added 3 extra screens that can take advantage of 4 row displays.
The screen in the bottom picture is blurred because the LCD is scrolling the device names, but the list is basically identical to the list you see on pfSense's "Status / Traffic Graph" page. Converting LCDproc's config screens to use the new OO Forms framwork means the config can work the same as the Traffic Graph:
Links to the code and ports package are in an earlier message, though I don't think many people have 4-row displays. Everything I wanted from LCDproc is done now, so I don't have any more changes planned.
Edit: Have added a requested i386 port as well
-
Thanks for updating teh package BTW! Love it.
-
CARP screen does not work because of this:
https://redmine.pfsense.org/projects/pfsense/repository/revisions/2a5960b07bb2a40aeaf81423b0c52d5629e87e49
Fix /usr/local/pkg/lcdproc_client.php:
–- /root/lcdproc_client.php 2016-09-06 10:42:24.394680000 +0200
+++ /usr/local/pkg/lcdproc_client.php 2016-09-06 11:29:38.170118000 +0200
@@ -272,8 +272,7 @@
$netmask = $carp['subnet_bits'];
$vhid = $carp['vhid'];
$advskew = $carp['advskew'];- $carp_int = find_carp_interface($ipaddress);
- $status = get_carp_interface_status($carp_int);
- $status = get_carp_interface_status("_vip{$carp['uniqid']}");
switch ($status) {
case "MASTER":
$mastercount++;
-
Is there a working version compatible with 2.3.2- Release?
-
Just installed this in 2.3.2_1. Seems to work fine.
I'm not sure if the previous hard time limit on php processes still applies. You can always start the default client with Shellcmd instead as have always done previously. Or if the service start issues still exist in the SDEC driver.
Steve
-
Seems to start fine with the SDEC driver, with the php client at least.
-
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.
-
Compiled package: pfSense-pkg-LCDproc-0.9.15.txz
I followed these instructions but I can not get it to work on my x750e…. I probably inputted it in the wrong section but the config shows it and it does not list in the Installed PKGs screen.
-
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.
-
Compiled package: pfSense-pkg-LCDproc-0.9.15.txz
I followed these instructions but I can not get it to work on my x750e…. I probably inputted it in the wrong section but the config shows it and it does not list in the Installed PKGs screen.
It will not show up in the installed packages section, as it is not installed that way.
If you can see it on the services screen it is fine.
Once you see it on the services menu enable the service and save. Next go back in and enable the screens you require, and save again. finally start the service from the services menu in diagnostics.
I have found that is is not necessary to manually edit the package file any more, if you do you may end up with two entries for LCDproc.
-
Hi!
So… I have a box with an LCD called AR-LCM02, it's a 2 row with 16 columns. I think this "custom" box was made from the board in this Appliance, an Acrosser AR-R5800: http://www.acrosser.com/products_datasheet.php?gid=362
The LCD controller connector is custom called LCM1 that is recognized by pfSense on the COM2, however I can't get it to work with LCDproc, I'm testing all drivers one at a time, so far no success.
The COM port settings I know because in their manual I can get Port Speed, parity and etc, has anyone else worked with his LCD before?
Manual of the LCD: http://www.acrosser.com/download/manual/LCM02_M10.pdf
-
How do I get this working on my Watchguard XTM 510? I don't see it listed under Packages.
I am using 2.3.2_1
Thanks
-
I believe it's just been added to the snapshots.
So it's probably best to wait until it gets added to 2.3.2, which they will do after more people have tested it.
Or help test it in the snapshot.
If you need it in a non-snapshot build now and want to install it outside of the package manager, there are instructions, but then it won't be managed in the Packages web UI.
-
Ooo, I missed this. Nice. :)
Everyone get to testing! ;)
Steve
-
Closing in on a month now. Has this been added to 2.3.2?
I have a few older WatchGuard boxes that I don't want to upgrade until this is available as an official plugin.
Can anyone confirm?
-
I done some fixes to this package while back to get it working right.. After all that work I hope someone will make package for the _dev version.. that is one I fixed up a bunch. I should start learning how to make a package.. I have phpsysinfo on mine (manual installed) and squidanalyzer (also manually installed)
-
I done some fixes to this package while back to get it working right.. After all that work I hope someone will make package for the _dev version.. that is one I fixed up a bunch.
The new ports package submitted to pfsense was created from the lcdproc-dev version as of August 2016, so contains your work.
I tried to figure out the differences between lcdproc and lcdproc-dev before starting. The -dev version had more work/improvements added to it than the plain package, and it appears the reason for having two versions was because Michele (mdima) created LCDproc-dev to allow early support for LCDProc 0.5.4 without interfering with the existing package. Since this pfsense 2.3 ports package would be using LCDProc 0.5.7 anyway, there didn't seem to be a reason to maintain two versions of the package, so it's built from the _dev package.
-
Closing in on a month now. Has this been added to 2.3.2?
Can anyone confirm?It's in 2.3.3 and 2.4 both of which are pretty stable currently.
Steve
-
Closing in on a month now. Has this been added to 2.3.2?
Can anyone confirm?It's in 2.3.3 and 2.4 both of which are pretty stable currently.
Steve
The man, the myth, and the legend himself! Hey Steve - Been a big fan of your work on the WatchGuard's. I think we've chatted a few times back in the day when I was tinkering around with an X750e. Appreciate all the work you've done for the community!
Not to hijack this thread but, say, I have a pair of new XTM5s (a 505 and a 510 specifically, but hardware is identical anyway - right?). I'm thinking about installing 2.4, probably waiting until it hits RELEASE (which I see we're closing in on it seems, and as you've said, it seems stable). Have you had any luck installing any of the Beta builds of 2.4 on a XTM5 series box? What's the latest pfSense-on-Watchguard thread going nowadays?
Thanks (as always) for pointing me in the right direction!
-
I found and fixed a problem with (some?) Matrix Orbital LCDs, which I first discovered playing with pfsense 2.4 beta described in the thread https://forum.pfsense.org/index.php?topic=124321.0. Following the instructions in this thread for pfsense 2.3, I found the same problem. So I am linking the above thread in case anyone runs into problems with bad characters showing in the display.
