-
Notifications
You must be signed in to change notification settings - Fork 759
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
firewall: transparent proxy rule leaks into rules page #695
Comments
|
Can you please refine the terminology and exact page names for steps 1., 2. and 3., I am unable to reproduce this with the current description. |
|
OK, I've updated the OP. |
|
Is this the error you're seeing? |
|
Exactly and all of these fields are filled up, but greyed out to prevent bad things to happen. |
|
Ok, it's a NAT rule and it shouldn't show up in the rules screen. |
|
OK, so it's the same rule as the Port Forward rule, but presented differently? |
|
exactly, and since it's a NAT rule it fails to save properly in the rules screen |
|
OK, thanks 👍 |
…ut hide edit and duplicate buttons If for some reason a config has "typeless" rules, which don't belong to any active nat rule the user won't notice this anymore (and doesn't have the ability to remove them). This can happen with imports from old configs for example or manually changed configs.
…ut hide edit and duplicate buttons If for some reason a config has "typeless" rules, which don't belong to any active nat rule the user won't notice this anymore (and doesn't have the ability to remove them). This can happen with imports from old configs for example or manually changed configs. (cherry picked from commit e1dd183)
Env
15.7.99_2050
Steps to reproduce
Expected result
I should be able to save the rule
Actual result
The Javascript validation rules get in the way, thinking that all greyed out fields are fields which have not been filled.
The text was updated successfully, but these errors were encountered: