pfSense on Watchguard M370
-
Part 2: Detecting and backing up chip
- You’ll need SPI programmer software that can read the chip from the CH341A/Mobo SPI. Listed below are the 2 pieces of software that I have found that will read the chip:
a. AsProgrammer v2.0.3a -
b. NeoProgrammer V2.2.0.8 - Note the following steps are for the AsProgrammer software. The steps are mostly same for both programmer software. Do not attempt the steps below unless the CMOS battery has been removed and the power cable has been disconnected from the M370.
a. Launch AsProgrammer
b. Click “Read ID” button and you should get a list of 3 chips (2 WINBOND W25Q128 chips and 1 Spansion. I believe you can select either of the WINBOND options but I used the W25Q128FV.
c. Next you’ll need to unprotect the chip by clicking the “Unprotect” button to the right of “Read ID”.
d. After Detecting/Selecting/Unprotecting the chip click the “Read IC” button. This reads the original bios from the chip.
e. Once the read completes run a verification check by clicking the “Verify IC” button to make sure the image read into memory is clean.
f. At this point, if the verification succeeded without errors, I would strongly suggest saving the original bios as a backup copy. If you receive an error either the chip is still protected, cables are not connected correctly, or USB port is not supplying enough power to the mobo. Do not proceed with Step 3 if you do not have a clean backup.
- You’ll need SPI programmer software that can read the chip from the CH341A/Mobo SPI. Listed below are the 2 pieces of software that I have found that will read the chip:
-
Part 3: Erasing Chip
- After saving the original bios the next step is the click the “Erase IC” button. This will completely erase the contents of the chip and can take a few minutes.
- After the Erase has completed, you’ll need to verify the chip was erased successfully by clicking the drop-down button next to the “Verify IC” button and selecting “Blank check”. Note whether the verification was successful or not before proceeding with the next step. Sometimes the chip must be erased twice before verification succeeds.
- After saving the original bios the next step is the click the “Erase IC” button. This will completely erase the contents of the chip and can take a few minutes.
-
Part 4: Reprogramming chip with modded bios
-
Open the modified bios file in AsProgrammer that you would like to flash to the chip.
-
Click the “Program IC” button to start the flash of the modified bios to the chip.
-
Click “Yes” in the pop-up window asking for confirmation to start the programming.
-
Programming can take several minutes to complete. There is a progress bar to show completion status.
bolded text
-
Once complete click the “Verify IC” button to verify the modified bios was flashed successfully.
-
If all steps completed successfully you should be able to disconnect your SPI programmer from the mobo SPI header, insert your CMOS battery back in, plug the power cable back in and power it on. The machine takes about a minute or so to boot up and post, then it will reboot, power on and immediately power off and reboot again, and after that you should be able to access the bios menu at this point.
-
-
WatchGuard original post:
WatchGuard original prompt to access bios:
Mod_Bios post:
Mod_Bios Menu:
-
Side note: I would not enable Turbo Mode option in the modified bios if you are running a 6th gen processor. pfSense will hang on boot if it's enabled with a 6th gen processor. Works fine with a 7th gen processor.
Example of my configuration with 6th gen processor:
-
This post is deleted! -
After comparing notes with @stephenw10 it does appear the M370 and M470 have different chipsets, so this guide should only be used for the M370 unless you're feeling adventurous.
On the M370 when I run pciconf -lv I get this:
isab0@pci0:0:31:0: class=0x060100 card=0x72708086 chip=0xa1488086 rev=0x31 hdr=0x00
vendor = 'Intel Corporation'
device = 'B150 Chipset LPC/eSPI Controller'
class = bridge
subclass = PCI-ISAFor the M470 it says:
isab0@pci0:0:31:0: class=0x060100 card=0x72708086 chip=0xa1498086 rev=0x31 hdr=0x00
vendor = 'Intel Corporation'
device = 'C236 Chipset LPC/eSPI Controller'
class = bridge
subclass = PCI-ISA -
Hi all, i hope you're doing great.
@HangmansNoose001380 @stephenw10 @soupman @all in the post.What a great accomplishment have been made here, this is terrific!!! Thanks for the update info and hard work.
The fact that you can flash a generic image to the units brings more opportunities to improve computing capabilities and also made the units more Software Friendly.With standard limitations i have manage to install, pFSense (obviously) and some Hypervisors (Proxmox, VMWare Esxi), also some routing software (VyOS, Mikrotik RouterOS, OpenWRT) and Debian, just checking what could be a good a way to take advantage more efficiently and effective on the units.
I have only tested some i3 6100 with up to 32Gb Ram plus Some SATA SSD, but can assure you that on M370 Neither e3-1225v5 or e3-1240v5 or e3-1275v3 will work in the units, this looks like a Chipset limitations, as comments above.
Right now, i have 5 units (M370) brand new that were sitting on my office shelf. Actually 6, that one is running our beloved pFSense.
This updates give me hopes to prepare them and take advantage to build, maybe a Small VM cluster or how knows, some kind off weird project.
I have some CPUs (i5 6th and 7th gen, also a i7 7700 that maybe would work, using the Generic BIOS.
I'll be following up and help in anything I can, let's take this units to the next level.
Thanks all for your hard work.
Regards.
-
@nicknitro I can tell you that when I modded the bios I updated the Microcodes and the modules for video and network and I am currently running an i5-7500:
-
Hi,
hast anyone a watchguard t70 or t30 running pfsense? I can get one of these and plan to start with pfsense on it.
Mathias
-
The T30 is an ARM device so nope. The T70 can be used but there is no driver for the switch interfaces so it requires hardware mods to use those ports. Significant risk of destroying it!
https://forum.netgate.com/topic/151470/watchguard-firebox-t70Steve
-
I recovered the bios of the m370 and it is indeed unlocked.
My experience.
Laptop
usb-c (3.0 and 3.1) ---usb-c to usb a adapter---ch341A did not work. Drivers had to be installed manually. Still asprogrammer did not see the ch341aDesktop
usb 3.0 -- ch341A worked, drivers loaded automatically after install.
recovery done with the desktop.The ch341a is a risky board because of the 3.3v fault on it.
Thanks to all for the hard work and insights. -
@soupman Thanks for the feedback. The earlier Ch341a's had a 3.3v issue that was corrected in the newer versions. It could also be possible to pull the 3.3v power connector (leave the ground) and just plug power into the box and program it with the it powered down, but I have not fully tested that method.
-
@stephenw10 Thanks a lot for your Feedback, than i will try the T70
-
@hangmansnoose001380
Can you tell me how to change the password in BIOS? I have an m470, which may be different from the m370 motherboard. I want to modify the BIOS myself. Is there a tutorial? -
@qinghua907 As stated above I don't have a method for removing the password as the Aptio V bios will regen it even if it is removed. The only way I have found to have an unlocked bios is to reflash a bios that doesn't have the password enabled (Lanner original/modified bios). I can't confirm this as I don't have a M470 but I believe the bios I used on the M370 is the same for the M470. I make no promises on this as it has not been tested. If you would like to test and validate if the same bios works or not pm me and I can send you a link to the bios I used. The instructions above should be the same but I take no responsibility for a bricked device. I would highly recommend following the section above to make a backup of the current bios and verifying it's valid before flashing the new bios. If you have a successful back you should always be able to revert to the default bios using the same methods.
-
@hangmansnoose001380 OK, please send me your BIOS download link, thank you
-
Just got a M470. I'm going to start testing to see if the same bios & process works for the M470.
-
Current testing:
Mod bios does indeed work for the M470. I assume this means it will also work with the 5 & 670. Xeon does work on the M470, currently running a Xeon E3-1260L v5. PCI-e works in the M470, won't run on the 370 as it requires the C236 chipset that is only in the M470+ models. Currently testing to make sure that all ports are working including the add-in card. Getting an E3-1240 v6 Xeon to test with as well as the microcode should allow any Skylake/Kabylake (5th/6th gen) processor. -
@hangmansnoose001380
Great. Xeon (R) CPU e3-1260l V5 is used on my m470. Can this CPU work in turbo boost mode on your m470? Look forward to your good news