Skip to content
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

Cannot save outbound NAT rule when setting destination to "any" #3303

Closed
oparoz opened this issue Mar 9, 2019 · 2 comments
Closed

Cannot save outbound NAT rule when setting destination to "any" #3303

oparoz opened this issue Mar 9, 2019 · 2 comments
Assignees
Labels
bug Production bug
Milestone

Comments

@oparoz
Copy link
Contributor

oparoz commented Mar 9, 2019

Describe the bug

Something broke in 19.1.3 when adding an outbound NAT rule with the destination set to "any"

The following input errors were detected:

    The field Destination bit count is required.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Firewall->NAT->Outbound'
  2. Create a new rule
  3. Set destination to "any"
  4. Press "Save"
  5. See error

Expected behavior
Rule should be saved and I should be able to reload the FW

Workaround

Set destination as single host or network. A new field is revealed which says "any", the destination is greyed out.
Be careful, every time you save the rule, it gets reset to destination = any and the bug will be back.

Environment

OPNsense 19.1.3 (amd64, OpenSSL).

@AdSchellevis
Copy link
Member

looks like an intended side affect of a550546

@AdSchellevis
Copy link
Member

@oparoz thanks for reporting, should be fixable with:

opnsense-patch edc971d0

@fichtner fichtner added the bug Production bug label Mar 9, 2019
@fichtner fichtner added this to the 19.7 milestone Mar 9, 2019
fichtner pushed a commit that referenced this issue Mar 9, 2019
…d and validated when needed, closes #3303

(cherry picked from commit edc971d)
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
EugenMayer pushed a commit to KontextWork/opnsense_core that referenced this issue Jul 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Production bug
Development

No branches or pull requests

3 participants