1.3 beta/alphas will be begin soon which has FreeBSD 6.3.

yes, the process is basically the same like when writing the image to a cf-card.

@heiko: Really, please try rc5, it is the latest snapshot.. Maybe, a broken CD ? http://snapshots.pfsense.org/FreeBSD6/RELENG_1_2/iso/pfSense.iso.gz (Live CD) http://snapshots.pfsense.org/FreeBSD6/RELENG_1_2/updates/pfSense-Full-Update-1.2-RC5.tgz Greetings Heiko The rc4 was even hanging so I installed the developer version http://snapshots.pfsense.com/FreeBSD6/RELENG_1_2/iso/pfSense-1.2-RC4-Develops-LiveCD.iso and its working fine. Now I want to knw whats the difference b/w standard and developer editon. And How do I upgrade to standard rc5 installation, Is it possible?

Well tried it out in a variety of ways.  But from the looks of it the NICs are not supported.  I'll look into fixing the problem if I can when I have the time.  It was a good idea while it lasted.

How were you able to intall PSENSE on the D201GLY2 motherboard? I have not been able to intall it not even using the embedded version? after formatting and partitioning it will not intall anything. And with the embedded version, it freezes at boot. Did you disable anyting on the BIOS? are you intalling on a Hard Drive or a CF card?

Then there is really something wrong with your cable or your local comport on the terminalemulationclient.  :(

still having the same problem here, even informing the linux reported hd geometry I got this BTX error; when I try to use grub, it gives me an 18 error message at boot (80gb hd) what can I do? I dont know what else to do… thanks

I am using a Dell Dimension 2300 (pfSense 1.2 RC4 clean install), I had my serial ports disabled and was getting the same problem as you, system locks at line: sio0: configured irq 4 Enabled Serial Port in BIOS, works fine now.  Thanks for the post!

pfSense is based on FreeBSD.  FreeBSD != Linux ;) Try using the FreeBSD 6.2 installer ISO.  That will tell you whether or not your hardware is supported.

sorry but I downloaded this snapshot today, right before trying to install it; thanks

It seems that a reboot resolved the problem. I suspect a DNS issue caused the problem. I changed the DNS server info before staring package installation. Although ping from webinterface to <any internet="" host="">did then work, installing packages did not. After reboot all is OK. Regards, Bert</any>

In my case timeout timed me out. So I installed again, with no wired NICs. Then timeout seemed a lot faster. Regards, Bert

@gmckinney: Try setting the USB to 1.1 instead of 2.0 in the bios - if I remember correctly there was an issue with that, at least in the Alix 1c version - not sure about the Alix.2c2 version - it could be a bios issue there - are you running the bios version 99 ( http://www.pcengines.ch/alix2.htm ). Also - if you search the forums you will find a "different" method to flash the Alix bios images to the unit instead of the FreeDOS method. gm… Thanks!  Shutting off USB in the BIOS at least got me up and running.  I'll work on updating the BIOS as time allows.  Wonder why it worked before today? – Dave W.

More informations are needed to help. Where do you get the error? Since you're installing to a CF i assume you're installing the embedded version. Could it be that the CF card is dead?

@mhab12: Any of you using squid? NO, Its not squid or any package causing the problem, I just ran a speed test with a fresh install showed my upload as 384K when its actually 1400K. Seems a had the same proplem with RC3 aa few months ago, but I had my RC2 cd around and just reloaded it,but my cd is now lost. I thought my P3 800 might not be enough, even though it has been,so I loaded it on a FX60 with 2 gigs of ram, still slow.

@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