Successful Install on Watchguard Firebox X700!
-
Yes I've seen that. I'm fairly sure that's forum user Brak, but I could be wrong.
Anyway he seems to selling at a very reasonable price so good luck to him. :)What he doesn't mention is that using the old lcdproc tar ball and the WGXepc program you have to reload all that stuff after each firmware update which is pretty tedious. Using a proper package will mean it isn't lost.
His lcdexec (the custom menus) implementation is pretty sweet though. Hopefully he might contribute it to the community sometime.Steve
-
Indeed that is me, I do hope no one finds my prices too high, as I'm more than willing to ship internationally (that's my main business since not many used fireboxes have international willing sellers.) The units are also completely upgraded with RAM and CPUs, plus I replace any super-loud fans (I can tell when I get a loud firebox unit just by the change in pitch in my server room through the wall, and that place has 10+ servers humming away). I think that's a fair price considering I'm more than willing to go out of my way to help people with their units or configuration after they buy. As for the updates, I make new images available to my buyers so they can have a seamless upgrade experience if they want it. I wish I was good enough to make my own update server, but I haven't yet been able to figure out making nanobsd update images or how they even work.
I'm doing to this to work on building enough money to start making real/new firewall appliances with pfSense running on them (and help pay for college, lol). Working on finding a good manufacturer right now.
As for the menu, I will be releasing it publicly and also moving my refurb units over once I can iron out why on earth it doesn't work with the real LCDProc/LCDProc-dev package. Either it never starts, or eventually crashes the whole unit or LCDProc… : / I do actually have an easy to use automatic installer for the just the LCD/LED stuff incase the reimage isn't a viable option, but I've had issue with it working consistently.
I actually have an even cooler version of the menu that will be able to let you change interface IPs, reset the DHCP servers to work on them, and change a few other settings. That said, until I can keep the units from locking up which is completely unacceptable, I can't really go too far with it. Stephen, I know you mentioned hard locks when using the LCDProc-Dev package in the other thread, do you think maybe we're seeing the same issue?
Also, if anyone knows anything... I guess I see so many fireboxes thru my door, I see hardware variances that no one else have ever noticed... But what's up with the fireboxes with the always on but dim LED back-light? Software can't control it, and while it does illuminate the screen, it's no where near as bright as a usual unit. Also, there is a variation with only 2 case fans. I know these aren't DIY removals of bad fans since the box is still factory sealed, and there isn't even a 3rd fan header off the PSU... Just a strange difference I noticed.
-
I have seen the 2 fan & smaller whinny CPU fan vs. the 3 fan and bigger CPU fan, but less whinny noise. The yellow and black pair cables for the fans are consistent with the # of fans, you're right. The 2 fan box also had the top lid with a WG emblem wedged on it.
Where can I find the LCDproc that gives me at least the menu with the options, I really don't care about monitoring the CPU or traffic on a 2x20, would rather see that on pfsense' webguir.
-
I've just noticed that my serial console has also stopped working since upgrading from 1.2.3 to 2.0.1 (i386 Nano install).
Is the workaround still the only fix?
If so, would this be the easiest way?
1. Copy the http://www.cps-texas.com/serialbandaid.sh file to my pfSense (not to /tmp).
2. Install the Shellcmd Package and add in the serialbandaid.sh command.
3. Re-boot
-
Yes that should work, though I've not tried it myself.
My X-core box is out of action and it looks permanent. :(
I've been putting tiny scripts like that in /conf simply because that folder does not get written over during a firmware upgrade. Coupled with using the ShellCMD package the complete solution should survive a firmware update.Steve
-
There seems to be a lot of variations of installing these.. could someone write a new install process for CF and HD so that we know what has to be done.. I have an X500 I am working on. I am also looking at getting an x550e.
JB
-
I'm in same boat. Gonna be doing an x500 hdd install soon.
For example, with a fresh install of 2.0.1 Can I still expect to get serial console automatically with embedded kernel? Or will I have to copy the serialband.sh file mentioned above? -
I'm in same boat. Gonna be doing an x500 hdd install soon.
For example, with a fresh install of 2.0.1 Can I still expect to get serial console automatically with embedded kernel? Or will I have to copy the serialband.sh file mentioned above?You'll still need the serial fix in my experience.
-
SerialBandAid.sh is the 1st thing I do when installing pfSense on Firebox X-core series. I messed up 2 installs to where I couldn't longin the box at all, and console would have saved me in these 2 occasions, so that's my #1 step! Thanks to the author!
-
Well I have my firebox x500 up and running. I found one of the easiest things to do was install 1.2.3 then use the webconfig to upgrade to 2.0.1 and then install the lcd-proc.
Only thing left on my list is the LED fix.
JB
-
Search for WGXepc app. For x500 use -l green or -l red
(WGXepc -l green_flash and WGXepc -l red_flash are too fast for my taste, you would have to use writeio for slow flashing) -
I just resurrected my X-Core box with tape and glue.
Last time I had one running it was with 1.2.3 and the serial port worked fine. Now I find with 2.0.1 it doesn't work after the bootup has finished as described by many others.
I have found this to be completely effective.
Add the following lines to /boot/loader.conf.local create the file if it doesn't exist. This file is copied across firmware updates.console="comconsole" comconsole_speed="115200"This will, as you probably guessed, change your console speed to 115200 so remember to change your settings. Putting 9600 in for speed doesn't work! No idea why not. :-\
Steve
-
Thanks for posting this. 9600 worked for me, but I switched mine to 115200 as well. It helped avoid the BSOD on my adapter.
-
No problem. :)
Interesting that 9600 worked for you. I've been playing around with 2.1, I could have got confused.
The new WGXepc has a choice of flashing speed for the X-Core box, might be more to your liking. ;)Steve
-
Cool! Got a link to it?
-
Yes, sorry, it's here.
Steve
-
Hey just to let you all know I picked up a cheap firebox x700 and got 2.0.1 running on it. I would like to thank stephen and the other members for helpful forum posts. I've created a tutorial on how I did it. http://simplyaccomplished.com/tutorials/firebox/index.php?view=1
-
Yes, sorry, it's here.
Steve
Got it! Thanks again! :) Very happy with my FB, only thing is I had to remove LCDd (lcdproc) it was crashing the webgui and the sshd but it kept working, and without it the lcd light stays on all the time so I unplugged the lcd. Any way of turning the light off?
-
I take it you were using the lcdproc-dev package? Which version? 0.93 has eliminated most of the bugs, including the one that locked you out of the web and ssh interfaces. Still a bit of tweaking to go though.
You can fall back to the old manually installed driver here.
Alternatively you can manually turn off the back light bysetting bit 1 at 0x379 to 0like this.Steve
Edit: Wrong data! The backlight is controlled by the strobe pin on the control port which is bit 1 at 0x37a. But it's inverted so to turn off the backlight you need to set it to 1!
[2.0.1-RELEASE][root@x-core.localdomain]/root(9): /conf/writeio 0x037a 0x01 Setting 37a to 1 -
I just resurrected my X-Core box with tape and glue.
Last time I had one running it was with 1.2.3 and the serial port worked fine. Now I find with 2.0.1 it doesn't work after the bootup has finished as described by many others.
I have found this to be completely effective.
Add the following lines to /boot/loader.conf.local create the file if it doesn't exist. This file is copied across firmware updates.console="comconsole" comconsole_speed="115200"This will, as you probably guessed, change your console speed to 115200 so remember to change your settings. Putting 9600 in for speed doesn't work! No idea why not. :-\
Steve
Many thanks Steve, I can confirm that this fails for me on 9600 but works on 115200.
