I re-loaded the 2gb image after successfully loading and booting from the 512mb image. A bad image load at first.  All is working now, thanks!

Yeah it worked… Just neede fstab edit from ad16a1s1 to ad4a1s1 Or something like that :)

It would be even better if the pfSense devs just built it to format & start at 2048 in the next 2.02 release. No reason not to these days.

Under system Information : ersion 2.0.1-RELEASE (i386) built on Mon Dec 12 18:24:17 EST 2011 FreeBSD 8.1-RELEASE-p6 Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /etc/inc/system.inc:2) in /etc/inc/auth.inc on line 1254 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/system.inc:2) in /usr/local/www/guiconfig.inc on line 47 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/system.inc:2) in /usr/local/www/guiconfig.inc on line 48 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/system.inc:2) in /usr/local/www/guiconfig.inc on line 49 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/system.inc:2) in /usr/local/www/guiconfig.inc on line 50 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/system.inc:2) in /usr/local/www/guiconfig.inc on line 51

I'm fairly sure since 2.0 all versions are using an SMP kernel since it now handles a single cpu with no problems. I also thought that it was a restriction of pf to a single process that limited the total potential throughput of pfSense. I realise that's a simplification. Steve

You can go right to 2.0.1, you don't need to go through 1.2.3. I've even upgraded a VM from 1.2 up to 2.0.1 before. The upgrade code takes care of all the needed bits from every old version.

See: http://forum.pfsense.org/index.php?topic=44072.0 It will probably not work without patching some files and recompiling. Steve

Hope 2.1 is better on these standard machines.  As for your comments, I have to agree with others in such places such as this - http://arstechnica.com/civis/viewtopic.php?f=10&t=1137301 - too much "KoolAid" of your product.  You have good product don't ruin it with those type of comments here and there…

The TEAK 3035 box turned up today with a VGA port on the back. There was no mention of that port in the specs! I popped in a 2.5" HDD and a memory upgrade and then installed the full LIVE version and installed it to the HDD without any problems at all. All is looking good so far. Thanks for your efforts Jim, although not required. Gordon

it was set for amd64…. on all 4 firewalls..... still the "upgrade" installed the x86 edition one of the firewalls was even a fresh install, everything set up from scratch..... (not imported any previous setups...)

I will do a "cold swap" means Take down the present Firewall and keep it intact Test the new one and if everything works well stay on the new one I have a quad Port Intel Card in the present Firewall and will move that one to the new box Thank for help

There is no index.html there, so lighty tosses a 404. It is not meant to be used by a browser.

Thanks,  Tried the second controller and it worked perfectly. Much Appreciated! ;D

I can get everything to work if I leave one IP associated with the parent interface instead of having all assigned to a VLAN.  This also means I then need to have the switch configured with the native vlan tied to that. This is what's working: pfsense vr0 = vlan20 (LAN) vr0_vlan10 = vlan10 (internet) vr0_vlan30 = vlan30 (VoIP) [typo in previous post had me showing this as 20 also] vr0_vlan40 = vlan40 (DMZ) switch interface FastEthernet0/23 description Neoware CA-10 Trunk switchport trunk encapsulation dot1q switchport trunk native vlan 10 switchport mode trunk spanning-tree portfast end Not sure why I need an untagged IP on this and it's obviously the "wrong" way to configure it but the only way I can get it to work on this nic driver.  I haven't found anything searching google about this driver behaving this way, but I did run across the re0 drivers having this problem. The only issue now that I see is poor network performance with max throughput at about 4-5Mbps which I haven't determined if that's due to the nic/driver or cpu. I'm glad it's working but would be happier if I could get tagging working as it should with no IP on the parent interface and all IP's on vlan interfaces only. Thanks for the pointers as it helped get me going in the right direction.  If you have in further insights I would appreciate those as well.

@cmb: Yeah you will have to re-flash in that instance. Upgrade overwrites the partition on the card, not the entire card, so you have to re-flash to rewrite the partitions to be the larger size. Thank you cmb!

I prefer to install packages and then restore config.

ok thanks for the fast reply

I would suggest you also set your self up a free opendns account and turn on most of the options. Two reasons, it will help you control your users in the form of stopping them accessing high bandwidth source sand consuming your bandwidth -although I don't think you're going to have bandwidth issues per say. The other thing it will help with is that you have a responsibility to prevent the cconnection being used for illegal use. Sounds very big brother, but sadly the digital economy bill does apply to what you are doing. You can't possibly know what is installed on each computer on your network, what they are going to download. Etc, We use pfsense in two locations, one is holiday apartments and the other is a leisure facility, you'll be surprised what appears on the blocked domains list report generated by opendns. And these are family environments…...oooooo Good luck with your project.