Project

General

Profile

Bug #11286

Endpoint port is mandatory if Endpoint is defined

Added by Viktor Gurov 3 months ago. Updated 3 months ago.

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

100%

Estimated time:
Affected Version:
2.5.0
Affected Architecture:
Release Notes:
Default

Description

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

EndPoint = 192.168.1.1

Associated revisions

Revision df799f2c (diff)
Added by Jim Pingle 3 months ago

Assume default WG port if empty. Fixes #11286

Revision e801e55b (diff)
Added by Jim Pingle 3 months ago

Assume default WG port if empty. Fixes #11286

While here, print a more user-friendly value when peer endpoints are
empty.

Revision c0d26370 (diff)
Added by Jim Pingle 3 months ago

Use gettext() on WireGuard endpoint text. Issue #11286

History

#2 Updated by Jim Pingle 3 months 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.

#3 Updated by Jim Pingle 3 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#4 Updated by Jim Pingle 3 months 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.

#5 Updated by Jim Pingle 3 months ago

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

#6 Updated by Jim Pingle 3 months 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.

Also available in: Atom PDF