Thanks Phil.

Successful update from 2.3.1_5 to 2.3.2 Thanks to pfsense team :)

Yeah the only reason to keep the gitrepo directory around is if you want to gitsync again, it'll be much quicker to update the existing than to checkout the entire thing. Outside of that, it has no impact on the system.

oh june ;) be sure to bump a topic every week if nobody replied to it :)

@skynetsysadmin: OMG, a whole 17watts! You only read what you wanna read. 17W is the chipset. You still didn't answer which CPU you use. Those 45 or 60 Watts add to the total. The system cost is always comprised of hardware price plus operating costs by usage period (unless parents pay the power bill). @skynetsysadmin: Do you even remember CRTs? My education included repairing them. Why do you ask, is yours broken?

still the serial settings are wrong … doesn't matter what the manufacturer states. the manufacturer states the serial settings that are in use when the OS has not taken over (while the BIOS is in control). somewhere in the bootprocess, pfSense takes over and puts the serial settings to something different ( as noted in the link i've posted) the 4GB card should work with a 4GB image

I found out what my issues was. I was using the same Mac address on both the Wan interface of the Draytek and the Wan interface on PFsense, even though i cleared it out from PFSense. i just added a few digits to PFSense and its all up and working. Thanks again Exolon!!!

Final question for anyone who might know.  I can see how I can replace the fans quite easily (there is an 8 pin molex connector (marked MSH 3/2695) connecting the four SAN ACE 40 fans to the PSU.  However, I have heard there is a way to solder a LM7806 voltage regulator to the fan bay, however I haven't got a clue how to do this.  Any ideas?

@jpvonhemel: So I reentered the code, but I notice my Disk Usage is still 106%. Here is a copy of me entering the code followed by a look at the /var/run directory. I'm not sure what I need to do to fix this. Run on shell: rm /var/run/php-fpm.core

Was supposed to be a few days back, but then they ran into some last minute problems during their last set of testing. They like to release Tues-Wed.

Hi Guy thanks for your replies, I've tried burning it to a CD but still no joy and even change the CD-Rom and still same result. if I try the install on a tower then it installs fine every time but its only when I try installing it on a HP or Dell desktop. I was thinking of installing PFSense on the tower and then removing the HDD and installing it then into one of the HP / Dell. I have 12 PFSense to build and need to sort this issue ASAP.

Update: got it working. If anyone is suffering from issues with VLANS , cable modems and pfSense read on, it might help. Seems the issue might have been due to my switch MAC add being utilized first instead of my firewall box at the ISP end, due to using VLANS? Anyway - to correct this - I attached my firewall box directly to the cable modem and did a system reset and obtained a WAN directly. I then setup my WAN VLAN in the gui and switched to it - obviously making sure all cables were put into their correct VLAN port…  (For some reason I couldn't get this to work via the console?) I am a happy man for now....

Thanks for all your help.

@Derelict: 2.0-RC is ancient. Being an RC config there is no guarantee all the necessary configuration upgrade code was in place. Nor is there any promise that it will be. The problem likely stems from choosing to leave an RC in place instead of finalizing on a RELEASE way back then. It is unrealistic to expect a seamless upgrade to a development snapshot from 5 years ago. Instead of upgrading you could save your config, install a nice, fresh, full install, then try to restore your config. Maybe try to restore just parts of it and see which part is failing. That might save you some work. Yes, I know it's quite old, due to both slices failing I can't tell you the exact version of the RC but I think it was like the last one before release, so I probably had hopes restoring the config could probably work fine. In regards of getting the system up and running with that config it did work perfect, my whole pre-2.0-config was restored and working on a fresh 2.3.1 install, all it did was to break the update to 2.3.1_5. So, I'm good, my problems are solved … I'm on the current stable build/patch and already have everything setup I need running again, was just asking if there is need to dig into that further as here are some threads on the forum about problems upgrading to 2.3.1_5 where I could imagine the problem could also be related to the config files. If so just let me know if I could help ... Besides all that, you guys are really doing a good job on pfSense, keep up the great work. I'll definitly go gold for you guys soon, would also like to buy an appliance but as I am from germany it unfortunately doesn't make any sense regarding shipping cost, taxes, etc.

Great! 2.3.2 should be out on Monday if all goes well with our testing, you will likely have to repeat the procedure again to reach 2.3.2, but after that point you should be OK since the bug is fixed in 2.3.2.

We successfully installed pfsense, we just transferred it to different machine. Thank you for all your response.

After some research it looks like i need the bwm port module. Does anyone know where or how to get that?

hi mate still not working

Putting the different types of devices into actual different subnets/VLANs has the advantage that a device that is physically connected to a particular VLAN port cannot fake being in the other VLAN/subnet. But if you don't have users/devices that are going to be messing about trying to set their own IP address to work-around your access rules, then they can all be in the same LAN/subnet and just give static-mapped IP addresses so you know which devices have which IP addresses. Make an Alias for the VOIP phones that includes the IP addresses of the VOIP phones. Make a rule on the relevant LAN/VLAN that matches the VOIP phones alias, passes the traffic, and set the gateway (in the advanced section of the rule settings) to the WAN gateway that you want the VOIP traffic to take. Set the system default gateway to where you want the other stuff to go, and put rile(s) to pass the rest of the stuff you want to allow, without bothering to put a gateway in the rule - it will be directed out the default gateway.

This is a known issue when pfSense runs on Hyper-V: https://forum.pfsense.org/index.php?topic=109901.0