-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
miniupnpd: multiple unhelpful messages in the log #15258
Comments
I don't really maintain this. It looks like some upstream bug. |
@neheb: this change is not part of upstream and it was accepted into openwrt by you. Moreover this patch is incorrect and and is breaking upnp protocol as desribed in comments. So please do not instruct users to forward openwrt bugs and issues to upstream projects like it already happened because upstream developers really do not have a time to investigate issues caused by downstream openwrt patches. |
@ptpt52 -- can you please advise me why have I started seeing these messages in the log? What do they mean? Why is the default setting on for these? |
I am trying to drop this option, Please help test #16011 |
This patch is causing several issues [1], which then were reported to upstream [2] and it was not accepted by upstream [3]. This results that nobody maintain this custom patch and it is not useful as it is changing addr_is_reserved behavior. [1] openwrt#15258 [2] miniupnp/miniupnp#542 [3] miniupnp/miniupnp#511 This reverts commit b76aa99. Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
This patch is causing several issues [1], which then were reported to upstream [2] and it was not accepted by upstream [3]. This results that nobody maintain this custom patch and it is not useful as it is changing addr_is_reserved behavior. [1] #15258 [2] miniupnp/miniupnp#542 [3] miniupnp/miniupnp#511 This reverts commit b76aa99. Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com> (cherry picked from commit 107f337)
This patch is causing several issues [1], which then were reported to upstream [2] and it was not accepted by upstream [3]. This results that nobody maintain this custom patch and it is not useful as it is changing addr_is_reserved behavior. [1] openwrt#15258 [2] miniupnp/miniupnp#542 [3] miniupnp/miniupnp#511 This reverts commit b76aa99. Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
This patch is causing several issues [1], which then were reported to upstream [2] and it was not accepted by upstream [3]. This results that nobody maintain this custom patch and it is not useful as it is changing addr_is_reserved behavior. [1] #15258 [2] miniupnp/miniupnp#542 [3] miniupnp/miniupnp#511 This reverts commit b76aa99. Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com> (cherry picked from commit 107f337)
This patch is causing several issues [1], which then were reported to upstream [2] and it was not accepted by upstream [3]. This results that nobody maintain this custom patch and it is not useful as it is changing addr_is_reserved behavior. [1] openwrt#15258 [2] miniupnp/miniupnp#542 [3] miniupnp/miniupnp#511 This reverts commit b76aa99. Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
Hi @stangri, is this still vaild? |
I no longer use miniupnpd, not sure if this issue persists. |
Maintainer: @neheb
Environment: x86-64, Sophos SG-105, 21.02-SNAPSHOT r15926
Description:
I keep seeing the messages like below in the log. Is it missing a
d
at the end (as in checking is ignored)? There's no indication on why is it being reported or what caused it. Is it possible to improve this message to make it more clear?The text was updated successfully, but these errors were encountered: