Internet unstable after enabling pfBlocker

Hey there…

I have some big issue with pfblocker and my stable FTTH connection.

I´am sitting on a 500/500mbit FTTH connection and after i enable pfblocker and use the entire speed for downloading things my entire pfsense-box goes offline. it does not reboot, but all connection to the Internet stoped.

So i have to turn off pfblocker and reboot my pfsense-box to get my internet to work 100% stable.

any ideas if my pfblocker is configured to much or if it just the hardware in the box who is to slow to handle all the pfblocker traffic through the 500mbit.

greetings




I’m running the development version and I see there is a new update v2.2.5_32 available (I’ve not updated).

If you are running the latest version perhaps there is an issue with that version.

I believe there is way to save pfblocker settings, if so, reinstalling the package might be the way to go.

Depending which version you are running you could try the the other stable/development package and see if you get the same result.

the problem is, i allready uninstalled and reinstalled the plugin several times. doesnt matter if i use the stable or the dev version. At the moment i use the dev version on 2.2.5_30 and now update to the latest. Lets hope that fix the problem.

now i tested with the latest update of pfblocker. But i have still the problem with the bad connection. :frowning:

Well, you have, as you know, an instability issue. The question is whether it is software or hardware related. (1) I would backup your settings and reinstall pfSense/packages/settings to rule out the software. If it persist still, then (2) I would install pfSense/packages/settings on different hardware. If it still persist, then (3) I would reinstall new pfSense, packages, and settings on the hardware that is different from the pfSense box you’re using now. One of either 1/2/3 is going to give you a situation where you have stability again. You now just have to rule stuff out to find it.

I think i found the issue, but can´t resolve it :confused:

Take a look at the last part of the config. This error am i getting every time.

May 29 19:35:08 pfsense php-fpm[43595]: /rc.start_packages: Restarting/Starting all packages.
May 29 19:35:09 pfsense php: [pfBlockerNG] DNSBL parser daemon started
May 29 19:35:09 pfsense php-cgi: haproxy: starting old pid:none
May 29 19:35:09 pfsense php-cgi: haproxy: started new pid:41214
May 29 19:35:12 pfsense php-fpm[43595]: [pfBlockerNG] Starting firewall filter daemon
May 29 19:35:12 pfsense php_pfb: [pfBlockerNG] filterlog daemon started
May 29 19:35:12 pfsense php_pfb: [pfBlockerNG] filterlog daemon started
May 29 19:35:12 pfsense php: [pfBlockerNG] DNSBL parser daemon started
May 29 19:35:13 pfsense getty[33237]: open /dev/ttyv0: No such file or directory
May 29 19:35:38 pfsense check_reload_status: Syncing firewall
May 29 19:36:59 pfsense check_reload_status: Syncing firewall
May 29 19:41:42 pfsense check_reload_status: Syncing firewall
May 29 19:42:53 pfsense check_reload_status: Syncing firewall
May 29 19:42:59 pfsense check_reload_status: Syncing firewall
May 29 19:43:00 pfsense check_reload_status: Syncing firewall
May 29 19:43:20 pfsense php: [pfBlockerNG] No changes to Firewall rules, skipping Filter Reload
May 29 19:43:28 pfsense check_reload_status: Syncing firewall
May 29 19:43:29 pfsense check_reload_status: Syncing firewall
May 29 19:54:02 pfsense check_reload_status: Syncing firewall
May 29 19:54:06 pfsense php: [pfBlockerNG] No changes to Firewall rules, skipping Filter Reload
May 29 19:54:08 pfsense check_reload_status: Syncing firewall
May 29 20:00:00 pfsense php: [pfBlockerNG] Starting cron process.
May 29 20:00:03 pfsense php: [pfBlockerNG] No changes to Firewall rules, skipping Filter Reload
May 29 20:28:27 pfsense php-fpm[345]: /index.php: Successful login for user ‘admin’ from: 192.168.166.204 (Local Database)
May 29 20:28:41 pfsense check_reload_status: Syncing firewall
May 29 20:29:03 pfsense check_reload_status: Syncing firewall
May 29 20:44:06 pfsense php-fpm[345]: /index.php: User logged out for user ‘admin’ from: 192.168.166.204 (Local Database)
May 29 20:44:21 pfsense php-fpm[345]: /index.php: Successful login for user ‘admin’ from: 192.168.166.204 (Local Database)
May 29 21:00:00 pfsense php: [pfBlockerNG] Starting cron process.
May 29 21:00:03 pfsense php: [pfBlockerNG] No changes to Firewall rules, skipping Filter Reload
May 29 21:14:39 pfsense check_reload_status: Syncing firewall
May 29 21:16:30 pfsense check_reload_status: Syncing firewall
May 29 21:19:03 pfsense rc.gateway_alarm[79877]: >>> Gateway alarm: WAN_DHCP (Addr:xxx.xxx.xxx.xxx Alarm:1 RTT:6.747ms RTTsd:5.981ms Loss:21%)
May 29 21:19:03 pfsense check_reload_status: updating dyndns WAN_DHCP
May 29 21:19:03 pfsense check_reload_status: Restarting ipsec tunnels
May 29 21:19:03 pfsense check_reload_status: Restarting OpenVPN tunnels/interfaces
May 29 21:19:03 pfsense check_reload_status: Reloading filter
May 29 21:19:03 pfsense check_reload_status: Linkup starting re0
May 29 21:19:03 pfsense kernel: re0: watchdog timeout
May 29 21:19:03 pfsense kernel: re0: link state changed to DOWN
May 29 21:19:04 pfsense php-fpm[346]: /rc.openvpn: Gateway, none ‘available’ for inet, use the first one configured. ‘WAN_DHCP’
May 29 21:19:04 pfsense php-fpm[346]: /rc.openvpn: Gateway, none ‘available’ for inet6, use the first one configured. ‘WAN_DHCP6’
May 29 21:19:04 pfsense php-fpm[346]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN_DHCP.
May 29 21:19:04 pfsense php-fpm[346]: /rc.linkup: DEVD Ethernet detached event for wan
May 29 21:19:05 pfsense check_reload_status: Reloading filter
May 29 21:19:06 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:06 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:06 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:07 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:07 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:07 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:07 pfsense check_reload_status: Linkup starting re0
May 29 21:19:07 pfsense kernel: re0: link state changed to UP
May 29 21:19:07 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:07 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:07 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:07 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:07 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:08 pfsense php-fpm[346]: /rc.linkup: DEVD Ethernet attached event for wan
May 29 21:19:08 pfsense php-fpm[346]: /rc.linkup: HOTPLUG: Configuring interface wan
May 29 21:19:08 pfsense check_reload_status: rc.newwanip starting re0
May 29 21:19:08 pfsense php-fpm[346]: /rc.linkup: calling interface_dhcpv6_configure.
May 29 21:19:08 pfsense php-fpm[346]: /rc.linkup: Accept router advertisements on interface re0
May 29 21:19:08 pfsense php-fpm[346]: /rc.linkup: Starting rtsold process
May 29 21:19:09 pfsense check_reload_status: Syncing firewall
May 29 21:19:09 pfsense php-fpm[40423]: /rc.newwanip: rc.newwanip: Info: starting on re0.
May 29 21:19:09 pfsense php-fpm[40423]: /rc.newwanip: rc.newwanip: on (IP address: xxx.xxx.xxx.xxx) (interface: WAN[wan]) (real interface: re0).
May 29 21:19:10 pfsense php-fpm[346]: /rc.linkup: Gateway, none ‘available’ for inet, use the first one configured. ‘WAN_DHCP’
May 29 21:19:10 pfsense php-fpm[346]: /rc.linkup: Gateway, none ‘available’ for inet6, use the first one configured. ‘WAN_DHCP6’
May 29 21:19:10 pfsense check_reload_status: Restarting ipsec tunnels
May 29 21:19:15 pfsense check_reload_status: Syncing firewall
May 29 21:19:15 pfsense check_reload_status: updating dyndns wan
May 29 21:19:15 pfsense check_reload_status: Reloading filter
May 29 21:19:24 pfsense check_reload_status: Syncing firewall
May 29 21:19:45 pfsense kernel: re0: watchdog timeout
May 29 21:19:45 pfsense kernel: re0: link state changed to DOWN
May 29 21:19:45 pfsense check_reload_status: Linkup starting re0
May 29 21:19:46 pfsense php-fpm[346]: /rc.linkup: DEVD Ethernet detached event for wan
May 29 21:19:47 pfsense check_reload_status: Reloading filter
May 29 21:19:48 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:48 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:49 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:49 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:49 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:49 pfsense check_reload_status: Linkup starting re0
May 29 21:19:49 pfsense kernel: re0: link state changed to UP
May 29 21:19:49 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:49 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:49 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:49 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:50 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:50 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:50 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:50 pfsense php-fpm[63138]: /rc.linkup: DEVD Ethernet attached event for wan
May 29 21:19:50 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:50 pfsense php-fpm[63138]: /rc.linkup: HOTPLUG: Configuring interface wan
May 29 21:19:50 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:50 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:50 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:19:50 pfsense check_reload_status: rc.newwanip starting re0
May 29 21:19:50 pfsense php-fpm[63138]: /rc.linkup: calling interface_dhcpv6_configure.
May 29 21:19:50 pfsense php-fpm[63138]: /rc.linkup: Accept router advertisements on interface re0
May 29 21:19:50 pfsense php-fpm[63138]: /rc.linkup: Starting rtsold process
May 29 21:19:51 pfsense php-fpm[58663]: /rc.newwanip: rc.newwanip: Info: starting on re0.
May 29 21:19:51 pfsense php-fpm[58663]: /rc.newwanip: rc.newwanip: on (IP address: xxx.xxx.xxx.xxx) (interface: WAN[wan]) (real interface: re0).
May 29 21:19:52 pfsense php-fpm[63138]: /rc.linkup: Gateway, none ‘available’ for inet, use the first one configured. ‘WAN_DHCP’
May 29 21:19:52 pfsense php-fpm[63138]: /rc.linkup: Gateway, none ‘available’ for inet6, use the first one configured. ‘WAN_DHCP6’
May 29 21:19:52 pfsense check_reload_status: Restarting ipsec tunnels
May 29 21:19:58 pfsense check_reload_status: updating dyndns wan
May 29 21:19:58 pfsense check_reload_status: Reloading filter
May 29 21:20:20 pfsense kernel: re1: watchdog timeout
May 29 21:20:20 pfsense kernel: re1: link state changed to DOWN
May 29 21:20:20 pfsense kernel: re1.171: link state changed to DOWN
May 29 21:20:20 pfsense kernel: re1.200: link state changed to DOWN
May 29 21:20:20 pfsense kernel: re1.172: link state changed to DOWN
May 29 21:20:20 pfsense kernel: re1.173: link state changed to DOWN
May 29 21:20:20 pfsense check_reload_status: Linkup starting re1
May 29 21:20:20 pfsense check_reload_status: Linkup starting re1.171
May 29 21:20:20 pfsense check_reload_status: Linkup starting re1.200
May 29 21:20:20 pfsense check_reload_status: Linkup starting re1.172
May 29 21:20:20 pfsense check_reload_status: Linkup starting re1.173
May 29 21:20:21 pfsense php-fpm[345]: /rc.linkup: Hotplug event detected for LAN(lan) static IP (192.168.166.1 )
May 29 21:20:21 pfsense php-fpm[63138]: /rc.linkup: Hotplug event detected for LAB_171(opt1) static IP (192.168.171.1 )
May 29 21:20:21 pfsense php-fpm[78137]: /rc.linkup: Hotplug event detected for GAST(opt3) static IP (192.168.200.1 )
May 29 21:20:21 pfsense check_reload_status: Reloading filter
May 29 21:20:21 pfsense check_reload_status: Reloading filter
May 29 21:20:21 pfsense php-fpm[345]: /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.172.1 )
May 29 21:20:21 pfsense php-fpm[63138]: /rc.linkup: Hotplug event detected for DMZ(opt4) static IP (192.168.173.1 )
May 29 21:20:24 pfsense check_reload_status: Linkup starting re1
May 29 21:20:24 pfsense kernel: re1: link state changed to UP
May 29 21:20:24 pfsense kernel: re1.171: link state changed to UP
May 29 21:20:24 pfsense kernel: re1.200: link state changed to UP
May 29 21:20:24 pfsense kernel: re1.172: link state changed to UP
May 29 21:20:24 pfsense kernel: re1.173: link state changed to UP
May 29 21:20:24 pfsense check_reload_status: Linkup starting re1.171
May 29 21:20:24 pfsense check_reload_status: Linkup starting re1.200
May 29 21:20:24 pfsense check_reload_status: Linkup starting re1.172
May 29 21:20:24 pfsense check_reload_status: Linkup starting re1.173
May 29 21:20:25 pfsense php-fpm[63138]: /rc.linkup: Hotplug event detected for LAN(lan) static IP (192.168.166.1 )
May 29 21:20:25 pfsense check_reload_status: rc.newwanip starting re1
May 29 21:20:25 pfsense check_reload_status: Reloading filter
May 29 21:20:25 pfsense php-fpm[63138]: /rc.linkup: Hotplug event detected for LAB_171(opt1) static IP (192.168.171.1 )
May 29 21:20:25 pfsense check_reload_status: rc.newwanip starting re1.171
May 29 21:20:25 pfsense php-fpm[63138]: /rc.linkup: Hotplug event detected for GAST(opt3) static IP (192.168.200.1 )
May 29 21:20:25 pfsense check_reload_status: rc.newwanip starting re1.200
May 29 21:20:25 pfsense php-fpm[63138]: /rc.linkup: Hotplug event detected for IOT(opt2) static IP (192.168.172.1 )
May 29 21:20:25 pfsense check_reload_status: rc.newwanip starting re1.172
May 29 21:20:25 pfsense php-fpm[63138]: /rc.linkup: Hotplug event detected for DMZ(opt4) static IP (192.168.173.1 )
May 29 21:20:25 pfsense check_reload_status: rc.newwanip starting re1.173
May 29 21:20:26 pfsense php-fpm[63138]: /rc.newwanip: rc.newwanip: Info: starting on re1.
May 29 21:20:26 pfsense php-fpm[63138]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.166.1) (interface: LAN[lan]) (real interface: re1).
May 29 21:20:26 pfsense php-fpm[63138]: /rc.newwanip: rc.newwanip: Info: starting on re1.171.
May 29 21:20:26 pfsense php-fpm[63138]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.171.1) (interface: LAB_171[opt1]) (real interface: re1.171).
May 29 21:20:26 pfsense php-fpm[63138]: /rc.newwanip: rc.newwanip: Info: starting on re1.200.
May 29 21:20:26 pfsense php-fpm[63138]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.200.1) (interface: GAST[opt3]) (real interface: re1.200).
May 29 21:20:26 pfsense php-fpm[63138]: /rc.newwanip: rc.newwanip: Info: starting on re1.172.
May 29 21:20:26 pfsense php-fpm[63138]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.172.1) (interface: IOT[opt2]) (real interface: re1.172).
May 29 21:20:26 pfsense php-fpm[63138]: /rc.newwanip: rc.newwanip: Info: starting on re1.173.
May 29 21:20:26 pfsense php-fpm[63138]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.173.1) (interface: DMZ[opt4]) (real interface: re1.173).
May 29 21:20:54 pfsense php-fpm[40423]: /rc.newwanip: Gateway, none ‘available’ for inet6, use the first one configured. ‘WAN_DHCP6’
May 29 21:20:59 pfsense php-fpm[40423]: /rc.newwanip: Resyncing OpenVPN instances for interface WAN.
May 29 21:21:00 pfsense php-fpm[40423]: OpenVPN terminate old pid: 40769
May 29 21:21:00 pfsense kernel: ovpns1: link state changed to DOWN
May 29 21:21:00 pfsense check_reload_status: Reloading filter
May 29 21:21:00 pfsense kernel: ovpns1: link state changed to UP
May 29 21:21:00 pfsense php-fpm[40423]: OpenVPN PID written: 97083
May 29 21:21:00 pfsense check_reload_status: Reloading filter
May 29 21:21:00 pfsense php-fpm[40423]: /rc.newwanip: Creating rrd update script
May 29 21:21:00 pfsense check_reload_status: rc.newwanip starting ovpns1
May 29 21:21:02 pfsense php-fpm[40423]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - xxx.xxx.xxx.xxx -> xxx.xxx.xxx.xxx - Restarting packages.
May 29 21:21:02 pfsense check_reload_status: Starting packages
May 29 21:21:31 pfsense php-fpm[82336]: /rc.newwanip: rc.newwanip: Info: starting on ovpns1.
May 29 21:21:31 pfsense php-fpm[82336]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.100.1) (interface: []) (real interface: ovpns1).
May 29 21:21:31 pfsense php-fpm[82336]: /rc.newwanip: rc.newwanip called with empty interface.
May 29 21:21:31 pfsense check_reload_status: Reloading filter
May 29 21:21:31 pfsense php-fpm[82336]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - -> 192.168.100.1 - Restarting packages.
May 29 21:21:31 pfsense check_reload_status: Starting packages
May 29 21:21:32 pfsense php-fpm[82336]: /rc.start_packages: Restarting/Starting all packages.
May 29 21:21:33 pfsense php-cgi: haproxy: reload old pid:41214
May 29 21:21:33 pfsense php-cgi: haproxy: started new pid:85655
May 29 21:21:37 pfsense php_pfb: [pfBlockerNG] filterlog daemon started
May 29 21:21:37 pfsense php: [pfBlockerNG] DNSBL parser daemon started
May 29 21:22:09 pfsense php-fpm[346]: /rc.start_packages: Restarting/Starting all packages.
May 29 21:22:10 pfsense php-cgi: haproxy: reload old pid:85655
May 29 21:22:10 pfsense php-cgi: haproxy: started new pid:38251
May 29 21:22:14 pfsense php: [pfBlockerNG] DNSBL parser daemon started
May 29 21:22:14 pfsense php_pfb: [pfBlockerNG] filterlog daemon started
May 29 21:22:28 pfsense check_reload_status: Syncing firewall
May 29 21:22:28 pfsense php-fpm[346]: OpenVPN terminate old pid: 97083
May 29 21:22:28 pfsense kernel: ovpns1: link state changed to DOWN
May 29 21:22:28 pfsense check_reload_status: Reloading filter
May 29 21:22:47 pfsense php-fpm[58663]: /rc.newwanip: Gateway, none ‘available’ for inet6, use the first one configured. ‘WAN_DHCP6’
May 29 21:22:52 pfsense php-fpm[58663]: /rc.newwanip: Resyncing OpenVPN instances for interface WAN.
May 29 21:22:53 pfsense php-fpm[58663]: OpenVPN PID written: 92970
May 29 21:22:53 pfsense check_reload_status: Reloading filter
May 29 21:22:53 pfsense kernel: ovpns1: link state changed to UP
May 29 21:22:53 pfsense php-fpm[58663]: /rc.newwanip: Creating rrd update script
May 29 21:22:53 pfsense check_reload_status: rc.newwanip starting ovpns1
May 29 21:22:55 pfsense php-fpm[58663]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - xxx.xxx.xxx.xxx -> xxx.xxx.xxx.xxx - Restarting packages.
May 29 21:22:55 pfsense check_reload_status: Starting packages
May 29 21:23:23 pfsense php-fpm[43595]: /rc.newwanip: rc.newwanip: Info: starting on ovpns1.
May 29 21:23:23 pfsense php-fpm[43595]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.100.1) (interface: []) (real interface: ovpns1).
May 29 21:23:23 pfsense php-fpm[43595]: /rc.newwanip: rc.newwanip called with empty interface.
May 29 21:23:23 pfsense check_reload_status: Reloading filter
May 29 21:23:23 pfsense php-fpm[43595]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - -> 192.168.100.1 - Restarting packages.
May 29 21:23:23 pfsense check_reload_status: Starting packages
May 29 21:23:23 pfsense php-fpm[43595]: /rc.start_packages: Restarting/Starting all packages.
May 29 21:23:23 pfsense php-cgi: haproxy: reload old pid:38251
May 29 21:23:24 pfsense php-cgi: haproxy: started new pid:73827
May 29 21:23:27 pfsense php: [pfBlockerNG] DNSBL parser daemon started
May 29 21:23:27 pfsense php_pfb: [pfBlockerNG] filterlog daemon started
May 29 21:24:00 pfsense php-fpm[78137]: /rc.start_packages: Restarting/Starting all packages.
May 29 21:24:01 pfsense php-cgi: haproxy: reload old pid:73827
May 29 21:24:01 pfsense php-cgi: haproxy: started new pid:84623
May 29 21:24:05 pfsense php: [pfBlockerNG] DNSBL parser daemon started
May 29 21:24:05 pfsense php_pfb: [pfBlockerNG] filterlog daemon started
May 29 21:26:33 pfsense rc.gateway_alarm[52862]: >>> Gateway alarm: WAN_DHCP (Addr:xxx.xxx.xxx.xxx Alarm:1 RTT:70.295ms RTTsd:297.714ms Loss:21%)
May 29 21:26:33 pfsense check_reload_status: updating dyndns WAN_DHCP
May 29 21:26:33 pfsense check_reload_status: Restarting ipsec tunnels
May 29 21:26:33 pfsense check_reload_status: Restarting OpenVPN tunnels/interfaces
May 29 21:26:33 pfsense check_reload_status: Reloading filter
May 29 21:26:34 pfsense php-fpm[40423]: /rc.openvpn: Gateway, none ‘available’ for inet, use the first one configured. ‘WAN_DHCP’
May 29 21:26:34 pfsense php-fpm[40423]: /rc.openvpn: Gateway, none ‘available’ for inet6, use the first one configured. ‘WAN_DHCP6’
May 29 21:26:34 pfsense php-fpm[40423]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN_DHCP.
May 29 21:26:37 pfsense kernel: re0: watchdog timeout
May 29 21:26:37 pfsense kernel: re0: link state changed to DOWN
May 29 21:26:37 pfsense check_reload_status: Linkup starting re0
May 29 21:26:38 pfsense php-fpm[345]: /rc.linkup: DEVD Ethernet detached event for wan
May 29 21:26:39 pfsense check_reload_status: Reloading filter
May 29 21:26:40 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:40 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0

May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0

May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:41 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense php-fpm[82336]: /rc.linkup: DEVD Ethernet attached event for wan
May 29 21:26:42 pfsense php-fpm[82336]: /rc.linkup: HOTPLUG: Configuring interface wan
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:26:42 pfsense check_reload_status: rc.newwanip starting re0
May 29 21:26:42 pfsense php-fpm[82336]: /rc.linkup: calling interface_dhcpv6_configure.
May 29 21:26:42 pfsense php-fpm[82336]: /rc.linkup: Accept router advertisements on interface re0
May 29 21:26:42 pfsense php-fpm[82336]: /rc.linkup: Starting rtsold process
May 29 21:26:43 pfsense php-fpm[40423]: /rc.newwanip: rc.newwanip: Info: starting on re0.
May 29 21:26:43 pfsense php-fpm[40423]: /rc.newwanip: rc.newwanip: on (IP address: xxx.xxx.xxx.xxx) (interface: WAN[wan]) (real interface: re0).
May 29 21:26:44 pfsense php-fpm[82336]: /rc.linkup: Gateway, none ‘available’ for inet, use the first one configured. ‘WAN_DHCP’
May 29 21:26:44 pfsense php-fpm[82336]: /rc.linkup: Gateway, none ‘available’ for inet6, use the first one configured. ‘WAN_DHCP6’
May 29 21:26:44 pfsense check_reload_status: Restarting ipsec tunnels
May 29 21:26:51 pfsense check_reload_status: updating dyndns wan
May 29 21:26:51 pfsense check_reload_status: Reloading filter
May 29 21:27:52 pfsense rc.gateway_alarm[34714]: >>> Gateway alarm: WAN_DHCP (Addr:xxx.xxx.xxx.xxx Alarm:0 RTT:113.466ms RTTsd:400.123ms Loss:5%)
May 29 21:27:52 pfsense check_reload_status: updating dyndns WAN_DHCP
May 29 21:27:52 pfsense check_reload_status: Restarting ipsec tunnels
May 29 21:27:52 pfsense check_reload_status: Restarting OpenVPN tunnels/interfaces
May 29 21:27:52 pfsense check_reload_status: Reloading filter
May 29 21:27:53 pfsense php-fpm[346]: /rc.openvpn: Gateway, none ‘available’ for inet6, use the first one configured. ‘WAN_DHCP6’
May 29 21:27:53 pfsense php-fpm[346]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN_DHCP.
May 29 21:28:13 pfsense check_reload_status: Syncing firewall
May 29 21:28:21 pfsense rc.gateway_alarm[84792]: >>> Gateway alarm: WAN_DHCP (Addr:xxx.xxx.xxx.xxx Alarm:1 RTT:73.623ms RTTsd:311.320ms Loss:21%)
May 29 21:28:21 pfsense check_reload_status: updating dyndns WAN_DHCP
May 29 21:28:21 pfsense check_reload_status: Restarting ipsec tunnels
May 29 21:28:21 pfsense check_reload_status: Restarting OpenVPN tunnels/interfaces
May 29 21:28:21 pfsense check_reload_status: Reloading filter
May 29 21:28:21 pfsense check_reload_status: Syncing firewall
May 29 21:28:22 pfsense php-fpm[78137]: /rc.openvpn: Gateway, none ‘available’ for inet, use the first one configured. ‘WAN_DHCP’
May 29 21:28:22 pfsense php-fpm[78137]: /rc.openvpn: Gateway, none ‘available’ for inet6, use the first one configured. ‘WAN_DHCP6’
May 29 21:28:22 pfsense php-fpm[78137]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN_DHCP.
May 29 21:28:24 pfsense kernel: re0: watchdog timeout
May 29 21:28:24 pfsense kernel: re0: link state changed to DOWN
May 29 21:28:24 pfsense check_reload_status: Linkup starting re0
May 29 21:28:25 pfsense php-fpm[78137]: /rc.linkup: DEVD Ethernet detached event for wan
May 29 21:28:26 pfsense check_reload_status: Reloading filter
May 29 21:28:26 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:28:26 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:28:28 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:28:28 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:28:28 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:28:28 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:28:28 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:28:28 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:28:28 pfsense kernel: arpresolve: can’t allocate llinfo for xxx.xxx.xxx.xxx on re0
May 29 21:28:28 pfsense kernel: arpresolve: can’t allocate CLOG####�3##��######

Well, that is a dogs breakfast. I think I would just do a fresh install of pfSense; take you 20m to get everything back up and running. Confirm you can access the internet and then install pfBlocker.

that is after a reinstall. i just installed the entire system new, installed the plugins, added the fw rules and then i allready got this error.

Okay…then reinstall (I know that sucks) and starting noting everything (fw rules/plugins/settings) you do until you have no internet connection. If you can’t reverse it from the log data you displayed above, then you gotta build it till you break it, which means starting from scratch. Again, remember to document meticulously (ah yes…quality assurance, baby). Then you’ll discover the beast that is causing you so much grief.

well, now i reinstalled pfsense from scratch… the problem is still there. i just configured my vlans and interfaces and fw rules. anything else is default.
I dont get it. If i change back to Edge Router Lite everything works just fine.
But everytime i use my full speed which is 500/500 fiber and pfsense is sitting directly in the wan port of my fiber modem. i got this issue.

send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr (Classified) bind_addr (Classified) identifier "WAN_DHCP "

That is strange, though there is a reason. Finding it is obviously much easier said than done. pfSense is on a different subnet, right?

nope, not on a different subnet, i fully turned off my Edge Router, and pfsense is running alone from fiber modem.

So you’re not “double NATed” then, right? If that is the case, then your pfSense is getting a public IP address straight from your ISP, your pfSense device is directly exposed to the Internet, and your pfSense is pushing a 192.168.X.XX address to your Edge switch, which you have then subneted (192.168.166/192.168.171) into VLans for your devices, right?

In my case, from my pic, I am double NATed. My ISP sends a public address to my fiber modem, and then my fiber modem, via DHCP, gives my pfSense box an IP address of 192.168.2.1. My pfSense network, which is a different subnet, is based on 192.168.5.X addresses (no Vlans) from the pfSense. So, I have two subnets: 192.168.2.X and 192.168.5.X.

So, when the Edge router is in production, you have Internet, whereas with the pfSense device, you do not. What then is the WAN/LAN IP addresses of the Edge router and the pfSense device when they are connected to your Fiber modem?

Yeah, that is true, the pfsense gets my static public ip on its WAN interface.

**I have also internet when the pfsense box is in production. The WAN ip of the Edge Router is exactly the same as the pfsense box WAN, and on the LAN site also the same IP. Both devices Edge Router and pfsense box has the same WAN and LAN ip scope.
I just turn either the one off i dont wan to use.

That is how it works with fiber and static public ip adresses here in Denmark.**

Then as soon as you enable pfBlocker, no internet, right?

nope, pfblocker is not the problem, because i got the problem after reinstall of pfsense without installing plugins

Well, I would try installing pfSense on a different device. Maybe this is hardware issue.

well, i allready ordered new hardware. This time it has only Inten NICs, so i hope if its a realtek related problem that it fixes the issue.

Good luck. Keep me in the loop.

Hi, I actually have the same arpresolve problem since yesterday (June 6th). I have just begun to look at my logs.

I have a lot of those lines :
Jun 7 11:14:33 kernel arpresolve: can’t allocate llinfo for 24.XXX.87.1 on re0

The re0 interface is my wan which is an onboard ethernet interface. I also have pfblocker that has benn running for a couple of weeks without problem.

I’ll maybe switch to my ethernet Intel 82576 Chip card if I don’t find a recent config change that I have done that cause this problem.