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.

Hey Alex Indeed, I recompiled the kernel under FreeBSD 8.0 removing the references to USB and I am able to boot pfSense 2.0. But my network cards are not working. I am really puzzled. My plan B is to install Linux and to get pfSense working inside a qemu virtual machine.

not sure what the plans are there. Eventually we'll have a more full-featured notifications system but that won't be ready any time soon. When that happens, notifying of a mirror failure would be possible. Not sure about mirroring to a loopback device or anything like that, that's all up to gmirror. We can't really automate a lot there safely.

Did you shutdown the first server before starting the second server? If they are running concurrently on the same network you will have multiple interfaces with the same IP address - an invalid configuration. In this case, PERHAPS "setting up gateway monitors" got stuck because a necessary response got sent to the correct IP address but the "wrong" interface.

Got the firewall up.  The interface has to be named and rules set before interface can be activated. My friend and I worked on this for a couple hours to get working. I have firewall up for 3 days now testing before I deploy it. I have a config with passwords XXXXX out if there is a way to post it, I would like to know. Bob

cmb hay thanks for the reply I really do appreciate it. I looked and I do have the CRL certificates for each of the road warrior client machines, do I enter them in the cert manager? Then what about the user accounts, is that something on top of OpenVPN authentication? Is it optional (must be)? That's all my questions, thanks again for shedding light on this for me.  And Oh I looked back and it was back with IPCop that I had individual control over the each client cert, I've not been able to do that sense I moved over to PFSense, until now. Take Care BigBSense!