Watchguard Firebox M400/M500
-
@zanthos Current programmer: CH341 the firewall is without powercord, i verify the pin but not function
ID(9F): FFFFFF(Unknown)
ID(90): FFFF(Unknown)
ID(AB): FF(Unknown)
ID(15): FFFF(Unknown)sigh sigh
-
Hi, I have a problem that I can't solve. I flashed the latest unlocked bios version and so far so good. The system works, but when I reboot the system does not start and tells me to insert a boot disk. In reality if I enter the bios and modify the boot with the primary disk and save the system it starts, but if I reboot the problem still happens. I noticed that it saves all settings except the boot order. Did it happen to anyone? Can it be the battery of the bios? Other ideas? Thanks everyone for the help
-
It could be the battery yes. What are you trying to boot from? Is that not enabled by default anyway?
Do you have anything else connected that it might be trying to boot from incorrectly?
Steve
-
@stephenw10 Thanks Steve, I installed pfsense on an ssd connected to the sata port. I don't have any other peripherals like usb or connected disks.
For the battery I have to try to replace it, the strange thing is that it does not save me the settings related to the boot, the rest is.
For example I have changed fan speed and it works. With the original bios never had problems.
Did you have problems?
Gabriele -
Nope, never saw an issue like that. The only quirk I've seen was the 4160 CPU will not reboot. Still running from CF though.
Do you have auto detect set or something that might be reconfiguring the drives at each boot maybe?
What does it try to boot from and fail?
Steve
-
@stephenw10 My configuration is:
- original cpu
- 16 GB ram
- boot from ssd
I don't have any extra peripherals.
Tomorrow I will try to replace the battery so I see if it fixes it.
Updates follow
Gabriele
-
Which BIOS did you use?
-
@stephenw10 I use the latest version modified from zanthos v 6.7
-
I noticed, however, that sometimes when I enter the bios it does not always allow me to change the boot order of the disk. it is strange that he gives me the same disk with uefi and not uefi boot which then, even if it does not keep in memory
-
An update, I replaced the bios battery and now everything works. It was probably almost empty and occasionally caused problems.
-
Datapoint:
Tried CT2K204864BD160B (2x16gb) UDIMM unbuffered and it did not work (constant beeps with 1 or 2 sticks) Not sure if ECC or 1.5v is a requirement or that 8gb/stick may be the max despite the lanner manual stating 32gb. I am using the stock Watchguard BIOS so I may try Zanthos's to see if I get different results.
-
Has anyone thought to do a YT video of how to get PFSense into an M400/M500 firebox yet so that others can benefit as the price of these units start to come down?
Thanks,
-
I haven't seen one. It's pretty easy though. Install to CF in something else and swap it in. Or write the installer to CF and install to SSD if you've installed one.
Steve
-
@stephenw10 And what about flashing the bios that I have seen in this thread?
Thanks,
-
That's optional. If you do that you can just boot from USB and install as any standard appliance.
Steve
-
Hi all! I'm excited to say that I recently acquired 2 Firebox M400s to tinker around with. I'll probably end up leaving the BIOS alone on them, but I do have a few hardware questions:
1-CPU: From what I've seen in this thread, it looks like the i3-4130 is the way to go as far as a plug and play CPU. If anyone has other thoughts here, let me know! (I have not ordered CPUs yet for these)
2-RAM: I've seen some debate here about whether or not a 16GB RAM configuration will work. Has anyone had success running 16GB on the stock BIOS? Or should I just stick with running 8GB in a 2x4GB configuration?
3-Storage: What are everyone's opinions here? (Pros and Cons?) I'm debating about getting a new CF card to install on or if I should just remove the CF card all together and drop an SSD in. If you're using a CF card, what size are you using? I've seen them from 4GB all the way up to 64GB. (I've seen pfsense successfully installed on a 16GB card, but wasn't sure if that was the only size you could use for this application or if any size would work.)
My final question (for now anyways, because I'm sure I will have more... lol) is for @stephenw10: For getting the Arm/Disarm lights working, will I need to have a modified BIOS, or can I leave that alone?
Thanks all!
-
I have not tried a 4130 but as you say others have reported good things about them. They are usually the cheapest CPU that will fit. I can tell you the 4160 runs fine but for some reason will not reboot which is very inconvenient!
You almost certainly don't need 16GB, I've yet to find a good excuse to upgrade from 4GB.
It will run from CF but you need to take steps to reduce writes if you do. Remove SWAP at install, enable RAM disks once booted. The CF is slooooow. Updates can seem to take forever. It's very easy to install to CF though.
You don't need to change the BIOS to run WGXepx64.
Steve
-
@zanthos ... Just sent you a PM :)
-
@zanthos ... NVM bud. I got it sorted :)
-
After ~5 months I thought it time to pursue M400v2 :)
I had ordered the necessary parts some time ago, and finally had the opportunity to complete the overhaul.
i.e. update to BIOSv6 w/NVMe Support + transition to an NVMe SSD
I am happy to say it has all been successful !
So my M400 is now running off a 256GB PCI-E Solid State Drive !
WooHoo !
Pic below of completed M400v2....
Thanks again to zanthos for all of the custom BIOS efforts !
PS ... a quick edit to note that what the pics do not show are the rubber bumpers underneath the M.2 SSD itself that keep it all raised up for air flow, etc. The anti-static layer is more of a precaution versus anything else.
