Project

General

Profile

Actions

Correction #14599

closed

Change Interface Names in TNSR Remote Office With Existing IPsec Hub to Something Else

Added by Kris Phillips almost 2 years ago. Updated over 1 year ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
NAT
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

When you search for something like "port forward" in our documentation, rather than bringing up the NAT page, it brings you to the Step 6 of this doc for the first result:

https://docs.netgate.com/tnsr/en/latest/recipes/tnsr-remote-office/index.html

Because of this, it's probably best we don't use "outside" for the WAN interface, but instead change it to something else like "outside-interface". Reason being is that when you're reading the docs and you get to the command for a port forward example, this command makes you think the rule is defining "this is on the outside" (similar to the ip nat outside command) rather than the interface being named "outside":

nat static mapping tcp local 172.21.89.12 8443 external outside 8443

This was confusing to me the first time I read it and I'm sure this would be confusing to a customer as well.

Actions #1

Updated by Jim Pingle over 1 year ago

  • Status changed from New to Rejected

Moved to https://redmine.netgate.com/issues/12213 as this Redmine isn't for TNSR docs.

Actions

Also available in: Atom PDF

OSZAR »