Project

General

Profile

Actions

Regression #15690

closed

pfSense doesn't send gateway event notifications

Added by Lev Prokofev over 1 year ago. Updated 16 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Notifications
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
Affected Architecture:

Description

tested on

24.03-RELEASE (amd64)
built on Mon May 13 15:17:00 MSK 2024
FreeBSD 15.0-CURRENT

During the gateway event, it doesn't send notifications via SNMP or via Telegram.

previously there were the following messages:

levhome-1.pfHome
MONITOR: WANGW is available now, adding to routing group Gateways
x.x.x.x|x.x.x.x|WANGW|20.376ms|47.33ms|18%|online|loss
Actions #1

Updated by Lev Prokofev over 1 year ago

The issue exists in the 24.08

    24.08-DEVELOPMENT (amd64)
built on Wed Aug 21 6:00:00 UTC 2024
FreeBSD 15.0-CURRENT
Actions #2

Updated by aleksei prokofiev over 1 year ago

Tested on 24.03, I can confirm such behaviour.

Actions #3

Updated by Azamat Khakimyanov 16 days ago

  • Status changed from New to Resolved

Tested on 26.03-RELEASE

In both cases
1. WAN wend DOWN
- when I forced WAN gateway DOWN

16:37:02 WAN_DHCP is down, omitting from routing group FailoverGW; 192.168.132.1|192.168.132.107|WAN_DHCP|0.321ms|0.201ms|0.0%|down|force_down

- when WAN gateway went DOWN because of packet loss

16:44:54 WAN_DHCP has packet loss, omitting from routing group FailoverGW; 8.8.8.8|192.168.132.107|WAN_DHCP|39.758ms|0.506ms|24%|down|highloss

2. and WAN went UP

16:39:03 WAN_DHCP is available now, adding to routing group FailoverGW; 192.168.132.1|192.168.132.107|WAN_DHCP|0.338ms|0.189ms|0.0%|online|none

I got email notifications.

Actions

Also available in: Atom PDF