This is the sticker/badge I'm gunna get made up as a dummy run, it will be 16mm x 20mm - unless anyone can think of any show stoppers. The first batch will be of 250. [image: badge-rc1.png] [image: badge-rc1.png_thumb]

Others have reported the same thing, where ntop reports just over 50% of traffic as bad. I believe it did have something to do with checksum offloading or NAT causing some checksums to appear bad. Either way it seems to be purely cosmetic.

i dit not allowed anything. but the ssh port (the pfsense ssh) is open on a Carp VIP (with ssh closed in forwarding and rules). i will send you the info asap.

You could sponsor it!

Reboot did the job, quality graphs now working. Must have been a corrupted RRD DB

No.

@wonslung: why not use static dhcp?  it's much more simple than using static ip and the results are the same Agreed.  Static IPs are for servers and network equipment.  Anything the end user touches is DHCP.  Addresses can be reserved so they always get the same one, but no end user equipment is ever static in my environments.

Personally I'd go with IPsec since I'm familiar with it, but it really shouldn't matter. All you'll want is to make sure that the VPN appears as an addressed interface on both ends, then set up the VPS to do NAT with the VPN interface being the "inside".  Configure pfSense with the proper rules so the box you're using is routed over the VPN and you should be good. I don't have my pfSense box hooked up right now (running an 1841 so I can learn IOS) otherwise I'd try it with my dedicated server and post specifics, but maybe someone else can fill in the blanks.

This problem may be solved, but we need testers. Please see http://forum.pfsense.org/index.php/topic,15669.0.html

i think it's more of a function of squid…..it can probably only cache from one wan at a time