Watchguard XTM 5 Series

dazedman

If you like, i can provide you a image of the Watchguard XTM 5 Fireware software,
to verify if port 5 is faulty or not.
I have once experienced same problem with a port of a Intel Pro 1000 Dual Gigabit not recognized,
and the problem was a mismatch after a config restore.

Grtz
DeLorean

That would be awesome! Do you have it somewher eI can download or would you like me to private message you a cloud link?

DeLorean

Hi Dazedman,

I send you the link from my site for dl the image.

Grtz
DeLorean

dazedman

Thanks for the image but with the hardware upgrade I have done it appears that the fireware does not like some of the hardware or the unlocked bios. The kernal panics and crashed out. I was able to load the recovery partition and it was also missing the 5th 1gb port when it booted up. I am fine knowing it is dead and placed a blank in the port so i dont make the mistake of trying to use it in haste.

thanks again for the help and tips.

Smoothrunnings

@stephenw10:

@Smoothrunnings:

Hey Steve, this link doesn't have anything in it or on it. It works but the page only has the subject. :)

I have popped into the CARP thread and asked my question.

Thanks,

Dammit! Auto html chewed off the last ) ::)

Try this.

Steve

Meant to ask you Steve how to do use the 10/100 port on the XTM? When I look the LAN available on mine unit it only lists the 4 x 4 ports. Do I need to install a driver to use it or enable something in PFsense?

Thanks,

stephenw10

Nothing special is required to use it. It should appear as fxp0 with the em ports.

I'm not quite sure what you mean by '4 x 4' ports though.

Steve

xtm5nics.png_thumb

Smoothrunnings

@stephenw10:

Nothing special is required to use it. It should appear as fxp0 with the em ports.

I'm not quite sure what you mean by '4 x 4' ports though.

Steve

Sorry I was thinking back to my x750e which has two separate 4 x 4 10/100/1000Mbit ports that are labeled differently.

stephenw10

Ah Ok. No em or fxp NIC on there. But as I said the fxp NIC should appear by default in any pfSense version on the XTM5.

Steve

Smoothrunnings

Has anyone tried to look through the Watchguard code to see if it's possible to get their VPN accelerator card working?

I am asking because I just ran R-Tools through my XTM 5 series 1GB CF Cards and managed to get the entire Linux OS with all the libs etc. It looks like the use ELF. It also has another partition that has Executable, Libary, and DLL. I don't see any Dll's in there but I do see ELF Library, Executable and Module at are ELF files.

Just wondering. :)

chpalmer

https://forum.pfsense.org/index.php?topic=43574.msg363472#msg363472

https://forum.pfsense.org/index.php?topic=43574.msg412994#msg412994

You havent read all 29 pages! ;D

stephenw10

Yes, unfortunately we hit a road block there. Doesn't look like anything has changed in last 3 years either….

Those chips are everywhere, it would be nice to see them supported. I still don't hold out much hope though.

Steve

Smoothrunnings

Is there a bios update for the XTM 5 series?

I got two more XTM 5 series today for a really good price. But I noticed with the first one that has 4GB of RAM on it that PFSense is only seeing 3005MB and I am also experiencing some weird with the boot. After installing Pfsense onto the HD and rebooting I can see all the info on the screen after the bios, but after that when I boot the system is black with the cursor moving on the screen, the Pfsense loads up find as I it beeps normally.

So I thought maybe the bios is out of date a bit?

Thanks,

stephenw10

The XTM 5 was updated during it's lifecycle. I believe the second gen just had newer CPUs and same board but I've never had one to be sure.

What models are they?

3GB detected sounds a lot like it's running 32bit.

I have seen issues with putty where the cursor moved but doesn't write anything at a reboot. If you restart putty at the reboot it usually displays fine after that.

I'm not aware of any updated BIOS versions but I've only ever looked in the one box.

Steve

Smoothrunnings

@stephenw10:

The XTM 5 was updated during it's lifecycle. I believe the second gen just had newer CPUs and same board but I've never had one to be sure.

What models are they?

3GB detected sounds a lot like it's running 32bit.

I have seen issues with putty where the cursor moved but doesn't write anything at a reboot. If you restart putty at the reboot it usually displays fine after that.

I'm not aware of any updated BIOS versions but I've only ever looked in the one box.

Steve

CPU maybe?

It has a Celeron 440 in it. I tried a E6700 that I had kicking around but it still only shows 3005MB, the bios shows 4062MB. I am using the same version I installed on my other boxes which have Core 2 Quad 9450's and 4GB of RAM and they show 4GB of ram in PfSense.. maybe I have to redownload and flash the CF card again?

Thanks,

stephenw10

It should be pretty obvious if you're running 32bit, it reported in multiple places. That's about the only reason I can think of for seeing 3GB though.

Does it report that at the beginning of the boot also? For example (not an XTM5):

Copyright (c) 1992-2016 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.0-RELEASE-p7 #9 5ee3f5a72da(RELENG_2_4): Fri Feb  3 13:37:02 CST 2017
    root@buildbot2.netgate.com:/builder/ce/tmp/obj/builder/ce/tmp/FreeBSD-src/sys/pfSense amd64
FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0)
VT(vga): resolution 640x480
CPU: Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (3292.60-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x306a9  Family=0x6  Model=0x3a  Stepping=9
  Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Features2=0x3d9ae3bf <sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,pcid,sse4.1,sse4.2,popcnt,tscdlt,xsave,osxsave,avx,f16c>AMD Features=0x28000800 <syscall,rdtscp,lm>AMD Features2=0x1 <lahf>Structured Extended Features=0x281 <fsgsbase,smep,erms>XSAVE Features=0x1 <xsaveopt>VT-x: (disabled in BIOS) PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 8589934592 (8192 MB)
avail memory = 8144412672 (7767 MB)</xsaveopt></fsgsbase,smep,erms></lahf></syscall,rdtscp,lm></sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,pcid,sse4.1,sse4.2,popcnt,tscdlt,xsave,osxsave,avx,f16c></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>

Steve

chpalmer

Compare your bios settings. Especially when it comes to video memory. Yours may have some memory reserved for other functions. I know mine did but no longer.. ;)

Smoothrunnings

@stephenw10:

It should be pretty obvious if you're running 32bit, it reported in multiple places. That's about the only reason I can think of for seeing 3GB though.

Does it report that at the beginning of the boot also? For example (not an XTM5):

Copyright (c) 1992-2016 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.0-RELEASE-p7 #9 5ee3f5a72da(RELENG_2_4): Fri Feb  3 13:37:02 CST 2017
    root@buildbot2.netgate.com:/builder/ce/tmp/obj/builder/ce/tmp/FreeBSD-src/sys/pfSense amd64
FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0)
VT(vga): resolution 640x480
CPU: Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (3292.60-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x306a9  Family=0x6  Model=0x3a  Stepping=9
  Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Features2=0x3d9ae3bf <sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,pcid,sse4.1,sse4.2,popcnt,tscdlt,xsave,osxsave,avx,f16c>AMD Features=0x28000800 <syscall,rdtscp,lm>AMD Features2=0x1 <lahf>Structured Extended Features=0x281 <fsgsbase,smep,erms>XSAVE Features=0x1 <xsaveopt>VT-x: (disabled in BIOS) PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 8589934592 (8192 MB)
avail memory = 8144412672 (7767 MB)</xsaveopt></fsgsbase,smep,erms></lahf></syscall,rdtscp,lm></sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,pcid,sse4.1,sse4.2,popcnt,tscdlt,xsave,osxsave,avx,f16c></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>

Steve

Yeah sorry. :(

I forgot I had installed the 32bit version on my CF card to do the x750e and x1250e!

All is good now.

Thanks.

billiumg

28 pages and cannot find my solution. Anyway, thanks in advance for the assist.

XTM 505 with 1GB CF (install image)
1gig RAM
60G SSD for OS
after booting and it goes for about 3 minutes, it gets stuck at ada1: Previously was known as ad4 and hangs.
tried difference drives, both 32 and 64 bit images
even tried direct install to ssd using vmware.
they all stop at the same place.

I have attached the putty screens.

all of you are Gods of the computers - long live the Gods - beer?

[firebox pfsense error.txt](/public/imported_attachments/1/firebox pfsense error.txt)

stephenw10

I don't see the putty screenshots attached can you repost them?

Steve

billiumg

thanks i put them on original post. but will add here also.

[firebox pfsense error.txt](/public/imported_attachments/1/firebox pfsense error.txt)

billiumg

so after playing with this….
i have determined it is stopping at the point after ada1: perviously was known as ad5. So what is the next part of the script?

this is where it is hanging. What is the next step? How do i fix? enable / disable. Was going to try nano image, but do not have a large enough cf card.

from a video is looking smp: ap cpu # .........

ok more weird. for kicks removed drives and just booted from CF Card and it passed the issue..... So will have to see about larger cf card later.