Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
duniter
duniter
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 191
    • Issues 191
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • nodes
  • typescript
  • duniterduniter
  • Issues
  • #1383

Closed
Open
Opened Jun 10, 2019 by Cédric Moreau@c-geekOwner

WS2P: allow `upnp: true` combined with `port` and/or `remoteport`

Today if we use upnp: true, then Duniter ignores the port and remoteport option. This means that we can't precise the ports we want to be opened by UPnP. UPnP decides of everything currently.

I would like to be able to choose which ports UPnP will use.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
2.0
Milestone
2.0
Assign milestone
Time tracking
None
Due date
None
Reference: nodes/typescript/duniter#1383