Project

General

Profile

Actions

Todo #14737

closed

Feedback on pfSense® software Configuration Recipes — Connecting OpenVPN Sites with Conflicting IP Subnets

Added by Joshua Diamant over 1 year ago. Updated over 1 year ago.

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

0%

Estimated time:

Description

Page: https://docs.netgate.com/pfsense/en/latest/recipes/openvpn-nat-subnets-conflict.html

Feedback:

throughout this page, there are some typos with the IP address subnets which make the examples hard to understand. 10.1.1/24 and in the multi-wan example there is another

Actions #1

Updated by Jim Pingle over 1 year ago

  • Status changed from New to Rejected

I reviewed the examples on that page and the addresses appear to line up properly as far as I can see.

There are two separate and unrelated examples on that page that are completely different (site to site, and site to multisite) and each example uses different sets of addresses.

If you can point to specific instances where something does not match, please list them, why you think the value is incorrect, and what you think the value should be.

Actions #2

Updated by Joshua Diamant over 1 year ago

Hi @Jim Pingle - here are some examples

Site 0 - 10.1.1/24
Site 1 - 192.168.0/24 -> 10.10.1/24
Site 2 - 192.168.0/24 -> 10.10.2/24
Site 3 - 192.168.0/24 -> 10.10.3/24

none of these address are full IP addresses. they are missing the 3rd or 4th oclet.

the same is true throughout the document for Examples before NAT, nat can make each remote site unique.... all of the addresses are incomplete.

Actions #3

Updated by Jim Pingle over 1 year ago

Those examples are meant to be that way, they are talking about entire subnets, not specific single addresses.

Especially in the code blocks that is done to make sure they fit in the given width.

Combined with the CIDR mask the meaning is quite clear as it is.

Actions

Also available in: Atom PDF