Asus AX53U and Zyxel WSM20: Problems after sysupgrade from 23.05.2 to 23.05.3

I started at
https://firmware-selector.openwrt.org/?version=23.05.3&target=ramips%2Fmt7621&id=asus_rt-ax53u

and used these packages:

base-files busybox ca-bundle dnsmasq dropbear firewall4 fstools kmod-gpio-button-hotplug kmod-leds-gpio kmod-mt7915-firmware kmod-nft-offload kmod-usb-ledtrig-usbport kmod-usb3 libc libgcc logd luci mtd netifd nftables odhcp6c odhcpd-ipv6only opkg ppp ppp-mod-pppoe procd procd-seccomp procd-ujail uboot-envtools uci uclient-fetch urandom-seed urngd arp-scan arp-scan-database iputils-arping iperf iperf3 libustream-openssl mesh11sd nmap static-neighbor-reports wpad-openssl

I renamed the file to
openwrt-23.05.3_my_1446f9d3b850-ramips-mt7621-asus_rt-ax53u-squashfs-sysupgrade.bin

"My" helps me to identify firmware with my individual packages.

Then I checked the download with sha256: cac528ff9a724946c40267a396a951e4f25858b654b30e0449bb03eaf365c580

As a next step I copied the download to the AX 53U with scp and checked again.

$ ssh root@192.168.178.18


BusyBox v1.36.1 (2023-12-28 13:27:49 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 23.05.2, r23630-842932a63d
 -----------------------------------------------------

You see, I used OpenWrt 23.05.2 before flashing.

root@AX53U-S1:~# sha256sum /tmp/openwrt-23.05.3_my_1446f9d3b850-ramips-mt7621-asus_rt-ax53u-squashfs-sysupgrade.bin 
cac528ff9a724946c40267a396a951e4f25858b654b30e0449bb03eaf365c580  /tmp/openwrt-23.05.3_my_1446f9d3b850-ramips-mt7621-asus_rt-ax53u-squashfs-sysupgrade.bin

Same checksum as before:

Now I flashed:

root@AX53U-S1:~# sysupgrade /tmp/openwrt-23.05.3_my_1446f9d3b850-ramips-mt7621-asus_rt-ax53u-squashfs-sysupgrade.bin 
Sun Mar 31 19:34:19 UTC 2024 upgrade: Saving config files...
Sun Mar 31 19:34:20 UTC 2024 upgrade: Commencing upgrade. Closing all shell sessions.
Command failed: Connection failed

Nothing special till now,

After a while I see the following. Same after I switched off the router.

$ ping 192.168.178.18
PING 192.168.178.18 (192.168.178.18) 56(84) bytes of data.
From 192.168.178.152 icmp_seq=2 Redirect Host(New nexthop: 192.168.178.18)
From 192.168.178.152 icmp_seq=3 Redirect Host(New nexthop: 192.168.178.18)
From 192.168.178.152 icmp_seq=4 Redirect Host(New nexthop: 192.168.178.18)

I have no idea what 192.168.178.152 is

$ ping 192.168.178.152
PING 192.168.178.152 (192.168.178.152) 56(84) bytes of data.
64 bytes from 192.168.178.152: icmp_seq=1 ttl=64 time=4.54 ms
64 bytes from 192.168.178.152: icmp_seq=2 ttl=64 time=4.38 ms
64 bytes from 192.168.178.152: icmp_seq=3 ttl=64 time=2.90 ms

The DHCP-server at 192.168.178.13/cgi-bin/luci/admin/network/dhcp shows:

Active DHCP Leases
Hostname	IPv4 address	MAC address	Lease time remaining
meshnode-0ec8 (meshnode-0ec8.lan)	192.168.178.152	C8:xxx:C8	11h 39m 18s
root@meshnode-0ec8:~# ubus call system board
{
	"kernel": "5.15.150",
	"hostname": "meshnode-0ec8",
	"system": "MediaTek MT7621 ver:1 eco:3",
	"model": "ASUS RT-AX53U",
	"board_name": "asus,rt-ax53u",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "23.05.3",
		"revision": "r23809-234f1a2efa",
		"target": "ramips/mt7621",
		"description": "OpenWrt 23.05.3 r23809-234f1a2efa"
	}
}

There is still 192.168.178.18 in the network file.

root@meshnode-0ec8:/etc/config# cat /etc/config/network | grep 192
	option ipaddr '192.168.178.18'
	option gateway '192.168.178.1'
	list dns '192.168.178.1'

So why the configuration of the AX53U was changed to something like mesh?

Actually I don't want to use mesh at the moment as long as I am not sure, that I really need it. But the packages for mesh should be available, if I want mesh.

This mesh-mystery didn't happen with 4 old devices with same extra mesh-packages, namely 3 TP-Link Archer C7 v5 and Netgear-Extender EX6150v2. All very similar configured.

root@meshnode-0ec8:/etc/config# ls -1
dhcp
dropbear
firewall
luci
mesh11sd
network
openssl
radius
rpcd
static-neighbor-report
system
ubootenv
ucitrack
uhttpd
wireless
root@meshnode-0ec8:/etc/config# cat /etc/config/mesh11sd 

config mesh11sd 'setup'
	option enabled '1'
	option debuglevel '1'
	option checkinterval '10'
	option interface_timeout '10'

	###########################################################################################
	# mesh_basename (optional)
	# The first 4 characters after non alphanumerics are removed are used as the mesh_basename
	# The mesh_basename is used to construct a unique mesh interface name of the form m-xxxx-n
	# Default: 11s
	# Results in ifname=m-11s-0 for the first mesh interface
	# Example: link
	# Results in ifname=m-link-0

	#option mesh_basename 'link'

	###########################################################################################
	# portal_detect (optional)
	# Detect if the meshnode is a portal, meaning it has an upstream wan link.
	# If the upstream link is active, the router hosting the meshnode will serve ipv4 dhcp into the mesh network.
	# If the upstream link is not connected, dhcp will be disabled and the meshnode will function as a level 2 bridge on the mesh network.
	# Default 1 (enabled). Set to 0 to disable.

	#option portal_detect '0'

config mesh11sd 'mesh_params'
	option mesh_fwding '1'
	option mesh_rssi_threshold '-70'
	option mesh_gate_announcements '1'
	option mesh_hwmp_rootmode '3'
	option mesh_max_peer_links '8'

config mesh11sd 'setup'
option enabled '1'

Must be done automatically.

I tried the same now with a Zyxel WSM20:

my packages with the WSM20:

base-files busybox ca-bundle dnsmasq dropbear firewall4 fstools kmod-gpio-button-hotplug kmod-leds-gpio kmod-mt7915-firmware kmod-nft-offload libc libgcc logd luci mtd netifd nftables odhcp6c odhcpd-ipv6only opkg ppp ppp-mod-pppoe procd procd-seccomp procd-ujail uboot-envtools uci uclient-fetch urandom-seed urngd arp-scan arp-scan-database iputils-arping iperf iperf3 libustream-openssl mesh11sd nmap static-neighbor-reports wpad-openssl

$ ping 192.168.178.15
PING 192.168.178.15 (192.168.178.15) 56(84) bytes of data.
From 192.168.178.152 icmp_seq=1 Redirect Host(New nexthop: 192.168.178.15)
From 192.168.178.104 icmp_seq=1 Redirect Host(New nexthop: 192.168.178.15)

So the ping to .15 shows now .152 (Asus) and .104 (Zyxel)

Connecting to .104 I see:

root@meshnode-4070:~# ubus call system board
{
	"kernel": "5.15.150",
	"hostname": "meshnode-4070",
	"system": "MediaTek MT7621 ver:1 eco:3",
	"model": "ZyXEL WSM20",
	"board_name": "zyxel,wsm20",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "23.05.3",
		"revision": "r23809-234f1a2efa",
		"target": "ramips/mt7621",
		"description": "OpenWrt 23.05.3 r23809-234f1a2efa"
	}
}
root@meshnode-4070:~# cat /etc/config/network | grep 192
	option ipaddr '192.168.178.15'
	option gateway '192.168.178.1'
	list dns '192.168.178.1'

What has been enabled re mesh automatically and how do I disable it, so I have the same behavior as with 23.05.2 ?

There was a big update in mesh11sd between 23.05.2 and 23.05.3 which introduce autoconfiguration. I would not be surprised if it was the culprit.

FWIW, I updated my 3 WSM20 with official standard image without problem.

2 Likes

I am not familiar with mesh. I never tried IEEE 802.11s, but 802.11r which did not work with all phones, with a few perfect, with some no change within 20min. And since all AP have the same SSID using mesh I cannot force to change to a special AP. If these phones disappear, 4 from the family, mesh gets interesting again.

Maybe I have to deactivate mesh setting(s), but I have no idea which to disable "auto mesh". For now I have to change the SSID with the phone and I have internet access again.

Maybe someone knows what I have to change exactly.

From Asus AX53U

root@meshnode-0ec8:~# mesh11sd status
{
  "setup":{
    "version":"3.1.0",
    "enabled":"1",
    "procd_status":"running",
    "portal_detect":"1",
    "portal_channel":"default",
    "mesh_basename":"m-11s-",
    "auto_config":"1",
    "auto_mesh_network":"lan",
    "auto_mesh_band":"2g40",
    "auto_mesh_id":"92d490daf46cfe534c56ddd669297e",
    "mesh_gate_enable":"1",
    "txpower":"20",
    "mesh_path_cost":"10",
    "checkinterval":"10",
    "interface_timeout":"10",
    "ssid_suffix_enable":"1",
    "debuglevel":"1"
  }
  "interfaces":{
    "m-11s-0":{
      "mesh_retry_timeout":"100",
      "mesh_confirm_timeout":"100",
      "mesh_holding_timeout":"100",
      "mesh_max_peer_links":"8",
      "mesh_max_retries":"3",
      "mesh_ttl":"31",
      "mesh_element_ttl":"31",
      "mesh_auto_open_plinks":"0",
      "mesh_hwmp_max_preq_retries":"4",
      "mesh_path_refresh_time":"1000",
      "mesh_min_discovery_timeout":"100",
      "mesh_hwmp_active_path_timeout":"5000",
      "mesh_hwmp_preq_min_interval":"10",
      "mesh_hwmp_net_diameter_traversal_time":"50",
      "mesh_hwmp_rootmode":"2",
      "mesh_hwmp_rann_interval":"5000",
      "mesh_gate_announcements":"1",
      "mesh_fwding":"1",
      "mesh_sync_offset_max_neighor":"50",
      "mesh_rssi_threshold":"-70",
      "mesh_hwmp_active_path_to_root_timeout":"6000",
      "mesh_hwmp_root_interval":"5000",
      "mesh_hwmp_confirmation_interval":"2000",
      "mesh_power_mode":"active",
      "mesh_awake_window":"10",
      "mesh_plink_timeout":"0",
      "mesh_connected_to_gate":"1",
      "mesh_nolearn":"0",
      "mesh_connected_to_as":"0",
      "mesh_id":"92d490daf46cfe534c56ddd669297e",
      "device":"radio0",
      "channel":"11",
      "tx_packets":"551860",
      "tx_bytes":"157262273",
      "rx_packets":"0",
      "rx_bytes":"0",
      "this_node":"c8:..:..:..:..:c8",
      "active_peers":"1",
      "peers":{
        "00:..:..:..:..:01":{
          "next_hop":"00:00:00:00:00:00"
          "hop_count":"0"
          "path_change_count":"0"
          "metric":"0"
        }
      }
      "active_stations":"3",
      "stations":{
        "a4:..:..:..:..:d2":{
          "proxy_node":"c8:..:..:..:..:c8"
        },
        "9c:..:..:..:..:94":{
          "proxy_node":"c8:..:..:..:..:c8"
        },
        "38:..:..:..:..:19":{
          "proxy_node":"c8:..:..:..:..:c8"
        }
      }
    }
  }
}

No idea, why I cannot connect to the WSM20, but it is pingable. Yesterday I could login via ssh. Weblogin doesn't work too with .104

https://openwrt.org/docs/guide-user/network/wifi/mesh/mesh11sd

On the wiki it states:

Auto_configuration:
From version 3.0.0 onwards, by default, Mesh11sd checks the wireless configuration for mesh options in addition to checking for a mesh capable version of the wpad package.
If a suitable version of wpad is installed (eg wpad-mesh-mbedtls), mesh11sd adds options to the wireless configuration to bring up 802.11s mesh interfaces, if they are not already present.

You have allowed mesh11sd to auto configure the mesh, your WSM20 is now a DHCP mesh client.

If you don't want a mesh auto configured, don't include the package mesh11sd.

@bluewavenet anything else that I'm missing on the mesh11sd defaults that are heavily detailed on the wiki?

1 Like

And the Asus AX53U is Mesh master?

Why I cannot connect via ssh to the WSM20?

That is a problem, if I do not include it in the firmware build. If I install it later, the router gets softbricked, if it is a wireless bridged router, because internet gets lost. I had this problem a few times with different models.

Is the really no other way to disable "mesh auto"?

Why doesn't the problem "mesh auto" exist with Archer C7?

root@C7v5-23:~# ubus call system board
{
	"kernel": "5.15.150",
	"hostname": "C7v5-23",
	"system": "Qualcomm Atheros QCA956X ver 1 rev 0",
	"model": "TP-Link Archer C7 v5",
	"board_name": "tplink,archer-c7-v5",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "23.05.3",
		"revision": "r23809-234f1a2efa",
		"target": "ath79/generic",
		"description": "OpenWrt 23.05.3 r23809-234f1a2efa"
	}
}

Installedwith the C7 is:

ath10k-firmware-qca988x base-files busybox ca-bundle dnsmasq dropbear firewall4 fstools kmod-ath10k-ct kmod-ath9k kmod-gpio-button-hotplug kmod-nft-offload kmod-usb-ledtrig-usbport kmod-usb2 libc libgcc logd luci mtd netifd nftables odhcp6c odhcpd-ipv6only opkg ppp ppp-mod-pppoe procd procd-seccomp procd-ujail swconfig uboot-envtools uci uclient-fetch urandom-seed urngd arp-scan arp-scan-database iputils-arping iperf iperf3 libustream-openssl mesh11sd nmap static-neighbor-reports wpad-openssl

root@C7v5-23:~# opkg list-installed | grep mesh
mesh11sd - 3.1.0-1

Since this mesh-chaos I see:

Nmap done: 256 IP addresses (255 hosts up) scanned in 17.20 seconds

That is nonsense.

1 Like

you are going to need to ssh the following commands in the ax53:

service mesh11sd stop
uci set mesh11sd.setup.auto_config='0'
uci commit mesh11sd
1 Like
root@meshnode-0ec8:~# service mesh11sd stop
root@meshnode-0ec8:~# uci set mesh11sd.setup.auto_config='0'
root@meshnode-0ec8:~# uci commit mesh11sd

There is still the redirection

$ ping 192.168.178.18
PING 192.168.178.18 (192.168.178.18) 56(84) bytes of data.
From 192.168.178.152 icmp_seq=2 Redirect Host(New nexthop: 192.168.178.18)
root@meshnode-0ec8:~# reboot
root@meshnode-0ec8:~# Connection to 192.168.178.152 closed by remote host.
Connection to 192.168.178.152 closed.
$ ping 192.168.178.18
PING 192.168.178.18 (192.168.178.18) 56(84) bytes of data.
64 bytes from 192.168.178.18: icmp_seq=1 ttl=64 time=4.09 ms

Looks like a reboot is necessary.

config mesh11sd 'setup'
	option enabled '1'
	option debuglevel '1'
	option checkinterval '10'
	option interface_timeout '10'
	option auto_config '0'

So adding at the end of section config mesh11sd 'setup' a new line with option auto_config '0' should do it too. Compare the orignal file above.

1 Like

The nmap problem still exists. The same router devices with same MAC are shown again and again.

Maybe I have to wait a few days until it disappears.

There is still the file

root@AX53U-S1:~# cat /etc/config/mesh11sd 

config mesh11sd 'setup'
	option enabled '1'
	option debuglevel '1'
	option checkinterval '10'
	option interface_timeout '10'
	option auto_config '0'

config mesh11sd 'mesh_params'
	option mesh_fwding '1'
	option mesh_rssi_threshold '-70'
	option mesh_gate_announcements '1'
	option mesh_hwmp_rootmode '3'
	option mesh_max_peer_links '8'

Does this file have any influences on mesh, which "should not work"?

root@AX53U-S1:~# mesh11sd status
{
  "setup":{
    "version":"3.1.0",
    "enabled":"1",
    "procd_status":"running",
    "portal_detect":"1",
    "portal_channel":"default",
    "mesh_basename":"m-11s-",
    "auto_config":"0",
    "auto_mesh_network":"lan",
    "auto_mesh_band":"2g40",
    "auto_mesh_id":"92d490daf46cfe534c56ddd669297e",
    "mesh_gate_enable":"1",
    "txpower":"",
    "mesh_path_cost":"10",
    "checkinterval":"10",
    "interface_timeout":"10",
    "ssid_suffix_enable":"1",
    "debuglevel":"1"
  }
  "interfaces":{
  }
}

Where do the IP-addresses .2 and .7 come from? Pretty sure it are the 2 devices with the auto-mesh-configuration, although there are are other WSM20 , but nor other Asus device.

.15 is the Zyxel WSM20 and .18 is the Asus AX53U. Other WSM20 have been recognized.

ssh to root@R7800

config dhcp 'lan'
option interface 'lan'
option start '50'
** option limit '179'**
option leasetime '12h'
option dhcpv4 'server'
option dhcpv6 'server'
option ra 'server'
list ra_flags 'managed-config'
list ra_flags 'other-config'
list dhcp_option '3,192.168.178.1'

So there should not be an DHCP-IP-address below .50

OpenWrt 23.05.3, r23809-234f1a2efa

root@AX53U-S1:~# nmap -sn 192.168.178.0/24
Starting Nmap 7.93 ( https://nmap.org ) at 2024-04-02 11:56 UTC

Nmap scan report for 192.168.178.0
Host is up (0.73s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.1
Host is up (0.0059s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.2
Host is up (0.22s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.3
Host is up (0.76s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.4
Host is up (0.22s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.5
Host is up (0.41s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.6
Host is up (0.39s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.7
Host is up (0.37s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.8
Host is up (0.25s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.9
Host is up (0.12s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.10
Host is up (0.10s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.11
Host is up (0.30s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.12
Host is up (0.28s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.13
Host is up (0.0072s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.14
Host is up (0.0070s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.15
Host is up (0.0042s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.16
Host is up (0.28s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.17
Host is up (0.0057s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.19
Host is up (0.31s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.20
Host is up (0.0048s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.21
Host is up (0.50s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.22
Host is up (0.0070s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.23
Host is up (0.22s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.24
Host is up (0.0065s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.25
Host is up (0.096s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.26
Host is up (0.69s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.27
Host is up (0.78s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.28
Host is up (0.31s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.29
Host is up (0.73s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.30
Host is up (0.19s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.31
Host is up (0.14s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.32
Host is up (0.12s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.33
Host is up (0.71s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.34
Host is up (0.37s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.35
Host is up (0.26s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.36
Host is up (0.45s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.37
Host is up (0.33s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.38
Host is up (0.65s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.39
Host is up (0.57s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.40
Host is up (0.57s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.41
Host is up (0.041s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.42
Host is up (0.31s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.43
Host is up (0.23s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.44
Host is up (0.39s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.45
Host is up (0.19s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.46
Host is up (0.0061s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.47
Host is up (0.38s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.48
Host is up (0.70s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.49
Host is up (0.45s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.50
Host is up (0.61s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.51
Host is up (0.59s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.52
Host is up (0.57s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.53
Host is up (0.0024s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.54
Host is up (0.39s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.55
Host is up (0.55s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.56
Host is up (0.15s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.57
Host is up (0.11s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.58
Host is up (0.24s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.59
Host is up (0.66s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.60
Host is up (0.58s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.61
Host is up (0.55s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.62
Host is up (0.42s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.63
Host is up (0.22s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.64
Host is up (0.60s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.65
Host is up (0.81s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.66
Host is up (0.51s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.67
Host is up (0.79s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.68
Host is up (0.60s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.69
Host is up (0.72s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.70
Host is up (0.016s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.71
Host is up (0.15s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.72
Host is up (0.46s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.73
Host is up (0.20s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.74
Host is up (0.62s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.75
Host is up (0.16s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.76
Host is up (0.36s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.77
Host is up (0.15s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.78
Host is up (0.70s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.79
Host is up (0.63s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.80
Host is up (0.72s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.81
Host is up (0.027s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.82
Host is up (0.70s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.83
Host is up (0.67s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.84
Host is up (0.70s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.85
Host is up (0.29s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.86
Host is up (0.71s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.87
Host is up (0.33s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.88
Host is up (0.60s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.89
Host is up (0.65s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.90
Host is up (0.49s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.91
Host is up (0.14s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.92
Host is up (0.72s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.93
Host is up (0.52s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.94
Host is up (0.68s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.95
Host is up (0.42s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.96
Host is up (0.15s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.97
Host is up (0.71s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.98
Host is up (0.096s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.99
Host is up (0.59s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.100
Host is up (0.32s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.101
Host is up (0.086s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.102
Host is up (0.50s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.103
Host is up (0.36s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.104
Host is up (0.46s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.105
Host is up (0.24s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.106
Host is up (0.095s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.107
Host is up (0.36s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.108
Host is up (0.32s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.109
Host is up (0.042s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.110
Host is up (0.78s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.111
Host is up (0.056s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.112
Host is up (0.74s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.113
Host is up (0.25s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.114
Host is up (0.59s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.115
Host is up (0.65s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.116
Host is up (0.26s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.117
Host is up (0.11s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.118
Host is up (0.42s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.119
Host is up (0.64s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.120
Host is up (0.12s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.121
Host is up (0.36s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.122
Host is up (0.16s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.123
Host is up (0.40s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.124
Host is up (0.60s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.125
Host is up (0.63s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.126
Host is up (0.57s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.127
Host is up (0.68s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.128
Host is up (0.40s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.129
Host is up (0.44s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.130
Host is up (0.090s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.131
Host is up (0.41s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.132
Host is up (0.34s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.133
Host is up (0.66s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.134
Host is up (0.016s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.135
Host is up (0.56s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.136
Host is up (0.36s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.137
Host is up (0.76s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.138
Host is up (0.42s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.139
Host is up (0.17s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.140
Host is up (0.44s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.141
Host is up (0.33s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.142
Host is up (0.36s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.143
Host is up (0.60s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.144
Host is up (0.49s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.145
Host is up (0.26s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.146
Host is up (0.72s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.147
Host is up (0.32s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.148
Host is up (0.35s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.149
Host is up (0.72s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.150
Host is up (0.32s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.151
Host is up (0.27s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.152
Host is up (0.59s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.153
Host is up (0.12s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.154
Host is up (0.79s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.155
Host is up (0.28s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.156
Host is up (0.20s latency).
MAC Address: F4:..:..:..:..:F9 (Xiaomi Communications)
Nmap scan report for 192.168.178.157
Host is up (0.18s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.158
Host is up (0.57s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.159
Host is up (0.067s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.160
Host is up (0.14s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.161
Host is up (0.68s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.162
Host is up (0.50s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.163
Host is up (0.65s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.164
Host is up (0.62s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.165
Host is up (0.33s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.166
Host is up (0.39s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.167
Host is up (0.69s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.168
Host is up (0.50s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.169
Host is up (0.63s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.170
Host is up (0.065s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.171
Host is up (0.21s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.172
Host is up (0.47s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.173
Host is up (0.21s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.174
Host is up (0.13s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.175
Host is up (0.29s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.176
Host is up (0.12s latency).
MAC Address: 38:E6:0A:8A:AF:19 (Xiaomi Communications)
Nmap scan report for 192.168.178.177
Host is up (0.14s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.178
Host is up (0.31s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.179
Host is up (0.47s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.180
Host is up (0.32s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.181
Host is up (0.46s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.182
Host is up (0.034s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.183
Host is up (0.45s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.184
Host is up (0.33s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.185
Host is up (0.55s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.186
Host is up (0.64s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.187
Host is up (0.094s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.188
Host is up (0.41s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.189
Host is up (0.14s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.190
Host is up (0.10s latency).
MAC Address: 4C:09:FA:10:03:CF (Frontier Smart Technologies)
Nmap scan report for 192.168.178.191
Host is up (0.64s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.192
Host is up (0.24s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.193
Host is up (0.26s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.194
Host is up (0.30s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.195
Host is up (0.38s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.196
Host is up (0.31s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.197
Host is up (0.062s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.198
Host is up (0.36s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.199
Host is up (0.18s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.200
Host is up (0.71s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.201
Host is up (0.079s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.202
Host is up (0.21s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.203
Host is up (0.040s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.204
Host is up (0.48s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.205
Host is up (0.27s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.206
Host is up (0.79s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.207
Host is up (0.096s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.208
Host is up (0.34s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.209
Host is up (0.38s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.210
Host is up (0.61s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.211
Host is up (0.00069s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.212
Host is up (0.42s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.213
Host is up (0.32s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.214
Host is up (0.77s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.215
Host is up (0.64s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.216
Host is up (0.0032s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.217
Host is up (0.28s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.218
Host is up (0.15s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.219
Host is up (0.52s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.220
Host is up (0.35s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.221
Host is up (0.0070s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.222
Host is up (0.0063s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.223
Host is up (0.57s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.224
Host is up (0.0033s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.225
Host is up (0.0029s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.226
Host is up (0.23s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.227
Host is up (0.0066s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.228
Host is up (0.095s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.229
Host is up (0.72s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.230
Host is up (0.17s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.231
Host is up (0.62s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.232
Host is up (0.79s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.233
Host is up (0.24s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.234
Host is up (0.16s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.235
Host is up (0.42s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.236
Host is up (0.071s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.237
Host is up (0.65s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.238
Host is up (0.28s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.239
Host is up (0.77s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.240
Host is up (0.66s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.241
Host is up (0.63s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.242
Host is up (0.22s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.243
Host is up (0.52s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.244
Host is up (0.15s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.245
Host is up (0.77s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.246
Host is up (0.15s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.247
Host is up (0.13s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.248
Host is up (0.71s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.249
Host is up (0.71s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.250
Host is up (0.52s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.251
Host is up (0.54s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.252
Host is up (0.56s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.253
Host is up (0.48s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)
Nmap scan report for 192.168.178.254
Host is up (0.37s latency).
MAC Address: D4:..:..:..:..:70 (Zyxel Communications)

Nmap scan report for 192.168.178.18
Host is up.
Nmap done: 256 IP addresses (255 hosts up) scanned in 4.96 seconds

Obviously nmap shows wrong devices. The Lan scan with the phone is correct, except .2 und .7 which could be configured automatiically after the openwrt update.

The DHCP server doesn't show .2 and .7 with "Active DHCP Leases", only 2 phones.

root@AX53U-S1:~# grep -r 192 /etc/config/
/etc/config/firewall:#	option src_ip	192.168.45.2
/etc/config/firewall:#	option dest_ip		192.168.16.235
/etc/config/firewall:#	option src_ip	192.168.45.2
/etc/config/firewall:#	option src_ip	192.168.45.2
/etc/config/network:	option ipaddr '192.168.178.18'
/etc/config/network:	option gateway '192.168.178.1'
/etc/config/network:	list dns '192.168.178.1'
root@WSM20-K0:~# grep -r 192 /etc/config/
/etc/config/firewall:#	option src_ip	192.168.45.2
/etc/config/firewall:#	option dest_ip		192.168.16.235
/etc/config/firewall:#	option src_ip	192.168.45.2
/etc/config/firewall:#	option src_ip	192.168.45.2
/etc/config/network:	option ipaddr '192.168.178.15'
/etc/config/network:	option gateway '192.168.178.1'
/etc/config/network:	list dns '192.168.178.1'

So where do these IP-addresses .2 and .7 come from?

Checking my non published list with MAC-acdresses:

.2 shows the MAC of the AX53U, while .18 says MAC is n/a

.7 shows the MAC of the WSM20, while .15 says MAC is n/a

So there must have been something with IP-addresses and "mesh-auto" too.

BTW the router with the dhcp-server was rebooted too.

Crazy, now I see .4 and .5 instead of .2 and .7. Not sure, if this changed after the reboot of the dhcp-server.

$ ping 192.168.178.4
PING 192.168.178.4 (192.168.178.4) 56(84) bytes of data.
From 192.168.178.18 icmp_seq=2 Time to live exceeded
From 192.168.178.15 icmp_seq=3 Redirect Host(New nexthop: 192.168.178.4)
From 192.168.178.18 icmp_seq=3 Time to live exceeded
From 192.168.178.18 icmp_seq=4 Time to live exceeded
From 192.168.178.18 icmp_seq=5 Time to live exceeded
From 192.168.178.15 icmp_seq=6 Redirect Host(New nexthop: 192.168.178.4)
From 192.168.178.18 icmp_seq=6 Time to live exceeded
From 192.168.178.18 icmp_seq=7 Time to live exceeded
From 192.168.178.18 icmp_seq=8 Time to live exceeded
From 192.168.178.18 icmp_seq=9 Time to live exceeded
From 192.168.178.18 icmp_seq=10 Time to live exceeded
From 192.168.178.15 icmp_seq=11 Redirect Host(New nexthop: 192.168.178.4)
$ ping 192.168.178.5
PING 192.168.178.5 (192.168.178.5) 56(84) bytes of data.
From 192.168.178.18 icmp_seq=1 Redirect Host(New nexthop: 192.168.178.5)
From 192.168.178.15 icmp_seq=1 Redirect Host(New nexthop: 192.168.178.5)
From 192.168.178.15 icmp_seq=1 Redirect Host(New nexthop: 192.168.178.5)
From 192.168.178.18 icmp_seq=1 Redirect Host(New nexthop: 192.168.178.5)
From 192.168.178.18 icmp_seq=2 Redirect Host(New nexthop: 192.168.178.5)
From 192.168.178.15 icmp_seq=2 Redirect Host(New nexthop: 192.168.178.5)
From 192.168.178.18 icmp_seq=3 Redirect Host(New nexthop: 192.168.178.5)
From 192.168.178.15 icmp_seq=3 Redirect Host(New nexthop: 192.168.178.5)
From 192.168.178.18 icmp_seq=4 Redirect Host(New nexthop: 192.168.178.5)
From 192.168.178.15 icmp_seq=4 Redirect Host(New nexthop: 192.168.178.5)
From 192.168.178.15 icmp_seq=5 Time to live exceeded
From 192.168.178.18 icmp_seq=6 Redirect Host(New nexthop: 192.168.178.5)
From 192.168.178.15 icmp_seq=6 Time to live exceeded

@linuxuser
If you do not want the mesh autoconfigured, do:

service mesh1sd stop
uci set mesh11sd.setup.auto_config='0'
uci commit mesh11sd
wifi
service mesh11sd start

You will now have to manually configure the mesh in the same way you had to do with v2.0.0 of mesh11sd.
But be aware mesh11sd connect and mesh11sd copy will no longer function.

2 Likes

This is a legacy config file from a previous version of mesh11sd, except you have manually edited the file.
See the warning about upgrading here:
https://openwrt.org/docs/guide-user/network/wifi/mesh/mesh11sd#tldr

Note: Mesh11sd uses the uci utility to manage dynamic configuration changes, both autoconfig and run time.

The autoconfiguration is done on every startup and is not a one off process.
In normal operation, config changes are not written to the config files in /etc/config but are kept in volatile storage by way of the uci utility.

Directly editing a config file might possibly break something, all changes should be done with the uci utility.

1 Like

Yes I did an update from 23.05.2 to 23.05.3, so I use better sysupgrade -n and configure everything new.

But:

So what can I do to be prepared for mesh later?

These are the packages I used for a custom build:

base-files busybox ca-bundle dnsmasq dropbear firewall4 fstools kmod-gpio-button-hotplug kmod-leds-gpio kmod-mt7915-firmware kmod-nft-offload kmod-usb-ledtrig-usbport kmod-usb3 libc libgcc logd luci mtd netifd nftables odhcp6c odhcpd-ipv6only opkg ppp ppp-mod-pppoe procd procd-seccomp procd-ujail uboot-envtools uci uclient-fetch urandom-seed urngd arp-scan arp-scan-database iputils-arping iperf iperf3 libustream-openssl mesh11sd nmap static-neighbor-reports wpad-openssl

Not sure what happens if I remove mesh11sd ? Is it added automatically then?

I really try to avoid to get a brick again. With some devices this can be a big problem. I had luck and I could use tftp without opening the case.

Are you using imagebuilder or the firmware selector?

You have wpad-openssl, so that is good, keep that.
You have mesh11sd, keep that.

Also add kmod-nft-bridge as mesh11sd needs it (unless you are very resource limited, which I guess you are not as you have included wpad-openssl).

To turn off auto_config in the image, do it in the uci-defaults (a file in imagebuilder or in the uci-defaults text box in the firmware selector.

Put this code into uci-defaults:

uci set mesh11sd.setup.auto_config='0'
uci commit mesh11sd
1 Like

https://firmware-selector.openwrt.org/

Most times not, but maybe these 2 could be a problem:

https://openwrt.org/toh/hwdata/tp-link/tp-link_archer_c7_v5
Flash MB: 16
RAM MB: 128

https://openwrt.org/toh/hwdata/netgear/netgear_ex6150_v2
Flash MB: 16
RAM MB: 256

AFAIK the flash size is 8MB, so 16 should be enough. These routers above are for testing only.

The others should be fine.

https://openwrt.org/toh/hwdata/asus/asus_rt-ax53u
Flash MB: 128
RAM MB: 256

https://openwrt.org/toh/hwdata/zyxel/zyxel_wsm20
Flash MB: 128
RAM MB: 256

https://openwrt.org/toh/hwdata/d-link/d-link_dap-x1860_a1
Flash MB: 128
RAM MB: 256

Thanks for the info

Do you think it can be a problem with the Archer C7 and 16MB Flash memory?

I don't understand how to do this with fw-selector. There is a field for scripts, which stayed empty till now.

Yes, if you go into "Customize installed packages and/or first boot script", it is the bottom text box for first boot script aka uci-defaults.

This is not a problem at all. I have numerous gl-inet mt300n-v2 routers in the field also with 16/128 and they are perfect for the job mounted in a weatherproof plastic box giving a closely achieved potential of a 300Mb/s backhaul at a very low cost.

1 Like

Sorry, I am unsure.

There is an empty box, and if you click on "settings" there is:

# Beware! This script will be in /rom/etc/uci-defaults/ as part of the image.
# Uncomment lines to apply:
#
# wlan_name="OpenWrt"
# wlan_password="12345678"
#
# root_password=""
# lan_ip_address="192.168.1.1"
#
# pppoe_username=""
# pppoe_password=""

# log potential errors
exec >/tmp/setup.log 2>&1

if [ -n "$root_password" ]; then
  (echo "$root_password"; sleep 1; echo "$root_password") | passwd > /dev/null
fi

# Configure LAN
# More options: https://openwrt.org/docs/guide-user/base-system/basic-networking
if [ -n "$lan_ip_address" ]; then
  uci set network.lan.ipaddr="$lan_ip_address"
  uci commit network
fi

# Configure WLAN
# More options: https://openwrt.org/docs/guide-user/network/wifi/basic#wi-fi_interfaces
if [ -n "$wlan_name" -a -n "$wlan_password" -a ${#wlan_password} -ge 8 ]; then
  uci set wireless.@wifi-device[0].disabled='0'
  uci set wireless.@wifi-iface[0].disabled='0'
  uci set wireless.@wifi-iface[0].encryption='psk2'
  uci set wireless.@wifi-iface[0].ssid="$wlan_name"
  uci set wireless.@wifi-iface[0].key="$wlan_password"
  uci commit wireless
fi

# Configure PPPoE
# More options: https://openwrt.org/docs/guide-user/network/wan/wan_interface_protocols#protocol_pppoe_ppp_over_ethernet
if [ -n "$pppoe_username" -a "$pppoe_password" ]; then
  uci set network.wan.proto=pppoe
  uci set network.wan.username="$pppoe_username"
  uci set network.wan.password="$pppoe_password"
  uci commit network
fi

echo "All done!"

So do I have to simply put

uci set mesh11sd.setup.auto_config='0'
uci commit mesh11sd

in the empty box or do I have to modify the "hidden" script!

I tried this as a test, but did not flash it:

Do you recommend other packages for the Archer C7:

ath10k-firmware-qca988x base-files busybox ca-bundle dnsmasq dropbear firewall4 fstools kmod-ath10k-ct kmod-ath9k kmod-gpio-button-hotplug kmod-nft-offload kmod-usb-ledtrig-usbport kmod-usb2 libc libgcc logd luci mtd netifd nftables odhcp6c odhcpd-ipv6only opkg ppp ppp-mod-pppoe procd procd-seccomp procd-ujail swconfig uboot-envtools uci uclient-fetch urandom-seed urngd arp-scan arp-scan-database iputils-arping iperf iperf3 libustream-openssl mesh11sd nmap static-neighbor-reports wpad-openssl kmod-nft-bridge