Recent content by prosperot

same here, I have manually updated the node.

I am getting a lot of lost wifi connections from some devices and these corresponding errors in the log. Any ideas why? In this case a Samsung A56 5G. I have replaced the macaddress with XX Dec 5 15:30:47 wlceventd: wlceventd_proc_event(645): wl1.1: Deauth_ind XX:XX:XX:XX:XX, status: 0, reason...

1500 ;-) I guess I am good!

The problem is that i don't have that option under 'special requirements'

True, but that only accepts MTU up to 1492, i need 1500. On the previous merlin it used to be an option on thay page under 'isp specific', but now that option is gone

On my BE88U with 3008.102.5 firmware, it is not possible to set Custom MTU settings on the tab WAN/special ISP requirements My ISP requiers a MTU of 1500. I have tried Chrome Edge and Safari browsers and cleared browser settings, but the problem persists.

On 3006.102.4 There was the option under WAN - 'Special requirements from ISP' to set a custom MTU value. In 3006.102.5 I can see that field at the bottom of the page when the page loads, but when it is finished loading, the custom MTU field disappears. And yes , I did a fresh install

I've had the same problem. A factory reset solved it. The Guest Network Pro is such a pain. Many IOT devices on it, can't connect to the internet. I am putting them all back to the main network.

After a firmware update of my AiMesh nodes last night, all is back to normal

The manual assignment of IP addresses doesn't seem to work here , when assigning then to an MAC address through the gui.

Ive had a simular problem with devices. It turned out that my router was low on DHCP adreases.. enlarging the DCHP address range solved my problems

As usual a dirty upgrade let to disappointing wifi speeds, but after a fresh install, everythings works grant! Thanks again for your hard work

Dirty upgrade from 388.8. Zero problems, no DNS nor Timemachine issues, Thanks to M!

Uae your router credentials

As usual a initial dirty upgrade caused speed problems but a clean upgrade solved it. Thanks!