2.3 LCDPROC
-
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.
-
I do not see it in 2.3. am i missing something?
-
I do not see it in 2.3. am i missing something?
It's not in the standard packages. You need to manually install using the instructions linked above in this thread. The procedure is well documented and worked flawlessly for me.
-
I do not see it in 2.3. am i missing something?
Only the snapshots for 2.3.3 and 2.4 have it as a "standard" package now. Otherwise as mentioned- its a manual install.
-
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
anyone knows if the package could work also in OPNSense?
-
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
anyone knows if the package could work also in OPNSense?
No Clue. You would have to ask them.
-
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); } -
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); } -
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> -
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> -
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:0All various Watchguard boxes.
-
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?
