On 2022-04-12, Łukasz Moskała wrote:
> I remember talking with network engineer at one company I used to work at.
> We used fortigate firewalls, and I asked why are we using SSLVPN instead of
> ipsec-based vpn, as both were supported.
>
> He said something along the lines of "ipsec does not work
On 12.04.22 15:26, Łukasz Moskała wrote:
I remember talking with network engineer at one company I used to work at.
We used fortigate firewalls, and I asked why are we using SSLVPN instead of
ipsec-based vpn, as both were supported.
He said something along the lines of "ipsec does not work when
Den tis 12 apr. 2022 kl 15:30 skrev Łukasz Moskała :
> I remember talking with network engineer at one company I used to work at.
> We used fortigate firewalls, and I asked why are we using SSLVPN instead of
> ipsec-based vpn, as both were supported.
> He said something along the lines of "ipsec d
Issue solved updating my linux strongswan client!!!
Sorry for the trouble...
Thanks to everybody 😊
On Tue, Apr 12, 2022 at 01:03:55AM +0200, Ettore Tagarelli wrote:
> If I use the "dynamic keyword I get this error: "no IP address found for
> dynamic" though "config address 192.168.98.1/24" is there.
> Using 0.0.0.0/32 instead of 0.0.0.0/0 causes that traffic is not routed
> ('cause /32 restrict
Dnia Tue, Apr 12, 2022 at 03:06:50PM +0200, Ettore Tagarelli napisał(a):
> Updated to 7.0
> ...same problem 🙁
I remember talking with network engineer at one company I used to work at.
We used fortigate firewalls, and I asked why are we using SSLVPN instead of
ipsec-based vpn, as both were suppor
On Tue, Apr 12, 2022 at 03:06:50PM +0200, Ettore Tagarelli wrote:
> Updated to 7.0
> ...same problem 🙁
What does the updated config look like?
"from 0.0.0.0/0 to dynamic" should work in 7.0.
Updated to 7.0
...same problem 🙁
On 2022-04-11, Ettore Tagarelli wrote:
> If I use the "dynamic keyword I get this error: "no IP address found for
> dynamic" though "config address 192.168.98.1/24" is there.
> Using 0.0.0.0/32 instead of 0.0.0.0/0 causes that traffic is not routed
> ('cause /32 restrict the only address possible
-- Forwarded message -
Da: Ettore Tagarelli
Date: mar 12 apr 2022 alle ore 01:03
Subject: Re: IKEV2 two devices can connect but only one can make traffic
To:
If I use the "dynamic keyword I get this error: "no IP address found for
dynamic" though "config add
If I use the "dynamic keyword I get this error: "no IP address found for
dynamic" though "config address 192.168.98.1/24" is there.
Using 0.0.0.0/32 instead of 0.0.0.0/0 causes that traffic is not routed
('cause /32 restrict the only address possible to 0.0.0.0) though
connection happens correctly.
On Mon, Apr 11, 2022 at 11:13:45PM +0200, Ettore Tagarelli wrote:
> this is my iked.conf
> as far as I know the "somename" Stuart wrote about is automatically added
> by iked.
I don't exactly remember how it worked back in 6.6 either but you
could try 0.0.0.0/32 instead of 0.0.0.0/0.
In any case I
this is my iked.conf
as far as I know the "somename" Stuart wrote about is automatically added
by iked.
user "cash" "password1"
user "phosh" "password2"
ikev2 passive esp \
from 0.0.0.0/0 to 192.168.98.1/24 \
local 192.168.99.3 peer any \
eap "mschap-v2" \
On 2022-04-11, Ettore Tagarelli wrote:
> Hello,
> I've an Openbsd 6.6 machine with IKEV2. I always used it with only one
> client connected and it always worked. Trying to connect with two clients
> (behind the same NAT) I found out that the connection seems established but
> only one client works
Hello,
I've an Openbsd 6.6 machine with IKEV2. I always used it with only one
client connected and it always worked. Trying to connect with two clients
(behind the same NAT) I found out that the connection seems established but
only one client works.
Can anybody help me? Thanks 😊
15 matches
Mail list logo
