You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hmm there is a broken default 'Traffic' Rule' of 'Support-UDP-Traceroute' on 21.02
which is disabled by default... but wouldn't work even if you enabled it as the port is 33434:33689 rather than 33434-33689
is this reported anyplace? I could report it... but where would I?
Lantizia: bugs.openwrt.org is the place for reporting issues
we'd appreciate the report :) Thank you for finding and mentioning!
This new default firewall rule (although disabled by default) seems to have been introduced with commit de8b88c.
I'm not sure if the colon (rather than a hyphen) affects the possibility of this rule working if it is activated without using LuCI.
But certainly from within LuCI... if try to edit this rule and re-save it (without changing anything) then it'll flag the field as having invalid contents and refuse to save.
If colons are valid in this context then I'll re-file this bug to the LuCI bug tracker instead.
The text was updated successfully, but these errors were encountered:
Just realised this is something I raised on the old bugtracker, but for some reason three alternate versions of this issue (all by me it seems) were imported by @openwrt-bot and then immediately closed? Perhaps this was me using the edit button on the old bugtracker to add more detail, and the migration took all the various versions?
So I'm not sure which is the most valuable but these are the alternate versions of this issue which I guess can be marked as dupes... #9130#9131#9132
Lantizia:
As mentioned on IRC/OFTC...
hmm there is a broken default 'Traffic' Rule' of 'Support-UDP-Traceroute' on 21.02
which is disabled by default... but wouldn't work even if you enabled it as the port is 33434:33689 rather than 33434-33689
is this reported anyplace? I could report it... but where would I?
Lantizia: bugs.openwrt.org is the place for reporting issues
we'd appreciate the report :) Thank you for finding and mentioning!
This new default firewall rule (although disabled by default) seems to have been introduced with commit de8b88c.
I'm not sure if the colon (rather than a hyphen) affects the possibility of this rule working if it is activated without using LuCI.
But certainly from within LuCI... if try to edit this rule and re-save it (without changing anything) then it'll flag the field as having invalid contents and refuse to save.
If colons are valid in this context then I'll re-file this bug to the LuCI bug tracker instead.
The text was updated successfully, but these errors were encountered: