[{"data":1,"prerenderedAt":275},["ShallowReactive",2],{"blog-post-zh-nanomq-newsletter-202208":3},{"post":4,"translationPath":-1},{"id":5,"title":6,"author":7,"body":8,"cover":258,"coverHeight":259,"coverWidth":56,"date":260,"description":261,"draft":262,"extension":263,"meta":264,"navigation":265,"path":266,"pinned":262,"seo":267,"sitemap":268,"stem":271,"tags":272,"__hash__":274},"blog_zh\u002Fzh\u002Fblog\u002Fnanomq-newsletter-202208.md","NanoMQ Newsletter 2022-08｜v0.11：MQTT 5.0 + MQTT over QUIC 桥接，新增 HTTP API 监控客户端状态",null,{"type":9,"value":10,"toc":243},"minimark",[11,28,32,35,40,49,58,61,67,70,81,92,98,101,107,110,114,117,123,126,130,139,142,148,151,157,166,169,172,176,185,188,194,198,205,211,215,237,240],[12,13,14,15,21,22,27],"p",{},"8 月，NanoMQ 继续保持稳步更新。最新的 0.11.0 版本已于 8月底正式发布（",[16,17,18],"a",{"href":18,"rel":19},"https:\u002F\u002Fgithub.com\u002Fnanomq\u002Fnanomq\u002Freleases\u002Ftag\u002F0.11.0",[20],"nofollow","）。此版本继续增强了桥接功能，增加了 ",[16,23,26],{"href":24,"rel":25},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fblog\u002Fthe-easiest-guide-to-getting-started-with-mqtt",[20],"MQTT"," 5.0 + MQTT over QUIC 桥接模式，新增和修复了对已连接客户端状态进行监控和查询的 HTTP API。此外各项性能优化和缺陷修复也在持续进行中。",[29,30,31],"h2",{"id":31},"桥接功能更新",[12,33,34],{},"作为 NanoMQ 最为广泛使用的功能之一，桥接功能本月得到重大更新升级，新增了 2 种桥接模式：MQTT over QUIC 桥接和 MQTT 5.0 协议桥接。",[36,37,39],"h3",{"id":38},"mqtt-over-quic-桥接","MQTT over QUIC 桥接",[12,41,42,43,48],{},"继 EMQX 5.0 全球率先发布 MQTT over QUIC 支持后，NanoMQ 项目也为了降低此功能的使用门槛在 0.11 版本推出了 MQTT over QUIC 桥接功能。目前 NanoSDK 已支持以 ",[16,44,47],{"href":45,"rel":46},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fblog\u002Fquic-protocol-the-features-use-cases-and-impact-for-iot-iov",[20],"QUIC 协议","作为 MQTT 的传输层，因此与其兼容的 NanoMQ 项目的桥接功能也一并得到了无缝升级。用户可以使用 QUIC 作为 MQTT 协议的传输层来与 EMQX 5.0 消息服务建立桥接进行数据同步，从而为无法集成或找到合适的 MQTT over QUIC SDK 的端侧设备和难以修改固件的嵌入式设备提供在 IoT 场景利用 QUIC 协议优势的捷径。",[12,50,51],{},[52,53],"img",{"alt":39,"src":54,"title":55,"width":56,"height":57},"\u002Fimages\u002Fblog\u002Fzh\u002Fnanomq-newsletter-202208\u002F01.webp","桥接结构示意图",1520,415,[12,59,60],{},"在需要与云端 MQTT 服务进行数据同步的各种物联网场景中，通过 NanoMQ 的多协议接入能力，可以将其作为边缘消息总线和统一的数据空间，统一汇聚诸如 HTTP、MQTT 3.1.1\u002F5.0、WebSocket、nanomsg\u002Fnng 和 ZeroMQ 等常用的 broker\u002Fbrokerless 消息协议，再由 NanoMQ 内部强大的 Actor 消息处理模型转化成标准的 MQTT 消息后，通过 QUIC 传输层的 0RTT 快速重连和被动地址切换等功能来克服网际漫游、弱网传输和 TCP 队头阻塞等各类常见的物联网连接问题。还可以通过 NanoMQ 的规则引擎对数据做重定向、本地缓存或持久化。依靠 EMQX+NanoMQ 的云边一体化的消息架构，用户能够快速且低成本的在泛物联网场景中完成跨时空地域的数据采集和同步需求。",[12,62,63],{},[64,65,66],"strong",{},"如何使用 MQTT over QUIC 桥接功能",[12,68,69],{},"目前 NanoMQ 的 QUIC 模组处于默认关闭状态，用户如需使用需通过编译选项打开后安装使用，完整的下载和编译安装命令可以参考：",[71,72,77],"pre",{"className":73,"code":75,"language":76},[74],"language-text","git clone https:\u002F\u002Fgithub.com\u002Fnanomq\u002Fnanomq.git\ncd nanomq ; git submodule update --init --recursive (同步submodule时可能耗时较久)\n\nmkdir build && cd build\ncmake -G Ninja -DNNG_ENABLE_QUIC=ON ..\nsudo ninja install\n","text",[78,79,75],"code",{"__ignoreMap":80},"",[12,82,83,84,87,88,91],{},"开启 QUIC 桥接功能的 NanoMQ 编译安装完成后，可以在配置文件",[78,85,86],{},"\u002Fetc\u002Fnanomq_bridge.conf","中配置 MQTT over QUIC 桥接功能和对应的主题，使用 ",[78,89,90],{},"mqtt-quic"," 作为 URL 前缀即是采用 QUIC 作为 MQTT 的传输层：",[71,93,96],{"className":94,"code":95,"language":76},[74],"## Bridge address: host:port .\n##\n## Value: String\n## Example: ## Example: mqtt-tcp:\u002F\u002Fbroker.emqx.io:1883 （这是标准MQTT over TCP）\nbridge.mqtt.emqx.address=mqtt-quic:\u002F\u002F54.75.171.11:14567\n\n## Protocol version of the bridge. （注意：QUIC桥接目前只支持V4即MQTT 3.1.1版本）\nbridge.mqtt.emqx.proto_ver=4\n\n## Whether to enable bridge mode for mqtt bridge\n## Value: boolean\nbridge.mqtt.emqx.bridge_mode=true\n\n## The ClientId of a remote bridge.\n## Default random string.\n## Value: String\n#bridge.mqtt.emqx.clientid=bridge_client\n\n## Ping interval of a down bridge.\n## Value: Duration\n## Default: 10 seconds\nbridge.mqtt.emqx.keepalive=60\n\n## The Clean start flag of a remote bridge.\n##\n## Value: boolean\n## Default: true\nbridge.mqtt.emqx.clean_start=true\n\n## The username for a remote bridge.\nbridge.mqtt.emqx.username=username\n\n## The password for a remote bridge.\nbridge.mqtt.emqx.password=passwd\n\n## Topics that need to be forward to IoTHUB\n##\n## Value: String\n## Example: topic1\u002F#,topic2\u002F#\nbridge.mqtt.emqx.forwards=topic1\u002F#,topic2\u002F#\n\n## Need to subscribe to remote broker topics\n##\n## Value: String\nbridge.mqtt.emqx.subscription.1.topic=cmd\u002Ftopic1\n",[78,97,95],{"__ignoreMap":80},[12,99,100],{},"然后启动 NanoMQ 即可：",[71,102,105],{"className":103,"code":104,"language":76},[74],"nanomq start --bridge \u003CPATH of nanomq_bridge.conf>\n",[78,106,104],{"__ignoreMap":80},[12,108,109],{},"验证 QUIC 桥接是否成功，只需往桥接的上下行主题发送数据即可，也可以使用 NanoMQ 自带的 nanomq_cli 工具中的 QUIC 客户端来与 EMQX 5.0 测试验证。",[36,111,113],{"id":112},"mqtt-50-桥接","MQTT 5.0 桥接",[12,115,116],{},"除了 QUIC 桥接，0.11 版本也支持使用 MQTT 5.0 进行桥接，用户只需在配置文件中修改桥接的协议版本即可：",[71,118,121],{"className":119,"code":120,"language":76},[74],"## Protocol version of the bridge. （注意：MQTT 5.0 只适用于 Vanila MQTT）\nbridge.mqtt.emqx.proto_ver=5\n",[78,122,120],{"__ignoreMap":80},[12,124,125],{},"之后用户就可以通过桥接连接转发 MQTT 5.0 消息了，享受诸如自定义属性等新特性。",[29,127,129],{"id":128},"http-api-更新","HTTP API 更新",[12,131,132,133,138],{},"通过 HTTP REST API 来对边缘服务进行监控和运维一直是广大普通用户的需求之一，NanoMQ 0.11 也新增了对当前连接的 ",[16,134,137],{"href":135,"rel":136},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fblog\u002Fmqtt-client-tools",[20],"MQTT 客户端","信息的查询 API，方便第三方应用快速准确的获取所有客户端的在线情况，或查询某个特定客户端的健康状态。",[12,140,141],{},"获取所有在线客户端的情况：",[71,143,146],{"className":144,"code":145,"language":76},[74],"$ curl -i --basic -u admin:public -X GET \"http:\u002F\u002Flocalhost:8081\u002Fapi\u002Fv4\u002Fclients\"\n\n{\"code\":0,\"data\":[{\"client_id\":\"nanomq-f6d6fbfb\",\"username\":\"alvin\",\"keepalive\":60,\"conn_state\":\"connected\",\"clean_start\":true,\"proto_name\":\"MQTT\",\"proto_ver\":5,\"recv_msg\":3},{\"client_id\":\"nanomq-bdf61d9b\",\"username\":\"nanomq\",\"keepalive\":60,\"conn_state\":\"connected\",\"clean_start\":true,\"proto_name\":\"MQTT\",\"proto_ver\":5,\"recv_msg\":0}]}\n",[78,147,145],{"__ignoreMap":80},[12,149,150],{},"通过客户端 ID 查询指定客户端的在线情况",[71,152,155],{"className":153,"code":154,"language":76},[74],"$ curl -i --basic -u admin:public -X GET \"http:\u002F\u002Flocalhost:8081\u002Fapi\u002Fv4\u002Fclients\u002Fnanomq-29978ec1\"\n\n{\"code\":0,\"data\":[{\"client_id\":\"nanomq-29978ec1\",\"username\":\"\",\"keepalive\":60,\"conn_state\":\"connected\",\"clean_start\":true,\"proto_name\":\"MQTT\",\"proto_ver\":5}]}\n",[78,156,154],{"__ignoreMap":80},[12,158,159,160,165],{},"关于 API 的请求和返回参数详情，请参阅 NanoMQ Docs（",[16,161,164],{"href":162,"rel":163},"https:\u002F\u002Fnanomq.io\u002Fdocs\u002Fzh\u002Flatest\u002Fhttp-api\u002Fv4.html#%E5%AE%A2%E6%88%B7%E7%AB%AF",[20],"https:\u002F\u002Fnanomq.io\u002Fdocs\u002Fzh\u002Flatest\u002Fhttp-api\u002Fv4.html#客户端"," ）。",[29,167,168],{"id":168},"其他功能更新",[12,170,171],{},"同时，NanoMQ 0.11 还响应用户和社区要求更新和优化了如下功能：",[36,173,175],{"id":174},"退避时间设置-backoff-timer","退避时间设置 （Backoff timer）",[12,177,178,179,184],{},"在 MQTT 协议中规定 Broker 要在 1.5 倍于客户端设置的 ",[16,180,183],{"href":181,"rel":182},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fblog\u002Fmqtt-keep-alive",[20],"Keep Alive"," 时间后踢出没有活动的连接。但是实际场景中许多用户希望能够自由灵活调节这一时间长度以适应不同的网络环境。所以新增了这一配置选项，用户通过配置该选项来调整 NanoMQ 处理非活动客户端的最大时间上限。",[12,186,187],{},"例如，如果按照以下设置，如果一个客户端的 Keep Alive 时间设置为 60s，且一直没有活动，NanoMQ 将会在 1.25 * 60 = 75s 后关闭此客户端的连接。",[71,189,192],{"className":190,"code":191,"language":76},[74],"## The backoff for MQTT keepalive timeout.\n## broker will discolse client when there is no activity for\n## 'Keepalive * backoff * timeout.\n##\n## Value: Float > 0.5\nkeepalive_backoff=1.25\n",[78,193,191],{"__ignoreMap":80},[36,195,197],{"id":196},"mqtt-over-quic-cli-工具","MQTT over QUIC CLI 工具",[12,199,200,201,204],{},"如果通过",[78,202,203],{},"-DNNG_ENABLE_QUIC=ON"," 开启了 QUIC 模块，那么会自动编译 nanomq_cli 中的 MQTT over QUIC 客户端工具：",[71,206,209],{"className":207,"code":208,"language":76},[74],"nanomq_cli quic --help\nUsage: quic conn \u003Curl>\n       quic sub  \u003Curl> \u003Cqos> \u003Ctopic>\n       quic pub  \u003Curl> \u003Cqos> \u003Ctopic> \u003Cdata>\n\n## subscribe example\nnanomq_cli quic sub mqtt-quic:\u002F\u002F54.75.171.11:14567 2 msg\n",[78,210,208],{"__ignoreMap":80},[29,212,214],{"id":213},"bug-修复及优化","Bug 修复及优化",[216,217,218,222,225,228,231,234],"ol",{},[219,220,221],"li",{},"为 NanoMQ 增加了自动化 CI 测试框架，以保证测试覆盖率。",[219,223,224],{},"修复了 WebSocket&TLS 的传输层。",[219,226,227],{},"增加了 nanomq_cli 工具的帮助信息。",[219,229,230],{},"修复了一个使用共享订阅时可能导致主题匹配不正确的问题。",[219,232,233],{},"修复了客户端使用持久会话后断开连接，会话总是比设定时间更早过期的问题。",[219,235,236],{},"修复了桥接连接使用非异步订阅方式可能造成的线程阻塞问题。",[29,238,239],{"id":239},"即将到来",[12,241,242],{},"下个版本中，NanoMQ 将为大家带来规则引擎的重发布和热更新功能，并且增加桥接连接的状态管理能力。未来 NanoMQ 还将继续设计和规划利用 QUIC 的 Multi-Stream 特性来应对物联网场景里的多种传输媒介共用带来的链接复用问题，也会在 QUIC 的 Flow Control 基础上完成多种类型数据流统一调度的本地数据网关代理功能。",{"title":80,"searchDepth":244,"depth":244,"links":245},2,[246,251,252,256,257],{"id":31,"depth":244,"text":31,"children":247},[248,250],{"id":38,"depth":249,"text":39},3,{"id":112,"depth":249,"text":113},{"id":128,"depth":244,"text":129},{"id":168,"depth":244,"text":168,"children":253},[254,255],{"id":174,"depth":249,"text":175},{"id":196,"depth":249,"text":197},{"id":213,"depth":244,"text":214},{"id":239,"depth":244,"text":239},"\u002Fimages\u002Fblog\u002Fzh\u002Fnanomq-newsletter-202208\u002Fcover.webp",684,"2022-09-01","八月，0.11.0 版本发布：增加了 MQTT 5.0 + MQTT over QUIC 桥接模式，新增和修复了对已连接客户端状态进行监控和查询的 HTTP API。",false,"md",{},true,"\u002Fzh\u002Fblog\u002Fnanomq-newsletter-202208",{"title":6,"description":261},{"loc":266,"images":269,"lastmod":260},[270],{"loc":54},"zh\u002Fblog\u002Fnanomq-newsletter-202208",[273],"NanoMQ Newsletter","tupHmMnXCiWOtErAeTXuGmEKjKz6jFbS2EDD7ehfRE0",1794542897680]