[{"data":1,"prerenderedAt":397},["ShallowReactive",2],{"blog-post-zh-nanomq-newsletter-202303":3},{"post":4,"translationPath":-1},{"id":5,"title":6,"author":7,"body":8,"cover":379,"coverHeight":380,"coverWidth":381,"date":382,"description":383,"draft":384,"extension":385,"meta":386,"navigation":387,"path":388,"pinned":384,"seo":389,"sitemap":390,"stem":393,"tags":394,"__hash__":396},"blog_zh\u002Fzh\u002Fblog\u002Fnanomq-newsletter-202303.md","QUIC 双向认证、DDS 代理功能升级",null,{"type":9,"value":10,"toc":363},"minimark",[11,28,33,36,45,54,57,62,65,68,79,82,88,91,94,98,101,121,124,130,134,142,145,148,173,176,182,185,191,194,198,208,214,220,224,246,252,256,285,291,294,298,301,304,307,321,324,357,360],[12,13,14,15,20,21,27],"p",{},"春分时节，万物复苏，",[16,17,19],"a",{"href":18},"\u002Fzh","NanoMQ"," 项目又如期为大家献上了最新的 0.17 版本。这一版本主要对 2 个重要功能进行了升级：",[16,22,26],{"href":23,"rel":24},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fblog\u002Fthe-easiest-guide-to-getting-started-with-mqtt",[25],"nofollow","MQTT"," over QUIC 的双向认证和 DDS 协议转换代理的序列化代码自动生成。另外还新增了 QUIC 传输层的配置参数，增加了 Retain 消息的持久化，以及发布了 NanoSDK 0.9 版本等诸多更新。",[29,30,32],"h2",{"id":31},"quic-双向认证-新增配置参数","QUIC 双向认证 & 新增配置参数",[12,34,35],{},"自从 1994 年提出了 SSL 协议的原始规范以来，TLS 协议也经过了多次版本的更新。最新推出的 TLS 1.3 有望成为有史以来最安全但也最复杂的 TLS 协议。相较于 TLS 1\u002F1.1\u002F1.2，1.3 版本具备更快的连接协商速度，新的密钥协商机制 PSK 和更安全的加密哈希算法。",[12,37,38,39,44],{},"QUIC 在功能层面等价于 TCP+TLS, 并且已采用最新的 TLS 1.3 代替其原有加密协议(QUIC Crypto)。",[16,40,43],{"href":41,"rel":42},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fblog\u002Fquic-protocol-the-features-use-cases-and-impact-for-iot-iov",[25],"QUIC 协议","默认基于 TLS 1.3 完成数据加密连接，且依赖其实现了0-RTT（1-RTT）快速重连握手功能。",[12,46,47],{},[48,49],"img",{"alt":50,"src":51,"title":50,"width":52,"height":53},"MQTT 3.1.1\u002F5.0 over QUIC","\u002Fimages\u002Fblog\u002Fzh\u002Fnanomq-newsletter-202303\u002F01.webp",1370,1498,[12,55,56],{},"当使用 TLS 进行数据加密传输时，如需要验证客户端合法性，经常会使用到双向认证。在之前的 NanoMQ 版本中， MQTT over QUIC 桥接默认只使用单向认证。从 0.17 版本开始用户能够通过配置开启 QUIC（TLS 1.3）的双向认证。",[58,59,61],"h3",{"id":60},"如何使用-quic-的双向认证","如何使用 QUIC 的双向认证",[12,63,64],{},"首先确认自己使用的 NanoMQ 版本已开启了 QUIC 选项，目前使用双向认证只需在配置中设置对应的客户端证书和私钥等文件路径，注意这部分配置无论是使用传统的 TCP 模式还是 QUIC 模式都一样有效：",[12,66,67],{},"旧配置文件格式：",[69,70,75],"pre",{"className":71,"code":73,"language":74},[72],"language-text","bridge.mqtt.emqx.tls.enable=false\nbridge.mqtt.emqx.tls.key_password=yourpass\nbridge.mqtt.emqx.tls.keyfile=\u002Fetc\u002Fcerts\u002Fkey.pem\nbridge.mqtt.emqx.tls.certfile=\u002Fetc\u002Fcerts\u002Fcert.pem\nbridge.mqtt.emqx.tls.cacertfile=\u002Fetc\u002Fcerts\u002Fcacert.pem\n","text",[76,77,73],"code",{"__ignoreMap":78},"",[12,80,81],{},"HOCON 格式:",[69,83,86],{"className":84,"code":85,"language":74},[72],"## 在 bridge 段落中的 connector 部分\n\nbridges.mqtt {\n    nodes = [\n        {\n            name = emqx\n            enable = true\n            connector {\n                ......\n                conn_properties = {\n                    ......\n                }\n                # # Ssl config ##\n                # # Ssl config is also valid when working in MQTT over QUIC mode ##\n                ssl {\n                    enable = false\n                    key_password = \"yourpass\"\n                    keyfile = \"\u002Fetc\u002Fcerts\u002Fkey.pem\"\n                    certfile = \"\u002Fetc\u002Fcerts\u002Fcert.pem\"\n                    cacertfile = \"\u002Fetc\u002Fcerts\u002Fcacert.pem\"\n                }\n            }\n",[76,87,85],{"__ignoreMap":78},[12,89,90],{},"NanoMQ 的 MQTT over TCP 部分采用的是 MbedTLS 库进行加解密，与标准的 TCP 连接不同，QUIC 部分采用的是 MsQUIC 子模块项目内置的 OpenSSL API。OpenSSL 和 MbedTLS 两个目前最流行的 SSL 库在 NanoMQ 项目中可以同时兼容运行。",[12,92,93],{},"目前 NanoMQ 的 MQTT over QUIC 桥接功能暂时不支持 Windows 环境下运行。由于平台兼容性问题，在 Windows 环境中需要替换使用 schannel 来进行 TLS\u002FSSL 加解密。计划在后续的版本中完成 Winodws 环境适配。",[58,95,97],{"id":96},"新增-quic-传输层配置参数","新增 QUIC 传输层配置参数",[12,99,100],{},"根据用户反馈，为了保持连接不断来克服一些极端弱网情况，新版本暴露了 2 个 QUIC 传输层参数供用户自行配置调优。",[102,103,104,115],"ul",{},[105,106,107,110,114],"li",{},[76,108,109],{},"quic_initial_rtt",[111,112,113],"strong",{},"："," 初始的 RTT（Round Trip Time） 预测值。QUIC 采用单向递增的 Packet Number 来标识数据包，即时是重传包也有独特的编号，不会引起重传的歧义性，这样采样 RTT 的测量更准确。QUIC 通过 ACK 记录的接收的数据报文和 ACK 报文之间的延迟来估算RTT，RTT 用于丢失检测和触发重传。这一值就是初始估计网络中的 RTT 情况，用户可以根据实际网络环境设置合理的 RTT 来保证连接不断。",[105,116,117,120],{},[76,118,119],{},"quic_send_idleTimeout","**：**重置 QUIC 传输层拥塞控制检测的最大空闲时间。拥塞控制会修改内部发送的滑动窗口大小，此值影响 QUIC 传输层对于网络变动的敏感度和自动流控。",[12,122,123],{},"配置选项如下：",[69,125,128],{"className":126,"code":127,"language":74},[72],"bridge.mqtt.emqx.quic_initial_rtt=60\nbridge.mqtt.emqx.quic_send_idleTimeout=60\n",[76,129,127],{"__ignoreMap":78},[29,131,133],{"id":132},"idl-序列化代码生成工具","IDL 序列化代码生成工具",[12,135,136,137,141],{},"此前我们提到需要用户自己根据 IDL 格式来开发转 JSON 的序列化\u002F反序列化代码，未来将提供一个自动化的代码生成工具。为了方便 MQTT 用户能够简单快速上手 DDS Proxy 功能，3 月这一工具正式发布：NanoMQ 推出了 IDL 代码生成器功能：idl-serial-code-gen （",[16,138,139],{"href":139,"rel":140},"https:\u002F\u002Fgithub.com\u002Fnanomq\u002Fidl-serial",[25],"）。此工具能够根据用户的 DDS IDL 文件来自动生成 JSON 序列化和反序列化代码。",[12,143,144],{},"由于 DDS 协议为不可读不可直接分析的二进制流，为了提高系统的可互操作性，需要将 DDS 系统的数据在 NanoMQ 中进行必要的转换以供其他中间件如 eKuiper 分析使用。idl-serial-code-gen 工具可以自动生成代码来完成 IDL 结构体和 JSON 格式文本之间的互相转换。",[12,146,147],{},"目前 idl-serial-code-gen 工具支持以下 IDL 特性。",[102,149,150,153,156,159,162,165],{},[105,151,152],{},"Primitive types",[105,154,155],{},"Structs",[105,157,158],{},"String and string with template",[105,160,161],{},"Sequence template",[105,163,164],{},"Enums",[105,166,167,168],{},"Part of ",[16,169,172],{"href":170,"rel":171},"https:\u002F\u002Fcyclonedds.io\u002Fcontent\u002Fguides\u002Fsupported-idl.html",[25],"Annotations",[12,174,175],{},"在上一版本的 NanoMQ DDS Proxy 中，默认所有主题都使用同一个 IDL 结构体定义，这限制了单实例能够转接的数据类型。新版本新增了 DDS 主题和 MQTT 主题的对应配置选项，供用户配置转发的 Topic 对应关系。",[69,177,180],{"className":178,"code":179,"language":74},[72],"forward_rules = {\n      ## DDS to MQTT\n    dds_to_mqtt = {\n        from_dds = \"MQTTCMD\u002Ftopic1\"\n        to_mqtt = \"DDS\u002Ftopic1\"\n        struct_name = \"remote_control_result_t\"\n    }\n    ## MQTT to DDS\n    mqtt_to_dds = {\n        from_mqtt = \"DDSCMD\u002Ftopic1\"\n        to_dds = \"MQTT\u002Ftopic1\"\n        struct_name = \"remote_control_req_t\"\n    }\n}\n",[76,181,179],{"__ignoreMap":78},[12,183,184],{},"同理 nanomq_cli 工具命令行启动时也需要指定结构体名称：启动DDS客户端订阅DDS主题 MQTT\u002Ftopic1 并指定接收的结构体名称 remote_control_req_t。",[69,186,189],{"className":187,"code":188,"language":74},[72],"$ .\u002Fnanomq_cli ddsproxy sub -t \"MQTT\u002Ftopic1\" --struct \"remote_control_req_t\"\n",[76,190,188],{"__ignoreMap":78},[12,192,193],{},"目前默认 DDS 和 MQTT 主题之间一一对应，不允许一个 MQTT 主题上转接多个 DDS 主题。",[58,195,197],{"id":196},"编译-idl-代码生成器-idl-serial-code-gen","编译 IDL 代码生成器 idl-serial-code-gen",[12,199,200,201,204,205],{},"编译 ",[76,202,203],{},"IDL"," 代码生成器 ",[76,206,207],{},"idl-serial",[69,209,212],{"className":210,"code":211,"language":74},[72],"$ git clone https:\u002F\u002Fgithub.com\u002Fnanomq\u002Fidl-serial.git\n$ cd idl-serial\n$ mkdir build && cd build\n$ cmake -G Ninja ..\n$ ninja\n$ sudo ninja install\n",[76,213,211],{"__ignoreMap":78},[12,215,216,217],{},"编译完成生成可执行文件 ",[76,218,219],{},"idl-serial-code-gen",[58,221,223],{"id":222},"生成-json-struct-转换代码","生成 Json\u003C->Struct 转换代码",[12,225,226,227,230,231,234,235,238,239,242,243],{},"使用 ",[76,228,229],{},"idl"," 文件 ",[76,232,233],{},"dds_structs.idl"," 生成 ",[76,236,237],{},"C"," 代码 ",[76,240,241],{},"idl_convert.c"," 和 ",[76,244,245],{},"idl_convert.h",[69,247,250],{"className":248,"code":249,"language":74},[72],"## 生成C代码 idl_convert.c 和 idl_convert.h\n$ .\u002Fidl-serial-code-gen  dds_structs.idl  idl_convert\n",[76,251,249],{"__ignoreMap":78},[58,253,255],{"id":254},"编译nanomq与dds-proxy","编译NanoMQ与DDS Proxy",[257,258,259,271],"ol",{},[105,260,261,262,242,264,266,267,270],{},"将以上步骤中生成的代码文件 ",[76,263,241],{},[76,265,245],{}," 拷贝到 ",[76,268,269],{},"nanomq_cli\u002Fdds2mqtt"," 路径下",[105,272,273,274,277,278,280,281,284],{},"通过 cmake 参数 ",[76,275,276],{},"IDL_FILE_PATH"," 指定 ",[76,279,229],{}," 文件路径 (不指定则默认为工程路径下的 ",[76,282,283],{},"etc\u002Fidl\u002Fdds_type.idl",")",[69,286,289],{"className":287,"code":288,"language":74},[72],"$ git clone https:\u002F\u002Fgithub.com\u002Fnanomq\u002Fnanomq.git\n$ cd nanomq\n## 拷贝以上生成的文件到 nanomq_cli\u002Fdds2mqtt\u002F路径下\n$ cp {YOUR_PATH}\u002Fidl_convert.* nanomq_cli\u002Fdds2mqtt\n$ mkdir build && cd build\n$ cmake -G Ninja -DIDL_FILE_PATH={IDL_PATH} -DCMAKE_PREFIX_PATH={DDS_LIBRARY_PATH} -DBUILD_DDS_PROXY=ON ..\n$ ninja\n$ sudo ninja install\n",[76,290,288],{"__ignoreMap":78},[12,292,293],{},"目前虽然有了自动化代码生成工具，但 DDS Porxy 功能编译安装过程较为繁琐，对于不熟悉工程结构和 DDS 操作的用户来说比较困难。下一版本将通过 Cmake 来集成这一工具并自动化编译过程，无需再手动生成源码文件和拷贝文件到工程下。",[29,295,297],{"id":296},"nanosdk-09-版本发布","NanoSDK 0.9 版本发布",[12,299,300],{},"与 NanoMQ 0.17 一同发布的还有 NanoSDK 0.9 版本。这一版本将 NanoMQ 中创新的 MQTT over QUIC 多流连接功能和在桥接中使用的新的回调函数同步至 NanoSDK。NanoSDK 0.10 版本也在筹备开发中，将提供 MQTT5 over QUIC 协议支持和继续增加类 Paho 的使用方法。",[29,302,303],{"id":303},"其他修复和更新",[12,305,306],{},"NanoMQ 0.17 版本还有一些小功能更新：",[257,308,309,315],{},[105,310,311,314],{},[111,312,313],{},"支持 Retain 消息持久化至 SQLite3","： 根据用户需求，为 NanoMQ 新增了，当开启 SQLite 的消息缓存和持久化功能时默认存储所有的 Retain 消息至 SQLite。",[105,316,317,320],{},[111,318,319],{},"MQTT5 桥接增加更多配置参数："," 为 MQTT5 桥接新增了遗愿消息相关的配置参数。",[12,322,323],{},"此外还有一些问题修复和优化：",[257,325,326,329,332,339,347,354],{},[105,327,328],{},"修复桥接连接中拒绝接受带有 Subscription Identifier 消息的问题。",[105,330,331],{},"修复桥接连接接收到 Retain 消息时会造成数据类型不兼容而导致的协议错误断开。",[105,333,334,335,338],{},"修正了 HTTP API ",[76,336,337],{},"api\u002Fv4\u002Fclients"," 中获取到的错误的会话保持状态。",[105,340,341,342,346],{},"修改了 Broker 的行为：当客户端使用会话保持功能并断开连接时， 之前 Broker 希望能够复用此 Socket 等待客户端自动重连，而不会主动关闭。如今已修改为普通关闭操作。此功能的讨论：（",[16,343,344],{"href":344,"rel":345},"https:\u002F\u002Fgithub.com\u002Fnanomq\u002Fnanomq\u002Fdiscussions\u002F1108",[25],"）",[105,348,349,350,353],{},"在 NanoNNG 模块中更新了新的 ",[76,351,352],{},"nng_mqtt_quic_open_conf"," API 用于开启 QUIC 连接。",[105,355,356],{},"优化 CMakeList 修复 OpenSSL 和 MbedTLS 库在编译阶段造成的不兼容问题。",[29,358,359],{"id":359},"即将到来",[12,361,362],{},"NanoMQ 项目目前的重点是提升 NanoSDK 的易用性和支持 MQTT5 over QUIC 桥接，并且将继续完善 DDS 协议代理功能和提供更多更丰富的文档和教程。原计划中的 SOME\u002FIP 协议代理将推迟至下一个版本发布。",{"title":78,"searchDepth":364,"depth":364,"links":365},2,[366,371,376,377,378],{"id":31,"depth":364,"text":32,"children":367},[368,370],{"id":60,"depth":369,"text":61},3,{"id":96,"depth":369,"text":97},{"id":132,"depth":364,"text":133,"children":372},[373,374,375],{"id":196,"depth":369,"text":197},{"id":222,"depth":369,"text":223},{"id":254,"depth":369,"text":255},{"id":296,"depth":364,"text":297},{"id":303,"depth":364,"text":303},{"id":359,"depth":364,"text":359},"\u002Fimages\u002Fblog\u002Fzh\u002Fnanomq-newsletter-202303\u002Fcover.webp",684,1520,"2023-04-03","本月，NanoMQ 发布了 0.17 版本，主要对 2 个重要功能进行了升级：MQTT over QUIC 的双向认证和 DDS 协议转换代理的序列化代码自动生成。",false,"md",{},true,"\u002Fzh\u002Fblog\u002Fnanomq-newsletter-202303",{"title":6,"description":383},{"loc":388,"images":391,"lastmod":382},[392],{"loc":51},"zh\u002Fblog\u002Fnanomq-newsletter-202303",[395],"NanoMQ Newsletter","ovKbUOjnEGexAIF_iM5kU_XetHsa02AENLxevb1JzXY",1794542897059]