What you are describing is like you seeing only one NIC.

Ehh. I was just hoping  ;). While that wasn't my biggest concern, I'm glad to hear that I'm able to make changes and still reboot the device(retaining those changes). I just got my ALIX in the mail today…unfortunately, dumb me left my null modem cable at work...and now I'm hungry so there's no way I'm going back tonight! THANKS for the info though!

From the trouble shooting link, the below is what cured my install! Thanks 8) Try using multiple partitions, one small one (~4GB) for / and another for /usr using the rest of the disk.

There are many ways to get in, even adding a rule on the CLI… http://doc.pfsense.org/index.php/I_locked_myself_out_of_the_WebGUI,_help!

@Alan87i: If I run the upgrade too the july 6 snap do you think it will work or die? You mean 2.0.1 RELEASE? Normally, backup your settings and then updgrade. Take a look on packages topic to see if there is any current issue with packages you use.

thanks for your reply

i try this thx

thanks jimp! pfSense-memstick-2.1-DEVELOPMENT-amd64-20120702-2135.img.gz recognized the AHCI mode.

@cmb: now I did, and it works, at least on the fxp NICs.

ok solved it. For any who have similar issue PFsense (any version) cannot be installed using a live CD. You have to physically pull the drive and connect it to a PC then install pfsense, unplug it right after it reboots and it will then work. be great if this pita bug could be fixed.

ahh right yes, it does this and i choose a new MAC for each. Makes no difference still doesnt work.

I solved it so I figured I'd post my solution and mistakes: I was using opt1 for the connection from pfsense to the two linux boxes.  LAN wasn't really doing anything and the pfsense vm had 3 vNetwork Adapters.  I removed one of them from the pfsense box so the WAN was bridged and the second network adapter was connected to vnet2.  I also moved the lan to 10.1.1.x/24. This got everything working as far as I can tell.  Now I'm just playing around with squidguard.

There were binary changes for 2.0.2 that are required to use it, it isn't just a source upgrade. If you gitsync to RELENG_2_0 it will most likely leave you with a broken system. You can gitsync back to RELENG_2_0_1 and get back to 2.0.1-RELEASE code.

Not tar. Can use gunzip, or assuming you're on Windows since you're using Nero, just use 7-zip or your zip program of choice to extract it.

Thank you Jimp its working fine….. have a nice day...