Recent content by mpilasy

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. M

    Release Asuswrt-Merlin 386.1 is now available

    My only issue with #2 is that guest2 and guest3 do not get "mesh"d out.
  2. M

    Asus Merlin 386.1 IoT-network configuration

    Access Intranet = Disabled means I don't want devices on the guest network to be able to interact (both ways) with devices on the LAN, right? Or does it just protect in one direction (aka guest can't see LAN but LAN can see guests)? Yeah, what I see is that if I have YazFi enabled, it does not...
  3. M

    new br1 interface merlin 386.1 routing table

    Great to hear! I will be testing that this evening. Thank you for the work you are doing.
  4. M

    Asus Merlin 386.1 IoT-network configuration

    I had high hopes for YazFi + 386.1 as well but unfortunately for now, the combo seems to not be in a perfect state. However, I have my iot devices connecting to Guest 1 2.4Ghz with Access Internet = disabled, Sync to AiMesh node = All. That puts them on the 192.168.101.x (seems hard-coded and...
  5. M

    new br1 interface merlin 386.1 routing table

    Is it safe then to say that YazFi does not currently work with the current version then? Also I am noticing that, indeed Guest 1 gets sent to the AiMesh nodes. However, on Guest 2, the clients do get attached back to br0 (so not br1 or a new br2) and Guest 2 is not on the nodes. Am I doing...
  6. M

    new br1 interface merlin 386.1 routing table

    I just discovered this as well. Is there any way to configure the LAN segment (to not be .101.xxx) either via the UI or even on the CLI. It seems like YazFi does not play with this very well yet. If one sets YazFi to use a different segment, the clients stay on 101. If You specify 101 is YazFi...
Top