Watchguard XTM 5 Series
-
Ah, I never considered 64bit. ::)
The code is sufficiently basic that it runs across multiple things. Code compiled in 8.1 still runs in 10 for example.
Are you running Nano? I take it the required 32bit compat libs and flags are not included.I don't have a 64bit FreeBSD machine running right now but feel free to compile te code yourself if you do:
https://sites.google.com/site/pfsensefirebox/home/WGXepc.cI'll have to do it myself eventually though.
Steve
-
I don't have a 64bit FreeBSD machine running right now but feel free to compile te code yourself if you do:
https://sites.google.com/site/pfsensefirebox/home/WGXepc.cSteve
Ah- I figured that might be the reason. Compiling is still above my paygrade a little. I may have to use the balance of the weekend and learn however… ;D
Im using this as my test box right now until the donator decides the 550e I built him isn't good enough... :(
-
Hi,
Thanks all of you guys, lot of information… I'm not bsd user but sometimes it saves my life.I just want to say, I installed Debian Wheezy and it works like a charm. But my eth1 ports is death.
If got something else usefull I'll share it in here.
Again thanks for everything...
-
I've recently aquired a XTM 510 which I'm installing PFsense on, I'd like to be able to boot off a hard drive in order to utilize caching, could someone point me in the write direction if that is even possible? Without a video output it seems the standard builds wont' work and the nano builds would only give 4gb of space?
Thanks
-
Ok. I've not tried this so it's based mostly on experience from other boxes….
The XTM5 has SATA connectors and a SATA power connector on the PSU so you can hook up a standard SATA drive. However you may have to construct some mounting hardware.
You may be able to boot the box from a USB stick with the memstick-serial image on it and then install directly to the SATA drive. Select the embedded kernel during the install to get a serial console. You probably need to have the unlocked BIOS to boot from USB though.
Alternatively you can install to the drive in a different box. Configure at least one interface so you can access the webgui and go in and select the serial console. Now transfer the drive back the XTM5 and boot. It will probably fail at the first boot because the sata connection number will be different. If it does then point it to the correct location at the mountroot> prompt and then edit the fstab once booted.Steve
-
http://www.cavium.com/acceleration_boards_FIPS.htm
Cavium provides a comprehensive Software Development Kit that includes C-source code for Linux and FreeBSD drivers. The SDK also includes APIs for OpenSSL, OpenSSH and PKCS#11, key management utilities, test utilities and reference code for easy portability. The Crypto-API’s are common between Cavium’s FIPS and the non-FIPS product providing customers with tremendous R&D leverage and re-use.
-
You are pointing out that they advertise FreeBSD as supported? That's true except there aren't actually any drivers instead there's an SDK to develop your own drivers and to get access to it you need sign an NDA etc. They are never going to end up in FreeBSD. I guess you may be able to poach them from some FreeBSD based commercial firewall, JunOS perhaps?
I tried to compile WGXepc by booting a 64bit live GhostBSD DVD but it was a no go. There are some references to i386 functions which wouldn't compile and their amd64 equivalents wouldn't either. I borrowed that code from LCDproc though and that seems to compile for 64bit so there must be a solution.
Steve
Edit: typo
-
You are pointing out that they advertise FreeBSD as supported? That's true except there aren't actually any drivers instead there's an SDK to develop your own drivers and to get access to it you need sign an NDA etc. They are never going to end up in FreeBSD. I guess you may be able to poach them from some FreeBSD based commercial firewall, JunOS perhaps?
I tried to compile WGXepc by booting a 64bit live GhostBSD DVD but it was a no go. There are some references to i386 functions which wouldn't compile and there amd64 equivalents wouldn't either. I borrowed that code from LCDproc though and that seems to compile for 64bit so there must be a solution.
Steve
I should have been to sleep by then when I posted that and didn't really finish what I meant to post. :o But you answered my question. Whether or not the drivers might be out there…
As always- thanks for the effort!
-
I've recently aquired a XTM 510 which I'm installing PFsense on, I'd like to be able to boot off a hard drive in order to utilize caching, could someone point me in the write direction if that is even possible? Without a video output it seems the standard builds wont' work and the nano builds would only give 4gb of space?
Thanks
Hi there. I run 2.1.2 on xtm 510 with 120GB SATA SSD drive. It works perfectly fine. Cache read speed for Squid is around 35MBps.
Edit:
-
Nice. :)
No gotchas in installing or mounting the drive?Steve
-
No problems at all. I have used a laptop to install pfsense on the HDD and then plugged it into Watchguard and that's it.
And stephenw10 I use your Bios on it. I also have x750e I use your bios on, version 8 - it allows booting from HDD (IDE) without any tweaks or any CF cards installed - nice. Thanks for this!
Edit:
WGXepc - I'm not knowledgeable enough to compile it to run on X64 so I stick to X86 on my xtm 510 until that's done by someone who knows what to do - stephenw10 - please let us know if you manage to get it compiled successfully.
-
No problem. Thanks for the feedback. :)
Steve
-
Forgot to mention that my xtm 510 runs with single 4GB DDR2-800 RAM stick. I did not boot with 8GB (2x 4GB) but it might do with say 6GB when running X64 would be useful.
-
Finally got the console to work, had to put together my own cable by splicing a standard serial cable into a different configuration, as mentioned it seems to be cisco standard but since I couldn't easily find pinouts here they are:
RJ45 - DB9
1 - 8
2 - 6 + 1
3 - 2
4+5 - 5
6 - 3
7 - 4
8-7Flashed the bios, some more options seem available but a lot of them seem to be view mode only though, I'll work on the HDD install after I get more familiar with PFSense and back into FreeBSD.
Edit: once the bios is flashed the battery has to be pulled to reset to default, that unlocked all the options in the bios and allowed it to boot normally again
Thanks for the help
-
Hey stephenw10,
i want to step deeper in what you have done.
Can you help me with opening the bios file in amibcp?
I tryed with your .rom file from page 3 and amibcp v4.53 but i always get the error: "Couldn't open the file."
What did you do to open the bios file in amibcp?
Thanks in advance. -
It's important to have the right version of AMIBCP. The first versions I had corrupted the BIOS pretty much every time. Unfortunately the machine I was using to run it was using XP so I retired it. It's now gathering dust so I need to get the data off it. I'll get back to you.
Did the rom file download OK, have you checked the MD5?Steve
-
Yes i checked the md5 and i flashed it on my XTM 5.
Everything works.
But im interested and want to get some feelings about modifing the bios.
Thanks in advance for your reply. I'll be waiting. -
I installed flashrom via pkg_add -r flashrom but I'm getting this when trying to read the original BIOS:
[2.1.3-RELEASE][root@pfSense.gorgarath.net]/root(8): flashrom -r og-bios.img flashrom v0.9.5.2-r1515 on FreeBSD 8.3-RELEASE-p16 (i386), built with libpci 3.1 .9, GCC 4.2.1 20070719 [FreeBSD], little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "Intel ICH7/ICH7R". Enabling flash write... OK. No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically.
I'd like to make sure I get a valid backup before flashing the modified BIOS. But as of right now, I can't flash the modified BIOS nor make a backup. Am I missing something or a jumper on the motherboard somewhere?
-
@lolman
You have to use the 3.XX series on the XTM5 bios. I believe the 4.XX is for UEFI bios only. I started out using 3.43 but that mostly corrupted the BIOS image! Using 3.51 allowed me to edit the Superio tables and didn't corrupt the BIOS.@mcdonnjd
Which model XTM5 do you have? It seems like it's different to those the rest of have so maybe it's one of the second generation models.Steve
-
@mcdonnjd
Which model XTM5 do you have? It seems like it's different to those the rest of have so maybe it's one of the second generation models.Steve
I was hoping you'd be the one responding as you seem to know a heck of a lot about these units. I just upped the memory to a pair of 2GB sticks and a Core2 Duo (E6550) @ 2.33GHz, though I'm thinking of downgrading one of the Core2 Quad (IRRC 3.0GHz) PCs down to a Core2 Duo once I check one to see what socket it is using.
I'm thinking I might have a different model, a later generation perhaps as I have 2 SATA power connectors on my PSU. I took some pics last night that I can post if needed. The BIOS version reported by the LCD and on the console match what you posted and I believe it's the same motherboard model, though I'd have to open it up (or check my pictures) again to be sure as I can't remember now.
On the back of it, it's a very generic XTM 5 Series and XTM 510. I don't see anything about revisions or anything to make it easy. If there's something you want me to look for or try, let me know.
Currently idling in the BIOS at 39 degrees on the CPU with the Core2 Duo. Didn't check what it was at before on the Celeron, though I only had it on at home in the living room before where it was much warmer than the server room at work. Doesn't sound like the fans are running loud either which is nice, though I can't really be sure they aren't as there's a ton of wind noise in this room already. Vcore is fluctuating at 1.319-1.334, I haven't looked up yet to see if that's in spec or not yet.
EDIT>>
I missed the label on the bottom of the chassis, Model #: NC2AE8.Also, do you think that either http://www.newegg.com/Product/Product.aspx?Item=N82E16811994023 or http://www.newegg.com/Product/Product.aspx?Item=N82E16817997007 would fit nicely inside so I could have a RAID-1 hard drive setup? They both probably would fit with some modifications, but curious if anyone things they would fit without having to do any work to them.