Re read jimps post, they are working fine. Don't use system tunables unless you know exactly what you are doing it are told to do so by someone who does.

Have you verified that your cable provider isn't doing some night time maintenance?  What do the cable modem logs show?

Not sure whether it's normal or not, anyway, the logging apparently is configurable via GUI.

And how would that work when its IP is not in that network.. Your gateway has to be in the same network as your IP.. So its IP is 192.168.89/24  What is pfsense IP in that network??  That would be your switches default gateway. Why would your switch need multiple svi's for management?? If you say you can get to its IP you have on its vlan 1 to manage it.. Its IP in the 192.168.89 serves no purpose if its not going to do routing for that vlan..

I can't answer your question as to how to see swap usage per process, however you might want to check these out: https://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/misc.html#idp60039016 https://forums.freebsd.org/threads/22576/ Basically, if you aren't experiencing performance issues or if you don't have write sensitive media then things are probably performing as designed. However, if you do have write sensitive media you have a couple of options: You can turn swap off: Manually, I believe you just remove it from /etc/fstab? Google knows though Do a clean install and specify 0 for swap size You can create a small RAM disk and run swap there. This is kind of counter-intuitive but if you need to avoid writes but are worried that the system may have issues without any swap at all it's a workaround. Unless you're having issues I would just leave it as is. FWIW I've disabled swap on my install (write sensitive media) and have had no issues yet, although I still wouldn't recommend it without a reason to do so.

@doktornotor: Sorry, I still don't follow. What access to WAN port? Plus, as discussed elsewhere, there's nothing wrong with your DNS. From full access I was trying to say that I was able to communicate through that port, with DNS, internet, … and there was no limitation resultant of the gateway state who was unknown in that time, from lan ports. Dont know if was that your question  :-\ I have already figure out what was happening, I have already posted the solution that I have found to solve the DNS problem in the first topic where you start helping.

A span port would be done on your switch.. Not on pfsense with a bridge.

Apologies, I really thought I had responded to this. The issue did in fact prove to be a faulty GS748Tv5 switch, where a fan had failed - yet somehow did not flag up in the GUI or in the status light in the front panel. For the past 4 weeks or so, on restarts have been required. Thanks for all your help.

Agreed. I may add "Copy to clipboard" functionality as well since that was just developed for other pages in the GUI

easyrule is not intended to be used as an API of sorts. It's meant to be an easy way to add a simple rule from the logs or console and not an all-purpose configuration manipulator. It isn't going to be given advanced capabilities such as this.

So if that is the case is the prefered method to have the multiple nic ports on separate subnets and have Pfsense route all ther traffic between the different machines rather than bridging ?. Blue screen was inaccurate.  It kernal paniced and locked up refusing remote access at all.  I had to hard reboot it and go back to the last known good config. It occured multiple times as soon as I added the webmanagement interface to a LACP group.  Without adding this interface, LACP works fine. Would love to hear for anyone with advise on how best to make all ports available for a home network.  Perfect is nto required.  Working well is good enough. Thanks Update:  It is a hard crash reboot not a hang and it was when I just added 3 of my 4 Intel i340-T4 ports to a LAGG (LACP).  As soon as I saved the server rebooted.  Port 1 (interface 0) was not added as it is my admin interface.

mount /dev/ada1 /mnt        >  Operation not permitted mount /dev/ada1s1a /mnt    > Device busy mount /dev/ada1s1 /mnt      > Operation not permitted mount /dev/ada1s1b /mnt    > Invalid arguement

You could back up your config and try a fresh install but honestly this sounds like a hardware issue.

If you apply the schedules in the inverse way, set scheduled rules to allow traffic, the states created by that schedule should be dropped when it ends. You can prevent that by setting "Do not kill connections when schedule expires" in    System > Advanced > Miscellaneous. Steve

Thank you Very Much KOM your a big help its working now… i just reset.