No, you cannot patch binaries with System Patches. Fix your log parser instead.

What happens if you disconnect the printer and reboot pfSense?

Also check your firewall logs to see if anything gets dropped on WAN when you're testing.

Read carefully what exactly I put and quote me if you can where I have associated these problems to the NSA. In the mean time enjoy paying your tax dollars to fund the terrorists!  ;D

This explains some of the challenges. http://ro.ecu.edu.au/cgi/viewcontent.cgi?article=1099&context=adf But there are things the researcher of this paper failed to mention, which is all Torrents have in common and Harvey66 mention, they do still have common characteristics or patterns. Like Harvey66 mentions, let the identifiable traffic go through Pfsense unhindered, the unidentifiable traffic can be NAT'ted through the Sophos box and then you can blame the Sophos box.

Hi, I guess you are right. "Certs" are backed up when you select "All" - you can find them in the exported config.xml file - search for the <cert>lines. But, some possibilities exist. Just edit the exported config.xml file - keep intact the format, throw everything away except the <cert><refid>54ca2cf9af6xx</refid> <crt>LS0tLS1CRUdJTiBDRVJUSUZJQ0..............................S0tLS0NCg==</crt> <prv>LS0tLS1CRUdJTiBSU.......................EgUFJJVkFURSBLRVktLS0tLQ0K</prv> <caref>54ca2cbc230bb</caref></cert> parts. Import your modified file. Note : respect the XML format, otherwise be prepared for special effects ;) Another idea : what about adding       "cert" => gettext("Certificats"),   to the file diag_backup.php - around line 190 ;)</cert>

Glad you got it working.

yep works like a champ after a reboot, not sure how I would have screwed it up but its working now thanks

Maybe Daypassers is a reference to a time schedule that allows access to the internet based on time of day, ie killing net access off at night to stop all night online gaming sessions. It might be easier if you setup your own pfsense box from scratch for net access, still keep your dads setup to learn from if you want to learn from it, but at least you have your own firewall setup which you can setup and learn from whilst making net access easier or less of a hassle when you have mates round who want some net access for their devices as one possibility. One of the main risks with swapping out your dads pfsense setup with your own, is if you have missed anything that stops one or more of your other devices from working that needs net access. If you do setup your own box, for a starter, you could do a trial run by downloading something like Virtualbox and install a virtual pfsense (FreeBSD). You can then add as many different networt connections to the virtual pfsense to mirror your dads network connection, and then compare the XML backups to look for differences to learn from. Virtual box lets you set up some pretty exotic networks virtually and using the physical network connections on the machine, so you can setup some pretty complex networks if you wanted to. Anyway good to here you got the net access working at least.  :)

Those look similar to what is found here. Are you talking regular pfSense or the ADI version. I would think the ADI version has those covered.. https://www.netgate.com/docs/rcc-dff-2220/freebsd.html

hi there I already made a guide and working perfectly to log the firewall see pictures. What im stuck and working on is to log the system logs for pfSense. [image: Clipboarder.2015.08.30-014.png] [image: Clipboarder.2015.08.30-014.png_thumb]

Here is an extra piece of potential useful information. The traffic data for the 3 month, 1 year, and 4 year periods which use 1 day averages appear to be correct. http://postimg.org/image/gpz0bxo43/full/

@Derelict: OP didn't say he was connecting LAN and WAN to the same switch. @Towawi: …then plug it into both the LAN and WAN port on my pfSense box... Don't do that! Better use the doc.pfsense article chpalmer linked. Consider Wan dirty and separate it as good as can be from your Lan.