@Marvin_S I've logged on to my router and it prompted me to downloaded this firmware. I was getting some issues before with internet dropping and hoping this would have fixed it but it didn't.

Now I am still getting the same issue where my internet will drop for awhile and then come back after some time without me doing anything. I will still be connected to the network but it will show as "No Internet" even though all the 5 LED lights remain green in the router. 

Any thoughts how to fix this?

  @araknet 

Yes, I have the same .. still did not find a time to fix it fully .. my case was having multiple satelite routers connected in mesh to AX55.

I had to remove all satelites, add them back to mesh (I only tried few) It seems sort´a stable , nevertheless Im still not fully UP ... some satelites are now unplugged as I have no time to finish the setup .. 

  @Czmaze

Another observation:

It seems like the AX55 in AP mode (IP 192.168.0.251 - Ethernet Backhaul) constantly (every 35 secs) renews its DHCP lease from the main Firewall DHCP server (in my case 192.168.0.1)

This schedule can also be seen in the log of the main Firewall. Why does this happen so often?

Please note that the WAN port is NOT used - only the LAN Switch (IP 192.168.0.251) is used. Is this an OK aproach?

This is a snippet from Advanced | System | System Log (MAC - anonymized):

2024-09-23 18:00:42 DHCPC INFO [18503] receive ack from server with ip 192.168.0.251, options(serverid=192.168.0.1;lease=86400;subnet=255.255.255.0;router=192.168.0.1;dns=8.8.8.8 8.8.4.4;)
2024-09-23 18:00:42 DHCPC INFO [18503] send select request with options(cliid=01/78:8c:b5:--:--:--:;)
2024-09-23 18:00:42 DHCPC INFO [18503] 1/2 lease passed, enter renewing state
2024-09-23 18:00:08 DHCPC INFO [18503] receive ack from server with ip 192.168.0.251, options(serverid=192.168.0.1;lease=86400;subnet=255.255.255.0;router=192.168.0.1;dns=8.8.8.8 8.8.4.4;)
2024-09-23 18:00:08 DHCPC INFO [18503] send select request with options(cliid=01/78:8c:b5:--:--:--:;)
2024-09-23 18:00:08 DHCPC INFO [18503] 1/2 lease passed, enter renewing state
2024-09-23 17:59:34 DHCPC INFO [18503] receive ack from server with ip 192.168.0.251, options(serverid=192.168.0.1;lease=86400;subnet=255.255.255.0;router=192.168.0.1;dns=8.8.8.8 8.8.4.4;)
2024-09-23 17:59:34 DHCPC INFO [18503] send select request with options(cliid=01/78:8c:b5:--:--:--:;)
2024-09-23 17:59:34 DHCPC INFO [18503] 1/2 lease passed, enter renewing state
2024-09-23 17:58:59 DHCPC INFO [18503] receive ack from server with ip 192.168.0.251, options(serverid=192.168.0.1;lease=86400;subnet=255.255.255.0;router=192.168.0.1;dns=8.8.8.8 8.8.4.4;)
2024-09-23 17:58:59 DHCPC INFO [18503] send select request with options(cliid=01/78:8c:b5:--:--:--:;)
2024-09-23 17:58:59 DHCPC INFO [18503] 1/2 lease passed, enter renewing state
2024-09-23 17:58:25 DHCPC INFO [18503] receive ack from server with ip 192.168.0.251, options(serverid=192.168.0.1;lease=86400;subnet=255.255.255.0;router=192.168.0.1;dns=8.8.8.8 8.8.4.4;)
2024-09-23 17:58:25 DHCPC INFO [18503] send select request with options(cliid=01/78:8c:b5:--:--:--:;)
2024-09-23 17:58:25 DHCPC INFO [18503] 1/2 lease passed, enter renewing state
2024-09-23 17:57:51 DHCPC INFO [18503] receive ack from server with ip 192.168.0.251, options(serverid=192.168.0.1;lease=86400;subnet=255.255.255.0;router=192.168.0.1;dns=8.8.8.8 8.8.4.4;)

Best regards

zEnterHacker 

  Hi @Marvin_S 

Firewall: Hardware Appliance - firmware up to date

F_DMZ----------DMZ_AX55masterAPethBack-------DMZ_AX55satelliteAPethBack
I
R_LAN-----S----LAN_AX55masterATethBack
E         W
W         I----LAN_AX55satelliteAPethBack
A         T
L         C
L         H

So I have two separate WiFi mesh networks (one for LAN users and one for GUEST users)
LAN users can access the DMZ network GUEST users can only access the internet via the Firewall

For LAN section a 24port switch is used to connect the two LAN_AX55s
For DMZ section the built-in 4 port switch of the DMZ_AX55master is used to connect to the DMZ_AX55satellite
No cables are connected to the WAN port of any of the AX55 - only built-in 4 port switches are used.

The systems runs flawlessly and reverts to normal WiFi mesh if I disconnect the cable to a satellite AP.

Only issues that I have found:

1/ All AX55s renew DHCP lease about every 35s even though the lease time is 86400s

SysLog form firewall confirming multiple DHCP renewals (every 35s) initiated by the AX55s
2024-09-26 11:00:51 DHCPSERVER 00900020 Debug(7) event=client_renewed action=renew client_hw=50-91-E3-xx-xx-xx client_ip=192.168.0.252 client_hostname="ArcherAX55" client_vendorclass="MSFT 5.0" client_params="1,3,6,12,15,28,33,42,121,249" rule=DHCP_DMZ1 recvif=if_DMZ1 recvzone="" srcip=192.168.0.252 destip=192.168.0.1 ipdf=1 ipproto=UDP ipdatalen=379 srcport=68 destport=67 udptotlen=379
2024-09-26 11:00:53 DHCPSERVER 00900020 Debug(7) event=client_renewed action=renew client_hw=78-8C-B5-xx-xx-xx client_ip=192.168.0.251 client_hostname="ArcherAX55" client_vendorclass="MSFT 5.0" client_params="1,3,6,12,15,28,33,42,121,249" rule=DHCP_DMZ1 recvif=if_DMZ1 recvzone="" srcip=192.168.0.251 destip=192.168.0.1 ipdf=1 ipproto=UDP ipdatalen=379 srcport=68 destport=67 udptotlen=379
2024-09-26 11:01:25 DHCPSERVER 00900020 Debug(7) event=client_renewed action=renew client_hw=50-91-E3-xx-xx-xx client_ip=192.168.0.252 client_hostname="ArcherAX55" client_vendorclass="MSFT 5.0" client_params="1,3,6,12,15,28,33,42,121,249" rule=DHCP_DMZ1 recvif=if_DMZ1 recvzone="" srcip=192.168.0.252 destip=192.168.0.1 ipdf=1 ipproto=UDP ipdatalen=379 srcport=68 destport=67 udptotlen=379
2024-09-26 11:01:27 DHCPSERVER 00900020 Debug(7) event=client_renewed action=renew client_hw=78-8C-B5-xx-xx-xx client_ip=192.168.0.251 client_hostname="ArcherAX55" client_vendorclass="MSFT 5.0" client_params="1,3,6,12,15,28,33,42,121,249" rule=DHCP_DMZ1 recvif=if_DMZ1 recvzone="" srcip=192.168.0.251 destip=192.168.0.1 ipdf=1 ipproto=UDP ipdatalen=379 srcport=68 destport=67 udptotlen=379

Senior Engineering Support claims that this is the smart DHCP detection feature that checks if the main DHCP works (on my Hardware Firewall).
OK fair enough .. so I switched all my local AX55 DHCP servers from "Auto" to "Off" and expected this constant DHCP renewing to stop - because the AX55 no longer needs this status info since its DHCP server is stopped.
Anyway I think the software guys forgot to stop this constant DHCP status request because it still keeps on renewing its DHCP lease every 35 secs. BUG? NO - but why not stop it when not needed?

2/ List of clients on the satellite is not consistent with the actual connected clients - clients you CANcan see on the WebGUI of the satellite.

Senior Engineering Support gave me a rather short answer claiming that Client Binding is not yet a feature of the AX55 AP and that I should not worry about it! :-)

Well well - I guess the Seniors did not thoroughly read this thread - because Pre-release 1.3.3 Build 20240628 rel.37017(4555) clearly should support this client binding feature also in AP mode ;-)

When running EasyMesh in AccessPoint mode (Ethernet Backhaul) clients connected to the Satellite AP cannot be seen on the Master AP.
They should appear on the Master under "Advanced | EasyMesh" and you should be able to bind clients on the Satellite to the Satellite AP via the web interface of the Master AP. Everything is in place, but Satellite connected clients will never appear in the list on the Master.

If I pull out the Ethernet cable of the Satellite AP - hereby forcing it into normal WiFi based Mesh mode - the Master AP is now able to see and manage clients on the Satellite.

Re-inserting the Ethernet cable - hereby forcing the AX55s back to use Ethernet Backhaul - makes the Master AX55 revert back to NOT showing Satellite connected clients. This must be a bug!

So if someone out there has the same client issue only when running in Ethernet Backhaul mode - please inform us here in the forum.

Thanks
zEnterHacker

PS: Sorry for the long post !