Adam, Sorry for the delay, yesterday was a crazy day! The box that Storm put in is not a switch at all (that's what the guys called that installed it), it's a router that can do PPPoE. The brand is MikroTIK, type is 750UP. I suppose they have it set up in pass-through, so packets are just passed along. It does solve the problem though. -Rob-

Working perfect after replacing the RAM. Thanks!

We don't consider SSDs (mSATA or otherwise) or eMMC as "embedded filesystems" in the traditional sense. They are high quality current-tier disks and don't suffer from the classic limits of flash media like CF or SD cards. They get full installations and can run any packages, assuming they don't eat up all the disk space and RAM of course.

your sure its not 127.0.0.1??  172.0.0.1 seems odd… Does your trace return this for the name? ;; ANSWER SECTION: 1.0.0.172.in-addr.arpa. 7200    IN      PTR    172-0-0-1.lightspeed.brhmal.sbcglobal.net. Can you post up this traceroute..  Are you in Birmingham, Alabama area??  That is what I believe brhmal stands for.

Don't setup squid as a transparent proxy.  It won't do anything to filter HTTPS sites.  If you decide to go the squid route, run it in explicit mode in conjunction with WPAD.

hi I find a way to solve this. use ssh connect to server and edit /etc/inc/services.inc file find {$custoptions} below this add this option dhcp-parameter-request-list 125; and save file restart dhcp it work fine

Just had an epiphany, the traffic stops look like they all happen just after the hour. within the first 5 minutes of the hour, must be a hourly cron job that is causing the problem?

Everything on the same LAN?  Your router should have nothing to do with it.  Are you crossing subnets? If your talking having your DVR on one connection and the cameras on another thats a different story.  (with the pfSense WANs in the path) Cameras open to the internet?  Can you see them from outside your setup?

I spun my 2.3 test box up to the 2/15 build this morning and it seems as though the patch works as expected: Testing methodology: Added 2 ports to a bridge Rebooted to verify that the config xml was sane (it was) Removed 1 of the ports Rebooted Removed other port Everything seems OK.

i have upgraded 2 month ago so i have the 2.2.6 version Jahonix :  i will do that tomorrow , i have phisycal access to pfsense

I will try another cable and check the MTU setting to see if that helps But the only thing is this issue with the speed taking a nosedive happened after I put Pfsense into the equation before 15down 2 up was the norm. but back to the drawing board And, KOM man i cant thank you enough for all the you have offered so far!!

Thanks. I had previously found the List mailing list, but didn't want want to clutter my inbox. I looks like there is a list that is just for announcements, and looking at the last several months of archives the only emails sent at all were new release announcements. https://lists.pfsense.org/mailman/listinfo/announce

Adding some comment here: As far as I understand, importing user's certificate in pfSense is not mandatory as long as OpenVPN server certificate is issued by same (or trusted) CA but not importing these users certificates will mean that revoking it will not be feasible or at least easy. Am I correct ? ???

Found this that seems to answer this question: http://timita.org/wordpress/2011/07/29/protect-your-windows-laptop-with-pfsense-and-virtualbox-part-1-preamble/

The mechanism for disk writes in pfsense for nanobsd was changed in 2.2.3 or somewhere around there.  Net effect was exactly what you are describing but it should have been fixed in 2.2.4 if memory serves.  Fact that you are using 2.2.6 I would not think you should be seeing that behavior.  Try a different USB key.  I have the same chipset (BLKD2500CCE Intel Desktop Board D2500CC) but I'm using a USB to SATA flash card adapter SYBA SD-ADA50024 and a WinTec FileMate 8GB 3FMCF8GBS-R compact flash card.  My backups are several Kingston DataTraveler USB keys (if the sata to USB dies) but I haven't used those enough (other than just booting to confirm functionality) enough to know if they have the slow down you describe or not. https://doc.pfsense.org/index.php/2.2.4_New_Features_and_Changes#Security.2FErrata_Notices The forcesync patch for https://redmine.pfsense.org/issues/2401 is still considered harmful to the filesystem and has been kept out. As such, there may be some noticeable slowness with NanoBSD on certain slower disks, especially CF cards and to a lesser extent, SD cards. If this is a problem, the filesystem may be kept read-write on a permanent basis using the option on Diagnostics > NanoBSD. With the other above changes, risk is minimal. We advise replacing the affected CF/SD media by a new, faster card as soon as possible. https://redmine.pfsense.org/issues/4814

than you both very much

https://forum.pfsense.org/index.php?topic=9642.0 got solution from this article