Watchguard Firebox M400/M500
-
Sorry to bother,
Do you recall the exact settings you changed in order to reduce fan speed? I lowered all of the Fanout values significantly (not much documentation from AMI on Fan out) and they're still screaming on my M500
I also noticed 2 sets of values under Main and then the corresponding heirarchy. Does location matter?
Also, did you try getting a BIOS from Lanner?
-
I found you have to set the values in both places. The whole editing process seems quite flaky to be honest.
I did not try to get a BIOS from Lanner.
Steve
-
Got it, editing the failsafe values seemed to take effect. Got PFsense loaded thanks to your ZFS auto install suggestion for UEFI. It was able to boot on all 3 SATA ports, no USB booting unfortunately, possibly needs UEFI as well.
Now just the green light.
Going from Atom Z525 to a 4160T. Should be able to make use of the 1GB connection I pay for now.
-
Nice. It would be nice to have the status LED come up red at boot but I've found no way to add SIO values to the bios like earlier BIOS types could.
Steve
-
Just returned from some testing with an Intel Xeon E3-1285L v3 3.1GHz
Installed pfSense this way:
- attached the msata SSD to my notebook (Win 10) and set it to offline
- created a new Hyper-V Gen 2 VM, unchecked secure boot and set to open-source VM
- direct attached the ssd as the VM SCSI disk
- installed pfSense from the ISO installer image (VGA) using ZFS Auto install
- shut down the VM
- detached the ssd and installed it to the M400 on SATA3
- power on the M400
- attach a network cable to igb1 (LAN) and to my computer
- log in to the web interface (192.168...)
- change console to Serial
- added "hw.ixgbe.unsupported_sfp=1" to /boot/loader.conf (maybe this is not necessary???)
ISP setup:
- inserted a generic BiDi SFP module from fiberstore (SFP-GE-BX, 1310/1490)
- created necessary VLAN and PPPoE connection
Speedtest to my 1000/1000 ISP:
Result is >900MBit up/down
Checked CPU using "top" command: >96% idle(No additional firewall rules, packages and filtering, just the factory settings)
I think i like the Setup
-
@zanthos said in Watchguard Firebox M400:
added "hw.ixgbe.unsupported_sfp=1" to /boot/loader.conf (maybe this is not necessary???)
It isn't. There are no ix NICs on the m400 only igb. Mostly that's not necessary even if you do have ix NICs, most SFP modules are accepted anyway.
It won't hurt having that set but it will likely be removed from loader.conf at a firmware update. Custom loader variables should be added to /boot/loader.conf.local.Steve
-
After a lot of hacking, bricking my M400, re-flashing via SPI, on and on and on, I finaly managed to unlock the BIOS of my M400 by flashing a self-modified BIOS from Lanner.
If it is allowed, I can upload it here…
-
Ooo fun. What mods did you have to do?
Hmm, I'm pretty sure it's an FW-7585 though. The 7584 has an H81 chipset and the m400 defintely has a C226, like the 7585.
-
Do you think this modification would work for the M440 model as well? I have 2 of these units that I would love to get pfSense working.
-
No, the M440 is completely different. You would need to start out with the UP-2010 BIOS. But as we have found it still won't help you there as the FreeBSD igb driver is, currently, unable to recognise the NIC/PHY combination.
Steve
-
@stephenw10 said in Watchguard Firebox M400:
Ooo fun. What mods did you have to do?
After a lot of trial and error the solution was using UEFI Tool (https://github.com/LongSoft/UEFITool). For whatever reason I had to use an old build which let me replace parts of my file.
I had to extract the BIOS part from the supplied Lanner BIOS and use this to replace the BIOS part of a backup ROM of my unit.
Maybe all the flashing (including Intel ME) finally did something else not covered in what i described above. But as I read some helping docs, Intel ME is stored in the BIOS chip which is a Winbond 25W64FV. So completely erasing this chip and reprogramming via SPI with my modified file finally did the trick.@stephenw10 said in Watchguard Firebox M400:
Hmm, I'm pretty sure it's an FW-7585 though. The 7584 has an H81 chipset and the m400 defintely has a C226, like the 7585.
I have been told by Lanner that the BIOS is exactly the same for both FW 7585 and 7584, even tough they have different chipsets. Probably the C226 is a superset of the H81...
At least it is recognized in the BIOS:
-
@zanthos
Does the unlocked bios allow the fans controls to be adjusted?
I've got the fans dialed down pretty well for now, but still interested to know as I need to move to a Xeon at some point.
Thanks -
Unlocked BIOS overview:
Main:
Advanced:
Advanced - CPU:
Advanced - SATA:
Advanced - USB:
Advanced - Super IO:
Advanced - H/W Monitor:
Advanced - H/W Monitor - Smart Fan:
Advanced - LAN Boot:
Advanced - Serial Console Redirection:
Chipset:
Chipset - Power:
Chipset - System Agent:
Chipset - Memory Configuration:
Boot:
Security:
Exit:
-
@ijay-xtm5 said in Watchguard Firebox M400:
Does the unlocked bios allow the fans controls to be adjusted?
I've got the fans dialed down pretty well for now, but still interested to know as I need to move to a Xeon at some point.
Thanks@ijay-xtm5
You can switch from Auto to Manual mode and define a value. Haven't played with this one tough...@zanthos said in Watchguard Firebox M400:
Advanced - H/W Monitor - Smart Fan:
-
Hmm, can you not change the target value in Smart mode?
-
Could you upload the modified bios along with a detailed step by step instruction on how to flash it over?
-
Hi there
Just managed to unlock (hopefully) everything in this BIOS.
Speedstep is now working
Unfortunately I cannot upload it here. File size limit
Also split files (7z and rar) don't work...Maybe @stephenw10 you can alter this setting?
-
It's better to host it somewhere separately and just link to it IMO. That's what I have always done for BIOS images.
I can put it with the other images on my Google site if you PM me.Do you believe it's flashable directly? You seemed to imply you had done a number of things there.
Steve
-
DISCLAIMER: I don't take any responsibility if you flash using my files. I won't provide help if you brick your device.
(Unbricking is possible using SPI, see below)Here's the BIOS:
https://1drv.ms/f/s!AgeHb7hLRzQ-iAw82hEAiVojSDWJ
@stephenw10 you may copy those files to your webhost. I cannot provide those files forever.Currently it's my Version 5.
There may be things to be enhanced. There may be bugs. Be warned!
How to flash:
a) SPI:
Use your favorite SPI programmer connected to the mainboard.
I used this one:
https://www.ebay.de/itm/CH341A-Series-Chip-SPI-Flash-USB-Programmer-24-EEPROM-BIOS-Writer-25-Neu/273040494657?hash=item3f927b5041:g:U8oAAOSw3wVaaagG:rk:1:pf:0
You will need a programming software. I used "AsProgrammer":
https://github.com/nofeletru/UsbAsp-flash/releases/
b) Software flashing:
Download Rufus here: https://rufus.ie/
Create a bootable FreeDOS Stick or CF Card. FreeDOS is embedded in Rufus. So no need to download.
Maybe your original M400 will not boot from USB. Then create CompactFlash card.
Download "freedos_ext_v5.7z" above and extract it to your just created FreeDOS drive. Overwrite all files!!
Maybe you will need to alter "autoexec.bat" to match your keyboard layout. Current setting is German ("keyb gr"). To have US keyboard layout, you will need "keyb us".
Connect via Serial to your M400. Use a CISCO style cable. Use 9600 8 N 1. I tried higher speeds, didn't work.
I can't help using AFUEFI.exe or AFUDOS.EXE. There are lots of parameters… Maybe someone here knows all the tricks or find help with your favorite Internet search engine.Good luck and please report back!
-
Just to be clear there is real risk doing this. Not until you've felt the regret of your shiny box failing to POST because you updated a firmware to get something you didn't really need in the first place will you understand that! Ask me how I know.
If you have an SPI reader then you can be reasonably confident of being able to recover it eventually if anything does go wrong. But if you don't...
Steve
