Project

General

Profile

Actions

Bug #11286

closed

Endpoint port is mandatory if Endpoint is defined

Added by Viktor Gurov about 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
WireGuard
Target version:
Start date:
01/22/2021
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.5.0
Affected Architecture:

Description

It's not possible to define endpoint without port, i.e.

EndPoint = 192.168.1.1

Actions #2

Updated by Jim Pingle about 3 years ago

  • Assignee set to Jim Pingle
  • Target version set to 2.5.0

In this case we should assume the default port (51820) rather than making the field required. I'll take a look at it.

Actions #3

Updated by Jim Pingle about 3 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #4

Updated by Jim Pingle about 3 years ago

  • Status changed from Feedback to In Progress
  • % Done changed from 100 to 90

One more little thing, in the tunnel list it isn't assuming the default port in the display. Also it's showing ":" for empty/dynamic peers, should show something more friendly instead.

Actions #5

Updated by Jim Pingle about 3 years ago

  • Status changed from In Progress to Feedback
  • % Done changed from 90 to 100
Actions #6

Updated by Jim Pingle about 3 years ago

  • Status changed from Feedback to Resolved

OK on current snapshot. If the endpoint is filled in and port is blank, the default port is used.

Actions

Also available in: Atom PDF