/jffs/configs/dnsmasq.conf.add
file detailed in the two links above.dnsmasq.conf.add
are only supported by Merlin's firmware. They are not supported by stock firmware.If you want certain options or features, like what your asking for, then your only option (if you want the Asus router to do the DHCP) is to use Asus-Merlin firmware. The whole point of the Asus-Merlin firmware is to fix certain Asus firmware issues, and extend the stock Asus firmware with additional options and features. In this case you would have to use Asus-Merlin firmware, enable JFFS, then create the filei'm asking that cause i don't know if merlin is improving the router...
perhaps stock firmware is the best if we don't need add ons from merlin no ?
dnsmasq.conf.add
file as indicated in the first link in my post above.https://www.asuswrt-merlin.net/featuresYes i Saw, and i know cause i'm on merlin right now, but i would like to return on stock to have more stability...
But if all is the same on merlin, just add features, there's no problem to go on merlin.
IS it right ?
https://github.com/RMerl/asuswrt-merlin.ng/wiki/About-Asuswrt/#about-asuswrt-merlinWith a few rare exceptions, Asuswrt-Merlin retains the features from the original stock Asus firmware.
About Asuswrt-merlin
Asuswrt-merlin takes advantage of the fact that complete source code is available from Asus by building on top of it. Asuswrt-merlin is my personal project, originally done for the RT-N66U, and eventually extended to support other flagship routers from Asus.
The general goal of this project is to provide an alternative to the original firmware, and remain in-sync with Asus's own development, so new features and bugfixes development by them can trickle down into Asuswrt-Merlin. This means there are some very strict design guidelines behind this project:
Thanks to Entware/Optware and user-scripts, many features not integrated in the firmware can be manually added. If you are advanced enough to need a feature, you will quite often be skilled enough to manually add it, or follow someone else's instructions on how to implement what you are looking for.
- Stay as close as possible to the original firmware. By limiting the amount of sweeping changes made to the code, it means that whenever Asus releases a new version of Asuswrt, it generally takes only a few hours of work to merge their latest changes into Asuswrt-merlin (a bit more if it's a major new release from Asus).
- The goal is to improve, not to replace the original firmware's functionality Projects like DD-WRT and Tomato have existed for years, and benefit from those years of development to offer a lot of new features. There is no point in reinventing the wheel - people looking for a completely different firmware with tons of advanced features should look at those excellent and well-established projects.
- Priorities: Stability > performance > features. Fewer changes to the code means fewer chances that new bugs might be introduced. A router firmware is the core of your home network. It must be rock-stable above all. And performance optimizations can have unexpected side-effect when dealing with things that aren't fully understood.
- Targeting the novice and average user. Asuswrt is designed to target both the novice and the average users. This project will aim at the same target userbase. There is enough doors left open with Entware and user-scripts so advanced users can fulfill their own requirements themselves. Not overcrowding the web UI with esoteric features will ensure that novice users won't be scared away.
Ok, so merlin is more optimized than stock if i understand well in terms of stability, wifi range, speed... ?
Only you can answer that based on your needs from the device and it's stock Asus firmware. For others; we've found that for our uses and needs certain features of the Asus-Merlin firmware, including add-on scripts and Entware, necessitate using the Asus Merlin rather than stock Asus firmware. Some just like to tinker with new things. And some will prefer to stay on stock Asus firmware because they don't see a need or benefit for their setup to using Asus-Merlin.It's better to have merlin than stock ?
dnsmasq.conf.add
, or any other of the numerous add-on scripts then you'll need to use Asus-Merlin firmware.Without yazdhcp, on stock firmware, limit IS 64 manually assignedOnly you can answer that based on your needs from the device and it's stock Asus firmware. For others; we've found that for our uses and needs certain features of the Asus-Merlin firmware, including add-on scripts and Entware, necessitate using the Asus Merlin rather than stock Asus firmware. Some just like to tinker with new things. And some will prefer to stay on stock Asus firmware because they don't see a need or benefit for their setup to using Asus-Merlin.
The amount of extra addresses that YazDHCP will add appears (if I remember right) to depend on the router. Currently on a RT-AC68U loaded with Asus-Merlin firmware running YazDHCP there is a max limit of 197 manually assigned IP addresses, up from the max 128 without YazDHCP. If you want to use YazDHCP, ordnsmasq.conf.add
, or any other of the numerous add-on scripts then you'll need to use Asus-Merlin firmware.
Correct, I didn't have access to a stock Asus firmware router at the time of that post and was going off a quick search here where someone claimed 128. Double checked on a stock Asus router and it is indeed 64. Above post has been corrected. Fact remains, YazDHCP adds the capability to expand the number of manually assigned addresses as does usingWithout yazdhcp, on stock firmware, limit IS 64 manually assigned
dnsmasq.conf.add
, both of which generally require one to use Asus-Merlin.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!