On Mon, Jan 23, 2023 at 9:59 AM Roberto Ferrari wrote:
>
> On 23/01/23 18:25, Reid Wahl wrote:
> > On Mon, Jan 23, 2023 at 7:51 AM Roberto Ferrari
> > wrote:
> >>
> >> Hello everybody,
> >> I'd like to understand a strange behavior of a cluster of mine with,
> >> basically, some IPAddr resource
On 23/01/23 18:25, Reid Wahl wrote:
On Mon, Jan 23, 2023 at 7:51 AM Roberto Ferrari wrote:
Hello everybody,
I'd like to understand a strange behavior of a cluster of mine with,
basically, some IPAddr resource and a systemd resource that deals with
netfilter-persistent.
Here the configuration:
On Mon, Jan 23, 2023 at 7:51 AM Roberto Ferrari wrote:
>
> Hello everybody,
> I'd like to understand a strange behavior of a cluster of mine with,
> basically, some IPAddr resource and a systemd resource that deals with
> netfilter-persistent.
> Here the configuration:
>
> primitive
Hello everybody,
I'd like to understand a strange behavior of a cluster of mine with,
basically, some IPAddr resource and a systemd resource that deals with
netfilter-persistent.
Here the configuration:
primitive FW-VIP-Outside IPaddr2 \
params ip=192.168.26.74 cidr_netmask=24
On 23/01/2023 10:38, S Sathish S wrote:
Hi Jan/Team,
Yes , In syslog we noticed "crypto: none" during startup of corosync service.
Ok, so then communication is unencrypted.
In Corosync communication which protocols/ports transfer sensitive data which
need to be secured ?
Corosync
>>> Jan Friesse schrieb am 23.01.2023 um 15:54 in
>>> Nachricht
:
> On 23/01/2023 12:51, Ulrich Windl wrote:
> Jan Friesse schrieb am 23.01.2023 um 10:20 in
> Nachricht
>> :
>>> Hi,
>>>
>>> On 23/01/2023 01:37, S Sathish S via Users wrote:
Hi Team,
corosync 2.4.4 version
On 23/01/2023 12:51, Ulrich Windl wrote:
Jan Friesse schrieb am 23.01.2023 um 10:20 in Nachricht
:
Hi,
On 23/01/2023 01:37, S Sathish S via Users wrote:
Hi Team,
corosync 2.4.4 version provide mechanism to secure the communication path
between nodes of a cluster by default? bcoz in our
>>> Jan Friesse schrieb am 23.01.2023 um 10:20 in
>>> Nachricht
:
> Hi,
>
> On 23/01/2023 01:37, S Sathish S via Users wrote:
>> Hi Team,
>>
>> corosync 2.4.4 version provide mechanism to secure the communication path
> between nodes of a cluster by default? bcoz in our configuration secauth
Hi A Gunasekar,
The pcs-0.9 branch is unsupported and no longer maintained since
2021-04-16. There will be no further releases and commits in that
branch. Pcs-0.9 only works with Pacemaker 1.x and Corosync 2.x and those
have been unsupported for quite some time as well.
I recommend updating
Hi Jan/Team,
Yes , In syslog we noticed "crypto: none" during startup of corosync service.
In Corosync communication which protocols/ports transfer sensitive data which
need to be secured ?
Or It will have only binary protocol like 5405 port for all corosync
communication?
Thanks and
Hi,
On 23/01/2023 01:37, S Sathish S via Users wrote:
Hi Team,
corosync 2.4.4 version provide mechanism to secure the communication path
between nodes of a cluster by default? bcoz in our configuration secauth is
turned off but still communication occur is encrypted.
Note : Capture tcpdump
11 matches
Mail list logo
