Antonio Aloisio

This is the logs for a working onboarding { "get_onboardinglist":{"FC:34:97:05:F5:E0":{"FC:34:97:3B:34:A0":{"model_name":"ZenWiFi_ET8","ui_model_name":"ZenWiFi ET8","rssi":-19,"source":1,"tcode":"US/01","type":0,"misc_info":{}}}} } { "get_onboardingstatus":{"cfg_obstatus":"2","cfg_obresult":"","cfg_newre":"","cfg_wifi_quality":"-65","cfg_obstart":"","cfg_obcurrent":"1642803255","cfg_obtimeout":"","cfg_obmodel":"","cfg_ui_obmodel":"","cfg_obrssi":"-16","cfg_obcount":"0","cfg_obreboottime":"","cfg_obstage":"0","cfg_obfailresult":"0","cfg_re_maxnum":"9","cfg_recount":"0","cfg_ready":"1"} }

let's analyze why get_onboardinglist doesn't return anything: reason 1: this data gets populated by a json file ONBOARDING_LIST_JSON_PATH The file gets created during scan then remove after. /tmp/onboarding.json {"FC:34:97:05:F5:E0":{"FC:34:97:3B:34:A0":{"status":0,"model_name":"ZenWiFi_ET8","rssi":-18,"ts":1642803863,"ts_eth":0,"source":1,"reboot_time":180,"conn_timeout":180,"traffic_timeout":60,"tcode":"US\/01","type":0}}} but...

on a working router cfg_server prints out this when aimesh node scan finds a new node: gnuton@RT-AX82U-F5E0:/tmp/home/root# amas-utils[amas-utils-int.h(LINE:1996)]:TRACE LINE!!! amas-utils[amas-utils-int.h(LINE:1997)]:LLDP_CUSTOM_TLV_CFG_SET:1997 lldpcli configure lldp custom-tlv replace oui F8,32,E4 subtype 7 oui-info...

$ rgrep lldpcli * lan.c: eval("lldpcli", "configure", "system", "interface", "pattern", bind_ifnames); rc.h:extern int lldpcli_det(void); rc.h:extern int lldpcli_det2(void); services.c: eval("lldpcli","configure","system","interface","pattern",buf); services.c: eval("lldpcli","configure","lldp","tx-interval","10"); services.c: eval("lldpcli","configure","lldp","tx-hold","2"); services.c: sprintf(exec_lldpd, "lldpd -L /usr/sbin/lldpcli -I %s...

Have you noticed this on DSL or RT AX82?

@Seicopath does the latest beta have the same problem? I

Ciao Andrea, Do you lose the connection to main node even if you are very close to the main node? Is there any reason for using repeater image for AI...

Does the standard version permits the DSL-AC68U to be a SLAVE Mesh node (not the primary one)? wrote: > Yes I loose the connection anyway, close or far from the...

If you wanna setup DSL-AC68U as slave AiMesh, just follow the standard procedure. 1. Reset DSL-AC68U to factory and LEAVE IT UNCONFIGURED, no PASSWORD, nothing 2. On the master node...

Is it the same issue described in this thread? this https://www.snbforums.com/threads/stuck-on-export-openvpn-configuration-file.29103/page-2