Successful Install on Watchguard Firebox X700!
-
Just managed to install latest build on Firebox x700.
How ever there's that problem with Bootup complete with embedded kernel.
I could also not reach the firebox by webgui.
What I did later was to reinstall using one cpu kernel on my other PC.
After that I enabled console in webgui and switched disks.
I managed to get past Bootup complete at first try on firebox.
NIC's working good and able to access webgui.
How ever after rebooting the device the problem with lockup at Bootup complete still persist when using serial-cable.
I can how ever use the firebox since my NIC's working good with this kernel.Sorry for the confusing post, my native language is not english.
I just wanted to post this so more people can work on getting this version working good on firebox.I have the same issue with 2.0
it always stops at bootup complete. if you need access to the console you need to use ssh. not sure why it stops there but it does :(
1.2.3 boots correctly
also it seems on any of the newer embedded builds the command to change the filesystem to read/write dosen't work for some reason.other than that 2.0 is great! cant wait for the 2.0 book to come out… u know after 2.0 comes out ;D
-
anyone else find that a reboot from the gui does nothing on 2.0?
-
I am pleased to see that this thread is still alive.
I can confirm that i get the same problem other people are getting.
It hangs on "boot complete" and no response from lan or console.
Have tried tried using liveinstall on a HDD and using pfSense-2.0-BETA5-4g-i386-20110215-1909-nanobsd.img.gz on a 8 GB CF Card. But still the same..The only thing i have not tried, and has been mentioned before here, is to do a 1.2.3 nana upgrade to 2.0
Will try when i come home and report back.
-
One of you needs to report this in the 2.0 feedback forum to try and get it solved.
When you say it hangs does the box become completely unresponsive?
The only bit of unusual hardware you have is the Safenet card. have you tried removing it?
I did a fresh install a few days ago on my Xe box with no problems using pfSense-2.0-BETA5-1g-i386-20110209-1815-nanobsd.img.gz.
Steve
-
Stephenw10 is right, the issue that you are having is very odd.
I did a full install on my firebox2 (old x700) a week or so back with no issues.
Got the lcd driver that Stephenw10 put together to work and now, with this help, have got the arm/disarm lcd turned green on both my fireboxes now as well!Both my fireboxes still have their safenet card, but both my installations are full on a (6GB-ish) ide disk that I rescued from laptops in years long past.
-
have got the arm/disarm lcd turned green on both my fireboxes now as well!
How did you do this??
-
See the arm/disarm thread for the whole story. Wait a day or so and I'll have a nice program to do it easily.
Steve
-
See the arm/disarm thread for the whole story. Wait a day or so and I'll have a nice program to do it easily.
Steve
Would love this, and realy appreciate all the time you use on making this happen, as a asked is this was possible loooong time ago in this thread.
-
When you say it hangs does the box become completely unresponsive?
For me yes the box was "dead" not responding to anything.
-
Report
Tried to do an nano 1.2.3 upgrade from the browser to 2.0 beta but browser was just hanging 4 ever… Aborted after 1 1/2 hours and
tried again to write 2.0 beta 4GB nano img to cf card and did remove safenet card before boot up but STILL the same.
hang on "boot complete"#""#¤%
Me want 2.0 Beta!!
but guess the higher powers want otherwise ???
-
Report
Tried to do an nano 1.2.3 upgrade from the browser to 2.0 beta but browser was just hanging 4 ever… Aborted after 1 1/2 hours and
tried again to write 2.0 beta 4GB nano img to cf card and did remove safenet card before boot up but STILL the same.
hang on "boot complete"#""#¤%
Me want 2.0 Beta!!
but guess the higher powers want otherwise ???
it stops at "bootup complete" for me 2 but I can access the web interface and everything else works fine.
now that the new lcd driver is working for rw you should be able to do a fresh 2.0 install and it should prompt you to setup interfaces before "bootup complete"but if that dosen't work for you im not sure I have done this now several times for tests with no issue. do you get bootup complete before assigning interfaces?
-
Does anyone have a definative answer on what type of 512MB RAM sticks to get?
I bought a Kingston KVR100X64C2/512 512MB which works in my main firebox, but an identically spec'd (AFAIK) RAM stick didn't work in my second firebox.
-
X-Core owners!
I need at least one person to test my arm/disarm led program as I don't have an X-Core box.
I have attached the program to a post in the arm/disarm thread here.
Obviously, since I can't test it, you shouldn't be running this on a production box that you can't afford to reboot. Since it is based on some fairly extensive testing by iFloris I'm confident it will work but who knows! :P
Any feedback would be good.Steve
Edit: Has now been tested and confirmed working.
-
I searched the thread for quiet fans, and the one link posted for overclockers UK does not work; does anyone have any model numbers for quiet fans? I'd rather not make holes in the box, so would prefer fans that fit the current formation
For my each of my fireboxes I used three Scythe 40 mm Fan Mini Kaze fans (SY124010L) as replacements for the three fans in the back and a larger Papst 60 mm Fan (612FL) as the cpu cooler.
The Scythes have a different connector, so I had to reuse the original firebox cables.
The Papst really isn't meant to be used the way I'm using them, but I cut out a part in the side of the fan, in effect creating the same airflow as the original firebox cpu fan.
Also, the circumference of the Papst is 5 mm larger than the original fan, which actually helps circulation.Both my fireboxes have been functioning for about six months while being cooled in this fashion with no problems even under somewhat heavy load.
dB pressure per firebox has gone from ±71.3 to ±44.2 after replacing the fans.Thanks just ordered the scythe fans and we'll see how that turns out.
Where did you cut/mod your Papst fan?
Anyone else using a fan without mods for the cpu? -
The 1.2GHz Celeron is about 30W maximum power dissipation is this right?
That's not much more than the processor in the X-e box and nowhere near the 68W on the processor in the X-Peak, both of those have a ducted cooling solution with no fan directly on the cpu.
Might it not be possible to use something similar here?
Maybe even consider a heatpipe arrangement to move hot air directly to the back. Perhaps something from an old laptop?Steve
-
Sigh… the problem with watchdog timeouts is still there with pfsense beta 2.0.
I'm pretty sure that there's a problem with the driver for realtek nics not pfsense itself.
I'm seriously thinking about replacing my firebox with someone else, but I'm not sure what else there is to run for the same amount of investment. -
A different firebox? ;)
The X-Peak or X-Edge boxes don't have Realtek NICs.
The X-Peak actually has all Intel NICs, and three of them are GigE, if you can find one.
It was reported a few pages back that the timeouts were no longer a problem. What is your setup?
Steve
-
I'm running latest beta, configured as a OpenVPN server.
I get watchdog timeouts when connected to the firebox by VPN on a client.
I can ping, do some small surfing, but immediatly when there's some more intensive traffic there's watchdog timeouts.
I've read quite a few threads about the watchdog timeout problem, and some thread said something about different MTU-sizes.
OpenVPN set a MTU-size for the tunnel itself, might be that problem. I tried to set it different sizes, but I would always get watchdog timeouts when running VPN. -
just noticed when updating to rc1 that it now says on the dashboard
"Hardware crypto SafeNet SafeXcel-1141 rng des/3des aes md5 sha1 null"
does that mean the safenet card now works?
-
It has always been supported as far as I know.
Just that now it is reported.Steve
Edit: For a long while anyway! And I should say support for the card hasn't changed, there are many reports of people failing to make it work in this thread but technically everything needed is there.
