The wiki is helpful...and contributors rock!

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.


Very Senior Member
Wow, I haven’t checked the wiki for a while, it’s grown massively since I last did.
I have a couple of things I regularly help people configure so will add them there I think!

Sent from my iPhone using Tapatalk


Asuswrt-Merlin dev
Hopefully this post inspires a similar quest for higher signal-to-noise ratios in everyone who comes here seeking:

Whomever wrote this page is very kind.

I was happy to find my questions answered by poking around on the wiki when my search terms for this forum's tools came up confusing more than helpful (that's a me thing, not a critcism!!)

In general, forum search engines suck, especially when you need to search for a short term like "ipv6". I recommend using Google for forum searches, using that format (as an example):

Code: IPv6 tunnel

The site parameter lets you limit search results to a specific site.


Asuswrt-Merlin dev
Open-source projects are often lacking in documentation. Forums are great place to ask questions, but they are often not doing a good job at exposing important information on how to configure or manage something (this is simply a limitation of the medium, not any forum's fault). You have to rely on search engines, or sticky posts (and I have to limit the number of sticky posts, otherwise everyone would just skip over them if they are too many of them).

That's why early on I started setting up a Wiki with a clear structure, which encouraged other contributors to add their own articles to it. These contributors are providing the bulk of the content now, I only maintain the pages related to firmware features that may change, like when I implement a new user script.

Funny story: back in 2013 (I believe) when I set out to implement OpenVPN support, I was basing my work on Tomato's own implementation. While I had to rewrite the webui portion from scratch, I still decided to keep the same settings as Tomato, because I didn't feel like documenting everything on my own, and "people will be able to refer to Tomato-related documentation to know how to configure things up". Nowadays, most of the large VPN providers supply documentation explicitly for Asuswrt-Merlin. Things sure have changed over the course of 6 years.

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!