Watchguard Firebox M400/M500
-
@korenchkin ...thanks for the reply.... I have a question, i hope you or someone can answer it.
in this image (opnsense) there is this option (highlighted). Not sure IF is just an add-on in order to look and find a update to intell cpus or is an actual microcode update... anyway, please clarify.
thank you
-
@jriofrio said in Watchguard Firebox M400/M500:
in this image (opnsense)
The OPNsense forum is a more sensible place to ask questions about an OPNsense package.
-
@jriofrio it is exactly what it is named,a microcode update,that updates in runtime cpu microcode,we don't need to talk about any specific solution,a microcode update in os does what the name says,updates usually old bios microcode(not sure where it resides,cpu dedicated memory for microcode maybe?),and it is lost on power off(or maybe cpu reset?)
If you want to play,you can update this microcode in bios using ami tools and won't need to run this in os...but it does not matter,i think this bios has latest microcode anyway...play with bios file,i think uefitool is a good start for reading that file -
@korenchkin ...alright thanks... I was thinking perhaps this plugin will do the job of updating the Me 9.1 code but no such luck.
I downloaded the files in your link. ... pardon my ignorance but, do i need to create a freedos boot usb flash drive and add the files to it and then boot the m400 then run the update as you stated it?
afuefix64.efi m400-91.rom /me
will that do it? -
Are you seeing it fail to reboot? Otherwise you don't need that.
-
@stephenw10 I think was yesterday that you asked me if it reboots ok.
so earlier today i reboot it through serial console and it hangs...
I used to just turn it off after i did some changes. i am waiting for a sata drive to arrive so it is not online just yet. I would like to solve all the issues before goes online.
hope the update of the Me 9.1 goes well too. -
@jriofrio this is efi shell,it just needs filesystem...it should pick up the right file...i think...for efi there is no mbr/boot sector...bios should know the name of the file to load(and be set to boot uefi,hopefully default)...i'm not certain about mbr/gpt partition table,windows uefi needs gpt,but here i probably didn't overthink it and it just booted...just try and see (and google for uefi flash boot/uefi shell,if something does not work right)
-
@korenchkin .... Alright, thank you very much for the clarification, it really did help.
I did the flashing and tested it. I restart it by the serial console and the web interface, both worked as was hoping for.
A little reading with your comment about efi it help a lot.anyway, a quick question if i may. Before the flashing ME91, i was checking the bios and i saw that the image re-flash for the ME was disable, so i enable it, just in case.
Q: should i disable it back?
thanks one more time...
-
Normally you set that and it applies to the following boot only and will automatically go back to disabled.
Out of interest I found I didn't need to set that to update the ME. Moving the jumper was sufficient.
-
@jriofrio nice,glad it worked,for both of you i guess :)
I think now you know same as me,so treat your bios as yours,you have it updated,you will not update it again i guess,so maybe it will help against malware to have it disabled...
