Watchguard Firebox X Peak platform
-
You have to call it from the right directory or use the absolute path:
/usr/local/bin/mbmon -IThe -I causes mbmon to use only the ISA bus sensors, which are the only ones available on the Firebox under FreeBSD.
Steve
-
/usr/local/bin/mbmon -IThat did it! Thanks…
# /usr/local/bin/mbmon Temp.= 66.0, 127.0, 85.0; Rot.= 0, 4440, 0 Vcore = 1.46, 3.39; Volt. = 3.31, 4.87, 11.80, -3.06, -6.14Nice and warm ;)
-
Ooo, that is warm. :o
You only seem to have one fan?Steve
-
Yeah, this is an x700 firebox. Has one fan direct on the CPU, then three tiny fans on the back panel. Having in the loft probably doesn't help either….
-
I just got a hard drive caddy that fits the X peak perfectly.
It's nice and snug in the plastic rails and has a little handle on the back to pull it out without opening the case. ;D
It's from a laptop, an ECS-320. In the UK it was sold rebadged as an Advent 7081 and also Patriot 2005.
Possible models that used the same caddy are Advent 7086, 7094, and ECS 321. Make sure you get the adapter with it. ;)Steve
-
Hey!
Thanks so much for your great work on these boxes. I just got an x8000 off fleabay and tossed in your BIOS checking image. Looks like I've got the same version as you…I just put in an order for some new fans for this thing (it literally sounds like a small jet starting up) which will hopefully quiet it down.
-
While doing some throughput testing on my other Firebox I hit the limits of the my X-peak.
I'm using TTCP to measure network throughput/bandwidth. It's a useful tool since it has windows and freebsd versions and they're compatible so you can have any box at either end of your test setup.
I have used my X-Peak as the receive end connected to one of the gigabit ports. I found I was maxing out my one section of gigabit network at around 360Mbps. I had blamed that on bad network cards and a long length of cat5e carelessly routed past mains cable (who knew when I installed it 10 years ago!).
However some testing showed that the cpu was pinned at 100%. Bear in mind that this box is receiving the data only so actual throughput would be lower.One interface 365Mbps in 19Mbps out = 100% cpu.
However! :P I am using an underclocked replacement cpu running at 1.2GHz. Scaling that may give 850Mbps with the original 2.8GHz cpu, assuming nothing else is limiting peformance. I might have to try that pin mod after all.
Steve
-
Does anyone have a source for the WG FIrebox X8000 hard drive caddy in the United States?
-
First of all… Thanks for the great infos till now.
It works great for me at my X8510e-F --> LCD/LED driver works like a charme.
At which time you plan a watchguard package for 2.0?But now....
I have a problem to get access to the bios (X8000) --> same biosversion like your box.
I flashed the bios with the help of your CF-image and of course with the /cc switch :)
biosid.com says it's ok --> your new "Steves" bios-messages shows up.
But still no boot info shows up at start in the consolewindow.There are still any secret steps to show it up? ???
BTW: The J3 connector on the PSU-Board is for a 12V fan.
Alex
-
At which time you plan a watchguard package for 2.0?
When I learn some proper programming skills. ::)
But still no boot info shows up at start in the consolewindow.
There are still any secret steps to show it up? ???
I take it you're not using a keyboard on the ps/2 connector?
The 'console redirect' function in the bios is very buggy.
To see anything using just the serial console you have to press keys. I don't know why, it should just show the POST but it doesn't.
Start pressing tab and enter as soon as you power on the box and keep pressing them until you see something.
If you really want to change something in the bios you'll need to hook up a keyboard directly.How do you know that about J3?
Steve
-
Ok. I will give it a try tomorrow.
The greenwire is marked with "ON/OFF" –> have a look at the atx-power-connector.
The PSU is a standard one, but without a case.
And so imho is it the connector for the case fan. ;)
It delivers 12V and GROUND.Alex
-
It works! :)
Phoenix - AwardBIOS v6.00PG, An Energy Star Ally Copyright (C) 1984-2003, Phoenix Technologies, LTD Modified by Steve for 115200 console. Main Processor : Intel(R) Pentium(R) 4 CPU 2.80GHz(133x21.0) Memory Testing : 524288K OK CPU Brand Name : Intel(R) Pentium(R) 4 CPU 2.80GHz Memory Frequency For DDR333 (Dual Channel Mode Enabled) Primary Master : SanDisk SDCFB-128 Vdi 1.24 Primary Slave : None Secondary Master : None Secondary Slave : FUJITSU MHT2060BH 0000104A Phoenix Technologies, LTD System Configurations +==============================================================================+ | CPU Type : Intel(R) Pentium(R) 4 CPU Base Memory : 640K | | CPU ID/ucod: 0F29/17 Extended Memory : 523264K | | CPU Clock : 2.80GHz Cache Memory : 512K | |------------------------------------------------------------------------------| | Diskette Drive A : None Display Type : MONO | | Diskette Drive B : None Serial Port(s) : 3F8 2F8 | | Pri. Master Disk : LRG,PIO 4, 128MB Parallel Port(s) : 378 | | Pri. Slave Disk : None DDR at Bank(s) : 0 2 | | Sec. Master Disk : None | | Sec. Slave Disk : LRG,ATA 100,59599MB | +==============================================================================+ PCI device listing ... Bus No. Device No. Func No. Vendor/Device Class Device Class IRQ -------------------------------------------------------------------------------- 0 29 0 8086 25A9 0C03 USB 1.0/1.1 UHCI Cntrlr 10 0 29 1 8086 25AA 0C03 USB 1.0/1.1 UHCI Cntrlr 5 0 29 4 8086 25AB 0880 Base Sys. Peripherals NA 0 29 5 8086 25AC 0800 I/O(X) APIC Cntrlr NA 0 31 2 8086 25A3 0101 IDE CntrlrCI Cntrlr 14 0 31 3 8086 25A4 0C05 SMBus Cntrlr 12 2 1 0 8086 1075 0200 Network Cntrlr 11 3 13 0 16AE 000A 1000 En/Decryption Cntrlr 9 3 14 0 8086 1079 0200 Network Cntrlr 9 3 14 1 8086 1079 0200 Network Cntrlr 9 4 9 0 8086 1209 0200 Network Cntrlr 5 4 10 0 8086 1209 0200 Network Cntrlr 11 4 11 0 8086 1209 0200 Network Cntrlr 12 4 12 0 8086 1209 0200 Network Cntrlr 10 4 13 0 8086 1209 0200 Network Cntrlr 5 4 14 0 8086 1209 0200 Network Cntrlr 11 4 15 0 8086 1209 0200 Network Cntrlr 12 Updating ESCD ... Success Building DMI Pool ............................ SuccessAdditionaly I've soldered in the two SATA-Ports.
Both of them are working!
The Sec. Slave Disk from the postscreen is an SATA 2,5" HDD.Alex
-
Nice work! :)
Does it boot from SATA? Did you have to solder any other components or just the connectors?
Looking good. ;D
Steve
-
No other components. Just the connectors.
Trying to boot from is the next step.
Stay tuned….Alex
-
Does anyone know the name of the connector that serves as a conversion between the 2.5 44 pin interface to the swap able caddy interface. It has to have a name.
-
After winning my X8000 on ebay I did some searching for the SafeXcel 1841 and found this PDF. I think someone might have already posted it. In the PDF SafeNet states they have FreeBSD OS support. I.E. They have drivers for FreeBSD. I was a little shocked that it was not covered under the safe(4) driver. If I don't hear from them in a few more days I am going to send another e-mail asking for a update. It looks like OpenBSD has the documentation for the SafeNet 1840 chip. http://www.openbsd.org/crypto.html
http://www.safenet-inc.com/WorkArea/DownloadAsset.aspx?id=8589938686
-
I have never found a name for the adapter, although I'm sure the interface has a name.
I found it by using Google Image search. ::)I have spent far too much time Googling the Safenet 1841, don't let me put you off though. I believe that Safenet will only allow you access to their driver support if you've bought their SDK at vast expense. You probably have to sign a NDA. The resulting driver wouldn't be free so unlikely to make it into FreeBSD. OpenBSD have had that message on their crypto page for a long time (at least 2006) which is a shame. I guess there's a more drive to support newer hardware and the 1841 is now quite old. It's way more powerful than the 1141 and 1171 supported by safe(4) though.
Steve
-
I noticed that someone in another thread had said the connector was the same as a "Dell Inspiron 5000 5000E HDD Adapter". So I ordered one to see if it would work out. I guess I'll have to figure out a way of making some rails for the drive.
I'm hoping that safenet will give me a binary blob. I might also ping a openbsd dev I know to see if they know the status of the safenet 1841 driver. I'll have to see how they respond when I send them a follow up e-mail on June 6th.
-
Has anyone has any watchdog timing errors pop up on 2.0 RC2? or any other version? I know some of the x700 people complained about them. It looks like all the checksum offloading is turn on currently.
-
If you can get any sort of driver working it would be great. :)
It's a powerful and relatively expensive (for the time) chip and at the moment it just sits there consuming 3W and getting hot.I've never had any problem with any of the interfaces on the X-peak. They are all Intel so I wouldn't expect to. The X-core has Realtek NICs and they are far more troublesome, especially the 10/100 type.
Steve
