-
Notifications
You must be signed in to change notification settings - Fork 457
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
Standardisation of port map description length to 1016 #746
base: master
Are you sure you want to change the base?
Standardisation of port map description length to 1016 #746
Conversation
miniupnpd was first developped for pf and use the pf rule "label" which is limited to 64 bytes to store the description. |
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.
This PR completely misses the fact that 64 characters is the hard limit in miniupnpd at least with pf backend.
570d38c
to
07de68b
Compare
Thanks for the PR review. |
07de68b
to
3cb5571
Compare
In fact the limit should be removed from miniupnpc (API needs to be changed) |
Currently used length limits for port map description:
Therefore the current daemon limit is 64 and the client limit is 80.
The maximum length is not defined in the UPnP IGD standards. The built-in Windows client allows any description length (>20k tested).
The provided PR changes the limit to 1016 bytes according to the PCP description option standard.