Thank you !
I'm currently using a solution from a third-party provider, and there
are not many things I can configure on gateway B (like adding CHILD_SAs,
for example).
I'll go with my own implementation of Strongswan for a better control
over the configuration.
Thanks !
Hoggins!
Le 13/03/2
On 13.03.2017 19:05, Hoggins! wrote:
> ... so if my gateway A keeps 192.168.22.0/24 as its "real" network, but
> gets – let's say – a TS 192.168.33.0/24 == 192.168.55.0/24, my road
> warriors would also be on 192.168.33.0/24 (if configured accordingly, of
> course), and be able to talk to gateway A
Thank you Noel, that's what I thought...
Le 13/03/2017 à 17:39, Noel Kuntze a écrit :
> On 12.03.2017 19:05, Hoggins! wrote:
>> Now I want to have road warriors connected on gateway B. That's cool
>> : they get a dynamic IP address on 192.168.22.0/24 and they can talk to
>> hosts on 192.168.55
On 12.03.2017 19:05, Hoggins! wrote:
> Now I want to have road warriors connected on gateway B. That's cool
> : they get a dynamic IP address on 192.168.22.0/24 and they can talk to
> hosts on 192.168.55.0/24. Great.
TL;DR:
Use a different subnet.
Long story:
You've got conflicting subnets
Hello list,
I got a question, not sure if I can do what I want, if it's ever doable.
Please be kind.
*TL;DR :* got a site2site tunnel between gateway A and gateway B, works
great. I would like to have road warriors connected to gateway B, and be
able to speak with hosts located behind gateway A.
