Then you don't have the proper provisioning to route the subnets to interfaces behind a router. https://docs.netgate.com/pfsense/en/latest/firewall/additional-ip-addresses.html#multiple-ip-subnets It doesn't sound like you are 100% on what it is you have there. I would read that first link in its entirety.

There is no setting for that in the GUI because generally speaking it's a terrible idea. There are a few threads here on the forum discussing it but highhly recommend you don't read them! Automatically updating without reading the release notes etc opens you up to the possibility of the firewall updating and rebooting at some inconvenient point. And at worst failing to reboot because of some required manual step that didn't happen. Now imagine how bad that might be is you're remote from the firewall and using it for VPN etc.... Subscribe or check the blog to get update announcements: https://www.netgate.com/blog/ Steve

@stephenw10 said in pfSense for 2 LANs: Yup, you can't do that in pfSense. Then I would setup pfSense between the switch and CentOS and configure is as routed only, no NAT, do CentOS can see the real source IP of clients. And to avoid double NAT which is bad in general. Steve Yea, that's what @viragomann suggested me. Next week I'll buy a new switch VLAN capable and do this. Thanks for now.

VBox on a desktop works well for a test like this. I used it for years until I got Proxmox setup. Steve

@anis_ferchichi said in barnyard is no longer exist: barnyard Hi, Recommend to your attention (from @bmeeks) : https://forum.netgate.com/topic/154632/attention-barnyard2-users-for-snort-or-suricata-please-read-this-notice?_=1606476384817

Ah, good to hear. Thanks for reporting back.

@jimp Yes would love this feature as wel. Tested it and works really fast en easy to setup. Timeline even for beta release would be great. OpenVpn has so much overhead, and just does not meet the speed requirements with low(er) end hardware.

@stephenw10 For me, just unplugging and reconnecting the WAN cable was enough to cause the change. The last time my prefix changed was almost 2 years ago, when there was a problem with the CMTS at my ISP.

@stephenw10 P.S. in case I did not imply it, Thank you for helping me. If you're ever in Illinois, I'll buy you a $drink

Yes, I understand. The goal of resetting the state table after enabling the rule is to understand whether the rule is not matching the traffic or you are not killing the required states when you kill them individually. It's probably the latter since it's very easy to use a filter expression against the state table that cannot be used the kill states. Steve

Opened a feature request: https://redmine.pfsense.org/issues/11102 Add a comments there if more is needed. Steve

Also just an FYI. I ran a file check 4 times and it came back clean everytime. It appears if I run a file check then reboot. PFSense will reboot just fine and obtain an IP. But if I don't run a file check, more often then not. It will not obtain an IP until I reboot like 4-8 times in a row.

I have seen that before if the firewall is under significant DDoS attack. It logs every blocked connection by default but you can disable that by unchecking Log firewall default blocks in Status > System Logs > Settings. Or by adding your own block rule on WAN without logging enabled. That leaves other blocked traffic still available for troubleshooting. What are you seeing in the logs currently? Steve

It's probably because you're sending all your traffic across the VPN, including the registration from the plex server. You probably want to exclude the plex server from the policy routing so it just uses the WAN directly. Steve

@ramses-sevilla said in Where are log files system / openvpn / firewall saved?: Do you know where are saved all log files? Here : [image: 1606133392678-4adabe7f-662f-4121-a70f-79ea8df481e5-image.png] Or here : /var/log/ ( as any othor unix/linix/freebsd/openbsd/etc OS) Note that : @kiokoman said in Where are log files system / openvpn / firewall saved?: 2.4.5 use a binary circular log format known as clog to maintain a constant log size without the need for rotation is a silent hint that explains the need of a quick Google lookup. Or reading the pfSense manual. As https://docs.netgate.com/pfsense/en/latest/monitoring/logs/manage.html or https://docs.netgate.com/manuals/pfsense/en/latest/the-pfsense-documentation.pdf page 139

@Cporter said in See all devices: Does that mean others have the same question and want to see the answer? Noop. They probably read, and abandon. You have a router on the LAN of pfSense. All that can be seen from a pfSense point of view is : the IP of the router source, and traffic to some other IP, where ever on the Internet. It is impossible to see or know what device are behind the router that emitted that traffic. The same goes for your ISP : they can not see if you have one PC, or 100 PC's behind your ISP router. It's part of the concept of routing. So : the fast answer is : your question doesn't make sense - is impossible to answer. You should use a switch behind pfSense, and attach all devices to this switch.

Hi, Open console or SSH. When you see the menu, chose option 8. Goto the root directory : cd / Execute du -h -d 1 From the list shown, take the biggest directory and 'cd' into it : Example : you find that the /var directory is the biggest one : cd /var and repeat the 'du -h -d 1' command, cd into the biggest etc. Report what you have found. To list a directory, type ls -al to see all the files and details. Example : [2.4.5-RELEASE][admin@pfsense.brit-hotel-fumel.net]/var/log: ls -al total 108324 drwxr-xr-x 9 root wheel 1024 Nov 12 09:51 . drwxr-xr-x 32 root wheel 512 Nov 12 09:51 .. -rw------- 1 root wheel 511488 Nov 23 08:41 dhcpd.log -rw-r--r-- 1 root wheel 9832 Nov 12 10:47 dmesg.boot -rw------- 1 root wheel 511488 Nov 2 11:09 filter.log -rw------- 1 root wheel 511488 Nov 20 11:53 gateways.log -rw------- 1 root wheel 511488 Nov 25 2018 ipsec.log -rw------- 1 root wheel 511488 May 9 2016 l2tps.log -rw-r--r-- 1 root wheel 0 Jan 29 2015 lastlog drwx------ 2 www www 512 Jan 13 2020 lighttpd drwxr-xr-x 2 munin munin 512 Jul 13 12:11 munin drwxr-xr-x 2 root wheel 512 Apr 6 2020 nginx -rw------- 1 root wheel 1000000 Nov 23 08:35 nginx.log drwxr-xr-x 2 root wheel 512 Jan 29 2015 ntp -rw------- 1 root wheel 511488 Nov 23 04:51 ntpd.log drwxr-xr-x 2 uucp uucp 512 Mar 19 2020 nut -rw------- 1 root wheel 511488 Nov 23 05:34 openvpn.log -rw------- 1 root wheel 232 Nov 23 08:43 openvpn.status drwxr-xr-x 2 root wheel 512 Nov 23 06:00 pfblockerng -rw------- 1 root wheel 511488 May 9 2016 poes.log -rw------- 1 root wheel 511488 Nov 23 06:44 portalauth.log -rw------- 1 root wheel 511488 Jun 4 08:40 ppp.log -rw------- 1 root wheel 511488 May 9 2016 pptps.log drwx------ 5 root wheel 512 Apr 19 2018 radacct -rw------- 1 root wheel 8634282 Nov 23 08:40 radius.log -rw------- 1 freeradius freeradius 12320 Nov 23 06:44 radutmp -rw------- 1 freeradius freeradius 0 Apr 17 2018 radwtmp -rw------- 1 root wheel 511488 Jul 27 2016 relayd.log -rw------- 1 root wheel 511488 Nov 22 21:33 resolver.log -rw------- 1 root wheel 511488 Nov 20 11:53 routing.log -rw-r----- 1 root wheel 89196103 Nov 23 06:44 sqltrace.sql -rw------- 1 root wheel 511488 Nov 23 08:03 system.log -rw------- 1 root wheel 2158303 Nov 12 10:47 userlog -rw-r--r-- 1 root wheel 591 Nov 23 07:23 utx.lastlogin -rw------- 1 root wheel 192348 Nov 23 07:23 utx.log -rw------- 1 root wheel 511488 May 9 2016 vpn.log -rw------- 1 root wheel 511488 Oct 25 2017 wireless.log

I think will start an ISP and call my packages.. .Ultimate Fiber 10ge, in the small print just put *fiber is used somewhere in the connection when you go to google.com - we promise that 100% ;) Your connection speed may vary..

That site comes up with tls 1.3.. [image: 1606053080061-site.png] So I don't think your setting had anything to do with fixing whatever issue you were having with the site. Maybe the cert was expired before.. With a 90 day cert age, and it being good til feb 13, would mean it was just recently renewed.. 11/15/2020, 4:03:38 PM (Central Standard Time) To be exact ;)