[pfSense] Diagnosing DNS Resolver SERVFAIL issues

2018-05-24 Thread Antonio
Hi, I've been happily using the "Outgoing Network Interfaces" set to my VPN interface to prevent DNS leaks and its been working pretty well until today when all of a sudden it stopped resolving DNS requests. In fact, [fri may25, 03:04 ][user@1:~]nslookup www.google.com Server:

[pfSense] Introducing flexibility of traffic routing when VPN is configured

2018-05-24 Thread Antonio
Hi, a while ago I successfully manage to setup a VPN connect on pfSense. I was a great success as it took me a while to get it working. I followed the guide here: https://www.expressvpn.com/support/vpn-setup/pfsense-with-expressvpn-openvpn/#additional. I have a wired network on 192.168.0.0 where

[pfSense] Custom pass entries for Suricata for all rules, for inline mode

2018-05-24 Thread Steve Yates
I know Bill (bmeeks) hangs out in the web forums but since they're offline, does anyone know if it is possible to allow an IP for Suricata when it's in Inline mode? I see lots of examples like: pass ip 1.2.3.4 any <> any any (msg:"pass all traffic from/to 1.2.3.4"; sid:10;)

[pfSense] Some upgrades from 2.4.2-1 to 2.4.3-1 failed at reboot

2018-05-24 Thread Odette Nsaka
Hi all, I upgraded some pfSense on APU CPU Type AMD GX-412TC SOC 4 CPUs: 1 package(s) x 4 core(s) AES-NI CPU Crypto: Yes (active) from 2.4.2-1 to 2.4.3-1 The first one via cmd-line (VPN - SSH). It was installed with the default single disk ZFS option on SD, then set up (via GUI) to use

Re: [pfSense] Bandwidth Mismatch between pfSense and Data Center Provider...

2018-05-24 Thread Chris L
On May 23, 2018, at 10:57 AM, Chuck Mariotti wrote: > > We've run into a data overage situation at a datacenter... We get charged a > premium per GB over 500GB (yes I know, stupid). Their reporting system seems > to indicate significantly less data usages vs pfSense's RRD

Re: [pfSense] Syntax error in rules.debug for lagg0 (WAN) after upgrade to 2.4.3_1

2018-05-24 Thread Steve Yates
Finally found https://redmine.pfsense.org/issues/8518 which is this bug (the extra incomplete gateway line). Fix seems to be to delete/comment out three lines in /etc/inc/filter.inc: