Notice about Filter Reload on PPPoE Reset
-
Was it after a reboot?
-
-
Hmm, how is that rule actually configured?
It's probably throwing that because the gateway is down, or doesn't exist, when the PPPoE resets. But I don't expect to see 'reply-to' on an outbound rule like that.
-
-
Hmm, this looks like a bug to me. There shouldn't be reply-to tags applied there.
As a workaround though you can just set 'Disable reply-to' on the rule. It no longer references the gateway so shouldn't throw that error.
Steve
-
@stephenw10 said in Notice about Filter Reload on PPPoE Reset:
Hmm, this looks like a bug to me. There shouldn't be reply-to tags applied there.
As a workaround though you can just set 'Disable reply-to' on the rule. It no longer references the gateway so shouldn't throw that error.
Steve
Thanks, done.
Is this maybe because of "reject"? I have no clue though. -
Does it with block as well and shouldn't IMO. Looking into it now.
-
@stephenw10 Just for completeness, as you already looking into it, it now popped out for a floating incoming block rule on WAN.
-
Hmm, that should have reply-to but it doesn't need it if that's your only WAN.
-
@stephenw10 Sure, if it is an incoming block on WAN? (Man I have no clue about all this
) -
Ah, no sorry, not for a block!
