If you want a ferrari with the power of a kia and the limitation of using only the right lane, stick with 378.
If you want a ferrari with the power of a ferrari and a choice of which lane to use you want to go eith this fork firmware.
Standard asus firmware maybee solid but it had lots of limitations in range and choice of channels
Is there still a reason to use this fork, now that Asuswrt-Merlin is rockstable and has been on 378 for a long while?
For the increments.....two reasonsHey John,
Just wondering why you changed the priority percentages in QOS to 5% increments? Also, does it need to add up to 100% total or can I have for example "Highest pirority = 90%" and "Low priority = 40%" etc, adding up to a total of more than 100%? I never really understood this section of QOS...
Anyway, thanks in advance! Firmware working great on my AC66U btw : - )
Of courseIs v14 better Then v13
Sent from my iPhone using Tapatalk
Greetings again,
I was lurking silently for a long time since I had no problems. Of course,John (and Merlin) still got my full respect and admiration for their awesome work.
To the point, : I use my dlna server every day since many years. and the playback is very choppy and stops/skips since I updated to v14E1 (from v14). I'm really not in the mood to reset my router to factory defaults, so I would like to know if there is a setting I should try to play with first.
Any help would be greatly appreciated,
Noble regards,
Ika
ps.: I will need to buy a new router for somebody next week and I was wondering if you had time to support the N18u (since you mentioned once that it's on your lists). I see that you still didn't had time to do it, but don't get me wrong please, I'm not complaining at all, just curious if it's still on your list somewhere or you actually tried and dropped the idea. I guess it would need a lot of work, so I understand if you won't do it.
For the increments.....two reasons
- First, IMO 1% steps implies a level of precision that just isn't there
- Second, when I was investigating/testing how QOS worked, it was just a pain to scroll through that big list every time I wanted to change things around
For your second question, yes, it can add up to more than 100%. I'm definitely not an expert on the various queuing algorithms, but I think of it as targets starting from the highest priority to the lowest. It tries its best to manage things to meet all the targets, but if your line is totally saturated, it will end up essentially allocating the bandwidth based on the relative proportions of the targets. (Any expert here is welcome to jump in!)
Can you give me an example of what you mean? I'm currently running on port 8080, and everything seems to be working fine.Hi John, you are missing a small part of code on HTTP port:
Changing HTTPS port will redirect you to the correct NEW HTTPS port, changing HTTP port will not redirect you to the NEW HTTP port, but to the OLD one.
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!