Recent content by cputoaster

I have some device dropping and reconnecting more often than before (my Pixel 9 Fold, Tesla Model Y, Freedom Pro Matter relays). What is your experience? Running MLO in AP mode.

I used a guest VLAN with ID 52 (default) on the BT10. On the gateway I configured a VLAN with ID 52 too so it would create a virtual Ethernet adapter on the physical one. This adapter then needs to be configured to be in some subnet and with a DHCP server or similar. I used plain Linux, so...

Just wanted to give another data point for others. I am switching over from 1Gb WAN -> 3x AX88u to 25Gb WAN -> Linux router (Debian, nft, dnsmasq) -> 3x BT10, always using 10Gb ethernet backhaul. While still waiting for the the WAN to be upgraded, I am happy to say that the BT10 works without...

Thank you very much! I just tried that, pings and ssh still work between hosts though, so something is not exactly working as intended. In the man page of ebtables there is something about DROP not actually dropping but making it routed, which I did not get my head around yet. Just to be sure I...

I am trying to isolate the one device on one port on my AX88U so it cannot see anything of the other ports / wifis / devices apart from the router in the simplest way. Tried different things, but nothing works, pings still work fine from the device on the port (eth4, ip 192.168.87.4) to other...

Sorry, I was unclear. I need a router that is good at 2.4Ghz for the IoT devices, the level of the AX88U is sufficient, but it should not be worse. The benefits of WiFi7 is only intended for my very recent and future PCs with 3-way MLO and have nothing to do with the IoT stuff other than that...

Apart from the crucial Merlin support, is it worth getting the ugly, but 2.4Ghz 4x4 BE96 over the BT10 2x2? I am mostly interested in the stable support of lots (>50) of IoT devices like Shelly switches and Bulbs at 2.4Ghz while having other 2.4Ghz transmitters like 802.15.4 and BT around too...

I think that this is much more compatible with my living room than black spiders. Even at this size. Would love to see Merlin on it.

AX88U is also my bet, got 3 of them more than 3y ago for a mesh and the support and performance is probably still close to SOTA. Interesting is also that the price actually went up by 10% since then here...

I also have 2.4ghz clients (Shelly) dropping off with 386 but it could well be a bug with the latest Shelly FW.

I have a star mesh config, with the AX88U router being connected to two AX88U nodes via Ethernet and one AX56U via wireless: With an IoT server (receiver) wired to one of the wired nodes, and binding to a multicast address (Shelly CoIoT multicast), I can only receive the multicast traffic...

In my setup, I meant the switch of the Asus router, not an additional piece of equipment. Your question about adding switches in between should probably work as long as they don't do any magic filtering.

I just changed the configuration by inserting a new AX56U mesh router because of weak signals: Mesh M1 AX88U WLAN --- Device B .55 Switch === Server S .2 II II Router R AX88U WLAN --- Mesh M3 AX56U WLAN --- Device C .64 Switch === Internet...

To partially answer my own question: It looks like the server S did not correctly join the multicast group. Manually adding the group address to the interface (via ip addr add ... autojoin) seems to make all respective traffic appear on the interface.

I have the following setup (all routers on merlin 384.19, double lines are cables): Mesh 2 AX88U WLAN --- Relay R .58 II II Mesh 1 AX88U WLAN --- Relay R2 .55 Switch === Server S .2 II II Router AX88U WLAN --- Contact C .65...