GS fails to decrypt mavlink and tunnel data does not get through

[parijip]

I am unable to get tunnel data going, however, with an Orange-cube connected to the drone - the gs gets the packets but is unable to decrypt. I have generated the keys on the GS - and copied the same to /etc/ on both the drone and gs.
wfb-cli gs and wfb-cli drone outputs are attached..

[parijip]

Attaching the nmcli and iw outputs from drone:

wifibroadcast@drone status:

wifibroadcast@gs status:

nmcli and iw output from gs:

[parijip]

The mtu of drone-wfb interface was autoset to 1443 (and not the default 1445). Used ifconfig command to set the mtu of the drone-wfb interface to 1445 to match with the gs-wfb interface on the gs, before posting the screenshots above.

[svpcom]

1443 is right mtu (radio_mtu - 2). Becase every packet prefixed with two byte length

[svpcom]

You need to use the same keypair from the both sides. I.e. if generate keypair then distribue gs.key to GS and drone.key to drone

[parijip]

I have generated the keys on gs using wfb_keygen. I copied the gs.key to /etc/ on gs and the drone.key onto /etc/ on drone.

[parijip]

Then is the mtu size showing up as 1445 on the gs side wrong? Should I force change that to 1443?

[parijip]

1 more info: the wfb-ng version on the gs is 22.11.30.42394 (as it works with another drone which is running this version of wfb-ng).
The wfb-ng version on the new drone that I am trying to setup is: 23.8.14.60981
Could this mismatch be the cause of the communication failure?

[parijip]

It is working once I changed the version of wfb-ng on the gs to 23.9.26.36320-1