@torontob: No interest for anyone to take the project for $4000 or because people who committed were not willing to wait longer? Thanks A little of column A and a little of column B.  Doing this project even remotely correctly would involve several thousand hours worth of effort at least and I doubt many developers with the requisite skill set would want to go to all that effort and then try to chase down money from all those different people.  Ultimately, the bounty was retired due to non interest as per the rules of the bounty forum.

Ya, I ask my friend he also do it the same, just act it like server he said. About ping, let's forget it =.=

For the d-link, you are double natting, which I dont like as it can and does break things. I would recommend disabling the DHCP server on the d-link and plug the pfsense cable that was going into the dlinks wan into its lan, after setting a static LAN IP on the router thats in the same subnet as the interface its plugging into. For the rules, I would make the opt rule the same as the LAN rule (if its not working) Otherwise it looks fine to me.

well, i dont know whats causing it but the graphs on the home page are correct, but the rrd graphs are incorrect. The WAN graph is graphing everything (VPN, WAN traffic etc) while the respective graph is empty. Is there a way to fix it without doing a reinstall?

Yeah I ran it on an Ubuntu box next to me same thing, I'm on Windows 7  x64 on my evga 780i. I'll go check that link. EDIT: Just turned traffic shaper on pfsense, got a whopping 61ms of uplink buffering, of course I effectively killed Comcast's speedburst, before I got 4.7 mbp/s on upload, now I got 2.0 mbp/s. Not that it really matters because my config is 13200/2200

@jimp: Why not swap the WAN and LAN ports so the IPMI interface will be on your LAN instead of on the WAN? If it's riding on the same physical port as WAN, that seems like a bad idea in general, but one with an easy solution. Of course, the obvious! Let me try and see if that will work. Although, IPMI may by default be dynamically assigned to the WAN interface depending on what interface you designate as WAN.

Just to followup, the change over went as smooth as can be. Changed IP in WAN settings - hit SAVE. Lost connection. Called Telco - gave the go ahead to make IP change. Clicky Clicky Ping Monitor shows new IP in place. Adjust IP in WebGUI Bookmark - login (ok new cert) - voila! all is well. Good Job PFSENSE Team for making such a rock solid Firewall App - I really (really!) did not want to drive 2.5 hours to make the change in person.

There are no shortage of power strips with network interfaces that you can control via either SSH or an HTTP interface.  APC do various models with individually switched sockets.  You could then easily use a script to SSH onto the power strip and toggle the sockets.

Anyway the problem already solve, Thanks for replying and viewing.

That's correct. This is called - like you just mentioned - Load Balancing. Your topic title is misleading.

Keep in mind that the $600 pays for support hours which can be used over the course of a year.  So if the setup only takes 1/2 an hour, you have plenty more time to use for setting up things like the traffic shaper, load balancing, high availability clustering or upgrading to 2.0 when its released.

Amazing info. Thanks guys. -Bruce

You don't even need to do that. They can be done static, just use a CARP VIP hardcoded to each of your usable IPs. A CARP VIP will have a unique MAC address and make the R2 happy. It may all just work with the CARP VIPs, though you may need to send some traffic sourced from the CARP VIP before the R2 will see it on its IP Allocation page. Easy enough to do from Diagnostics > Command: ping -c1 -S <carp vip=""></carp>

1.2.3-RELEASE built on Sun Dec 6 23:38:21 EST 2009

http://forum.pfsense.org/index.php/topic,31112.0.html