[As Good As Solved!] Watchguard Firebox Arm/Disarm LED
-
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 greenSteve
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 greenSteve
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/WGXepcSteve - 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
-
-
Yep!
I am a new pfsense user and also have a firebox x700. Just did the led fix and its working great. Running 4GB CF card with pfsense 2.0.1-Release.
Thanks.
-
Another firebox resurrected. ;D
With any luck we might be able to get this included with the lcd driver soon. Stuck on some bugs at the moment though. I'll post here when things are closer to working.Steve
-
Another firebox resurrected. ;D
With any luck we might be able to get this included with the lcd driver soon. Stuck on some bugs at the moment though. I'll post here when things are closer to working.Steve
So there are bugs…. ;D Good to know, because my Light will not turn/change color no mater what i do, by script or by manual running the prog, its a no go.
When it did not work, i just ignored it and accepted that it would not work.
But now that you mention that there might be bugs in it i want to give it a go and see if i can get it to work.
So any pointer would be helpful to where to start looking....I am running pfSense-2.0.1-RELEASE-2g-i386-nanobsd.img.gz and the program runs like it should, no errors or feedback when i run it and nothing happens.
So if you think this could be a "bug" let me know and i will give you all the info you need.. ;)
-
The bugs I mentioned are in the LCD driver/package not WGXepc. Since lcdproc includes code for associated leds we hoped to eventually have the leds controllable through the lcd driver.
WGXepc should be working for any firebox however there are some models that are untested.
Which box is not working? What happens when you run the program?Steve
-
-
Hmm, interesting.
The code is absolutely terrible! :D I'm embarrased to release the source. So I could have easily overlooked some input condition that could causer that. However it should either operate correctly or spit out a message showing the correct syntax. Then it tries to recognise which box you have and either sets the led colour or displays a message saying 'you have an unknown box' or something similar.
Anyway the correct syntax is:WGXepc -l greenTry that.
Steve
