Insecure migration settings

[Alessandro 123]

aes128-gcm@openssh.com seems faster than arcfour and is ok

 

[fabian]

aes128-gcm@openssh.com seems faster than arcfour and is ok

so placing it first in the Ciphers line in /root/.ssh/config should work then

 

[dmkjr]

After editing the /datacenter config, do you need to restart any services? Also, do you need to do this on both nodes that you is involved in the transfer?

Edit: I see that editing the /datacenter file is shared across nodes.

 

[fabian]

you shouldn't need to reload any services, and the file is shared across all cluster nodes like you already found out

 

[Dark26]

is it working ?

migration: [type=]<secure|insecure> [,network=<CIDR>]
For cluster wide migration settings.

network=<CIDR>
CIDR of the (sub) network that is used for migration. Used as a fallback for replications jobs if the replication network setting is not set

type=<insecure | secure> (default = secure)
Migration traffic is encrypted using an SSH tunnel by default. On secure, completely private networks this can be disabled to increase performance.

migration_unsecure: <boolean>
Migration is secure using SSH tunnel by default. For secure private networks you can disable it to speed up migration. Deprecated, use the migration property instead!

I try with migration: type=insecure and it still use ssh.

if i put migration_unsecure: 1 instead it's working.


i have the last version of pve. ( 9.0.11)