please help Freeze pfsense

Ruslan 1

Good day. Periodically get pfsense freeze. the problem is visible in the picture. I cannot understand what this may be connected with. Please tell me what could be the problem. alt text

Many thanks!!!

viragomann

@ruslan-1
That pic isn't really helpful for troubleshooting. Possilby the system log gives a hint.

Is the system virualized?

Ruslan 1

@viragomann Not. the system works on a real machine. intel (R) Celeron (R) CPU G1610 @ 2.60GHz. 4GB of RAM. 5 network "realtek".

Disable hardware checksum calculation - YES
Disable hardware handling of TCP segments - YES
Disable hardware boot on large reception - YES

All that I could find in the logs:
May 4 23:20:29 dpinger 87625 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 185.103.176.1 bind_addr 185.103.178.88 identifier "ALMATV_DHCP "
May 4 23:20:29 dpinger 87086 send_interval 1000ms loss_interval 2000ms time_period 30000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 95.56.237.24 bind_addr 192.168.0.5 identifier "WiFiMostGW "
May 4 23:20:22 dpinger 17365 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 185.103.176.1 bind_addr 185.103.178.88 identifier "ALMATV_DHCP "
May 4 23:20:22 dpinger 17102 send_interval 1000ms loss_interval 2000ms time_period 30000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 95.56.237.24 bind_addr 192.168.0.5 identifier "WiFiMostGW "

and

May 5 08:48:44 dpinger 45363 WiFiMostGW 95.56.237.24: Clear latency 30878us stddev 7382us loss 0%
May 5 08:47:18 dpinger 45363 WiFiMostGW 95.56.237.24: Alarm latency 29101us stddev 6178us loss 21%
May 5 08:31:22 dpinger 45688 ALMATV_DHCP 213.232.246.1: sendto error: 65
May 5 08:31:22 dpinger 45363 WiFiMostGW 95.56.237.24: sendto error: 65
May 5 08:31:21 dpinger 45688 ALMATV_DHCP 213.232.246.1: sendto error: 65
May 5 08:31:21 dpinger 45363 WiFiMostGW 95.56.237.24: sendto error: 65
May 5 08:31:21 dpinger 45688 ALMATV_DHCP 213.232.246.1: sendto error: 65
May 5 08:31:20 dpinger 45688 ALMATV_DHCP 213.232.246.1: sendto error: 65
May 5 08:31:20 dpinger 45363 WiFiMostGW 95.56.237.24: sendto error: 65
May 5 08:31:20 dpinger 45688 ALMATV_DHCP 213.232.246.1: sendto error: 65
May 5 08:22:02 dpinger 45363 WiFiMostGW 95.56.237.24: Clear latency 27907us stddev 6631us loss 0%
May 5 08:20:35 dpinger 45363 WiFiMostGW 95.56.237.24: Alarm latency 30362us stddev 8648us loss 21%

Gertjan

@ruslan-1

Between your 'pfSense' and the used gateway the connection is very bad.
Maybe it's only the gateway that has issues replying to the 'dpinger' pings. dpinger will decalre the uplink as bad, and, depending on your settings, even reset the interface that connects to the 'bad' gateway.

Easy solution;: use another ISP.

stephenw10

@ruslan-1 said in please help Freeze pfsense:

5 network "realtek".

Be sure you don't see any watchdog timeouts from the Realtek driver in the system log.

If you do, try the alternative driver. Or just try it anyway.

Steve

Ruslan 1

@stephenw10

Good day. found in the journal

kernel arpresolve: can't allocate llinfo for 185.103.176.1 on re3

I'll try to reinstall the driver tonight. Thank you.

stephenw10

That indicates the system does not have an interface with a subnet covering that IP for the kernel add it to.
Usually it means the WAN has gone down and that IP is the WAN gateway.

Steve