I don’t think the cipher is your problem, it is the route. In theory you would download the WIndows configuration from the Orbi and then import it to your Beryl and it would work. So I would do this:

  1. Install the most recent firmware for the Orbi, which I think is around October 2021.
  2. Change the router username/password to something really, really strong.
  3. Set up your DDNS method.
  4. Set up your VPN Server as TUN/UDP/their default port. Unfortunately that’s all you are offered.
  5. Download the configuration file for Windows.
  6. Upload it to your Beryl VPN Client.
  7. If it doesn’t work, open the configuration file in a text editor and see that your ddns name & port is specified as the destination. If not, change it and try again. (Also, make sure it includes certificates.)
  8. If that doesn’t work, sanitize the configuration file in a text editor and post it here.

2.4 and 2.5 have changed how the cipher negotiation works, and you are seeing notes to that effect. Normally the server and the client will advertise their preferred cipher, and if they don’t match, then they will negotiate a common cipher. Because you are using the cipher that is in the configuration file, they should match, but unless one or both is set not to negotiate a cipher it should still work. What you are seeing is a warning that the configuration file is specifying -CBC, but it isn’t in the list of ciphers that your client is prepared to negotiate. But as long as the server speaks one of those as well, it should go through.

More on cipher negotiation here: https://community.openvpn.net/openvpn/wiki/CipherNegotiation

The bigger problem is that it looks like the client is trying to get to 192.168.1.0 (which sounds like the LAN network of the Orbi) and doesn’t know how to get there, not least because there are a billion subnets out there with that stupid choice.