PfSense on Watchguard hardware

Prowler

Steve,

I can tell you from my experience that i believed that the x550e was only 10/100 because that's what the firebox manual said. When i bought my first firebox i purposely stayed away from buying a x550e for that reason alone. I talked with several other firebox owners and they all had the same misconception that i did. The wiki should somehow indicate that the x550e is indeed capable of gigabit with pfsense in spite of what the firebox manual states.

The front buttons on my x750e have worked in the past. I had forgotten that the lcd driver and configs did not stick before i upgraded to 2.0.3. I'll try your fix and see what happens. I have often thought about replacing the LCD with something faster, more capable, and more reliable. I wouldn't mind for the backlight to stay on, but have read about its often limited life.

I'll start looking over the wiki, and let you know if i see anything else. BTW, i just bought a x550e tonight!

Prowler

Steve,

I was going to try your fixes for lcdproc, but mine has been crash free now for about 6 days. It even starts properly upon boot. I have been rebooting the firebox everyday in an attempt to break it, but it seems solid now.

I did uninstall and re-install the package, but other than that i didn't do anything else. Have you noticed any change in yours?

Mike

stephenw10

The boxes I have running currently are all using the shellcmd start method.
There have been some developments recently that may help this situation, I commented in the lcdproc-dev thread. I'm not holding out much hope.
Do you have the standard CPU in your x750e? Are you running 2.0.3?

Steve

ttblum

I'm noticing the Marvel 88e8001 NICs aren't listed in the FreeBSD hardware compatibility, they work OK on the X-Core-e models?

stephenw10

Yes, they work fine supported by the sk(4) driver. They're PCI though so that limits them.

Steve

Roofus

Hi,

As the Bios iso still valid? Tried downloading, looks too small a file (1 MB) and physdiskwrite.exe would fail. Tried another Bios.iso (8MB) and physdisk would succeed.

Thanks

stephenw10

Which file exactly? The FreeDOSBIOS2 file is gzipped and should be ~4.2MB. When I downloaded it a minute ago it still matched the MD5 given in the docs. It's not an ISO which might be causing your problem.

Steve

Roofus

It is the FreeDOSBios2.img.gz file when I download it the size is 1KB (not 1MB as I mentioned before).

Followed the 'Download this image' link

Write to CF fails with error.

Andrew

2014-08-28_09-05-52.jpg_thumb

stephenw10

Perhaps you downloaded the little padlock picture? The URL given by the hyperlink is correct:
https://sites.google.com/site/pfsensefirebox/home/FreeDOSBios2.img.gz

Steve

Roofus

I have tried two PC's, two different networks and same result.

I am correct that the .gz file should not be 1KB !

Thanks

stephenw10

Yes, you are certainly are right. 1K is far too small, it's probably some error message instead of the real file. How are you downloading it? Just tested it from my pfSense box:

[2.1.4-RELEASE][root@pfsense.fire.box]/tmp(7): fetch -o /tmp https://sites.google.com/site/pfsensefirebox/home/FreeDOSBios2.img.gz
/tmp/FreeDOSBios2.img.gz                      100% of 4239 kB 2180 kBps
[2.1.4-RELEASE][root@pfsense.fire.box]/tmp(8): md5 FreeDOSBios2.img.gz 
MD5 (FreeDOSBios2.img.gz) = 5ebb3f11925a8a78f7829e3ca0823f5d

Seems to be working fine.

Steve

Roofus

Using windows IE,+ right click + save as.

You have given me an idea, I'll use Chrome and try again.

Hmm, just used chrome and it worked :o

stephenw10

Google sites doesn't like IE? ::) If you go to the site and just click the file it takes you to a 'download page' of some sort. I expect you were actually downloading the html for that instead.
I'll add a note to the docs.

Steve