Bug #2073
closed
APIPA broadcasts forwarded by route-to
Added by Chris Buechler almost 13 years ago.
Updated almost 5 years ago.
Category:
Operating System
Description
If there is a host with an APIPA IP sending broadcasts that match a route-to rule, the traffic gets forwarded by route-to. antispoof should block that scenario, since that IP subnet isn't defined on the source interface. We should change route-to should never forward anything destined to a broadcast MAC address to prevent such scenarios.
To work around, just add a rule to block APIPA, 169.254.0.0/16. Or ideally don't use overly permissive rulesets, the default rules will not permit this to happen.
- Description updated (diff)
- Status changed from New to Resolved
- Target version set to 2.2
fixed by implementing the appropriate behavior per RFC 3927 - block it.
Except with no way to disable this rule, this can affect bridged interfaces, and since the rule is processed so far in advance you can not make a rule to allow said traffic without giving up filtering the bridge completely. Also can cause spam to the default block log.
There is no GUI knob to disable it, but there is a setting. You can set it in the config.xml directly or via PHP (e.g. Diag > Command, PHP Execute box):
$config['system']['no_apipa_block'] = true;
write_config("Disable APIPA Blocking rule");
Jim Pingle wrote:
There is no GUI knob to disable it, but there is a setting. You can set it in the config.xml directly or via PHP (e.g. Diag > Command, PHP Execute box):
[...]
Alright ill try that, seems reasonable.
Also available in: Atom
PDF