[prev in list] [next in list] [prev in thread] [next in thread]
List: strongswan-users
Subject: [strongSwan] Idea for NATted hub-and-spoke Site-to-Site Usable Example
From: "Nicholas Jenkins" <nick () notashutin ! com>
Date: 2020-02-23 4:25:07
Message-ID: 006101d5ea01$3c4b91b0$b4e2b510$ () notashutin ! com
[Download RAW message or body]
This is a multipart message in MIME format.
I found the "Usable Example" documentation invaluable.
However.it overlooks a Site-to-Site scenario that I think could have
relevance: NATted hub-and-spoke.
How do we determine interest in, and if interest exists, how do we arrange
additional documentation for new "Usable Examples"?
Interest?:
I wanted to build a family network over site-to-site VPN.
Why? Although I had Road-Warrior setup for last 2 years, I
recognized that if my family needed support for their WAP or Network
Printer, that this would be much easier with a routed (flat) network, rather
than only having access to their PC via Road-Warrior VPN.
Design Constraints: I already had my home server exposed via
NAT-T/IKEv2 on the Internet to support Road-Warrior, but:
1. I didn't want my family to have to expose any technology (computer
or router) on the Internet
a. Fewer keys to manage
b. Fewer points of ingress/egress to be compromised
2. Although my ISP service is business-class, and thus not constrained,
their service is all residential, and could possibly be constrained from
hosting VPN services.
So, this would mean needing a computer inside their LAN, behind NATting
ISP-uplink router to initiate VPN connection back to my VPN. communication
may be bi-directional, but VPN session initiation would need to start at the
remote family sites (thus, NATted hub-and-spoke).
I noticed that all of the Site-to-Site scenarios assume ability to initiate
connection from either side (i.e. truly "peers"), and I don't think I saw
any addressing where 1 side was behind a NAT router (specifically a
different network appliance as the NAT router. not just the local device
NATting).
I'm happy to provide documentation + config examples if there is interest?
Kind regards.
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type \
content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 \
(filtered medium)"><style><!-- /* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1737774878;
mso-list-type:hybrid;
mso-list-template-ids:-176011754 -211014518 67698713 67698715 67698703 67698713 \
67698715 67698703 67698713 67698715;} @list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:2.25in;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:3.75in;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.75in;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:5.25in;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" \
vlink="#954F72"><div class=WordSection1><p class=MsoNormal>I found the “Usable \
Example” documentation invaluable.<o:p></o:p></p><p \
class=MsoNormal>However…it overlooks a Site-to-Site scenario that I think could \
have relevance: NATted hub-and-spoke.<o:p></o:p></p><p class=MsoNormal>How do we \
determine interest in, and if interest exists, how do we arrange additional \
documentation for new “Usable Examples”?<o:p></o:p></p><p \
class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Interest?:<o:p></o:p></p><p \
class=MsoNormal>I wanted to build a family network over site-to-site \
VPN.<o:p></o:p></p><p \
class=MsoNormal> \
Why? Although I had Road-Warrior setup for last 2 years, I recognized that if my \
family needed support for their WAP or Network Printer, that this would be much \
easier with a routed (flat) network, rather than only having access to their PC via \
Road-Warrior VPN.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p \
class=MsoNormal> \
Design Constraints: I already had my home server exposed via NAT-T/IKEv2 on the \
Internet to support Road-Warrior, but:<o:p></o:p></p><ol style='margin-top:0in' \
start=1 type=1><li class=MsoListParagraph style='margin-left:.75in;mso-list:l0 level1 \
lfo1'>I didn’t want my family to have to expose any technology (computer or \
router) on the Internet<o:p></o:p></li><ol style='margin-top:0in' start=1 type=a><li \
class=MsoListParagraph style='margin-left:.75in;mso-list:l0 level2 lfo1'>Fewer keys \
to manage<o:p></o:p></li><li class=MsoListParagraph \
style='margin-left:.75in;mso-list:l0 level2 lfo1'>Fewer points of ingress/egress to \
be compromised<o:p></o:p></li></ol><li class=MsoListParagraph \
style='margin-left:.75in;mso-list:l0 level1 lfo1'>Although my ISP service is \
business-class, and thus not constrained, their service is all residential, and could \
possibly be constrained from hosting VPN services.<o:p></o:p></li></ol><p \
class=MsoNormal style='margin-left:1.0in'>So, this would mean needing a computer \
inside their LAN, behind NATting ISP-uplink router to initiate VPN connection back to \
my VPN… communication may be bi-directional, but VPN session initiation would \
need to start at the remote family sites (thus, NATted \
hub-and-spoke).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p \
class=MsoNormal>I noticed that all of the Site-to-Site scenarios assume ability to \
initiate connection from either side (i.e. truly “peers”), and I \
don’t think I saw any addressing where 1 side was behind a NAT router \
(specifically a different network appliance as the NAT router… not just the \
local device NATting).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p \
class=MsoNormal>I’m happy to provide documentation + config examples if there \
is interest?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p \
class=MsoNormal>Kind regards.<o:p></o:p></p><p \
class=MsoNormal><o:p> </o:p></p></div></body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic