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

Router error on ttl > 0 #24

Open
pietrovismara opened this issue May 28, 2016 · 5 comments
Open

Router error on ttl > 0 #24

pietrovismara opened this issue May 28, 2016 · 5 comments

Comments

@pietrovismara
Copy link
Contributor

I instantiate my client like this:

        client.portMapping({
          public: publicPort,
          private: privatePort,
          ttl: 0
        }, function(err) {
          // Will be called once finished
          console.log("done", err);
        });

If ttl is greater than 0 i get this status code 500 and this response from the router api:

{
    "@": {
        "xmlns:s": "http://schemas.xmlsoap.org/soap/envelope/",
        "s:encodingStyle": "http://schemas.xmlsoap.org/soap/encoding/"
    },
    "s:Body": {
        "s:Fault": {
            "faultcode": "s:Client",
            "faultstring": "UPnPError",
            "detail": {
                "UPnPError": {
                    "@": {
                        "xmlns": "urn:schemas-upnp-org:control-1-0"
                    },
                    "errorCode": "725",
                    "errorDescription": "OnlyPermanentLeasesSupported"
                }
            }
        }
    }
}

I found the solution of setting ttl to 0 in this issue zerotier/ZeroTierOne#242
This could be probably added to the README.md file.

@indutny
Copy link
Owner

indutny commented Jun 1, 2016

@pietrovismara the zerotier/ZeroTierOne#242 seems to be a length stream of text. May I ask you to post a relevant excerpt here?

Thanks!

@pietrovismara
Copy link
Contributor Author

I'm talking about this comment.
The problem seems to be about the lease duration, setting it to 0 as suggested in the comment made the port forwarding works.

@indutny
Copy link
Owner

indutny commented Jun 1, 2016

Ok, would you be interested in contributing this change to a readme? 😉

@boltgolt
Copy link

Had the same issue, and setting the ttl to 0 seems to fix it. I'm a bit worried that this change won't allow nat-upnp to get to the UPnP IGD if it's one hop away, though.

@remy33
Copy link

remy33 commented Aug 22, 2017

I had the same problem, It's a shame you didn't fix the ReadMe!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants