On 04/24/14 22:28, Mike Belopuhov wrote:
On 24 April 2014 22:25, Alexander Hall wrote:
On 04/24/14 21:53, Stuart Henderson wrote:
On 2014/04/24 20:30, Mike Belopuhov wrote:
On 24 April 2014 20:25, Chris Cappuccio wrote:
Mike Belopuhov [m...@belopuhov.com] wrote:
more like it's not sup
On 2014/04/24 22:28, Mike Belopuhov wrote:
> On 24 April 2014 22:25, Alexander Hall wrote:
> > On 04/24/14 21:53, Stuart Henderson wrote:
> >>
> >> On 2014/04/24 20:30, Mike Belopuhov wrote:
> >>>
> >>> On 24 April 2014 20:25, Chris Cappuccio wrote:
>
> Mike Belopuhov [m...@belopuhov.co
On 24 April 2014 22:25, Alexander Hall wrote:
> On 04/24/14 21:53, Stuart Henderson wrote:
>>
>> On 2014/04/24 20:30, Mike Belopuhov wrote:
>>>
>>> On 24 April 2014 20:25, Chris Cappuccio wrote:
Mike Belopuhov [m...@belopuhov.com] wrote:
>
>
> more like it's not supported an
On 04/24/14 21:53, Stuart Henderson wrote:
On 2014/04/24 20:30, Mike Belopuhov wrote:
On 24 April 2014 20:25, Chris Cappuccio wrote:
Mike Belopuhov [m...@belopuhov.com] wrote:
more like it's not supported and is not supposed to work.
it's like running nginx and apache at the same time
hey,
On 2014/04/24 20:30, Mike Belopuhov wrote:
> On 24 April 2014 20:25, Chris Cappuccio wrote:
> > Mike Belopuhov [m...@belopuhov.com] wrote:
> >>
> >> more like it's not supported and is not supposed to work.
> >> it's like running nginx and apache at the same time
> >
> > hey, nginx and httpd run c
On 24 April 2014 20:25, Chris Cappuccio wrote:
> Mike Belopuhov [m...@belopuhov.com] wrote:
>>
>> more like it's not supported and is not supposed to work.
>> it's like running nginx and apache at the same time
>
> hey, nginx and httpd run concurrently quite fine on
> different IP addresses, same
Mike Belopuhov [m...@belopuhov.com] wrote:
>
> more like it's not supported and is not supposed to work.
> it's like running nginx and apache at the same time
hey, nginx and httpd run concurrently quite fine on
different IP addresses, same box :)
On 24 April 2014 12:12, Philipp
wrote:
> Am 22.04.2014 17:28 schrieb Mike Belopuhov:
>
>> more like it's not supported and is not supposed to work.
>
> not supposed as in 'not wanted'?
>
not supposed.
>
>> it's like running nginx and apache at the same time but
>
> Quite frankly: I'm doing that
Am 22.04.2014 17:28 schrieb Mike Belopuhov:
more like it's not supported and is not supposed to work.
not supposed as in 'not wanted'?
it's like running nginx and apache at the same time but
Quite frankly: I'm doing that in some locations ;-)
worse since there are kernel tentacles involved
On 22 April 2014 17:40, Claer wrote:
> On Tue, Apr 22 2014 at 28:17, Mike Belopuhov wrote:
>
>> On 22 April 2014 17:13, Philipp
>> wrote:
>> > It happened! A remote peer *requires* IKEv2 - and I've to do that on a
>> > machine running isakmpd with somewhat 25+ IKEv1 peers.
>> >
>> > First hurdle:
On 22 April 2014 17:13, Philipp
wrote:
> It happened! A remote peer *requires* IKEv2 - and I've to do that on a
> machine running isakmpd with somewhat 25+ IKEv1 peers.
>
> First hurdle: I cannot bind iked to a certain (carp) IP-address. Mad
> workaround: start isakmpd (with Listen-on) first.
> Se
It happened! A remote peer *requires* IKEv2 - and I've to do that on a
machine running isakmpd with somewhat 25+ IKEv1 peers.
First hurdle: I cannot bind iked to a certain (carp) IP-address. Mad
workaround: start isakmpd (with Listen-on) first.
Second hurdle: iked loads "its" SAs and eventually
12 matches
Mail list logo
