Search results

  • 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. RMerlin

    Is the firmware 32 or 64 bit?

    You can use the AES optimized operands even in 32-bit. I compile openssl with -march=armv8-a
  2. RMerlin

    3004.388.7 alpha 1 Build(s) ] Testing available build(s)

    Try launching miniupnpd in debug mode: killall miniupnpd miniupnpd -f /etc/upnp/config -v Look for errors when you run the software that tries to open a port.
  3. RMerlin

    386.13 alpha Build(s) ] Testing available build(s)

    The OUI database is merely the list of MAC addresses assigned to manufacturers. It's only used to identify which manufacturer a device's from.
  4. RMerlin

    Adding an AIMesh Node - why is this so hard?!?

    There's a possibility it could be actual compatibility - could be something that's different in 386 vs 388 proprietary code, where 388 better deals with Asuswrt-Merlin nodes than 386. Hard to tell since most of the process is within a blackbox, and everyone's personal experience seems to differ...
  5. RMerlin

    Adding an AIMesh Node - why is this so hard?!?

    Just because the result is the same does not mean the cause also is the same.
  6. RMerlin

    Adding an AIMesh Node - why is this so hard?!?

    The issue that was fixed in 388 was that a closed source component wasn't getting updated by my GPL merges. At the time the same specific issue didn't exist with the 386 releases (I can't remember if it's because Asus never updated that component for these older models, or if I was properly...
  7. RMerlin

    Adding an AIMesh Node - why is this so hard?!?

    AiMesh is supported, and I had no issue doing the two test setups I've done these past few months with two different models both running Asuswrt-Merlin. Often, the issue is with people not following instructions. For instance the setup instructions states that you need to keep both devices...
  8. RMerlin

    Cannot connect to a website

    It's also possible that the IP provided by your ISP is blacklisted by that specific site.
  9. RMerlin

    Current plans regarding separate version branches

    The risks are really small for an AiMesh node. Even if a local PC were to be compromised with a malware that targets Asus routers, it would most likely only try to attack the default gateway, which is the main router. There is still a small chance that a malware may scan the whole network...
  10. RMerlin

    Current plans regarding separate version branches

    More like the Extended Support provided by Microsoft or the PHP folks - past a certain point in time, only critical fixes will be provided, with no new features.
  11. RMerlin

    Current plans regarding separate version branches

    Well it seems Asus changed their own plans. A few weeks ago I was told they planned to keep supporting the RT-AC68U for a while longer, and now they just added it to the End of Life list. I updated the first post accordingly. So for all 386 models, I will probably try to get one final GPL...
  12. RMerlin

    Current plans regarding separate version branches

    I don't, sorry.
  13. RMerlin

    News RT-AC68U End of Life Announced by Asus

    Asus must have changed their plans, because I asked them back then, and they were aiming for the end of the year for dropping its support.
  14. RMerlin

    cru not using sytem date

    Gotcha. I might have forgotten to cherry-pick that one since my development night ended prematurely as my laptop broke on me.
  15. RMerlin

    Current plans regarding separate version branches

    I thought I'd make a post clarifying the current plans regarding the separate versions (386 and 388), and future plans. 386 branch: This branch is for older models that Asus didn't move to the 388 codebase. This includes three Broadcom SDKs: - SDK 6.x (RT-AC68U) - SDK 7.14 (RT-AC88U...
  16. RMerlin

    Release Asuswrt-Merlin 386.12_6 is now available for AC models

    This thread has gone completely off the rails. This thread has served its original use, so I'm locking it.
  17. RMerlin

    Best practices when using add-ons?

    Locking this thread since it has degenerated. I'll let Tim sort out the rest tomorrow, because I'm currently half-asleep to be honest...
  18. RMerlin

    3004.388.7 alpha 1 Build(s) ] Testing available build(s)

    I didn't ask them for updated GPLs, since I already merged a recent one earlier this year. I will however use this release cycle to test some significant updates that will require to be well tested. The IGD2 implementation is something I had finalised many years ago, but I kept disabled due to...
  19. RMerlin

    cru not using sytem date

    That was already merged in master, in fact Dave's PR was against the Master branch, so that was merged first.
Top