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...

Thank you for the advice! Will give it a shot and post my findings

@SEMIJim: I encounter "shoulds" all day long, day in, day out.  If all the "shoulds" turned out to be reality, my job would be significantly more boring than it is ;) You're right, poor turn of phrase. Steve

It appears to have been arp - pointing out that the CARP interface had a different MAC was the key - thank you so much!

No, just in case customers ask. I am happy with default package :)

That would be great!.

I hope you meant 172.16.1.x range, since 172.168. is a routeable IP address used on the Internet… To access your D-Link change the IP of your desktop/laptop to 192.168.1.2 and then set the IP of the D-Link to be something outside of the DHCP range pfSense is allocating (eg 172.16.1.2).

Those are strictly for the WRAP because of a BIOS bug it has that won't be fixed by PC Engines since it's end of life. The 4801 and all other hardware must use the standard images. The 4801 works fine.