Issue about gateway Latency trouble on Backup CARP

thetmdth666

Hi all! I'm Tommy.

So my backup is every so many hours producing Gateway logs like these:

Jan 30 12:06:44 dpinger 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 192.168.0.42 bind_addr 192.168.0.12 identifier "HQ_192 "
Jan 30 12:06:44 dpinger 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 72.50.252.1 bind_addr 72.50.252.3 identifier "GW_WAN "
Jan 30 06:05:23 dpinger 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 192.168.0.42 bind_addr 192.168.0.12 identifier "HQ_192 "
Jan 30 06:05:23 dpinger 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 72.50.252.1 bind_addr 72.50.252.3 identifier "GW_WAN "

The primary doesn't have any of those.

I just noticed a latency issue on my internal monitoring and noticed these on both Primary and Secondary:

Jan 30 13:25:42 dpinger HQ_192 192.168.0.42: Clear latency 463us stddev 148us loss 5%
Jan 30 13:24:28 dpinger HQ_192 192.168.0.42: Alarm latency 770us stddev 2460us loss 21%
Jan 30 13:21:09 dpinger HQ_192 192.168.0.42: Clear latency 544us stddev 222us loss 5%
Jan 30 13:19:54 dpinger HQ_192 192.168.0.42: Alarm latency 530us stddev 65us loss 22%
Jan 30 13:00:46 dpinger HQ_192 192.168.0.42: Clear latency 7402us stddev 58032us loss 5%
Jan 30 12:59:32 dpinger HQ_192 192.168.0.42: Alarm latency 453us stddev 38us loss 22%

Any help would be greatly appreciated.

Thank you in advance.

[spam links removed]

Harvy66

Looks like buffer bloat. I would recommend the Traffic Shaping forum. You could try enabling FairQ on your WAN interface and check the box on the child queue to enable Codel. This works well enough for most people. For now it gets more complicated quickly beyond this, but soon it may be as easy as a few check boxes to fix buffer bloat.