Successful Install on Watchguard Firebox X700!
-
@Steve,
Thanks you very much. I will try to find me a cheap 2GB-4GB CF card. I do have 10+ laptop HD's sitting around but I prefer the CF solution to avoid any mechanical issues that might arise with those older beat up Laptop HD's :D. I might need to kick up the Installed RAM on the x700 from factory 256MB to 512MB since the writes go towards the RAM instead of the CF as far my understanding goes from what I've read.Regards,
Lee -
The NanoBSD image has no swap, mounts the partitions noatime to prevent writes to the card when reading files and all logs are sent to ram. The CF card will not suffer from write failure with 256MB.
Steve
-
Ok cool.
-
Hey guys, I've been reading through this thread for a while.
I've been considering picking up a used X700 off of ebay, mostly for nostalgia reasons as a couple jobs back we used Watchguard as our primary firewall/router/vpn source. So the idea of picking one up and using pfsense on it is very intriguing.
But…I'd really like to limit my headaches.
What is the easiest way to get this working? I don't plan to swap out the cpu or add additional memory, this is really for my home network so at most we're talking a VPN tunnel or two, a couple PCs, and QoS. Overkill I know. I also have a spare 40gb notebook IDE drive in its the easiest way.
Thanks guys, appreciate all the effort that has gone into this!
-
Using a hard drive requires some modification to the case as there isn't drive caddy provided, just a blank.
To install to the drive you will need to first install it into a laptop (or pc via an adpater) and boot that from the pfSense install CD. Then follow the prompts to install to the drive. You will have to boot the laptop into pfSense in order to turn on serial console access in the GUI. When you swap it back into the firebox it will likely ask you for the location of the root partition as the path will have changed. Once it's booted you can change that.Using a CF card is far easier. Just write the NanoBSD image to the card, insert it into the firebox and boot. Unfortunately the current pfSense (2.0 release) has a strange bug that can cause the serial console to not appear after the initial setup. There's a workaround for it though in the forum.
If it were me I'd go the CF route. ;)
Steve
-
Just picked one of these up for cheap. Does anyone have a junk one that would be willing to sale me the drive bay cover?
Thanks
-
Where abouts are you?
Steve
-
Tampa Florida. Ill pay shipping plus what ever u want for the item.
thanks
-
I don't actually have a spare one myself and I'm in the UK anyway but perhaps someone closer can help you out.
Steve
-
So firebox arrived, And i got pfsense on it. But if i do a hard power off, and then try to power back on, i get nothing on console. It even had an ipaddress on the Lan side, and i was able to access. But after the hard power off, i get no ipaddress.
Anyone seen this before?
Thanks
-
The serial console problem has been seen by several users see this thread:
http://forum.pfsense.org/index.php/topic,34814.15.html
It is not yet well understood but the workaround seems to be effective.Not sure about the LAN not coming up. Did you set a static IP?
Steve
-
this does not seam to be my problem, I get a full boot one time, and then if i turn it off it will not boot the next time. if i wait 5 mins with the power off system will boot up fine. I tried an image of monowall and it did not do this. So i am not sure if it is the cf cards i am using, but that seams to be the only difference.
-
Hmm. So does it reboot if you issue a reboot command from the GUI, without physically de-powering it?
Have you checked the CMOS battery? If it's flat it can cause the bios to not boot on each initial power up.
Different sized CF cards? UDMA capable CF cards can cause a problem, you have to disable UDMA either in pfSense (usually is by default) or the bios.Steve
-
if i reboot it from the web page or from the console it powers down, but will not come back up until i wait 5 min or so.
Ill check the cmos battery this evening. It came with a 32mb card i think. and i am using a 4gb card the card is the first thing i thought of and ill have to order one.
-
If it doesn't do it with a monowall image then I doubt it's a problem with the card.
Does it show anything on the console when you reboot?Steve
-
i have not tried monowall on the 4gb cf, i am about to do that. And no nothing on the console at all.
-
so just tried the 4gb cf i have with monowall 1.33 and it is booting every single time. I have hard powered it off 5 times back to back and it works fine. So i guess the cf card is ok.
-
I wanted to see if anyone else has had these same issues on their watchguard/pfsense box. I flashed the embedded 2G image to a 2GB CF card and so far everything seems to be working fine, including the LCD, on my X1000. However I have the following issues:
1. I used the serial band-aid trick posted here, http://forum.pfsense.org/index.php/topic,34814.15.html, to try and get the serial console to work beyond boot. I get serial output until I see the message Bootup complete, then I get /etc/rc: /usr/local/share/misc/serialbandaid.sh: Permission denied. I thought that it might be a permissions issue, so I tried to chmod +x and even chmod 777 the file but just get an error that says Read-only file system. Has anyone else come across this?
2. Has anyone tried upgrading the ram? Mine had 256MB of PC133. I tried to put in two different 512MB sticks of different brand but identical speed and timing ram and the system will not boot. I get the first beep after a few seconds when I power on but the system seems to hang. Don't know why or where because I get no serial output when this happens. Just wondering if anyone has had any luck doing this.
-
The file system is supposed to be mounted read only for the nanoBSD image.
However there is currently a bug that means it sometimes isn't. See: http://redmine.pfsense.org/issues/1279
It appears some progress has been made on this and it's related to package installation. I guess you haven't installed any packages?The correct way to modify files in nanobsd is to first remount the filesystem see:
http://doc.pfsense.org/index.php/Remount_embedded_filesystem_as_read-writeThe X-core seems to be picky about it's memory. Reading back through this thread (now TL/DR!) there are a number of posts about ram not working.
Unless you're running memory hungry packages you won't need more than 256MB.Steve
-
[…]
then I get /etc/rc: /usr/local/share/misc/serialbandaid.sh: Permission denied. I thought that it might be a permissions issue, so I tried to chmod +x and even chmod 777 the file but just get an error that says Read-only file system. Has anyone else come across this?Had this issue on a 2.0 release installation (full install on hard disk). I did a chmod 755 ont the serialbandaid.sh file, and now it's working. I have no problem with the read-only file system because of the HD install, but 755 is enough (probably 555 should also do it)
