@submicron: Use a remote shell?  Given your self-proclaimed extensive experience in all things networking, one would assume that you can come up with an appropriate set of test scenarios to troubleshoot this problem. Never said I couldn't… l33t

The graphs are generated on demand. My suggestion would be to setup something that fetches the webpages or just the graph urls. The status_rrd_graph_img.php will return the rrd graphs. You'll have to look at the status_rrd_graph.php for which arguments you need.

blak111 - :-[  I am so sorry - I did not understand that the first time you said it!  Thank you!  Apologies for being dense ;D Thanks everyone, for your answers and your patience!

Setup a DHCP range for OPT1 and plug one of the switch ports(not the WAN) on the router into OPT1. Also make sure you disable DHCP on the wireless router. It wont be doing any routing or NAT, just acting as a wireless access point. Setup some firewall rules for OPT1 that allow traffic out to the Internet. Then go to captive portal and enable it for the OPT1 interface. Click Enable and then select the OPT1 interface. Select the option for local user manager. Go to the Users tab at the top and add a new user. Once someone connects to the wireless and gets a DHCP address from pfSense they will be prompted with the captive portal page when they attempt to access a web site. They can use the username and password setup on that users page.

All you should have to do is create the appropriate Virtual IPs so you can NAT the addresses, and it should work OK. Is that not working?

You can start here: http://www.paessler.com/ it works fine with the snmp of pfsense, you can download and test it for free.

doesn't work for some reason… tried it.

The 2.0 branch has lagg support, but I would suspect the problem lies with running it in a VM. Do the interface graphs show saturation?

@scottnguyen: why speculate on something far down the road? Is illegal to ask theoretical questions - just out of pure interest ?

Doesn't matter, you can restore a configuration from any version to any equal or newer version, and sometimes older versions. You may not always be able to restore a configuration to an older release, but even that is possible between 1.2.1 and 1.2.  2.0 configurations cannot be used on 1.x, but 1.x configs can be restored on 2.0.

There haven't been any bugs related to outbound FTP since before 1.2 was released. There were a couple issues fixed between 1.2 and 1.2.1 with handling of FTP servers residing inside your network behind NAT, specific to certain configurations where you're using CARP and multiple FTP servers.

I typically find signal 11 related to hardware, and moreover, memory at fault.  You may want to check on the FreeBSD site as well.

Hey, thanks for the reply. I know that it's a different system but I've seen the thing in action. And I have no idea on how it works, that's why I asked.  :) I figure that even if it exists it probably doesn't work with PFS. :) Any thanks for the helping. Bye

There's already a great traffic shaper for pfSense and trafficsqueezer is Linux-specific.  Additionally, there's a good chance that you never got much of a reply to your posts because they are almost incomprehensible.  Slow down, organize your thoughts and type clear, concise sentences and you're much more likely to get a useful response.

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