OpenVPN doesn't start (hangs) in routing domain.

2016-02-18 Thread Rafał Ramocki
nc interfaces (in main routing domain I have all of this interface types too). How-To-Repeat: Run openvpn in udp server mode with certificate authentication and on tun interface in routing domain (in my case no. 3). Fix: No fix but I found workaround. I'm running openvpn in standard routi

Re: OpenVPN doesn't start (hangs) in routing domain.

2016-02-22 Thread Rafał Ramocki
Użytkownik Stuart Henderson napisał: On 2016/02/16 08:47, Rafał Ramocki wrote: Hi, Synopis: When OpenVPN installed by pkg_add is started in rdomain it hangs during initialization. Category: system user kernel amd64 i386 Environment: System : OpenBSD 5.8 Details : OpenBSD 5.8 (GENERIC.MP

Segmentation fault in sasyncd (running with iked)

2017-07-30 Thread Rafał Ramocki
>Synopsis: Segmentation fault several seconds of running sasyncd >Category: system >Environment: System : OpenBSD 6.1 Details : OpenBSD 6.1 (GENERIC.MP) #8: Tue Jun 27 08:50:26 CEST 2017 rob...@syspatch-61-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENE

Bug in kernel (?) that prevents sasyncd to synchronize states on standby node at startup.

2024-02-19 Thread Rafał Ramocki
3) there is also SADB_X_EXT_MTU extension that will cause message parser fail if it will appear. Additionally in current there is also SADB_X_EXT_IFACE extension that that pfkeyv2_parsemessage is also unaware. Rafał Ramocki Technical Care Center E-mail: [ mai

Re: Bug in kernel (?) that prevents sasyncd to synchronize states on standby node at startup.

2024-02-22 Thread Rafał Ramocki
Hi, Can you just let me know if this patch have a chance to be included in future releases or should I change something in it or take another approach? From: "Rafał Ramocki" To: "bugs" Sent: Friday, February 16, 2024 5:43:04 PM Subject: Bug in kernel (?) that

HA IPSec with AWS - no second flow

2024-03-11 Thread Rafał Ramocki
Hello, Hello, I'm not sure if I'm doing something wrong or if is it a common problem. I have iked.conf set up in the following way: ikev2 active from 10.2.15.0/24 to 172.31.0.0/20 from 10.2.15.0/24 to 172.31.16.0/20 from 10.2.15.0/24 to 172.31.32.0/20 from 169.254.74.238 to 169.254.74.237 l

Re: HA IPSec with AWS - no second flow

2024-03-11 Thread Rafał Ramocki
eab780 I think that (L) marking means that this flow is loaded into the kernel and some of them are missing. It may be some change in iked to fix this, I think. PS: I'm working with devices of different vendors and I think that in some way OpenBSD have problem with this. - Origin