Recent content by matthew_eli

Ok, it seems reinstalling Scribe did the trick. BTW, why I'm seeing a different port in the log for dropbear than the one I'm selecting for accessing the router via SSH? Is that normal?

I'm using latest develop versions for both Scribe and uiScribe

But I can't find any entries anywhere in the scribe logs

But I can't find any entries anywhere in the scribe logs

Hi, is that normal I don't see any dropbear entrues in my system log when I succesfully enter via SSH? I've a RT-BE86U with 102.3 merlin FW installed and scribe

Does this FW have the 802.1q option in WAN section?

I've the same issue you have. After some weeks of uptime, this strange lines shows up for me on syslog. RT-BE86U here, Merlin 3006.102.3. It could be related to Bonding on port 1/2? Mar 12 01:11:46 RT-TATI BONDING: option disabled Mar 12 01:11:46 RT-TATI hour_monitor: value = 1(0x1) Mar 12...

I had the same issue with RT-BE86U. Merlin fixed it in: https://github.com/RMerl/asuswrt-merlin.ng/commit/6fe22fe3525b2adab3f4b8fceb44c5ba2bd0b599 But this was on a separate branch; I don't know if this shall be re-applied for all models now

Ok, probably I sorted this out: I deleted and then re-configured an IoT network (2,4GHz only, as before), but not assigning it to all AiMesh nodes by default, but selecting them one by one...now I can share also the Guest Network (5GHz only) to all AiMesh nodes, by selecting them one by one. I...

But previously I had a GT-BE98 with Gnuton build (102.1beta2) and I were able to assign to all my mesh nodes both a 2,4GHz network (IoT) and a 5GHz one (Guest). The nodes were the same. What changed is the release of the fw and ASUS that grouped all the WiFi networks (both the main and the...

Hi, I've a RT-BE86U and with both 102.2 and 102.3 alpha 2, if I set an IoT network only on 2,4GHz channel, shared on all AiMesh nodes and a 5 GHz Guest network, this one cannot be shared on AiMesh nodes because I run out of the free slots on them. It's strange because only IoT netwotk (2,4GHz)...

Ok, but I guess you don't have to specify any VLAN tag for your WAN connection, otherwise you'd be forced to use the 10 Gbit port

Hi, yes that’s correct. Anyway, just like in the GT-AX6000, ASUS added this possibility of configuring the VLAN tag for WAN (as it should be) in the 802.1q options in the WAN section. In this way I also suspect you don’t have to sacrifice the 10Gbit WAN/LAN port instead of the 2.5Gbit

Hi @visortgw, is the 802.1q options panel present on the WAN section?

Ah, so is it a client policy at last?