Introduction to firmware of third-party Routers

I recently paid more attention to the functions of routers. I have read a lot of information and summarized my views on the firmware of a third-party Router Based on my previous experience.

Now most third-party router firmware, such as Tomato, DD-WRT and so on are based on OpenWRT.

The firmware architecture of these third-party routers can be divided into front-end (Frontend) and back-end (Backend). The back-end is basically OpenWRT, and the front-end generally refers to the graphic user interface (GUI, it is mainly reflected in the Web management interface. OpenWRT is compiled by default without the front-end.

The common frontend of OpenWRT in China is:

1. LuCI: Based on Apache License, which is currently the mainstream, is the best combination of self-compiled OpenWRT;

2. X-WRT: Based on GPL, not very active, not very popular, as if not how to update;

3. gargoyle: Based on GPL, it provides a complete set of routing functions, powerful traffic monitoring, and powerful bandwidth management and QoS. It is no inferior to Tomato. If you do not want to compile or set it yourself, however, Gargoyle is the best choice if you want to use OpenWRT with the copyright regulations in one step. It is suitable for common users or small and micro enterprise users who are pursuing stability. The default Interface style is traditional, however, themes with fashion styles can be changed, but they do not support multiple languages and are not popular in China. However, Chinese patches have already emerged;

4. tomato front-end: private, non-GPL (source code for self-compilation, cannot be modified at will), copyright vague, free version, but there are also a lot of paid enhancements, the interface is simple, stable Operation, powerful QoS, and less support for models;

5. dualWan front-end: private, non-GPL (with source code for self-compilation, you cannot modify the source code as needed), copyright blurring, free version, and paid version with enhancement features, derived from the Tomato front-end, it is a typical representative of the Chinese Tomato. It has powerful multi-dial functions and has little support for models;

6. DD-WRT front-end part: Copyright fuzzy, part of the private, non GPL (provide source code, can not be modified at will), there are free version, also have paid version of enhanced functions, beautiful interface, powerful relay capabilities, many languages are supported and the model is the most widely supported, but the free version has a moderate QoS performance;

If you want to play routing, it is recommended to start with the most convenient from the DD-WRT; if you want to use tossing QoS, then use tomato; more dial dualwan; pay attention to copyright or small and micro enterprise users, if you don't want to worry about it, you can choose gargoyle. If you want to focus on copyright awareness, You can compile openwrt to integrate various components such as Luci-free and independent, with powerful functions and everything available, this may be the final choice of many vro players.

After a series of experiences, including self-compiled openwrt and Luci components, I found that all aspects are good. The only pity is that QoS is too bad!

Therefore, I need to connect multiple computers to watch videos and play games as needed. For bandwidth management and QoS, I finally chose gargoyle or self-compiled openwrt with TC modules and Luci components!

In addition, many people are playing wayos in China, and the backend of wayos is also openwrt. Its front-end is private and fully commercialized. It does not have a free version. Similar to tomato, it has powerful multi-dial and QoS functions, the cracked version can be used on certain routers, but cannot be called a third-party router firmware.