Watchguard XTM 5 Series
-
I found it here. First hit on Google. ;)
Steve
-
I found it here. First hit on Google. ;)
Steve
I think I found that one too, but when I went to the link it gave, it wanted me to download a downloader program, which I am not going to try to actually use because who knows what that actually does. However, this time, I cancelled the downloader and started typing this up with the other page still opened and it popped up with the AMIBCP download after a minute. So apparently, I was just too impatient before.
Thanks again!
-
Yes, the world of bios modification is somewhat like wading through a cess pool at times. ;)
Obviously anything you've downloaded from some anonymous upload site (after you've closed the pop-ups) linked to from a forum by some guy in Beijing must be treated with some suspicion!Steve
-
Right, after Ermal's helpful nudge in the right direction (and mostly because it was just a cut and paste job from lcdproc!) here is a WGXepc compiled for 64bit. Works fine on my XTM5. I still have to compile it for 32bit to make sure it's good there too.
https://sites.google.com/site/pfsensefirebox/home/WGXepc64
When I tried to fetch it directly to my XTM5 box I got a certificate error, which was slightly alarming, so you may have to sftp it across. Don't forget to set the permissions.Give it a try anyone running amd64.
Steve
-
Right, after Ermal's helpful nudge in the right direction (and mostly because it was just a cut and paste job from lcdproc!) here is a WGXepc compiled for 64bit. Works fine on my XTM5. I still have to compile it for 32bit to make sure it's good there too.
https://sites.google.com/site/pfsensefirebox/home/WGXepc64
When I tried to fetch it directly to my XTM5 box I got a certificate error, which was slightly alarming, so you may have to sftp it across. Don't forget to set the permissions.Give it a try anyone running amd64.
Steve
I got the certificate error as well. I moved a copy to my webserver and fetched it from there.
Just added the shell command package and doing a re-boot now. Finally a green light on this thing. ;D
Thank You Sir!
-
Right, after Ermal's helpful nudge in the right direction (and mostly because it was just a cut and paste job from lcdproc!) here is a WGXepc compiled for 64bit. Works fine on my XTM5. I still have to compile it for 32bit to make sure it's good there too.
https://sites.google.com/site/pfsensefirebox/home/WGXepc64
When I tried to fetch it directly to my XTM5 box I got a certificate error, which was slightly alarming, so you may have to sftp it across. Don't forget to set the permissions.Give it a try anyone running amd64.
Steve
I was getting that error before when trying to pull the BIOS to my watchguard.
-
Interesting… I was able to edit my original BIOS to enable the extra menus, but everything was still read only, not sure what I missed. So I figured I'd just take a shortcut and edit your modified ROM and started by re-ordering the menus so they matched the original BIOS and had the Exit menu on the end. However, now when trying to access the BIOS, it just gives me a blank screen with 'WAIT' in the middle of it.
The box will still boot up and everything seems to be working correctly with the exception of not being able to get into the BIOS. Kinda scratching my head on this one. Think I'll try going back to my original BIOS and try enabling the menus and getting them to not be read only.
At least this is kinda fun and I've got some time to kill before we move to the new house where I'll be putting this into operation.
-
Interesting… I was able to edit my original BIOS to enable the extra menus, but everything was still read only, not sure what I missed.
You have to change the 'user access level' from 2 to 3. See:
https://forum.pfsense.org/index.php?topic=43574.msg262490#msg262490Steve
-
Interesting… I was able to edit my original BIOS to enable the extra menus, but everything was still read only, not sure what I missed.
You have to change the 'user access level' from 2 to 3. See:
https://forum.pfsense.org/index.php?topic=43574.msg262490#msg262490Steve
I can't thank the post, so I gave some karma instead. I had read that post before (and the entire thread) but had missed that setting. I got lazy and read one of the books we picked up from the library instead of working on this. Luckily, I'm a rather fast reader and already finished the book, so I'll probably get to this after a trip to Walmart for some fireworks and food.
Any idea why when I modified your BIOS image it would just pause at that WAIT screen?
-
Not sure why it failed to open the setup screens. To be honest my experience with BIOS editors has me thinking that they are far from fool proof. ;) The later version seems significantly better at not producing corrupt images but the fact that it can at all, and without any indication, tells you what sort of program you're dealing with. These editors were never intended for making complex changes, as soon as you want to do anything fancy like adding new menus you're basically into writing machine code.
It's not helped by the fact that the Watchguard BIOS has a load of additional code not in a standard AMI bios. There's code for controlling the LCD and a complete copy of Redboot to allow serial firmware uploading. Who knows what else there is. ;)Steve
-
Right, after Ermal's helpful nudge in the right direction (and mostly because it was just a cut and paste job from lcdproc!) here is a WGXepc compiled for 64bit. Works fine on my XTM5. I still have to compile it for 32bit to make sure it's good there too.
https://sites.google.com/site/pfsensefirebox/home/WGXepc64
When I tried to fetch it directly to my XTM5 box I got a certificate error, which was slightly alarming, so you may have to sftp it across. Don't forget to set the permissions.Give it a try anyone running amd64.
Steve
Thanks Steve,
I was waiting for this. I'm moving this week but will reload my 510 with X64 soon, try it and report back.
Cheers
Marian -
Not sure why it failed to open the setup screens. To be honest my experience with BIOS editors has me thinking that they are far from fool proof. ;) The later version seems significantly better at not producing corrupt images but the fact that it can at all, and without any indication, tells you what sort of program you're dealing with. These editors were never intended for making complex changes, as soon as you want to do anything fancy like adding new menus you're basically into writing machine code.
It's not helped by the fact that the Watchguard BIOS has a load of additional code not in a standard AMI bios. There's code for controlling the LCD and a complete copy of Redboot to allow serial firmware uploading. Who knows what else there is. ;)Steve
Well, I went and modified my original BIOS and got it all working how I wanted it. I also found where you enabled the red arm light as well. Only thing I haven't found yet is where you changed it from WG BIOS to pfSense on the LCD screen.
Would you recommend running on mirrored hard drives or the CF card or a combination of the two?
-
The BIOS is modular and all but one module is compressed. The code that writes to the LCD at boot is in the main module. You need to extract the module with mmtool then open it in a hex-editor and search for the string 'Watchguard'. It will probably appear in a few places but it was fairly obvious which one it was as I recall. Change it then re-insert the module.
I am running from the CF card and have not had any issues (with any box). There are some things you can't do running from CF. I was just wondering how you planned to setup mirrored drives but remembered you have two SATA power connectors. I'm sure you can get a 'Y' connector of some sort anyway. What are you planning to run?
Steve
-
The BIOS is modular and all but one module is compressed. The code that writes to the LCD at boot is in the main module. You need to extract the module with mmtool then open it in a hex-editor and search for the string 'Watchguard'. It will probably appear in a few places but it was fairly obvious which one it was as I recall. Change it then re-insert the module.
I found it in module 1B and changed it, but when trying to replace it, I'm getting an error saying "1Bh This is non-editable module!!" and won't let me replace it. I also tried deleting it and inserting it with the same error. Using mmtool v3.26.
I am running from the CF card and have not had any issues (with any box). There are some things you can't do running from CF. I was just wondering how you planned to setup mirrored drives but remembered you have two SATA power connectors. I'm sure you can get a 'Y' connector of some sort anyway.
Yeah, my box has dual SATA power connectors, so that part is easy. I've found a couple of dual 2.5" hard drive brackets that I think will fit the chassis, may need the sides trimmed off, but haven't looked too far into it. Not sure I've ever seen a Y adapter for SATA, but I wouldn't be surprised to find they exist, though a 4 pin Molex to dual SATA are much more common.
What are you planning to run?
I'm not entirely certain yet. I may put a squid/dansg setup directly on the firewall for simplicity instead of having it on a separate server, and also because the re-purposed Barracuda SPAM firewall that's currently running it only has a 10/100 NIC and not 10/100/1000, though it's still faster than fetching from the internet. While I don't know much about snort, I would like to learn, so I'll probably be installing that as well. Those are the two packages I can think of offhand that would most likely benefit the most from a hard drive install. IIRC, when running from the CF, /var is a md device correct? Which means logs are gone if the power goes out. So that's also a consideration for installing to a hard drive.
I could always work out a hybrid setup where I install to CF but put /var, squid, and snort on a physical drive with fallback to md if the hard drive goes out. And I'd need some sort of alternate non-caching squid/dansg config for when the drive goes dark. Not sure what I'd have to do with snort in that instance.
It would certainly be a lot easier to either do a full hard drive install or run completely from CF than an unsupported hybrid install.
In any case, any thoughts on why I can't replace module 1B (Single Link Arch BIOS) with mmtool?
-
Hmm, I think you need a special modified version of the tool that allows it. I think that s the only version I ever tried so I probably didn't hit that particular barrier. I can't find and reference to it now though. Could be I'm thinking of Award bios tools. I'll check what I used.
Steve
-
Hmm, I think you need a special modified version of the tool that allows it. I think that s the only version I ever tried so I probably didn't hit that particular barrier. I can't find and reference to it now though. Could be I'm thinking of Award bios tools. I'll check what I used.
I found a version that works and updated that bit. Think I got just about everything set now in regards to BIOS modding. :)
-
Right, after Ermal's helpful nudge in the right direction (and mostly because it was just a cut and paste job from lcdproc!) here is a WGXepc compiled for 64bit. Works fine on my XTM5. I still have to compile it for 32bit to make sure it's good there too.
https://sites.google.com/site/pfsensefirebox/home/WGXepc64
When I tried to fetch it directly to my XTM5 box I got a certificate error, which was slightly alarming, so you may have to sftp it across. Don't forget to set the permissions.Give it a try anyone running amd64.
Steve
Hi Steve,
I have finally got around to install X64 on my xtm 510 and try your WGXepc64 on it. It works perfectly fine, thanks.
Cheers
Marian -
Good to hear, thanks for thee feedback! :)
Steve
-
Well, I finally got around to doing a permanent mount for my serial port. I got this header to DB9 connector out of a HP dc5100 PC that we were sending to the recycling company at work:
.I think I did a pretty good job with the Dremel when cutting out this hole for it:
I decided to use a drill then to put the holes for the nuts instead of cutting out a slot for them. I'm not entirely certain if this is working or not yet though as I had to smack it around with a hammer to get a nice mark of where to cut. I have several of these serial ports, so if I did end up breaking this one (I'll have to test later tonight or this weekend) I have a spare that should work just fine.
So I now have an alternate console port for when needed for FreeDOS or anything else that doesn't want to work over the RJ45 console port. Only thing left is to get myself a cheap serial GPS unit for NTP for the rest of the time that I'm not using it as a console.
-
Nice work. :)
Steve
