Bug #15041
closedIcmp payload default of 0 can give issues as this is not a official supported value as monitoring of a gateway.
0%
Description
Icmp payload for monitoring a gateway has a default value of 0. The result of the ICMP request can be influenced by firewalls and the chosen endpoint. Result can be dropped or delayed answers. Also the answer will have a different size as the request (18 padded zero's).
Better would be to use the same default as ping implementations inside different OS variants like 32 for Windows or 56 for Linux and FreeBSD. I have no preference which implementation is followed as long as the prone to error situation of zero payload is resolved. Lower then 32 or 56 payload including zero should be possible to set by administrators who know what they are monitoring (inside their LAN or any endpoint that is known not to give issues).
Files
Updated by Marcos M over 1 year ago
- Status changed from New to Closed
The payload size can already be configured in the gateway's advanced settings.
Updated by Jim Pingle over 1 year ago
- File clipboard-202311281032-d8ddr.png clipboard-202311281032-d8ddr.png added
- Status changed from Closed to Not a Bug
The default in pfSense is 1, not 0. The default in dpinger is 0 but pfSense uses 1 when it's unset, not 0.
https://docs.netgate.com/pfsense/en/latest/routing/gateway-configure.html#advanced-gateway-settings
Updated by Jim Pingle over 1 year ago
To be extra certain I ran a packet capture of a monitoring ping on a default install and confirmed the size is 1 byte:
Updated by Leon Straathof over 1 year ago
I understand that the value already can be edited, and that the default payload is 1 instead of zero does not change the fact that the default value gives problems if you try to use it to monitor something outside of your LAN as your ISP could either block it or give it less prio. This is because zero or 1 is not a global standard. Please make the default value something that adheres to something that is standard. I found this a problem because the default value does not work at all with my IPS giving wild fluctuating monitoring results and it took me ages to figure out why. I do not state that monitoring is broken yes you can edit the value, but only the default value is so bad that it can lead to people need to trouble shoot for a long time to only find the default value is just stupid. Default values should be a good starting point working for most users. Thats why i recommended to change it to either the default used in Linux or in Windows. I have no preference just as long as it is some value that ISP's recognise as a valid default size.