We found that the RV340 would not accept some FQDN entries in
Client-to-Site Tunnel / Advanced / Remote Endpoint FQDN [name]
whereas, it would accept the FQDN entries in
Client-to-Site Tunnel / Basic / Remote ID FQDN [name]
(You may know that these FQDN entries need not be resolvable names).
The problem was that, unknown to us, our years-old FQDN addresses had not been compliant with the FQDN rules. They include an underscore "_" while only dashes "-" are special characters compliant with the rules.
Making the entries compliant allows the RV340 to accept them in all locations in the settings.
So, I guess the "bug" is that they were being accepted in some setting locations.
