Problem with the number of devices connected to the Wi-Fi of Cudy WR3000

salemaidroos · March 24, 2025, 6:26pm

I have a network consisting of a MikroTik router which is considered the main distribution router for the network and 30 access points and they are working fine.
Except for one access point which is Cudy WR3000 v1, I noticed that it shows 7 phones connected, but when I go to the MikroTik and look at the connected phones in the access point, I find that the number of connected phones is 0 in the active list and 1 in the hotspot list?!
Although it should show that the number of connected phones is 7 in the hotspot same what appear in Cudy access point!
Also sometimes clients cannot connect to the Wi-Fi network from this access point unless I restart it.

I hope you can help me solve this problem.

Thank you in advance..

frollic · March 24, 2025, 6:42pm

Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:

Remember to redact passwords, MAC addresses and any public IP addresses you may have:

ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall

brada4 · March 24, 2025, 8:08pm

In microscope science? Can you humanly read your own post?

salemaidroos · March 24, 2025, 8:44pm


root@SAM-NET:~# ubus call system board
{
        "kernel": "6.6.73",
        "hostname": "SAM-NET",
        "system": "ARMv8 Processor rev 4",
        "model": "Cudy WR3000 v1",
        "board_name": "cudy,wr3000-v1",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "24.10.0",
                "revision": "r28427-6df0e3d02a",
                "target": "mediatek/filogic",
                "description": "OpenWrt 24.10.0 r28427-6df0e3d02a",
                "builddate": "1738624177"
        }
}
root@SAM-NET:~# cat /etc/config/network

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd3e:090c:0df7::/48'
        option packet_steering '1'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'lan1'
        list ports 'lan2'
        list ports 'lan3'
        option ipv6 '0'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr 'xxxxxxxx'
        option netmask '255.255.255.0'
        option delegate '0'
        option gateway 'xxxxxx'
        option defaultroute '0'

config device
        option type '8021q'
        option ifname 'br-lan'
        option vid '42'
        option name 'br-lan.42'
        option ipv6 '0'

config device
        option type 'bridge'
        option name 'brvlan42'
        list ports 'br-lan.42'
        option ipv6 '0'

config interface 'vlan42'
        option proto 'none'
        option device 'brvlan42'
        option delegate '0'

root@SAM-NET:~# cat /etc/config/wireless

config wifi-device 'radio0'
        option type 'mac80211'
        option path 'platform/soc/18000000.wifi'
        option channel 'auto'
        option band '2g'
        option htmode 'HE20'
        option cell_density '0'
        option country 'US'
        option frag '2346'
        option rts '2347'
        option txpower '26'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'vlan42'
        option mode 'ap'
        option ssid 'SAMNET/42'
        option encryption 'none'
        option isolate '1'
        option disassoc_low_ack '0'

config wifi-device 'radio1'
        option type 'mac80211'
        option path 'platform/soc/18000000.wifi+1'
        option channel '157'
        option band '5g'
        option htmode 'VHT80'
        option country 'US'
        option cell_density '0'
        option frag '2346'
        option rts '2347'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'vlan42'
        option mode 'ap'
        option ssid 'SAMNET/42-5G'
        option encryption 'none'
        option isolate '1'
        option disassoc_low_ack '0'

config wifi-iface 'wifinet3'
        option device 'radio1'
        option mode 'mesh'
        option encryption 'sae'
        option mesh_id 'xxxxx'
        option mesh_fwding '1'
        option mesh_rssi_threshold '0'
        option network 'lan'
        option key 'xxxxxxx'
        option disabled '1'

root@SAM-NET:~# cat /etc/config/dhcp

config dnsmasq
        option domainneeded '1'
        option boguspriv '1'
        option filterwin2k '0'
        option localise_queries '1'
        option rebind_protection '1'
        option rebind_localhost '1'
        option local '/lan/'
        option domain 'lan'
        option expandhosts '1'
        option nonegcache '0'
        option cachesize '1000'
        option authoritative '1'
        option readethers '1'
        option leasefile '/tmp/dhcp.leases'
        option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
        option nonwildcard '1'
        option localservice '1'
        option ednspacket_max '1232'
        option filter_aaaa '0'
        option filter_a '0'

config dhcp 'lan'
        option interface 'lan'
        option start '100'
        option limit '150'
        option leasetime '12h'
        option dhcpv4 'server'
        option ignore '1'
        option dynamicdhcp '0'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'
        option loglevel '4'

root@SAM-NET:~# cat /etc/config/firewall

config defaults
        option syn_flood '1'
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'

config zone
        option name 'lan'
        option input 'ACCEPT'
        option output 'ACCEPT'
        option forward 'ACCEPT'
        list network 'lan'

config zone
        option name 'wan'
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'
        option masq '1'
        option mtu_fix '1'

config forwarding
        option src 'lan'
        option dest 'wan'

config rule
        option name 'Allow-DHCP-Renew'
        option src 'wan'
        option proto 'udp'
        option dest_port '68'
        option target 'ACCEPT'
        option family 'ipv4'

config rule
        option name 'Allow-Ping'
        option src 'wan'
        option proto 'icmp'
        option icmp_type 'echo-request'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-IGMP'
        option src 'wan'
        option proto 'igmp'
        option family 'ipv4'
        option target 'ACCEPT'

config rule
        option name 'Allow-DHCPv6'
        option src 'wan'
        option proto 'udp'
        option dest_port '546'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-MLD'
        option src 'wan'
        option proto 'icmp'
        option src_ip 'fe80::/10'
        list icmp_type '130/0'
        list icmp_type '131/0'
        list icmp_type '132/0'
        list icmp_type '143/0'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Input'
        option src 'wan'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        list icmp_type 'router-solicitation'
        list icmp_type 'neighbour-solicitation'
        list icmp_type 'router-advertisement'
        list icmp_type 'neighbour-advertisement'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-ICMPv6-Forward'
        option src 'wan'
        option dest '*'
        option proto 'icmp'
        list icmp_type 'echo-request'
        list icmp_type 'echo-reply'
        list icmp_type 'destination-unreachable'
        list icmp_type 'packet-too-big'
        list icmp_type 'time-exceeded'
        list icmp_type 'bad-header'
        list icmp_type 'unknown-header-type'
        option limit '1000/sec'
        option family 'ipv6'
        option target 'ACCEPT'

config rule
        option name 'Allow-IPSec-ESP'
        option src 'wan'
        option dest 'lan'
        option proto 'esp'
        option target 'ACCEPT'

config rule
        option name 'Allow-ISAKMP'
        option src 'wan'
        option dest 'lan'
        option dest_port '500'
        option proto 'udp'
        option target 'ACCEPT'

root@SAM-NET:~#

psherman · March 24, 2025, 10:21pm

You don't need to redact this -- it won't reveal anything sensitive/secret about your network.

salemaidroos:

config device
        option type '8021q'
        option ifname 'br-lan'
        option vid '42'
        option name 'br-lan.42'
        option ipv6 '0'

config device
        option type 'bridge'
        option name 'brvlan42'
        list ports 'br-lan.42'
        option ipv6 '0'

config interface 'vlan42'
        option proto 'none'
        option device 'brvlan42'
        option delegate '0'

This is not configured properly. I would expect that any devices connected to this network are unable to use the network/internet.

Let's take a moment to discuss your desired configuration. I'm guessing, please confirm or correct:

The lan interface is used for management of the AP
The uplink port and the corresponding upstream port has this VLAN untagged
This lan is not used for wifi
VLAN42 is tagged on the uplink port and the corresponding upstream port.
VLAN42 is intended for use with wifi
VLAN 42 connects to the upstream 'Tik "hotspot" network
You're using port lan2 for the uplink
(what do you want the other 3 ports to do? -- should they be access ports or trunk ports? If access, lan, VLAN42, or a combination?)

brada4 · March 24, 2025, 11:21pm

You will not outwit bugs (op config is the only viable)

github.com/openwrt/openwrt

Clients are unable to connect to the wireless network

opened 10:45AM - 19 Jan 25 UTC

grifos

target/ramips bug Official Image release/24.10

### Describe the bug Since the first 24.10.0 RC releases, wireless clients coul…d not establish a successful network connection. The OpenWrt logs were showing clients connected then disconnected after about 30 seconds. The clients showed similar logs but never had any actual network connectivity at all. ``` Tue Jan 7 13:08:29 2025 daemon.info hostapd: wl1.101: STA aa:bb:cc:01:23:45 IEEE 802.11: authenticated Tue Jan 7 13:08:29 2025 daemon.info hostapd: wl1.101: STA aa:bb:cc:01:23:45 IEEE 802.11: associated (aid 1) Tue Jan 7 13:08:29 2025 daemon.notice hostapd: wl1.101: AP-STA-CONNECTED aa:bb:cc:01:23:45 auth_alg=open Tue Jan 7 13:08:29 2025 daemon.info hostapd: wl1.101: STA aa:bb:cc:01:23:45 RADIUS: starting accounting session 7D707FBCB13EEE03 Tue Jan 7 13:08:29 2025 daemon.info hostapd: wl1.101: STA aa:bb:cc:01:23:45 WPA: pairwise key handshake completed (RSN) Tue Jan 7 13:08:29 2025 daemon.notice hostapd: wl1.101: EAPOL-4WAY-HS-COMPLETED aa:bb:cc:01:23:45 Tue Jan 7 13:09:00 2025 daemon.notice hostapd: wl1.101: AP-STA-DISCONNECTED aa:bb:cc:01:23:45 Tue Jan 7 13:09:23 2025 daemon.info hostapd: wl1.101: STA aa:bb:cc:01:23:45 IEEE 802.11: authenticated Tue Jan 7 13:09:23 2025 daemon.info hostapd: wl1.101: STA aa:bb:cc:01:23:45 IEEE 802.11: associated (aid 1) Tue Jan 7 13:09:23 2025 daemon.notice hostapd: wl1.101: AP-STA-CONNECTED aa:bb:cc:01:23:45 auth_alg=open Tue Jan 7 13:09:23 2025 daemon.info hostapd: wl1.101: STA aa:bb:cc:01:23:45 RADIUS: starting accounting session BB50B2A50135313A Tue Jan 7 13:09:23 2025 daemon.info hostapd: wl1.101: STA aa:bb:cc:01:23:45 WPA: pairwise key handshake completed (RSN) Tue Jan 7 13:09:23 2025 daemon.notice hostapd: wl1.101: EAPOL-4WAY-HS-COMPLETED aa:bb:cc:01:23:45 Tue Jan 7 13:10:08 2025 daemon.notice hostapd: wl1.101: AP-STA-DISCONNECTED aa:bb:cc:01:23:45 Tue Jan 7 13:10:10 2025 daemon.info hostapd: wl1.101: STA aa:bb:cc:01:23:45 IEEE 802.11: authenticated Tue Jan 7 13:10:10 2025 daemon.info hostapd: wl1.101: STA aa:bb:cc:01:23:45 IEEE 802.11: associated (aid 1) Tue Jan 7 13:10:10 2025 daemon.notice hostapd: wl1.101: AP-STA-CONNECTED aa:bb:cc:01:23:45 auth_alg=open Tue Jan 7 13:10:10 2025 daemon.info hostapd: wl1.101: STA aa:bb:cc:01:23:45 RADIUS: starting accounting session 60129E9B594E6574 Tue Jan 7 13:10:10 2025 daemon.info hostapd: wl1.101: STA aa:bb:cc:01:23:45 WPA: pairwise key handshake completed (RSN) Tue Jan 7 13:10:10 2025 daemon.notice hostapd: wl1.101: EAPOL-4WAY-HS-COMPLETED aa:bb:cc:01:23:45 Tue Jan 7 13:10:16 2025 daemon.notice hostapd: wl1.101: AP-STA-DISCONNECTED aa:bb:cc:01:23:45 ``` ### OpenWrt version r28304-6dacba30a7 ### OpenWrt release 24.10.0-rc5 ### OpenWrt target/subtarget ramips/mt7621 ### Device Netgear WAX202 ### Image kind Official downloaded image ### Steps to reproduce 1- Configure a wireless network. Use a custom interface name, for example: `wl1.101` 2- On Network > Interfaces > Devices, configure the corresponding wireless device `wl1.101` with default settings 3- The wireless clients can no longer connect to that SSID. Restarting the wireless device seems to resolve but the problem reappears after a reboot. ### Actual behaviour I reconfigured the AP from scratch and it looks like the WiFi fails when I configure the wireless network devices under Network > Interfaces > Devices. I'm using custom wireless interface names and as long as the corresponding device is left unconfigured the WiFi works fine, while if I configure it, even if leaving everything default (like with the code below), the WiFi starts failing. Restarting the wireless device (on the Wireless page) seems to fix it, but after a reboot the problem reappears. ``` uci add network device # =cfg1f0f15 uci set network.@device[-1].name='wl1.101' ``` I then unconfigured the wireless devices on my other MT7621+MT7915E devices and now they're also working fine under 24.10.0-rc5. ### Expected behaviour Clients should connect successfully to the wireless network even when the wireless device is configured on the OpenWrt device. ### Additional info Thank you for the work you do guys, OpenWrt is magnificent. ### Diffconfig ```text ``` ### Terms - [x] I am reporting an issue for OpenWrt, not an unsupported fork.