There is no way to do this without setting up your own local copy of the package repository and making pfsense use this afaik.

Install a developer ISO. That contains a lof of things that is stripped out of the release image.
You can add binaries from a stock freebsd 6.1 installed on another box, just copy them over with SCP.

i have my own setup for pppoe and i've patched ppp with Session-Octets-Limit attribute but as i can see pfsense is using mpd i think you can try this patched version to limit session based on traffic: http://www.foggy.ru/soft/mpd/

Regards

hi,
thanks, OK, I will do it!

hi,
yes, I will do it and sorry, for the delay….

In my system log was often written "failed: could not allocate llinfo" and I was looking, whet the reason and the problem for it is. The configuration of the pfsense box(es) is as follows: There are two pfsense boxes (A) and (B) which have a virtual IP and are connected with carp. All interfaces (WAN, LAN and SYNC) have static IPs.

The problem for the system log entry was, that from both boxes (A) and (B) the LAN interface was not coming up correctly. Therefore, the did not work correctly and the system log entry was written. After "ifconfig down" and up, it works and the system log is not any more posted.

At this time, I did not figured out, why the LAN interfaces does comes up correctly. Currently, it is only a test environment and when the pfsense boxes are changed with the right machines, I will see, if the problem exists any more....

Yes, but it's unsupported deep water with no lifeguard  ;)

Some Graphs

status_rrd_graph_img.php.png
status_rrd_graph_img.php.png_thumb
status_rrd_graph_img2.php.png
status_rrd_graph_img2.php.png_thumb
status_rrd_graph_img.php.png_thumb
status_rrd_graph_img2.php.png_thumb

Thanks I found it status_rrd_graph_img.php  ;)

Yes, this is some kind of invalid trafficshaper configuration. Sounds like your parent queue has X bandwidth and you created some childqueues 1,b,c,… with a+b+c+... > X  ;)

Ohh okI didn't realise that it grabed the details from the traffic shaper. I did notice that the interfaces page show the nic speed.

The embedded image forwards the console output to the serial port. If you are using a monitor your not going to see anything after it starts to load freebsd.

Your bootime is related to hardwarespeed and/or wan setting. If you have DHCP at WAN and it doesn'T get a lease right away it might take a bit longer for example.

pfSense's loadbalancer is roundrobin every new connection to the next gateway in the pool. If it doesn't do this it's not configured properly. See http://wiki.pfsense.com/wikka.php?wakka=OutgoingLoadBalancing .

could do i got confused with scott lat time i tryed to do it though will post the diff
again anyway

If /tmp/config.cache exists, it is read otherwise /cf/conf/config.xml

Update:  It turns out that after I updated my onboard NIC drivers to the most current version this version allows you to set the wake-up type (after enabling WOL in APM for the NIC, which is also a setting through this driver) to several different things, one of which was magic packet. Now all is well. Thanks fly out to squarepusher for putting me on to the idea of multiple events triggering a WOL scenario.

I bet this $280 NIC will WOL and then some more…and for that much it better wake me from bed, too.

http://killernic.com/KillerNic/

Make sure you have the ftp helper enabled at the interface where your client is behind.

Seems like this is your gym room as well, eh?

Anyway we really should setup gallery2 to be used as a pfSense Machine Gallery. There we could also provide pfSense screen shots.

Regards
Daniel S. Haischt