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
UPnP: T4211: T4620 Fix upnp template #1476
Conversation
<description>The IPv4 to which this rule applies</description> | ||
</valueHelp> | ||
<constraint> | ||
<validator name="ipv4-address" /> | ||
<validator name="ipv4-host" /> | ||
<validator name="ip-prefix"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ip-prefix
also allows IPv6 addresses. If this is the case, you should use ip-host, too and add ipv6 to the completion helper.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think all 4 options should be listed in the completion help: ipv4, ipv4net, ipv6, ipv6net as the validator also allows everything.
ipv4 shows <x.x.x.x>
ipv4net shows <x.x.x.x/x>
ipv6 shows <h:h:h:h:h:h:h:h>
ipv6net shows <h:h:h:h:h:h:h:h/x>
Also the completion help looks different to the user - we should list all available options - its free for us.
<description>The IPv4 to which this rule applies</description> | ||
</valueHelp> | ||
<constraint> | ||
<validator name="ipv4-address" /> | ||
<validator name="ipv4-host" /> | ||
<validator name="ip-prefix"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think all 4 options should be listed in the completion help: ipv4, ipv4net, ipv6, ipv6net as the validator also allows everything.
ipv4 shows <x.x.x.x>
ipv4net shows <x.x.x.x/x>
ipv6 shows <h:h:h:h:h:h:h:h>
ipv6net shows <h:h:h:h:h:h:h:h/x>
Also the completion help looks different to the user - we should list all available options - its free for us.
There is how it looks like with this 2 commits
Validate
Validate
I don't expect |
From the doc miniupnpd IP/mask format must be nnn.nnn.nnn.nnn/nn Comment out invalid option "anchor"
I excluded the IPv6 option as the daemon doesn't like IPv6 for
|
Change Summary
Fix UPnP jinja2 template, incorrect value
rules
instead ofrule
So rules didn't work at all.
Incorrect logic do
disabled
ruleAddress must be in the format
address/mask
due to https://github.com/miniupnp/miniupnp/blob/fa42d8f9316bf9c1ca14317e5a6e0d4a21365629/miniupnpd/miniupnpd.conf#L174Types of changes
Related Task(s)
Component(s) name
upnp
Proposed changes
How to test
VyOS config:
Expected:
Checklist: