Don't think so, no. Active, automatic network diagram spending no time and no money?  Good luck.

@firewalluser: @kevindd992002: @divsys: By default "Pass" rules are not logged (to save log space). If you need to ensure a rule gets logged, check the "Log" box while editing the rule. https://doc.pfsense.org/index.php/Firewall_Rule_Troubleshooting has more info. Got it, thanks! I have an issue with the firewall though. It's been working fine since yesterday. I have different NAT rules to forward connections and other services through NAT (RDP and mail servers included). This is in a test network inside our company. For some reason, I cannot access these services from an external network since yesterday and I've made no changes in the firewall rules. I highly suspect that this is a configuration change in our front end firewall (which I don't have access since my pfsense firewall is just a backend firewall) but I need to confirm if this is really the case. I've been given two public IP's. One public IP is the main WAN connection of my pfsense box and the other is in a NAT 1:1 rule. I don't see any blocks on the firewall logs but when I do a packet capture, I do see that the connections are being logged. That means that the packets do reach my pfsense backend, right? Also setup a separate device running a syslog server of sorts, rsyslog is more compatible, this way if your fw gets targetted you have a separate device with historical logs to check through anything thats been going on as its quite easy to hide activity on pfsense as the gui log only goes back 2000 entries. System log, Settings tab, scroll down the bottom, tick everything and put in the ip address of the syslog server. Dont forget to use a firewall on the device running the syslog server at the very least as well. The more you log everything from every device on your network and isolation the devices on your network, the easier it becomes at spotting anomolies which could be bugs which have exploitable potential, also test how things react when things are not working properly, ie a public facing server when pfsense goes down for example. Sometimes its when things go wrong that new exploits present themselves in conditions which are not usually tested for, aka break things.  :) Thanks for the suggestion but I'll have to plan that for a later date as my pfsense VM is more for personal purposes than for production.

Routinely have thousands of Captive Portal users on a 200M line (Soon 300M) on a 2.1.5 C2758.

Thanks a lot! I think I get it now  ;D

So you say you have reinstalled the box. Did you reconfigure it from scratch? I cannot see any value in reinstalls if you keep importing the same (very likely broken) configuration after that.

Hello, you might to have a look here for some guidance. https://forum.pfsense.org/index.php?topic=98270.0

Dear Johnpz, How do I turn off squid and snort. I am unable to access pfsense through webgui. Should I access the shell from pfsense console and give the following command: killall -HUP squid killall -HUP snort Thank you. Regards, Ashima

I havent had that problem so to avoid resource burn, I'll let someone else step in if google doesnt throw up anything.

Has anyone taken fail2ban and pushed the jailed ips to pfsense.  It does a pretty good job of detecting hacks on the system.  Only problem is I want to move the ip filtering off of my server and on to a pfSense appliance.

@Derelict: This sounds to me like Skype might be checking to see if the private addresses can communicate locally. Only one way to find out and thats to test the scenario, maybe even testing on different subnets behind the same gateway might be interesting.

I would need some wifi devices to have access to the wired file server but I suppose I could set the wired and wireless on different subnet and set specific rules for what can cross over? Tag two SSIDs to the AP.  Put an internal SSID on your internal VLAN and the guest SSID on the guest VLAN. No need for any rules.  Internal wifi clients will be on the same broadcast domain as your LAN.

@jimp: You can set timeouts for TCP on individual rules, just keep in mind you must set the timeout on an interface rule and again on a floating rule (quick, outbound, on the WAN for example) but that gets tricky since by the time the WAN floating rules outbound get parsed NAT has applied, so you may not be able to distinguish based on source address unless you NAT each interface out a different IP address… or if you can match based on destination that would work for certain. Or you can mark the traffic on the LAN in rule and match the mark on the floating out rule.

@dennypage: In my case, it's appears to be the result of the /var/log/dmesg.boot snapshot being created too early in the boot process. Ah, thanks! At least I can work around it with the shellcmd package. Or of course a shell script, but I'm a lazy sod.

Would it work correctly ? Probably.  Try it and see how it goes. Diagnostics - Backup/Restore. What about the packages ? If you backed up your config with packages then they will be reinstalled as part of the restore. Do I need to back up them too ? Obviously.  Otherwise, how would pfSense know to install them?

Might I suggest a sticky at the top of this forum for the majority of people who never read this link https://forum.pfsense.org/index.php?topic=70.0 Example sticky for this forum. –------------------------------------------------------------------------------------ Title:Need help? 20 seconds reading this post to save time. Content: Before posting: 1. Use the FAQ at this link. https://www.pfsense.org/get-support/support-faq.html 2. Use the WIKI at this link for step by step guides & other info. https://doc.pfsense.org/index.php/Main_Page 3. Always search the forum using link top right of this webpage, to limit search to a subform, use the search from within the subforum. keywords work best. 4. Investigate the pfsense bugtracker here https://redmine.pfsense.org/projects/pfsense/issues?set_filter=1 and the pfsense packages bugtracker here https://redmine.pfsense.org/projects/pfsense-packages/issues?set_filter=1 If you dont know the terminology, investigate links like http://www.linktionary.com/f/firewall_term.html & http://www.techrepublic.com/article/jargon-explained-learn-the-terms-used-with-firewall-technologies/ Before posting. If you still havent found the knowledge you are looking for, when describing your problem, question or observation, include the following information. 1. What version of pfsense and the hardware including model of network cards, you are currently or planning to use. 2. Use Gliffy (its free and webbased) to draw your network layout. https://www.gliffy.com/uses/network-diagram-software/ 3. Ensure your post title is descriptive to attract the relevant knowledgable users. Lan problem, wan problem is not descriptive. 4. Describe your problem, question or observation in as much detail as possible to avoid unnecessary questions being posted asking for more information, dragging out the total time it takes for you to resolve your post. Whilst life is hard enough, doing simple things like including the links to places for people to investigate can help which might be noted by seeing an increase in web traffic elsewhere on the site, and a slightly more structured format and increase of relevent information when posting in the forums, hence the suggestion and format for above.

@heper: @coder1: Is that correct? Since wireless isn't enabled until you login to the pfsense computer and configure it. yes sweet! Thanks for the confirmation. Just want to make sure I have everything conceptualized in my head correctly when my switch comes in the mail.

almost every software vendor/developer on the planet uses 'AMD64' to point out that its designed for a modern 64-bit cpu. (also known as x64, x86_64 ) https://en.wikipedia.org/wiki/X86-64#Industry_naming_conventions