[As Good As Solved!] Watchguard Firebox Arm/Disarm LED
-
It should work fine with any install type.
I've tested it with NanoBSD installs of 1.2.3-release and 2.0Beta.Steve
-
stephenw10.
I been trying to follow this thread as of late. I am a bit confused on WG FB hardware versioning? Will your proggy work on an x550 WG FB?
If so,Ill give it a spin in a couple days and post a report.Thanks,
Barry -
I'm assuming you mean the X550e right?
If so then yes it should work fine. I used the X750e to test it and that's the same box but with a 4 port add on card.
You get all the functions on that box.Steve
Edit: Just to add, if you have an unusual Firebox then it probably won't be detected as a Firebox and the program will just exit. Even if it happens to have the gpio_sel register set in such a way that it is detected as a Firebox the likely result is that nothing will happen. Even if, in a bizarre coincidence, there is something present at the gpio being altered it all gets reset by the bios at boot time so you can just turn it off and on again. ;D
-
Sorry for the delay.
I've tried the program and it seems to work!
[2.0-BETA5][admin@firebox1.domain]/etc/rc.d(15): chmod 0755 WGXepc [2.0-BETA5][admin@firebox1.domain]/etc/rc.d(16): ./WGXepc Found Firebox X-Core WGXepc Version 0.3 17:2:2011 WGXepc can accept two arguments: -f (fan) will return the current fan speed or if followed by a number in hex, 00-FF, will set it. -l (led) will set the arm/disarm to the second argument: red, green, red_flash, green_flash, off Not all functions are supported by all models [2.0-BETA5][admin@firebox1.domain]/etc/rc.d(17): ./WGXepc -l green Found Firebox X-Core [2.0-BETA5][admin@firebox1.domain]/etc/rc.d(18): ./WGXepc -l red Found Firebox X-Core [2.0-BETA5][admin@firebox1.domain]/etc/rc.d(19): ./WGXepc -l red_flash Found Firebox X-Core [2.0-BETA5][admin@firebox1.domain]/etc/rc.d(20): ./WGXepc -l green_flash Found Firebox X-Core [2.0-BETA5][admin@firebox1.domain]/etc/rc.d(21): ./WGXepc -l green Found Firebox X-Core
The commands do what they are supposed to, and response is immediate.
-
Excellent! ;D
-
stephen,
I will have to look at my WG FB. I am thinking mine is not the 'e' suffix? Doesn't the 'e' suffixed WG FB's have the gigE ethernet?
Mine only has 10/100 nics in it. I should know what the model is too?:(.
Won't know for a couple days,when I get back to work. I'll give your prog a spin regardless and report.
I guess,I'm not real clear. Does your prog do the 'native' green to red routine at bootup,when everything is up, ,or is it simply capable of you manually toggling the led to do whatever you want it to?thanks,
Barry -
Hmm, x550 no e?
Be interesting to see if it detects it.
At the moment the program is 'manual' only.
It's easy to put a bash script in /usr/local/etc/rc.d to make it go green at the end of boot.Steve
Edit:
I can't find any mention of the x550 on Watchguard's website, but a lot of the good information is hidden away. The models I haven't yet any gpio information on are:
X-Peak-E; almost certainly the same as the X-Core-E but with more ram, faster CPU and vpn card.
SSL-100; looks like an X550E with different software, maybe an encryption card, 2GB ram!
SSL-500/1000; also same as X550E.
SSL-Core; looks like an X-Core but has different software using the harddisk bay!All the other newer models are still way too valuable to show up on Ebay! ::)
Edit: X-Peak-E confirmed working. Same board as the X-Core-E.
-
stephenw10,
I miscombobulated on the model number. My FB is x500 ( no 'e').
I believe this is/was the first generation 1u cased FB. It has the 1.2GHZ celeron cpu,FYI.
I would guess the mobo is significantly different than the board you were testing on.
The second gen 1u cased FB's were numbered x550e,x750e,etc,I believe the 'e' designates gigE nics?
In three-four days ill down your code and try it on this box and file a report,,,:)
FWIW. This simple box does handle two 3mb up/down connections with about 350 pc's and 1000 users,(possible)
Using squid,squidGuard,Lightsquid, load balance,failover.Take Care,
Barry -
X500 (all the X-Core boxes) have been confirmed working. No off mode for the led for some reason.
Steve
-
Here is the new program incorporating all the new values for the X-Core.
Obviously rename it WGXepc (remove the .png extension). Copy it to your box and chmod it to 0755. Run it! ;DBecause the new memory locations were quite high I felt it would be dangerous to simply write all the values on every box, which what the previous programs did. This new one tries to find out which Firebox model it's running on by reading the gpio_sel register and comparing it with known values. It works fine for me here on the three boxes I've tested it on but I don't have an X-Core and I can imagine that a different bios version might cause detection problems. Deal with that if it happens. Hopefully this might stop people randomly installing it on any box and messing with some important setting! ::)
It seems to run fine on 1.2.3 and 2.0Beta5.
Steve
Steve - what syntax do I use when I copy this to the /tmp dir. to run this? (yes-will rename it first!)
thx
H. -
You can use the upload feature in the web gui to copy it /tmp. However /tmp only exists in memory so you have to move it somewhere else if you want it to survive a reboot.
It's up to you where you put it but /usr/local/bin seems good. Since you are running a full install you shouldn't have any problems with a read-only filesystem.
You can use WinSCP (if you're running Windows) to copy the file directly to /usr/local/bin.Then you can put a script in /usr/local/etc/rc.d that runs on startup.
Here's mine, called WGXepc.sh#!/bin/sh # /usr/local/bin/WGXepc -l green
Steve
Edit: And make sure the file permissions are set to 0755 or it won't run. You can do this from WinSCP or from the command line:
chmod 0755 /usr/local/bin/WGXepc
-
Steve…
Thanks - will set this up now...
H. -
You can use the upload feature in the web gui to copy it /tmp. However /tmp only exists in memory so you have to move it somewhere else if you want it to survive a reboot.
It's up to you where you put it but /usr/local/bin seems good. Since you are running a full install you shouldn't have any problems with a read-only filesystem.
You can use WinSCP (if you're running Windows) to copy the file directly to /usr/local/bin.Then you can put a script in /usr/local/etc/rc.d that runs on startup.
Here's mine, called WGXepc.sh#!/bin/sh # /usr/local/bin/WGXepc -l green
Steve
Edit: And make sure the file permissions are set to 0755 or it won't run. You can do this from WinSCP or from the command line:
chmod 0755 /usr/local/bin/WGXepc
Steve - working great!
-
Good to hear. ;D
Steve
-
I added you LED package and it works perfectly. I got both your LCD package and your ARM/Disarm light package running and they are working great.
Since the lcd backlight is not working correctly, I was wondering if I could open the case up and take a USB light and add it internally so you could see the display. How do you think it would be to do that.
RC -
Steve, just to let you know: your arm/disarm LED script is working fine on my Core X700! Thanks!
pfSense 2.0-RC3 (i386) built on Thu Jul 14 02:02:34 EDT 2011 (nanobsd 4g) running on a 4GB Hitachi microdrive.
-
Thanks for the feedback. ;D
Steve
-
For those who are complete noobs at this like me, I thought I would add two pointers to help you out.
-
In Windows, to use WinSCP, your login should be root, admin never worked for me. root will allow you to change file permissions.
-
You also must give your WGXepc.sh startup script file execute privileges. I used 0755 again like WGXepc.
Don't forget the following post to display different settings:
http://forum.pfsense.org/index.php/topic,7920.msg135626.html#msg135626Thanks stephenw10!
-
-
In Windows, to use WinSCP, your login should be root, admin never worked for me. root will allow you to change file permissions.
Good point, I've become too used to logging in as root. A bad habit.
The reason is that the admin account always shows the menu when you log in via ssh, root does not have to.Steve
-