indutny / indutny/node-nat-upnp

Router error on ttl > 0

Open
#24 5 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
148
Forks
62
PR merge metrics
No merged PRs in 30d

Description

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:

``` json
{
"@": {
"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 https://github.com/zerotier/ZeroTierOne/issues/242
This could be probably added to the README.md file.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with README.md and the client.portMapping usage shown in the issue. Document that setting ttl to 0 resolves the router response indicating that only permanent leases are supported, and verify the example clearly communicates this behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
documentation, networking
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.