Watchguard XTM 5 Series
-
@stephenw10 Hi Steve
I have tried to install WGXepc however after installed I'm receiving error message. Have no idea why this is happening, Can you please see attach picture and tell if anything has been done wrong? Thank You
-
This post is deleted! -
S stephenw10 referenced this topic on
-
@mr-john-0 said in Watchguard XTM 5 Series:
Go up a few posts to April 26th. I had the same issue.
-
Yeah, needs to be the 64bit binary; WGXepc64
-
@stephenw10 He is trying to also put it in -conf which is locked down now as well..
If I read the post right.. Im taking some school for my job and my brain is mush!
-
Oh, good point, I keep forgetting that! Put in it /root.
-
-
After several hour I think I it is still loud maybe because I’m using INTEL Quad Core Q6600, seems like I will need to consider replacing all 4 fans. The only quite fan I know is Noctua A4x20 PWN (4 Pins) dimension 40x40x20mm it is very expensive so if anyone have any better choice please note that I’m open for suggestion.
-
The 2 CPU fans on the XTM5 are in fact controllable just not (yet) by WGXepc directly. See: https://forum.netgate.com/post/1039661
However even if you turn them down they will always be quite loud with a high power CPU in a very high ambient like that.
Steve
-
Thank u Steve but those script seems to be too complicated for me to understand how to apply them. I have decided purchase 4 of Noctua NF A4x20 PWM 4 Pins fans. Hope it would help reducing the noisy fan from XTM5 unit
-
It seems that the newer images will no longer write on these boxes.. has anyone successfully written a 2.6 or 2.7 image to one? Mine just hangs.
I have 2.7 snaps on it now but had to load an earlier image back when I loaded it and did upgrades to be able to test on 2.7 Now it will not update to the later snaps and I want to try to re-load from scratch.
-
Running on mine but I also upgraded to it.
It fails to boot the installer from USB? Or fails to boot the installed image?
What install options did you use?
Steve
-
If I install the USB stick in one of the front ports it will ignore it even though I have the boot options in BIOS set to look at USB first.
If I pull the SATA to the hard drive the unit will go through BIOS then the countdown or press escape to boot now option.. The one beep and stops.
I have an older 2.4.5 image I am going to try right now. I believe that worked last time I did this.
-
@stephenw10 said in Watchguard XTM 5 Series:
It fails to boot the installer from USB? Or fails to boot the installed image?
Steve
It fails to boot from USB and I used no options.
I think the answer is in the BIOS but for now I got it to update after a couple of days of fooling around with it.
2.7.0-DEVELOPMENT (amd64)
built on Thu Sep 22 18:30:19 UTC 2022
FreeBSD 14.0-CURRENT -
@chpalmer I just got this box back out as I had been using a Meraki from work that still had life left on its license. Downloaded the latest OPNsense and pfSense and was able to install one to each of the hard drives in the box. After I get home from the wife's lunch break today I'll blow them both away and reinstall pfSense using the 2nd drive for squid caching.
Only trouble I had was I tried making the freebsd-boot partition larger, but both would not boot if I made them 1024K instead of 512K.
-
By latest do you mean a 2.7 snapshot or 2.6? Or Plus maybe?
-
@stephenw10 pfSense-CE-memstick-serial-2.6.0-RELEASE-amd64.img.gz was the file I downloaded and put on my USB drive.
-
I know I previously used WGXepc64 on this box in the past, but after installing to this hard drive, I tried downloading WGXepc64 to /root. I did a chmod 755 to make it executable. But when running it, I get a "Syntax error: redirection unexpected (expecting word)" when trying to do any of the commands.
-
@mcdonnjd said in Watchguard XTM 5 Series:
I know I previously used WGXepc64
Did you grab this version- https://github.com/stephenw10/WGXepc/raw/master/WGXepc64
And on 2.6??
-
@chpalmer I did. But I also screwed up when adding the 2nd drive to the box. Box would fail to boot. Since I hadn't gotten very far in setting up pfSense, I decided to just wipe it and start over, and create the partition during install. After redoing the basic setup, I re-downloaded it and now it is working. I'm not sure why.
Maybe it was a bad download the first time, I didn't get much of a chance to dig into it. But it's nice to have a green armed LED again. Need to eventually get around to remembering how I customized the BIOS image so that I can change the bootup option to say pfSense V2.6 (or maybe get ahead of it and change it to 2.7 despite being on 2.6) instead of 2.2. But that's minor and only seen during boot.
