Re: if_ipsec(4) and IKEv1 [security/ipsec-tools, racoon.conf]

2018-02-27 Thread Andrey V. Elsukov
On 27.02.2018 14:20, Harry Schmalzbauer wrote: > Thank you very much for your explanation! > > Unfortunately, I couldn't get the P2P idea behind if_ipsec(4) and I > tought I'd just need a few minutes to switch from policy based tunnels > to route based – local brain contraints seem to require me m

Re: if_ipsec(4) and IKEv1 [security/ipsec-tools, racoon.conf]

2018-02-27 Thread Harry Schmalzbauer
Bezüglich Andrey V. Elsukov's Nachricht vom 27.02.2018 11:50 (localtime): > On 27.02.2018 12:56, Harry Schmalzbauer wrote: >> Hello, >> >> I'm out of ideas how to quick-start with if_ipsec(4) and IKEv1. >> >> I'm familar with security/ipsec-tools, but I couldn't find out how >> racoon(8) would int

Re: if_ipsec(4) and IKEv1 [security/ipsec-tools, racoon.conf]

2018-02-27 Thread Andrey V. Elsukov
On 27.02.2018 12:56, Harry Schmalzbauer wrote: > Hello, > > I'm out of ideas how to quick-start with if_ipsec(4) and IKEv1. > > I'm familar with security/ipsec-tools, but I couldn't find out how > racoon(8) would interact with cloned if_ipsec(4) interfaces yet. You need to manually configure if

Re: if_ipsec(4) and IKEv1 [security/ipsec-tools, racoon.conf]

2018-02-27 Thread Harry Schmalzbauer
Bezüglich Harry Schmalzbauer's Nachricht vom 27.02.2018 10:56 (localtime): > Hello, > > I'm out of ideas how to quick-start with if_ipsec(4) and IKEv1. > > I'm familar with security/ipsec-tools, but I couldn't find out how > racoon(8) would interact with cloned if_ipsec(4) interfaces yet. > > Als

if_ipsec(4) and IKEv1 [security/ipsec-tools, racoon.conf]

2018-02-27 Thread Harry Schmalzbauer
Hello, I'm out of ideas how to quick-start with if_ipsec(4) and IKEv1. I'm familar with security/ipsec-tools, but I couldn't find out how racoon(8) would interact with cloned if_ipsec(4) interfaces yet. Also, how to tell racoon(8) to generate such tunnel interfaces, hence policies? I guess the