WatchGuard x750e Hard drive install
-
Ah interesting.
Differences I can see between what you did and what I did:
You used the embedded kernel, I used the standard (SMP) kernel.
You disabled stuff in the bios, I didn't.I chose to use the standard kernel since most people who want to do a full install do so because they want to use all the packages. None of which are available with the embedded kernel. Why are you using a HD?
I may have to go back and test again. Thanks for your results.
Steve
-
steve, i dont think the stuff that i disabled in the bios would make much difference, i only disabled the stuff that wasnt required like LPT1 and com2. guess its my old throw back to the old DOS days, trying to free up memory resources. As im new to freebsd i wasnt sure on how it managed its memory, even though i have 1Gb of ram installed in the box.
The reason i moved over to a HDD was that even though having a 16Gb sandisk CF card installed. i was running in to issues trying to load packages, i was attempting to run snort and dansguardian and the HVAP antivirus. but for some reason everytime HVAP would try and update it would overload the log files and use all the available memory and then crash the box.
Even though im using the embedded kernel, it looks like thier are more packages available, than what thier is on the nano CF card images. As i have noticed that freeswitch is now available for install. i will need to do a comparison between the nano and full installs to find out whats available, package wise that is.
Btw just seen the pic that you uploaded of your firebox setup. you need help ;D
im sure thier is bound to be a support group some of some kind for that kind of fixation lol.
do watchguard phone you up if they are looking for spares.Colin
-
Ah. Well that's interesting about packages with the embedded kernel. I must be confusing it with the old (pre-nano) embedded install. :-\
It can't hurt to free up resources. Even if you have loads of ram that won't help when you run out of interrupts or I/O address space because some device is misbehaving.
The reason you were having trouble with HAVP is likely that it uses /tmp to download update to. In the Nano install /tmp is a ramdrive of a fixed size that can be exceeded. Having a larger CF card won't help. In fact anything over 4GB isn't used anyway unless you rolled your own image for 16GB. It is possible to set the size of /tmp larger though if you have sufficient memory.
Yes I need help. ::)
It started out that I wanted to use pfSense at home and looking for suitable hardware. I wanted as many interfaces as I could reasonably afford for maximum isolation between network segments and reading through the forums the Firebox seemed an ideal platform. I was looking at X500s and X700s and ebay for a while when the X6000 came up for very little money and I couldn't resist. Then after I got more involved on the forum people were asking questions about boxes I didn't have and they were so cheap on ebay I couldn't resist. Then I was addicted! ;D
Just a few weeks ago some XTM5 boxes sold for ~£100. It was all I could do to resist. That's just stupid cheap compared to a 7 interface firewall platform new.Steve
-
Ive just checked the amount of packages available on the full install with the embeded kernel. i have 87 packages available for install. i dont have the nano image running at the moment so cant do a direct comparison between the two. but thier is definitely more packages available.
Colin
-
I appear to have 82 available under Nano.
If you look at the list xml file: http://www.pfsense.org/packages/pkg_config.8.xml there are 6 packages marked 'noembedded':
pure-ftpd
ntop
FreeSWITCH
FreeSWITCH Dev
Lightsquid
phpSysInfoClearly I've misunderstood quite what the embedded kernel provides. :-\
Steve
-
steve
I've Just been playing about with the PHPsysinfo package, it looks quite good at reporting back some of the data from the box regarding temps and disk/memory usage. it looks like thier might be an issue with the package reading the fan data back, but i think that might just be due to the monitoring chip in the box. The speeds reported are way out. i have your WGXepc app running and have the fans throttled back to 20% of normal.
A couple of screen grabs attached of the PHPsysinfo report.
Colin
-
Forgot to attach the second screen grab.
-
Nice!
Yes the PWM employed by the SuperIO chip to control the fan speed completely screws the speed readout once you go below a certain level. Hex value BB I seem to recall. That's why you can't use a value below BB in the bios for the initial fan speed. The completely fictitious huge values crash the bios setup code.Steve
