Error(s) loading the rules // after yesterdays update // 2.0-RC2 (i386) // 26.05
-
Hi,
I've got the exact same problem.
Just did an upgrade 2 hours ago to the latest snapshot (i386,full).scrub in on $WAN all fragment reassemble
scrub in on $LAN all fragment reassemble
scrub in on $AON all fragment reassemble
scrub in on $ all fragment reassemble#System aliases
loopback = "{ lo0 }"
WAN = "{ pppoe0 }"
LAN = "{ em0 }"
AON = "{ em1 }"
= "{ }"
OpenVPN = "{ openvpn }"I then reverted back snapshot by snapshot and found the latest one that works for me is 20110524-1226. The problem starts with 20110524-1717 and isn't fixed by the snapshot which was the latest one 2 hours ago (20110527-0112)
-
When that file is correct, what shows up on that line?
-
loopback = "{ lo0 }"
WAN = "{ pppoe0 }"
LAN = "{ em0 }"
AON = "{ em1 }"
OpenVPN = "{ openvpn }"..
scrub in on $WAN all fragment reassemble
scrub in on $LAN all fragment reassemble
scrub in on $AON all fragment reassembleso.. nothing ;)
-
If someone is still getting this, we'll need to see the output of this then:
global $FilterIflist; include "filter.inc"; include "shaper.inc"; filter_generate_optcfg_array(); var_dump($FilterIflist);You can paste that into the PHP execute box under Diagnostics > Command.
Somehow an empty entry must be sneaking in there, would be nice to know what it is in order to track it down.
-
It would also help to know if you have any of the following enabled: PPTP server, L2TP server, PPPoE server, or IPsec.
-
Here it is:
array(5) { ["wan"]=> array(14) { ["if"]=> string(6) "pppoe0" ["ip"]=> string(13) "[PubIP_ofWAN]" ["type"]=> string(5) "pppoe" ["sn"]=> int(32) ["mtu"]=> string(4) "1492" ["mss"]=> string(0) "" ["descr"]=> string(3) "WAN" ["sa"]=> string(13) "[PubIP_ofWAN]" ["nonat"]=> NULL ["alias-address"]=> string(0) "" ["alias-subnet"]=> string(2) "32" ["gateway"]=> NULL ["spoofcheck"]=> string(3) "yes" ["bridge"]=> NULL } ["lan"]=> array(13) { ["if"]=> string(3) "em0" ["ip"]=> string(11) "192.168.1.1" ["sn"]=> int(24) ["mtu"]=> int(1500) ["mss"]=> string(0) "" ["descr"]=> string(3) "LAN" ["sa"]=> string(11) "192.168.1.0" ["nonat"]=> NULL ["alias-address"]=> NULL ["alias-subnet"]=> NULL ["gateway"]=> NULL ["spoofcheck"]=> string(3) "yes" ["bridge"]=> NULL } ["opt1"]=> array(13) { ["if"]=> string(3) "em1" ["ip"]=> string(14) "[PubIP_ofOpt1]" ["sn"]=> int(30) ["mtu"]=> int(1500) ["mss"]=> string(0) "" ["descr"]=> string(3) "AON" ["sa"]=> string(14) "[IPofNETAddressofOpt1]" ["nonat"]=> NULL ["alias-address"]=> NULL ["alias-subnet"]=> NULL ["gateway"]=> string(5) "AONGW" ["spoofcheck"]=> string(3) "yes" ["bridge"]=> NULL } ["pppoe"]=> array(0) { } ["openvpn"]=> array(4) { ["if"]=> string(7) "openvpn" ["descr"]=> string(7) "OpenVPN" ["type"]=> string(4) "none" ["virtual"]=> bool(true) } }I have an ipsec tunnel configured, but it's inactive (enable ipsec is not checked)
-
Looks like you have a pppoe server entry that's empty.
I added some protections against that just now. Should be fixed in the next snapshot, or you can gitsync now and pull in the change
https://github.com/bsdperimeter/pfsense/compare/a1b86994a0…f40a03a45c
-
Very strange.. never set one up.
I'll gitsync and report back
thank you very much :)
-
GREAT!
Your commit did it ;)Thank you very much!
-
new snap is building now that has those commits in it, so it should be OK once it uploads later this evening.
-
new snap is building now that has those commits in it, so it should be OK once it uploads later this evening.
Awesome, thanks!
This issue creeped up on me Monday's daily build. Decided to come post about it today. Been trying new dailies all week waiting for a fix. Each time after a rule change, manually editing out the empty or erred rules in /tmp/rules.debug
and reloading the rules from the shell.pfctl -f /tmp/rules.debug
