Erratic behaviour of Mango (loss of wifi, timeouts and so on)

Gentlemen, good morning.

I have a home network comprising a Fritzbox 7590 (the "source" of my internet connection) with its own wifi and wifi channel and a few devices connected on the LAN ports.
From one of these LAN ports, I have a tiny switch where I have connected two mango and one Beryl AX.
The cable from the switch is connected to the devices' WAN port, and their "local" IP is fixed and outside of the Fritz DHCP range.
Each device outputs its own wifi, and each wifi is configured with its own channel and SSID to avoid conflict.
To keep wiring neat, all of those devices are within 10 cm of each other.

The two Mango have just one client and provide a different VPN to such client.
The Beryl is just used for the adguard filter and occasionally for vpn.
This is why 3 devices. each one performs (well, should perform) one function only so no mess or errors should happen.

What is happening is that, pretty often, parts of this contraption stops responding, with Mangos being more prone to fail than the Beryl.
It looks like the Mango's wifi disappears or , if it's there, no traffic can pass, to the point that it's impossible to load the admin access page (with timeout or partial load).
If i leave open the "overview" page on all devices, i see often "holes" in the status graph, and when it happens i get timeout warnings (the usual "check network environment or reboot).

Local network-wise, the configuration of the devices is stock, apart for the local IP that is fixed on both devices and fritz to avoid conficts.

The funny part is that sometimes everything works like a charm for days, and some days there is no damned way to have it working, even plugging all power supplies off and rebooting all together.

I have the feeling that for some reason some of the device go nuts and starts polluting the wireless environment to the point that nothng works anymore, but i cant' understand why the "full reboot" does not solve anything as well as why some days everything works.

I live in an apartment and the wireless is quite crowded, but i suppose this is quite a normal condition nowadays

So far I tried the most obvious things , such as checking lan cables and checking power supplies... but i have no clues on how to improve this situation.
It may be useful to note that until a few ways ago all the mango were on 3.x firmware, and i've updated to 4.3.18 . Beryl is updated to 4.7. Same behaviour with both firmwares.

anyone is experiencing disruption of this kind? Any ideas for a solution?

thak you .
E.

Generally I assume the Mango1, 2, Beryl 1 and Fritz are not the same subnet, right?

So they are supposed to be not IP conflict occurs.

Is it possible to test them one by one separately?

For example, take out Mango 1 separately, connect Mango's WAN port to ISP/Fritz router's LAN port, and see if Mango will work normally.

Good morning, Bruce, and thank you for your feedback.

All devices are on the same subnet (10.0.0.x) which is the LAN address pool for the whole home.

Each device has its own ip which is static inside of the lan (say, 10.0.0.1 for the fritz, 10.0.0.2 for the mango1 , 10.0.0.3 form mango2 , .4 for beryl, .5 for my tv , .6 for raspberry and so forth.)

There is a dhcp pool , and all fixed IPs are of course outside of this pool.

None of the gl.inet devices is used as a server for outside world, so there are no NAT or open ports that may cause issues, i guess.

In this sense i suppose there are no conflicts.

Each gl.inet generates a wifi with a dedicated SSID and the IP range of this wifi is different from the LAN (lan is 10.0.0.x while wifi is 192.168.8.x which is default). The wifi serves just two clients.

I hope this clarify the setup. I feel that there should be no conflicts.

Concerning the test of single devices, i have erratic behaviour even with one device .

Originally I have been using only one mango, switching its configuration according to my needs but the configuration change led to massive crashes (i was switching between a openvpn and a wireguard vpn and turning on / off the client device).
I decided to go for dedicated devices in order to avoid the change in setup and in order to leave clients on.
The beryl is "just" an add-on because i like the adguard.

Hope this helps you to help me.
Thank you.
E.

Looks strange.

Can SSH to the router via cable LAN with the PC when the issue occurs?

If can, please export the issue syslog and send to me via PM.

Hello, Bruce.

Ok, I will try to.
I assume the ssh password is the same as the management interface, is it?
How do I proceed with exporting the Syslog?
I suppose files are somewhere like /var/log/syslog and that doing a cat for the filename while logging the terminal output would work, but I'm not into Linux enough, so I ask.

thank you and have a nice weekend.
E.

Yes.

logread > /tmp/logread/system.log
dmesg > /tmp/logread/kernel.log

Then export system.log and kernel.log with WinSCP.