Snort 2.7.0.1_3 is the only package I currently have installed. Regards Ben

Thanks for the reply. My question is will this work - with the subnetting in particular. If I have a 26 bit range if IP addresses assigned by my provider. Can I just create 5 networks out of that space by increasing the subnet to 28 bit without any additional configuration changes? -Toz

@Cry: You're contradicting yourself.  Either you're running this on physical hardware, or in a virtual system (VMWare etc).  Which is it? Physical hardware. Ended up installing vmware server. Booting the livecd iso within vmware and installed to the CF. After finishing the install, pull the CF card and installed it in the real hardware, just needed to reconfigure the interfaces.

Thanks GruensFroeschli for the quick reply. I'll try the fix on the given link. :)

load the phpsysinfo package and this is one way that you can see how many processors are in use. RC

pkg_add -r rsync

For clarification, there was a period of time where the update just defaulted to the non SMP kernel on upgrade.  It now prompts for the kernel type on upgrade.

That error is "normal", I'm not sure where it comes from but it's not the cause of your issues. Is the LAN and WAN on the same subnet by chance? That won't work. Aside from that, no other issues come to mind that would cause problems in this type of setup.

The released version of snort and the version available in the packages aren't necessarily going to be the same thing. As for the updates - if you visit the "Installed Packages" page it'll show you any packages that have updates to apply.  See, simple ;)

I know that much  ;D I guess I can play around with the settings.

General advice is to go with 1.2 (as you'd have seen if you'd searched the forum).

@eweri: Login via ssh and than /etc/rc.conf_mount_rw mv /etc/ttys /etc/ttys_back cp /etc/ttys_wrap /etc/ttys reboot This worked for me, thanks

I also tired with antoher CD drive and it doesnt worked until i replaced RAM. As i mention before…after i replace ram it worked.

Install the full version of pfSense Ensure you have   a) "enough" RAM (value of "enough" varies according to your network and needs, but I'd suggest that 256 MB is the absolute lowest)   b) fast "enough" CPU (the better the network cards you have the less this may matter - varies according to your network and needs)   c) Good network cards - Intel Server cards are preferred, but anything other than RealTek is a good start (lower quality cards will put more load on the CPU) Install Squid Configure according to taste ;)

@jle2005: No, if your subnet mask is 255.255.255.248 then you should use /29. You should also check the Gateway and DNS for the right IP setting. My mindset was I'm configuring the NAT that is why the /32 netmask, anyways, it's now working when set to /29.  So simple yet overlooked. Thanks.

did you follow that: http://blog.pfsense.org/?p=149 which file are you using to upgrade? could it be that you're using a "new install" file to upgrade?

fixed no irq problem any more still only ONE wan connection at a time i can only connect to 1 modem at a time and only true dhcp, static does not work at all ????

http://forum.pfsense.org/index.php/topic,1828.0.html –> http://devwiki.pfsense.org/FullInstallOnWRAP

@jrpadilla: System is hanging on boot up when recognizing COMPAQ motherboard? HARD LOCK system locked. Please help. Just today I was installing pfSense 1.2 RC release in our HP D220 MT desktop and was frustrated all day coz the install always hang, I thought at first it was caused by the corrupt cd installer so I downloaded and burned a new copy but still have the same problem, simply it won't go away. I also changed the cdrom drive as mentioned on another thread in this forum but to no avail, still have the same problem, it always says that pnp bios bad checksum. I almost called it a day until I gave it one more try, I found two workarounds in order to install pfSense 1.2 RC3 in this particular hardware. 1. Press F10 during bootup to enter setup and Disable ACPI in bios, save the changes and let the system boot from the cd installer and let the default mode load. 2. Instead of disabling ACPI in the BIOS, when the FreeBSD loader appear press 2 to load  FreeBSD ACPI disabled and you're good to go. HTH