[问答]

用了4个ESP8266组成mesh网，为什么mac list info到后面越来越多，超过了4个？

问答对人有帮助，内容完整，我也想知道答案 0 我用了4个ESP8266组成mesh网，都用了一个程序，只有程序中Dev值不一样（用于标识设备的），下面是输出的log，为什么mac list info到后面越来越多，超过了4个？还有route fail, discard, dst:32:66:3a:66:63:22, src:7d:0d:0a:00:2f:fc hop:1是在哪个函数中打印的？另外经常会p2p mesh is busy或者bcast is busy等发送失败？ ESP-TOUCH FLOW INIT... ESP-TOUCH SET STAtiON MODE ... SC version: V2.5.4 flush ssid:CMCC-djT2 pwd:9vabnpbm mesh version: v1.3.3 mode : sta(2c:3a:e8:15:30:67) add if0 scandone scandone scandone SC_STATUS_FIND_CHANNEL **START ESP-TOUCH** ESP-TOUCH TIMEOUT wzj esptouch_over mode : sta(2c:3a:e8:15:30:67) + softAP(2e:3a:e8:15:30:67) add if1 dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1) bcn 100 connect_dest_chan:0 scandone scan-ch:0 scandone connect_dest_chan:0 scandone state: 0 -> 2 (b0) state: 2 -> 3 (0) state: 3 -> 5 (10) add 0 aid 4 cnt connected with CMCC-djT2, channel 4 dhcp client start... ip:192.168.1.21,mask:255.255.255.0,gw:192.168.1.1 Got IP, IP:192.168.1.21Mask:255.255.255.0GW:192.168.1.1 espconn_mesh_connect, ip:192.168.1.10,rport:7000, port:10040 espconn_mesh_pack_connect, idx:0, 27437209 rip:192.168.1.10rp:7000 con_cb IP:192.168.1.10 rp = 7000, lp = 10040 mesh_enable_cb rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb free heap:42896 free heap:42896 new root:2c:3a:e8:15:30:67 =====mac list info===== root: 2c:3a:e8:15:30:67 mcast mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb recv entrance mesh_json_proto_parser len:32, data:{"Dev":"1","bcast":"2c:3a:e8:15: p2p mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb free heap:42896 =====mac list info===== root: 2c:3a:e8:15:30:67 free heap:42896 mcast mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb recv entrance mesh_json_proto_parser len:32, data:{"Dev":"1","bcast":"2c:3a:e8:15: p2p mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb =====mac list info===== root: 2c:3a:e8:15:30:67 free heap:42896 mcast mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb recv entrance mesh_json_proto_parser len:32, data:{"Dev":"1","bcast":"2c:3a:e8:15: =====mac list info===== root: 2c:3a:e8:15:30:67 p2p mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb free heap:42896 mcast mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb =====mac list info===== root: 2c:3a:e8:15:30:67 recv entrance mesh_json_proto_parser len:32, data:{"Dev":"1","bcast":"2c:3a:e8:15: free heap:42896 p2p mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb free heap:42896 =====mac list info===== root: 2c:3a:e8:15:30:67 mcast mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb recv entrance mesh_json_proto_parser len:32, data:{"Dev":"1","bcast":"2c:3a:e8:15: free heap:42896 p2p mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb =====mac list info===== root: 2c:3a:e8:15:30:67 mcast mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb recv entrance mesh_json_proto_parser len:32, data:{"Dev":"1","bcast":"2c:3a:e8:15: free heap:42896 =====mac list info===== root: 2c:3a:e8:15:30:67 p2p mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb mcast mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb add 1 aid 1 station: 2c:3a:e8:15:2f:fc join, AID = 1 idx:1, rip: 2.255.255.2:29976, mac:2c:3a:e8:15:2f:fc new child node:2c:3a:e8:15:2f:fc =====mac list info===== root: 2c:3a:e8:15:30:67 idx:0, 2c:3a:e8:15:2f:fc =====mac list end====== recv entrance mesh_json_proto_parser len:32, data:{"Dev":"1","bcast":"2c:3a:e8:15: free heap:40656 cidx:0, count:1 mac_list: idx:0, 2c:3a:e8:15:2f:fc p2p mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb cidx:0, count:1 mac_list: idx:0, 2c:3a:e8:15:2f:fc mcast mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb as root, grp_id:18:fe:34:00:00:50 mac:2c:3a:e8:15:30:67 root:2c:3a:e8:15:2d:04 =====mac list info===== root: 2c:3a:e8:15:30:67 idx:0, 2c:3a:e8:15:2f:fc =====mac list end====== route fail, discard, dst:32:66:3a:66:63:22, src:7d:0d:0a:00:2f:fc hop:1 cidx:0, count:2 mac_list: idx:0, 2c:3a:e8:15:2f:fc idx:1, 7d:0d:0a:00:2f:fc recv entrance mesh_json_proto_parser len:32, data:{"Dev":"2","bcast":"2c:3a:e8:15: add 2 aid 2 station: 2c:3a:e8:15:2d:04 join, AID = 2 free heap:40584 recv entrance mesh_json_proto_parser len:32, data:{"Dev":"1","bcast":"2c:3a:e8:15: route fail, discard, dst:3a:66:63:22:7d:0d, src:0a:00:e8:15:2f:fc hop:1 cidx:0, count:3 mac_list: idx:0, 2c:3a:e8:15:2f:fc idx:1, 7d:0d:0a:00:2f:fc idx:2, 0a:00:e8:15:2f:fc free heap:40584 cidx:0, count:3 mac_list: idx:0, 2c:3a:e8:15:2f:fc idx:1, 7d:0d:0a:00:2f:fc idx:2, 0a:00:e8:15:2f:fc p2p mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb station: 2c:3a:e8:15:2d:04 leave, AID = 2 rm 2 cidx:0, count:3 mac_list: idx:0, 2c:3a:e8:15:2f:fc idx:1, 7d:0d:0a:00:2f:fc idx:2, 0a:00:e8:15:2f:fc mcast mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb =====mac list info===== root: 2c:3a:e8:15:30:67 idx:0, 2c:3a:e8:15:2f:fc idx:1, 7d:0d:0a:00:2f:fc idx:2, 0a:00:e8:15:2f:fc =====mac list end====== route fail, discard, dst:32:66:3a:66:63:22, src:7d:0d:0a:00:2f:fc hop:1 cidx:0, count:3 mac_list: idx:0, 2c:3a:e8:15:2f:fc idx:1, 7d:0d:0a:00:2f:fc idx:2, 0a:00:e8:15:2f:fc free heap:41320 recv entrance mesh_json_proto_parser len:32, data:{"Dev":"2","bcast":"2c:3a:e8:15: route fail, discard, dst:3a:66:63:22:7d:0d, src:0a:00:e8:15:2f:fc hop:1 cidx:0, count:3 mac_list: idx:0, 2c:3a:e8:15:2f:fc idx:1, 7d:0d:0a:00:2f:fc idx:2, 0a:00:e8:15:2f:fc recv entrance mesh_json_proto_parser len:32, data:{"Dev":"1","bcast":"2c:3a:e8:15: free heap:41320 =====mac list info===== root: 2c:3a:e8:15:30:67 idx:0, 2c:3a:e8:15:2f:fc idx:1, 7d:0d:0a:00:2f:fc idx:2, 0a:00:e8:15:2f:fc idx:3, 2c:3a:e8:15:2f:56 =====mac list end====== route fail, discard, dst:32:66:3a:35:36:22, src:7d:0d:0a:00:2f:56 hop:1 cidx:0, count:5 mac_list: idx:0, 2c:3a:e8:15:2f:fc idx:1, 7d:0d:0a:00:2f:fc idx:2, 0a:00:e8:15:2f:fc idx:3, 2c:3a:e8:15:2f:56 idx:4, 7d:0d:0a:00:2f:56 cidx:0, count:5 mac_list: idx:0, 2c:3a:e8:15:2f:fc idx:1, 7d:0d:0a:00:2f:fc idx:2, 0a:00:e8:15:2f:fc idx:3, 2c:3a:e8:15:2f:56 idx:4, 7d:0d:0a:00:2f:56 mcast mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb cidx:0, count:5 mac_list: idx:0, 2c:3a:e8:15:2f:fc idx:1, 7d:0d:0a:00:2f:fc idx:2, 0a:00:e8:15:2f:fc idx:3, 2c:3a:e8:15:2f:56 idx:4, 7d:0d:0a:00:2f:56 p2p mesh is busy rip:192.168.1.10rp:7000, lp:10040 esp_mesh_demo_con_cb recv entrance mesh_json_proto_parser len:32, data:{"Dev":"4","bcast":"2c:3a:e8:15: route fail, discard, dst:3a:35:36:22:7d:0d, src:0a:00:e8:15:2f:56 hop:1 cidx:0, count:6 mac_list: idx:0, 2c:3a:e8:15:2f:fc idx:1, 7d:0d:0a:00:2f:fc idx:2, 0a:00:e8:15:2f:fc idx:3, 2c:3a:e8:15:2f:56 idx:4, 7d:0d:0a:00:2f:56 idx:5, 0a:00:e8:15:2f:56 route fail, discard, dst:32:66:3a:66:63:22, src:7d:0d:0a:00:2f:fc hop:1 0 本主题由 Harmony技术专家于 2024-7-11 11:04 审核通过
2024-7-11 07:59:15　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × wang21cj 该类别下有 38 个回答。邀请回答 hgimtk 该类别下有 38 个回答。邀请回答新星之火12138 该类别下有 33 个回答。邀请回答 chm5 该类别下有 32 个回答。邀请回答 zyh34997 该类别下有 32 个回答。邀请回答就好国dd 该类别下有 32 个回答。邀请回答 zaichenxi 该类别下有 31 个回答。邀请回答 heks 该类别下有 31 个回答。邀请回答四川赵赵该类别下有 29 个回答。邀请回答 flowerddd 该类别下有 29 个回答。邀请回答 muwersddg 该类别下有 29 个回答。邀请回答 caosurround 该类别下有 28 个回答。邀请回答星星公交站该类别下有 28 个回答。邀请回答 vinww特烦恼该类别下有 28 个回答。邀请回答 xwgc888 该类别下有 27 个回答。邀请回答 h1654155143.8331 该类别下有 27 个回答。邀请回答 lkjflksjfsa 该类别下有 27 个回答。邀请回答 723662364d 该类别下有 27 个回答。邀请回答 overheat 该类别下有 27 个回答。邀请回答 gvjhvbc 该类别下有 27 个回答。邀请回答举报 duke刘相关推荐 • 如何解决用ESP8266实现PC与STM32F4通讯的问题？ 1872 • 生产者消费者队列状态数据越来越多如何解决？ 10183 • 如何使用ESP8266实现STM32连网？ 1360 • Esp8266会让Mac电脑进入重启循环的原因? 201 • esp8266有没有一种方法可以在连接尝试时读取客户端的mac地址？ 285 • 请问如何用ESP8266发送大量的数据？ 2926 • ESP32-C3蓝牙MESH如何与JDY-24M蓝牙MESH组网通信？ 502 • 3 esp8266 wemos d1 esptool.py chip_id无响应的原因？怎么解决？ 159 • ESP8266 DevKitC V1如何下载FW到定制ESP8266板？ 375 • ESP8266是否可以将内存升级到4MB以上？ 199 1个回答

答案对人有帮助，有参考价值 0 1. MAC列表信息越来越多，超过了4个设备：这可能是因为在Mesh网络中，设备之间的连接可能会发生变化，导致某些设备的MAC地址被重复添加到列表中。另一个可能性是，您的Mesh网络可能与其他附近的设备发生了干扰，导致其他设备的MAC地址也被添加到了列表中。 2. route fail, discard, dst:32:66:3a:66:63:22, src:7d:0d:0a:00:2f:fc hop:1 这个信息是在哪个函数中打印的？这个信息可能是在路由选择或者数据传输过程中打印的。具体是哪个函数，需要查看您的代码实现。通常，这类信息会在路由选择失败或者数据包传输失败时打印。 3. 经常会p2p mesh is busy或者bcast is busy等发送失败：这可能是由于网络拥塞或者设备之间的通信冲突导致的。在Mesh网络中，设备之间的通信是相互依赖的，当一个设备忙于处理其他任务时，可能会导致其他设备发送失败。为了解决这个问题，您可以尝试以下方法： a. 优化代码，减少不必要的通信和任务处理。 b. 调整设备的发送间隔，避免过多的数据包同时发送。 c. 检查设备的信道设置，确保它们在不同的信道上工作，以减少干扰。关于您的日志信息，这里是一个简要的解释： - ESP-TOUCH FLOW INIT...：ESP-TOUCH流程初始化。 - ESP-TOUCH SET STATION MODE ...：设置设备为STA（Station）模式。 - SC version: V2.5.4：SmartConfig版本为V2.5.4。 - flush ssid:CMCC-djT2 pwd:9vabnpbm：清除SSID为CMCC-djT2，密码为9vabnpbm的网络配置。 - mesh version: v1.3.3：Mesh网络版本为v1.3.3。 - mode : sta(2c:3a:e8:15:30:67)：设备模式为STA，MAC地址为2c:3a:e8:15:30:67。 - add if0scandonescandonescandoneSC ...：添加接口，扫描完成。

2024-7-11 16:18:07 评论举报张波