Optimize settings and resolve warnings - used inconsistently

[deleted]

I am configuring a server and some vpn clients. After adjusting the settings, I still receive the following warnings, both client-side and server-side:
Client config:

proto udp
client
remote xxxx 1194
dev tap0
nobind
compress lzo
tun-mtu 1500
fragment 1300
mssfix
route-nopull
mute 3
resolv-retry infinite
connect-retry 15 60
ca ca.crt
cert xxx.crt
key xxx.key

Warnings:

Thu Oct  4 07:32:33 2018 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1586', remote='link-mtu 1578'
Thu Oct  4 07:32:33 2018 WARNING: 'cipher' is used inconsistently, local='cipher AES-256-GCM', remote='cipher BF-CBC'
Thu Oct  4 07:32:33 2018 WARNING: 'auth' is used inconsistently, local='auth [null-digest]', remote='auth SHA1'
Thu Oct  4 07:32:33 2018 WARNING: 'keysize' is used inconsistently, local='keysize 256', remote='keysize 128'

Server config:

dev tap0
ifconfig 192.168.200.1 255.255.255.0
server-bridge 192.168.200.1 255.255.255.0 192.168.200.200 192.168.200.254
mode server
client-to-client
tls-server
proto udp
port 1194
client-config-dir /dir/config
dh dh2048.pem
ca ca.crt
cert xx.crt
key xx.key
log xx.log
status xx.log
keepalive 10 60
tun-mtu 1500
fragment 1300
mssfix
mute 3
compress lzo

Warnings:

Thu Oct  4 08:32:39 2018 teste/177.73.140.43:58414 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1578', remote='link-mtu 1586'
Thu Oct  4 08:32:39 2018 teste/177.73.140.43:58414 WARNING: 'cipher' is used inconsistently, local='cipher BF-CBC', remote='cipher AES-256-GCM'
Thu Oct  4 08:32:39 2018 teste/177.73.140.43:58414 WARNING: 'auth' is used inconsistently, local='auth SHA1', remote='auth [null-digest]'
Thu Oct  4 08:32:39 2018 teste/177.73.140.43:58414 WARNING: 'keysize' is used inconsistently, local='keysize 128', remote='keysize 256'

Should I worry about them?
Should I configure these options manually on the server and client side or leave the automatic configuration?
In addition I appreciate if you give me the configuration suggestions for improvements. Clients are configured and shipped to different parts of my country, I do not have physical access to them. And the vpn server is a cloud server.
Even with the errors the connection is established and it seems stable, even if it is repeated a few times in the log.
The openvpn version is 2.4.0 on both sides.

TinCanTech

These Warnings are known and understood and they do not constitute a security threat.
They can be safely ignored for the time being.

In time they will probably be resolved but they are not currently a priority.

[deleted]

TinCanTech wrote These Warnings are known and understood and they do not constitute a security threat.
They can be safely ignored for the time being.

In time they will probably be resolved but they are not currently a priority.

Thanks for your quick reply. I'll ignore the warnings and wait for updates.
About setup, is there any improvement that can be implemented?

TinCanTech

JonatasP wrote About setup, is there any improvement that can be implemented?

You are using --dev tap etc .. --dev tun is preferred ..

If you mean "can you change your setup to silence the Warnings" ..
then it is partially possible but not worth the time.

[deleted]

TinCanTech wrote
JonatasP wrote About setup, is there any improvement that can be implemented?
You are using --dev tap etc .. --dev tun is preferred ..

If you mean "can you change your setup to silence the Warnings" ..
then it is partially possible but not worth the time.

If the warnings do not influence the good functioning of vpn or generate some security flaw, then there are no problems.
I remember that I used tap because I needed a bridge between the lan interface and theVPN, now I really do not need it anymore.
Then I'll make the suggested change.
Thanks.