136
21.7 Legacy Series / Re: Are the default CARP rules incorrect?
« on: October 06, 2021, 04:59:09 pm »
carp traffic uses non routable multicast traffic (destination 224.0.0.18, https://en.wikipedia.org/wiki/Multicast_address). Originally we started with the following two rules when carp was enabled:
https://github.com/opnsense/core/blob/92dbe83e75637f478697abfbaaaf8bd3a424e846/src/etc/inc/filter.inc#L3428-L3431
Eventually the first (block) rule translated into being discarded, which wasn't really intentional, but likely doesn't change much either since the source address doesn't really matter to determine which machine has the highest priority.
Looking into the origin of the block rule https://github.com/pfsense/pfsense/commit/986a3accd40a7d45c0a3d48d2b42d2c58a231d99
and https://redmine.pfsense.org/issues/598 one could argue that deleting it wouldn't be an issue at all... we've never seen these issues in the years we accidentally disabled it...
Best regards,
Ad
Code: [Select]
block in quick proto carp from (self) to any
pass quick proto carp
https://github.com/opnsense/core/blob/92dbe83e75637f478697abfbaaaf8bd3a424e846/src/etc/inc/filter.inc#L3428-L3431
Eventually the first (block) rule translated into being discarded, which wasn't really intentional, but likely doesn't change much either since the source address doesn't really matter to determine which machine has the highest priority.
Looking into the origin of the block rule https://github.com/pfsense/pfsense/commit/986a3accd40a7d45c0a3d48d2b42d2c58a231d99
and https://redmine.pfsense.org/issues/598 one could argue that deleting it wouldn't be an issue at all... we've never seen these issues in the years we accidentally disabled it...
Best regards,
Ad

