[eolo]

Router/Version: Netgear R7000
Mode: AP
Firmware: DD-WRT v3.0-r43334 std (06/04/20)
Kernel: Linux 4.4.226 #304 SMP Thu Jun 4 07:59:59 +04 2020 armv7l
Reset: erase nvram
Previous build: stock Netgear

I have two Netgear R7000 and use them only as AP with 4 SSID (same SSIDs on the two AP):
SSID-1: wl0 - wpa2 psk, mac filter (2.4G bridged on home LAN)
SSID-2: wl0.1 - wpa2 psk, VAP for guest access, not bridged
SSID-3: wl0.2 - wpa2 psk, VAP for IOT access, not bridged
SSID-4: wl1 - wpa2 psk, mac filter (5G bridged on home LAN)

For VAP to work i need the startup workaround:
sleep 10;stopservice nas;wlconf eth1 down;wlconf eth1 up;wlconf eth2 down;wlconf eth2 up;startservice nas

I don't use WAN, NAS, openvpn, wol, nothing at all, only dnsmasq and iptables for VAP. On the APs is enabled snmp and syslog to external server.

The dhcp server for SSID-1 and SSID-2 is on my wan router (Mikrotik).

All works fine (I have about 10 wifi client for each AP) on both SSID, BUT after some days (more or less every week) SSID-1 (wl0) became unusable: the SSID-1 is visibile, the wifi client associates but it doesn't receive the IP address.

On the same AP SSID-2, SSID-3 and SSID-4 are functioning. If I check with the brctl command the client mac-address is present on the bridge br0, so I suppose that the router doesn't forward dhcp packet from the client to the dhcp server, or the other way around.

The dhcp server is OK because if I connect to SSDI-4 (bridged on LAN together with SSDI-1) on the same AP the client starts immediately.
Likewise if I go to the other AP the client starts immediately also on SSID-1.

I searched on forum but seems that I'm the only one with that problem.
Tried to change firmare version on an AP, newer r43516 and an older DD-WRT v3.0-r37015M kongac, but no luck, after some days wl0 stops working with both releases.

I need to restart the AP (from GUI, SSH or with power button) to restore SSID-1 functionality.

I think it's unlikely an hardware problem, because it occurs on different R7000.

So I need help to troubleshout the problem.

Do you think I can report this as a bug?

I think that if it was a configuration error the AP wouldn't work immediately, and not after some days.

Advice welcome!

[wabe]

[eolo]

[eolo]

I've done some other searches on the web, and found similar problems here:
https://community.netgear.com/t5/Nighthawk-WiFi-Routers/R7000-2-4ghz-not-working-but-5ghz-is-fine/td-p/1372110

Seems like a firmware related problem, and who resolved installed Advanced Tomato.

[wabe]

[HalfBit]

I have a couple R7000s running 40270M, only one active at a time, and I haven't seen this issue. I have the following setup:

SSID-1 - wl0 - 2.4G bridged to LAN (br0)
SSID-2 - wl0.1 - 2.4G VAP bridged to guest wifi (br1)
SSID-3 - wl1 - 5G bridged to LAN (br0)
SSID-4 - wl1.1 - 5G VAP bridged to guest wifi (br1)

All four APs are using WPA2-PSK with AES algorithms.

I have seen a certain client drop from the SSID-1 network, but I'm pretty sure that is a hardware problem with the laptop which is 8-9 years old.

I currently have 16 days of uptime, but I've had much longer than that without issue. You might try that build, but you've already done a newer and older one so maybe not.

Have you tried a full reset of the config and configure again from scratch?

[egc]

[eolo]

[eolo]

[eolo]

After 20 day of uptime no more problem.

I recap my actions:

- R7000 updated to r44175
- channel reconfigured to minimize interference with neighbor
- to choose the channels I must modify "channel width" from 40 MHz to 20 MHz

I don't know which action was decisive, but I'm very happy.

Thankyou to all for your support.