@dotdash: Iax: There is a choice of which kernel in the installation. OldGuru: From my limited understanding, some of the files removed from the post rc2 up kernel affected the APIC, which may be used on a mp capable machine, even if it's using a single/single-core processor. In my case, the box ran the stock FreeBSD kernel and the RC2 up kernel, but using the RC3 up kernel resulted in none of the ethernet interfaces working. Switching to the SMP kernel made everything work again. ty for your help, but Id just like to get my RC2 back, I did an upgrade and I dont see where to select a kernel.Doing an upgrade shouldn't create a problem like this, anyway TY

@la_tengo_como_burro: Has anybody been able to install PFsense on an Intel D201GLUY2 or "Little Valley" Motherboard? Look here, not solved.

According to the blog http://blog.pfsense.org/ the 1.2-RC4 was released January 16th, 2008. If you go to: http://cvstrac.pfsense.com/timeline you can see the commits to RELENG_1_2 since that time.

Got it figured out.  For some reason this board shows 3 interfaces with MACs even thought it only has the 2 (maybe the firewire?).  I was using autodetect for the interfaces, and it was picking up fwe0 for WAN and rl0 for WAN.  I plugged the solid state drive with monowall on it(which works fine) back in, and it had rl0 as WAN and vr0 as LAN.  Manually setting pfsense to those seems to have got it installed and working fine.

1. To verify: NONE of the IP blocks you're using are reserved? (I.E., non-routeable in the Internet)     If so, depending on your setup, this may make things a little weird… 2. Knowing the ports your video conferencing apps use would be very helpful as well as the P2P apps,   assuming they don't change.  If they do, this again could be very tricky.  However if you KNOW   (and I can't emphasize this enough) that ALL of your video conferencing is on one block and ALL of   those file sharers are on the other, then simply using traffic shaping to knock down the bandwidth on   anyone using it all would be an easy fix with the caveat that it would apply to any traffic taking up all   the link.  I realize this sounds like I'm beating around the bush, but P2P app writers and traffic shaper   writers are currently waging a war to see who can beat who: methods P2P apps use include encrypting   traffic so firewalls can't sniff the packets to see what protocol is being used. Anyway, once you know these 2 things, you'll be much more ready to make a decision on how to proceed (or even IF you can!). For the purposes of this discussion as well, it might be useful to know what each network connects to--that is, which side WAN or Internet (not necessarily the same--the WAN could be leased lines or a VPN running over the Internet but separate from it) vs LAN, if there's more than one LAN, etc.  In other words, exactly how you're positioning the firewall in relation to all the networks. I hope this helps. Mike

Ok, here's an update: pfSense is working fine on a different box (the one the store owner wanted to sell me in the first place!).  The errors went away on that box when the 2nd NIC was installed and it boots without error on that machine.  The firewall is configured and running smoothly now! :) The Netvista box wouldn't run with anything.  I'll play with that when I have time, but it's not a priority. And pfSense still doesn't boot on my Acer Aspire 5520-5912 AMD Turion X2 laptop, "oopsing" and spilling registers while still in the boot loader.  I'm taking a wild guess it doesn't like 64 bit chips or laptop hardware, but I really have no idea since it doesn't even hit the kernel yet when this happens. Thanks again to everyone for the help.  And as far as the thread on adding stuff, I'll make sure to read that later–maybe it is better, even on such a simple network as this, to run one machine as dedicated. Mike

Taken to german:  http://forum.pfsense.org/index.php/topic,7719.msg43500.html#msg43500

it's possible upgrade from 1.0.1 to 1.2rc4?

See: http://devwiki.pfsense.org/BootTroubleShooting http://devwiki.pfsense.org/BootOptions You should also try downloading the FreeBSD 6.2 (i386) ISO and see if that produces the same problem.  If it does then it's likely that your hardware (whatever it is - you still haven't said) doesn't work with pfSense/FreeBSD.

I have same problem but my problem was telindus anex B ADSL modem and when I change him with SpeedTuch modem everything work perfectly

eisa peittää

If you meant I should set virtual NIC's setting to "Bridged: Connected directly to the physical network", then yes, I have done that for all 4 virtual NIC's. And in Manage Virtual Network, I have assigned my physical NIC to VMnet0. PS: I only have one physical NIC, hopefully this is not a problem.

To make the DashBoard running after a PfSense update, you shuld do: Remove Dashboard Package Manual edit file /conf/config.xml, and remove from "<widgets>" to "</widgets>" Reboot Reinstall the Dashboard

You can leave them plugged. I suspect you dont have a DHCP on WAN –> per default pfSense tried to get an IP on WAN per DHCP. If it does not got one you have to wait until it times out. It WILL continue after hanging on this line. Just wait long enough.

Hi, just want to give a quick status about the situation: The 8408E (LSI Logic) isn't recognized in FreeBSD 6.2 / FreeBSD 6.3 by the mfi(4) kernel module / kernel. In the system is another SAS RAID Controller - LSI Logic AS1068 (integrated). I got this controller working with PFSense 1.2RC4 and the mpt(4) kernel module! I think this is the controller which Dell calls PERC5/i. Thanks for any interest - and thank you for this great project (best UTM interface out there!). Bye, unknown

Your /var is 17 GB.  Now repeat the du command inside /var.

blocked - myip:137, 138, 1035, & 1447 also occasionally myip:137 (source) - different ip (not physically connected to same network but having same network id):137 I have an 8 port gigabit switch segmented off from our true network to test pfsense. I have 1 NIC from pfsense server going to our real network and the other NIC going to the little 8 porter. I then have a laptop plugged in the switch testing the firewall. Do I need to just unblock these ports? Thnx

I think this might interrest you: http://blog.pfsense.org/?p=149 I usually do it this way.